• more lunacy from the BBC

    From john larkin@3:633/10 to All on Monday, April 06, 2026 07:52:26

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."



    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Monday, April 06, 2026 15:25:01
    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 06, 2026 08:38:55
    On Mon, 06 Apr 2026 15:25:01 GMT, Jan Panteltje <alien@comet.invalid>
    wrote:

    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.

    "Holiday photos."

    Why does that thing need a pilot? The crew could be asleep the whole
    trip.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Monday, April 06, 2026 16:12:11
    john larkin <jl@glen--canyon.com> wrote:
    On Mon, 06 Apr 2026 15:25:01 GMT, Jan Panteltje <alien@comet.invalid>
    wrote:

    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.

    "Holiday photos."

    Why does that thing need a pilot? The crew could be asleep the whole
    trip.

    Because space travel, like astronomy, is primarily a cultural activity.

    Cheers

    Phil Hobbs


    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Edward Rawde@3:633/10 to All on Monday, April 06, 2026 12:30:26
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Ask a few random people "What does Digital mean?"
    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"




    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics



    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 07, 2026 03:16:20
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    If you asked them about digital electronics you might get a more
    sensible answer.

    These days hardware electronics is split between analog, digital and
    mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast digital
    electronics than regular digital electronic engieers.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while
    the religious proselytise furiously.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Edward Rawde@3:633/10 to All on Monday, April 06, 2026 13:32:51
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Are you on Earth or some other planet?


    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.


    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 07, 2026 05:07:07
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten,
    because that's how they were originally counted. Digital massage means applying pressure with a finger.

    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed
    the idea that we should do some of the fast number crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an attractive idea, but he'd
    seen it go wrong quite often. When I said that it had always worked for
    me his response was that I was an an analog engineer, which did make
    sense. The TTL specialists were never happy with terminated transmission lines.

    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about
    John Larkin being rude about a perfectly simple - if half-baked - EDN
    circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 07, 2026 05:07:49
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten,
    because that's how they were originally counted. Digital massage means applying pressure with a finger.

    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed
    the idea that we should do some of the fast number crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an attractive idea, but he'd
    seen it go wrong quite often. When I said that it had always worked for
    me his response was that I was an an analog engineer, which did make
    sense. The TTL specialists were never happy with terminated transmission lines.

    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about
    John Larkin being rude about a perfectly simple - if half-baked - EDN
    circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Edward Rawde@3:633/10 to All on Monday, April 06, 2026 15:23:01
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>>> into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten, because that's how they were originally counted. Digital
    massage means applying pressure with a finger.

    I'm not sure what you're answering here but I have various search engines at
    my disposal if I need information I don't already have.


    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed the idea that we should do some of the fast number
    crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an
    attractive idea, but he'd seen it go wrong quite often. When I said that it had always worked for me his response was that I was
    an an analog engineer, which did make sense. The TTL specialists were never happy with terminated transmission lines.

    I can remember a time when I wanted an ECL 22V10 but there wan't one
    (more than 30 years ago) it doesn't matter if there is now.


    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about John Larkin being rude about a perfectly simple - if
    half-baked - EDN circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney





    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From bitrex@3:633/10 to All on Monday, April 06, 2026 16:15:46
    On 4/6/2026 11:38 AM, john larkin wrote:
    On Mon, 06 Apr 2026 15:25:01 GMT, Jan Panteltje <alien@comet.invalid>
    wrote:

    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.

    "Holiday photos."

    Why does that thing need a pilot? The crew could be asleep the whole
    trip.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    The shiny, "progressive" face of the military-industrial complex. We can defund all that it's cool.

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 07, 2026 15:48:12
    On 7/04/2026 5:23 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>>>> into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten, because that's how they were originally counted. Digital
    massage means applying pressure with a finger.

    I'm not sure what you're answering here but I have various search engines at my disposal if I need information I don't already have.

    The problem is that they don't give you information that you didn't
    realise that you needed.

    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed the idea that we should do some of the fast number
    crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an
    attractive idea, but he'd seen it go wrong quite often. When I said that it had always worked for me his response was that I was
    an an analog engineer, which did make sense. The TTL specialists were never happy with terminated transmission lines.

    I can remember a time when I wanted an ECL 22V10 but there wan't one
    (more than 30 years ago). It doesn't matter if there is now.

    Programmable logic deice with ECL compatible input and outputs became available in the 1990s. They were then much too expensive for the sort
    of applications that I was looking at at that time. A lot of the
    advantage of ECL lay in its capacity to drive terminated transmission
    lines, which you need to move fast signal around, and when you could get pretty much all the logic into a single big prograamble chip you didn't
    need to move anything like as many signals around the board.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From brian@3:633/10 to All on Tuesday, April 07, 2026 07:15:16
    In message <10r0j8e$26mpq$1@dont-email.me>, Jan Panteltje <alien@comet.invalid> writes
    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far
    into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.


    They'll be out of range of the cell-phone networks for uploading to
    Facebook or Instagram. The 2 sec delay might screw up the protocol
    anyway.

    <Https://www.chron.com/culture/article/artemis-iphones-internet-communica tions-22191351.php>

    Brian
    --
    Brian Howie

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Tuesday, April 07, 2026 10:17:28
    brian <nospam@b-howie.co.uk>wrote:
    In message <10r0j8e$26mpq$1@dont-email.me>, Jan Panteltje ><alien@comet.invalid> writes
    john larkin <jl@glen--canyon.com>wrote:

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>into space."

    Maybe they meant personal digital cameras...

    Plenty of digital cameras for example on Mars landers...
    Other space probes...
    And Hubble and Webb telescopes.
    But it is nice that they follow the mission.


    They'll be out of range of the cell-phone networks for uploading to >Facebook or Instagram. The 2 sec delay might screw up the protocol
    anyway.

    < >Https://www.chron.com/culture/article/artemis-iphones-internet-communications-22191351.php>
    Brian


    It is interesting, I would like photos of the backside of the moon with my Xiaomi smartphone
    it's camera is amazing.

    When going back in time, in those days of the first Moon landing I had a Werra 35 mm camera, (East German made):
    https://camera-wiki.org/wiki/Werra
    and a Durst enlarger:
    https://realcamera.co.uk/product/durst-m601-darkroom-enlarger-set-for-6x6-medium-format-w-schneider-80mm-componon-lens/
    Made and developed my own enlargements in BW.

    For video I had a vidicon camera that I designed and build in 1968.

    And in the seventies a Philips LDL100 video recorder!
    https://www.radiomuseum.org/r/philips_video_recorder_ldl_1000_00.html
    Around 1972 I modified it for color...

    Many years later I bought a Kodak instant camera, instant pictures...
    That was better stuff !

    Several cameras now, Canon.. and some IR models for Raspberry Pi, Sony Super HAD ultra low light ones, some digital security ones..
    Canon is a nice camera too, runs special software you can install, recorded this with it:
    https://panteltje.nl/pub/stars_2009_08_18_1536x1152_canon_a470_chdk.avi




    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Tuesday, April 07, 2026 11:39:22
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>>>> into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten, because that's how they were originally counted. Digital
    massage means applying pressure with a finger.

    I'm not sure what you're answering here but I have various search engines at >my disposal if I need information I don't already have.


    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed the idea that we should do some of the fast number
    crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an
    attractive idea, but he'd seen it go wrong quite often. When I said that it had always worked for me his response was that I was
    an an analog engineer, which did make sense. The TTL specialists were never happy with terminated transmission lines.

    I can remember a time when I wanted an ECL 22V10 but there wan't one
    (more than 30 years ago) it doesn't matter if there is now.


    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about John Larkin being rude about a perfectly simple - if
    half-baked - EDN circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney




    There are $5 FPGAs now with 10 ns pin-pin delays, 3000 logic blocks, 1
    ns rise/fall, PLLs, cmos and LVDS levels. The internal logic is almost
    zero delay.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Wednesday, April 08, 2026 16:36:08
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>>>>> into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten, because that's how they were originally counted. Digital
    massage means applying pressure with a finger.

    I'm not sure what you're answering here but I have various search engines at >> my disposal if I need information I don't already have.


    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us.

    I was the lead hardware engineer on an instrument project, and expressed the idea that we should do some of the fast number
    crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an
    attractive idea, but he'd seen it go wrong quite often. When I said that it had always worked for me his response was that I was
    an an analog engineer, which did make sense. The TTL specialists were never happy with terminated transmission lines.

    I can remember a time when I wanted an ECL 22V10 but there wan't one
    (more than 30 years ago) it doesn't matter if there is now.


    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about John Larkin being rude about a perfectly simple - if
    half-baked - EDN circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney




    There are $5 FPGAs now with 10 ns pin-pin delays, 3000 logic blocks, 1
    ns rise/fall, PLLs, cmos and LVDS levels. The internal logic is almost
    zero delay.

    "Almost zero" isn't a lot of help.

    Identifying the source of these $5 FPGAs would also be helpful, if you
    were posting to to be helpful as opposed to posting to make yourself
    look as if you might be competent.

    Google says that Microchip IGLOO2/SmartFusion2, Microchip ProASIC3
    (e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts will do it.

    The Microchip ProASIC3 A3P1000 seems to be in that price bracket.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, April 08, 2026 05:52:31
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    https://www.bbc.com/news/articles/clye6j0g840o

    "This is the first time that digital cameras have been taken this far >>>>>>>> into space."

    Ask a few random people "What does Digital mean?"

    They will tell you - correctly - that it pertains to fingers.

    Digits are fingers (and toes). It is also the numbers from one to ten, because that's how they were originally counted. Digital
    massage means applying pressure with a finger.

    I'm not sure what you're answering here but I have various search engines at
    my disposal if I need information I don't already have.


    If you asked them about digital electronics you might get a more sensible answer.

    These days hardware electronics is split between analog, digital and mixed signal.

    Analog electronic engineers can mostly handle digital and mixed signal electronics, and some of them can do better with fast
    digital electronics than regular digital electronic engieers.

    No doubt you are one of the better ones or you wouldn't be telling us. >>>>
    I was the lead hardware engineer on an instrument project, and expressed the idea that we should do some of the fast number
    crunching in emitter-coupled logic. One of the better digital engineers in the team expressed scepticism and said it might be an
    attractive idea, but he'd seen it go wrong quite often. When I said that it had always worked for me his response was that I was
    an an analog engineer, which did make sense. The TTL specialists were never happy with terminated transmission lines.

    I can remember a time when I wanted an ECL 22V10 but there wan't one
    (more than 30 years ago) it doesn't matter if there is now.


    Have you produced a circuit to meet my LED drive specification yet?
    There are many reasons why I think you never will.

    One or more LED's? That's not a specification. The thread is all about John Larkin being rude about a perfectly simple - if
    half-baked - EDN circuit, which he clearly couldn't make sense of.

    I shouldn't have chipped in to the extent that I did.

    The number of different responses will be similar to the number of different responses
    to a question such as "What does God mean or what does God do?"

    Not really. Most people are totally ignorant about electronics, while the religious proselytise furiously.

    --
    Bill Sloman, Sydney




    There are $5 FPGAs now with 10 ns pin-pin delays, 3000 logic blocks, 1
    ns rise/fall, PLLs, cmos and LVDS levels. The internal logic is almost
    zero delay.

    "Almost zero" isn't a lot of help.

    Of course it is, if you actually design stuff. The clbs in an Efinix
    chip are 4-input LUTs, so you can do any weird 4-input logic function
    with the same near-zero delay. I tested that on a proto board; adding
    some logic doesn't noticably affect pin-pin delay. The delay seems to
    be dominated by io cells.

    I just added an extra-cost feature to a pulse generator box, based on
    the behavior of the 4-input LUTs.


    Identifying the source of these $5 FPGAs would also be helpful, if you
    were posting to to be helpful as opposed to posting to make yourself
    look as if you might be competent.

    Try digikey for efinix chips. Lots of them.


    Google says that Microchip IGLOO2/SmartFusion2, Microchip ProASIC3
    (e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts will do it.

    The Microchip ProASIC3 A3P1000 seems to be in that price bracket.

    Yes, there are lots of cheap FPGAs around. Which do you use?


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, April 09, 2026 00:00:38
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    There are $5 FPGAs now with 10 ns pin-pin delays, 3000 logic blocks, 1
    ns rise/fall, PLLs, cmos and LVDS levels. The internal logic is almost
    zero delay.

    "Almost zero" isn't a lot of help.

    Of course it is, if you actually design stuff. The clbs in an Efinix
    chip are 4-input LUTs, so you can do any weird 4-input logic function
    with the same near-zero delay. I tested that on a proto board; adding
    some logic doesn't noticably affect pin-pin delay. The delay seems to
    be dominated by io cells.

    By "almost zero" you mean that you can't measure it, and can't be
    bothered to make any kind of quantitative estimate

    I just added an extra-cost feature to a pulse generator box, based on
    the behavior of the 4-input LUTs.

    Of course you have. An extra-performance feature might induce people to
    pay the extra cost, if you could quantify the improvement.

    Identifying the source of these $5 FPGAs would also be helpful, if you
    were posting to to be helpful as opposed to posting to make yourself
    look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Google says that Microchip IGLOO2/SmartFusion2, Microchip ProASIC3
    (e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts will do it.

    The Microchip ProASIC3 A3P1000 seems to be in that price bracket.

    Yes, there are lots of cheap FPGAs around. Which do you use?

    None of them. In the exceedingly unlikely event of my getting a job I'd
    start looking, but my colleagues would probably tell me what they used.
    In the bad old day, the software to program the parts cost money, so you
    tried to use parts that other people had used.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, April 08, 2026 09:36:30
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    There are $5 FPGAs now with 10 ns pin-pin delays, 3000 logic blocks, 1 >>>> ns rise/fall, PLLs, cmos and LVDS levels. The internal logic is almost >>>> zero delay.

    "Almost zero" isn't a lot of help.

    Of course it is, if you actually design stuff. The clbs in an Efinix
    chip are 4-input LUTs, so you can do any weird 4-input logic function
    with the same near-zero delay. I tested that on a proto board; adding
    some logic doesn't noticably affect pin-pin delay. The delay seems to
    be dominated by io cells.

    By "almost zero" you mean that you can't measure it, and can't be
    bothered to make any kind of quantitative estimate

    I've certainly quantified it. Pin-pin delays on a T20 vary from about
    8 to 12 ns and follow no obvious location-related pattern. Adding some
    logic creates delays a tiny fraction of that. Core supply voltage is a
    big deal on prop delay.

    I wasn't able to see any crosstalk effects.

    Here's our test board, a quickie from JLC.

    https://www.dropbox.com/scl/fi/npkdfdb4shr2m2jokqa1l/X116_On_Plate.jpg?rlkey=negw6radsojplh0zso6gha2vb&raw=1

    This has our 250 MHz 50-cent DDS synthesizer too.


    I just added an extra-cost feature to a pulse generator box, based on
    the behavior of the 4-input LUTs.

    Of course you have. An extra-performance feature might induce people to
    pay the extra cost, if you could quantify the improvement.

    The thing has four delay-and-width outputs. The change allows multiple
    timing channels to be piped to one output, to do double (or triple or
    quad) pulses. The added prop delay is zero.



    Identifying the source of these $5 FPGAs would also be helpful, if you
    were posting to to be helpful as opposed to posting to make yourself
    look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.


    Google says that Microchip IGLOO2/SmartFusion2, Microchip ProASIC3
    (e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts will do it.

    The Microchip ProASIC3 A3P1000 seems to be in that price bracket.

    Yes, there are lots of cheap FPGAs around. Which do you use?

    None of them. In the exceedingly unlikely event of my getting a job I'd >start looking, but my colleagues would probably tell me what they used.
    In the bad old day, the software to program the parts cost money, so you >tried to use parts that other people had used.

    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, April 09, 2026 03:20:55
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>> were posting to to be helpful as opposed to posting to make yourself
    look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same
    search string "pin-to-pin delays less than 10nsec" but since the first
    search didn't pick up the efinix chips, it would have been a waste of time.

    You claim to be using efinix chips that do do that well, so why not tell
    us which ones are that good?

    Google says that Microchip IGLOO2/SmartFusion2, Microchip ProASIC3
    (e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 parts will do it.

    The Microchip ProASIC3 A3P1000 seems to be in that price bracket.

    <snipped the rest>

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, April 08, 2026 10:55:18
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>> were posting to to be helpful as opposed to posting to make yourself >>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2, >Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6 >parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same >search string "pin-to-pin delays less than 10nsec" but since the first >search didn't pick up the efinix chips, it would have been a waste of time.

    You claim to be using efinix chips that do do that well, so why not tell
    us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Gerhard Hoffmann@3:633/10 to All on Wednesday, April 08, 2026 21:56:50
    Am 08.04.26 um 19:55 schrieb john larkin:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>>> were posting to to be helpful as opposed to posting to make yourself >>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same
    search string "pin-to-pin delays less than 10nsec" but since the first
    search didn't pick up the efinix chips, it would have been a waste of time. >>
    You claim to be using efinix chips that do do that well, so why not tell
    us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The I/O cells are intentionally slowed down, esp. for rise/fall time.

    Some Xilinx families had options for the I/O cells so you could make
    some of them faster. Making them ALL faster was the sure way to
    disaster because of ground bounce, esp. when all had the same clock.

    I once had a bus fight between a 74AS244 with guaranteed 8*64 mA
    outputs and a now museum-grade XC3020. The AS244 said 8*LOW and
    the XC3020 wanted 8 * HIGH. The XC3020 won hands-down, even within
    valid Voh.

    Gerhard



    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, April 08, 2026 16:04:58
    On Wed, 8 Apr 2026 21:56:50 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 08.04.26 um 19:55 schrieb john larkin:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>>>> were posting to to be helpful as opposed to posting to make yourself >>>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same
    search string "pin-to-pin delays less than 10nsec" but since the first
    search didn't pick up the efinix chips, it would have been a waste of time. >>>
    You claim to be using efinix chips that do do that well, so why not tell >>> us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The I/O cells are intentionally slowed down, esp. for rise/fall time.

    Some Xilinx families had options for the I/O cells so you could make
    some of them faster. Making them ALL faster was the sure way to
    disaster because of ground bounce, esp. when all had the same clock.

    I once had a bus fight between a 74AS244 with guaranteed 8*64 mA
    outputs and a now museum-grade XC3020. The AS244 said 8*LOW and
    the XC3020 wanted 8 * HIGH. The XC3020 won hands-down, even within
    valid Voh.

    Gerhard


    The T20 has selectable drive strength and speed on the pins, or at
    least on most of them.

    Here's the IBIS:

    https://www.dropbox.com/scl/fi/iexn69krencv11tu6mfkm/trion_drive_strength.pdf?rlkey=i108xdvz2lyy2bknaqxhphz82&dl=0

    Even the "slow" edges have crazy fast rise times.

    The T20 BGA seems to have no signal crosstalk and no ground bounce. I
    ran a bunch of stuff (250 MHz DDS, 50 MHz DDG, four 64-bit
    pseudorandom shift registers) and it was stone quiet. Pulled 24 mA
    core current.





    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, April 09, 2026 16:21:20
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>>> were posting to to be helpful as opposed to posting to make yourself >>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same
    search string "pin-to-pin delays less than 10nsec" but since the first
    search didn't pick up the efinix chips, it would have been a waste of time. >>
    You claim to be using efinix chips that do do that well, so why not tell
    us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    Not plainly enough for me to have been able to read it. And these posts
    are supposed to be informative, as opposed to schemes for dispensing clues.

    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The surface of the board is more extensive and noisier than that the
    surface of the chip. You need to drive 50R transmission lines to get
    signals around the board. Some of the clock lines inside package may
    need some attention too.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, April 09, 2026 08:23:07
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>>>> were posting to to be helpful as opposed to posting to make yourself >>>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you.
    I could have done the same exercise on the efinix range, using the same
    search string "pin-to-pin delays less than 10nsec" but since the first
    search didn't pick up the efinix chips, it would have been a waste of time. >>>
    You claim to be using efinix chips that do do that well, so why not tell >>> us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    Not plainly enough for me to have been able to read it. And these posts
    are supposed to be informative, as opposed to schemes for dispensing clues.

    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The surface of the board is more extensive and noisier than that the
    surface of the chip. You need to drive 50R transmission lines to get
    signals around the board. Some of the clock lines inside package may
    need some attention too.

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    https://www.dropbox.com/scl/fi/iexn69krencv11tu6mfkm/trion_drive_strength.pdf?rlkey=i108xdvz2lyy2bknaqxhphz82&dl=0

    If a trace is short, just run it and don't worry. The "slow" drive
    option on the efinix chips is still crazy fast.

    50r traces would be fat and reduce pcb wiring density and increase
    supply noise and ground bounce and stuff.

    If a run several inches long and it's a level only, let it ring a
    little. Everything will settle an a naosecond.

    We have one board we're developing now, where an FPGA drives a trace,
    then a ribbon cable, then a trace on another board, and finally a CMOS receiver. Total run might be 8", and some signals are edge-sensitive,
    and picoseconds matter . In that case, we'll keep all the pcb traces
    75 ohms, to mostly match the ribbon cable, and set the FPGA drive
    strength to mostly source terminate. I don't mind sourcing a little
    low and having a bit of overshoot at the receiver, which compensates
    for various losses.

    We Spiced all that, and bought a new Rigol fet probe to snoop the
    first boards.

    No big deal, just engineering in the 21st century.

    https://www.dropbox.com/scl/fi/yxe2pjl1kosjan8ngu0zx/B_RF_3.jpg?rlkey=yxtn5nvr5pv8p0p11tlx8hk8g&raw=1


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, April 10, 2026 01:55:00
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you >>>>>>>> were posting to to be helpful as opposed to posting to make yourself >>>>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2,
    Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you. >>>> I could have done the same exercise on the efinix range, using the same >>>> search string "pin-to-pin delays less than 10nsec" but since the first >>>> search didn't pick up the efinix chips, it would have been a waste of time.

    You claim to be using efinix chips that do do that well, so why not tell >>>> us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    Not plainly enough for me to have been able to read it. And these posts
    are supposed to be informative, as opposed to schemes for dispensing clues. >>
    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit
    slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how
    many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The surface of the board is more extensive and noisier than that the
    surface of the chip. You need to drive 50R transmission lines to get
    signals around the board. Some of the clock lines inside package may
    need some attention too.

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    You don't have a lot of choice if you want to use non-dispersive buried strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace
    or relatively thick and low dielectric constant layers to sandwich the
    trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond signals you can't go far before the reflection from an unterminated line become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of
    transmission line. ECL deliberately chose a smaller voltage swing to
    keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their
    parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I
    worked on in the 1990s. It never got built - the academic customer ran
    out of funding after we'd got the circuit diagrams sorted out, and were running into the dire printed circuit layout tools that the Radboud
    University had foisted on us. I'd done quite well with software we'd had
    up to that point, but some Orcad rep had got at the adminstration at
    just the wrong moment.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, April 09, 2026 09:40:09
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    Identifying the source of these $5 FPGAs would also be helpful, if you
    were posting to to be helpful as opposed to posting to make yourself >>>>>>>>> look as if you might be competent.

    Try digikey for efinix chips. Lots of them.

    But no specific part numbers.

    Do you own a web browser? Seems not.

    Since I clearly used one to find the "Microchip IGLOO2/SmartFusion2, >>>>> Microchip ProASIC3(e.g., A3P1000) and AMD/Xilinx Artix-7/Spartan-6
    parts"listed below, that's a singularly stupid assertion, even for you. >>>>> I could have done the same exercise on the efinix range, using the same >>>>> search string "pin-to-pin delays less than 10nsec" but since the first >>>>> search didn't pick up the efinix chips, it would have been a waste of time.

    You claim to be using efinix chips that do do that well, so why not tell >>>>> us which ones are that good?

    I just named (and you snipped) the T20 and my proto board shows it in
    plain sight.

    Not plainly enough for me to have been able to read it. And these posts
    are supposed to be informative, as opposed to schemes for dispensing clues. >>>
    We're going to use the T120 in a new design, because it has so much
    dual-port sram and a nice DDR DRAM interface. We think it may be a bit >>>> slower than the T20 as far as logic goes.

    If I had an assortment of Efinix chips, I could xray them, and see how >>>> many are bond-outs of the same silicon. I'd suspect that bigger chips
    might have slower pin-pin delays.

    That's the bummer about FPGAs: the internals keep getting faster but
    the i/o cells don't.

    The surface of the board is more extensive and noisier than that the
    surface of the chip. You need to drive 50R transmission lines to get
    signals around the board. Some of the clock lines inside package may
    need some attention too.

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    You don't have a lot of choice if you want to use non-dispersive buried >strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace
    or relatively thick and low dielectric constant layers to sandwich the >trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond >signals you can't go far before the reflection from an unterminated line >become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of >transmission line. ECL deliberately chose a smaller voltage swing to
    keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their
    parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I
    worked on in the 1990s. It never got built - the academic customer ran
    out of funding after we'd got the circuit diagrams sorted out, and were >running into the dire printed circuit layout tools that the Radboud >University had foisted on us. I'd done quite well with software we'd had
    up to that point, but some Orcad rep had got at the adminstration at
    just the wrong moment.

    Pity. Failures are discouraging.

    LVDS makes sense sometimes, but not in this case. It takes twice as
    many FPGA balls, twice as many ribbon cable wires, and forces the PCB
    to have more layers (to route out the BGA) which is expensive and
    makes the dielectrics even thinner.

    The 6-layer board with single-ended 75 ohm traces will work fine.

    The two outer rows of a 0.8mm BGA can be routed out on layer 1, with 5
    mil traces. But every row after that needs microvias and another PCB
    layer. And each row going in has fewer i/o pins. That's an exponential catastrophe.

    Real life poses interesting problems.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, April 10, 2026 03:41:39
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    You don't have a lot of choice if you want to use non-dispersive buried
    strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace
    or relatively thick and low dielectric constant layers to sandwich the
    trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond
    signals you can't go far before the reflection from an unterminated line
    become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of
    transmission line. ECL deliberately chose a smaller voltage swing to
    keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their
    parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I
    worked on in the 1990s. It never got built - the academic customer ran
    out of funding after we'd got the circuit diagrams sorted out, and were
    running into the dire printed circuit layout tools that the Radboud
    University had foisted on us. I'd done quite well with software we'd had
    up to that point, but some Orcad rep had got at the adminstration at
    just the wrong moment.

    Pity. Failures are discouraging.

    LVDS makes sense sometimes, but not in this case. It takes twice as
    many FPGA balls, twice as many ribbon cable wires, and forces the PCB
    to have more layers (to route out the BGA) which is expensive and
    makes the dielectrics even thinner.

    The 6-layer board with single-ended 75 ohm traces will work fine.

    Yuck.

    The two outer rows of a 0.8mm BGA can be routed out on layer 1, with 5
    mil traces. But every row after that needs microvias and another PCB
    layer. And each row going in has fewer i/o pins. That's an exponential catastrophe.

    Real life poses interesting problems.

    Why the insistence ball grid arrays? The T20 is available in 100-pin and 144-pin LQFP packages which are a great deal easier to route. Only the
    timing outputs and clocks need to be fast - the data I/O can be
    multiplexed or even serial.

    It's elegant to fit all the logic into one package, but if splitting it
    over a couple of packages makes the routing easier and lets you get away
    with fewer layers it may be worth thinking about.

    And ribbon cables aren't particularly wonderful transmission lines.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, April 09, 2026 18:21:28
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:

    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    You don't have a lot of choice if you want to use non-dispersive buried
    strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace
    or relatively thick and low dielectric constant layers to sandwich the
    trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond
    signals you can't go far before the reflection from an unterminated line >>> become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of
    transmission line. ECL deliberately chose a smaller voltage swing to
    keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their
    parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I
    worked on in the 1990s. It never got built - the academic customer ran
    out of funding after we'd got the circuit diagrams sorted out, and were
    running into the dire printed circuit layout tools that the Radboud
    University had foisted on us. I'd done quite well with software we'd had >>> up to that point, but some Orcad rep had got at the adminstration at
    just the wrong moment.

    Pity. Failures are discouraging.

    LVDS makes sense sometimes, but not in this case. It takes twice as
    many FPGA balls, twice as many ribbon cable wires, and forces the PCB
    to have more layers (to route out the BGA) which is expensive and
    makes the dielectrics even thinner.

    The 6-layer board with single-ended 75 ohm traces will work fine.

    Yuck.

    You dislike success?



    The two outer rows of a 0.8mm BGA can be routed out on layer 1, with 5
    mil traces. But every row after that needs microvias and another PCB
    layer. And each row going in has fewer i/o pins. That's an exponential
    catastrophe.

    Real life poses interesting problems.

    Why the insistence ball grid arrays? The T20 is available in 100-pin and >144-pin LQFP packages which are a great deal easier to route. Only the >timing outputs and clocks need to be fast - the data I/O can be
    multiplexed or even serial.

    BGAs are small and have near zero lead inductance. And believe it or
    don't, they solder better.

    I can't multiplex fast pulses with picosecond jitters specified.

    Our FPGA configuration and runtime data i/o are already a shared SPI
    interface from the RP2040 CPU.


    It's elegant to fit all the logic into one package, but if splitting it
    over a couple of packages makes the routing easier and lets you get away >with fewer layers it may be worth thinking about.

    FPGA-internal routings are small and fast.


    And ribbon cables aren't particularly wonderful transmission lines.

    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm transmission line.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    75 is a convenient impedance for PCB traces and for source termination
    in our FPGA.



    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, April 10, 2026 16:51:21
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    50r terms make no sense for single-ended cmos logic levels between
    chips.

    You don't have a lot of choice if you want to use non-dispersive buried >>>> strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace >>>> or relatively thick and low dielectric constant layers to sandwich the >>>> trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond >>>> signals you can't go far before the reflection from an unterminated line >>>> become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of
    transmission line. ECL deliberately chose a smaller voltage swing to
    keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their
    parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I
    worked on in the 1990s. It never got built - the academic customer ran >>>> out of funding after we'd got the circuit diagrams sorted out, and were >>>> running into the dire printed circuit layout tools that the Radboud
    University had foisted on us. I'd done quite well with software we'd had >>>> up to that point, but some Orcad rep had got at the adminstration at
    just the wrong moment.

    Pity. Failures are discouraging.

    They aren't enjoyable, but if you make a habit of pushing the boundaries
    they do happen, and you can't let them discourage you.

    LVDS makes sense sometimes, but not in this case. It takes twice as
    many FPGA balls, twice as many ribbon cable wires, and forces the PCB
    to have more layers (to route out the BGA) which is expensive and
    makes the dielectrics even thinner.

    The 6-layer board with single-ended 75 ohm traces will work fine.

    Yuck.

    You dislike success?

    Self-proclaimed success is always somewhat suspect.

    The two outer rows of a 0.8mm BGA can be routed out on layer 1, with 5
    mil traces. But every row after that needs microvias and another PCB
    layer. And each row going in has fewer i/o pins. That's an exponential
    catastrophe.

    Real life poses interesting problems.

    Why the insistence ball grid arrays? The T20 is available in 100-pin and
    144-pin LQFP packages which are a great deal easier to route. Only the
    timing outputs and clocks need to be fast - the data I/O can be
    multiplexed or even serial.

    BGAs are small and have near zero lead inductance. And believe it or
    not, they solder better.

    Not a lot of help if the points that they get soldered to are hard to
    connect to anything else. I'd expect the inner areas pf the ball array
    to be devoted to power supply connections for precisely that reason.

    I can't multiplex fast pulses with picosecond jitters specified.

    What did you thing I meant by "Only the timing outputs and clocks need
    to be fast - the data I/O can be multiplexed or even serial"?

    Our FPGA configuration and runtime data i/o are already a shared SPI interface from the RP2040 CPU.

    As I was saying they would be.

    It's elegant to fit all the logic into one package, but if splitting it
    over a couple of packages makes the routing easier and lets you get away
    with fewer layers it may be worth thinking about.

    FPGA-internal routings are small and fast.

    Which isn't much help if the external routings aren't.

    And ribbon cables aren't particularly wonderful transmission lines.

    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm transmission line.

    That was standard operating practice at Cambridge Instruments in the
    late 1980s. I was one of the first to use it in production, but one of
    my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination
    in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, April 10, 2026 02:00:05
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    50r terms make no sense for single-ended cmos logic levels between >>>>>> chips.

    You don't have a lot of choice if you want to use non-dispersive buried >>>>> strip-line to move signals around a printed circuit board.
    Trying to get a higher impedance trace means either a very narrow trace >>>>> or relatively thick and low dielectric constant layers to sandwich the >>>>> trace.

    The signals covers about 20cm in one nanosecond, so with sub-nanosecond >>>>> signals you can't go far before the reflection from an unterminated line >>>>> become embarrassing.

    You don't actually want to use CMOS logic levels on that kind of
    transmission line. ECL deliberately chose a smaller voltage swing to >>>>> keep the current levels tolerable.

    https://en.wikipedia.org/wiki/Low-voltage_differential_signaling

    took the idea a bit further. I'd be surprised if your efinix chips
    didn't offer LVDS drivers. The efinix website says that some of their >>>>> parts do.

    I did specify LVDS signals for the backplane of a fancy timing unit I >>>>> worked on in the 1990s. It never got built - the academic customer ran >>>>> out of funding after we'd got the circuit diagrams sorted out, and were >>>>> running into the dire printed circuit layout tools that the Radboud
    University had foisted on us. I'd done quite well with software we'd had >>>>> up to that point, but some Orcad rep had got at the adminstration at >>>>> just the wrong moment.

    Pity. Failures are discouraging.

    They aren't enjoyable, but if you make a habit of pushing the boundaries >they do happen, and you can't let them discourage you.

    LVDS makes sense sometimes, but not in this case. It takes twice as
    many FPGA balls, twice as many ribbon cable wires, and forces the PCB
    to have more layers (to route out the BGA) which is expensive and
    makes the dielectrics even thinner.

    The 6-layer board with single-ended 75 ohm traces will work fine.

    Yuck.

    You dislike success?

    Self-proclaimed success is always somewhat suspect.

    The two outer rows of a 0.8mm BGA can be routed out on layer 1, with 5 >>>> mil traces. But every row after that needs microvias and another PCB
    layer. And each row going in has fewer i/o pins. That's an exponential >>>> catastrophe.

    Real life poses interesting problems.

    Why the insistence ball grid arrays? The T20 is available in 100-pin and >>> 144-pin LQFP packages which are a great deal easier to route. Only the
    timing outputs and clocks need to be fast - the data I/O can be
    multiplexed or even serial.

    BGAs are small and have near zero lead inductance. And believe it or
    not, they solder better.

    Not a lot of help if the points that they get soldered to are hard to >connect to anything else. I'd expect the inner areas pf the ball array
    to be devoted to power supply connections for precisely that reason.

    I can't multiplex fast pulses with picosecond jitters specified.

    What did you thing I meant by "Only the timing outputs and clocks need
    to be fast - the data I/O can be multiplexed or even serial"?

    Our FPGA configuration and runtime data i/o are already a shared SPI
    interface from the RP2040 CPU.

    As I was saying they would be.

    It's elegant to fit all the logic into one package, but if splitting it
    over a couple of packages makes the routing easier and lets you get away >>> with fewer layers it may be worth thinking about.

    FPGA-internal routings are small and fast.

    Which isn't much help if the external routings aren't.

    And ribbon cables aren't particularly wonderful transmission lines.

    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm
    transmission line.

    That was standard operating practice at Cambridge Instruments in the
    late 1980s. I was one of the first to use it in production, but one of
    my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond >rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination
    in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz
    either, but they are great otherwise, like for 200 ps edges.

    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that
    the 25 mil stuff is close to 75 ohms.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Saturday, April 11, 2026 00:06:40
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines.

    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm
    transmission line.

    That was standard operating practice at Cambridge Instruments in the
    late 1980s. I was one of the first to use it in production, but one of
    my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond
    rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination
    in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but
    doing it right might be difficult.

    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz
    either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that
    the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's dielectric constant to get a reliable value.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, April 10, 2026 08:13:10
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines.

    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm
    transmission line.

    That was standard operating practice at Cambridge Instruments in the
    late 1980s. I was one of the first to use it in production, but one of
    my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond
    rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination >>>> in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but
    doing it right might be difficult.

    We do stuff like this all the time, and this case isn't a big deal. Of
    couse it will work first time.


    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz
    either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    No, they are great. We did some ATLC e/m simulations to get a good
    wideband match to the PCB, to get the pads and stackups right. The fat
    center pin isn't ideal but can be corrected for.

    https://www.dropbox.com/scl/fi/vfi56wy5hkwva51bx77z6/SS_SMA_Edge.JPG?rlkey=nbmbyb0f54uslcpc0nh7rs21p&raw=1

    https://www.dropbox.com/scl/fi/dncsaketsakdormve3i45/Edge_alone_3.jpg?rlkey=13i4pozj116gwk474dc3dnmxt&raw=1

    That was interesting. The center pin sims to 100 ohms in free air, not
    soldered to a board.


    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that
    the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's >dielectric constant to get a reliable value.

    Silly me, I just measured the impedance of the cable that we stock. My
    old 11802 TDR seems to be pretty good.

    Your attitude is that everything that I do is wrong and that you are
    always smarter. I gently suggest that you reconsider.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Saturday, April 11, 2026 03:05:16
    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines. >>>>>
    The fine-pitch one that we are using is great. I alternate the fast
    signals with real or effective grounds and get a really clean 75 ohm >>>>> transmission line.

    That was standard operating practice at Cambridge Instruments in the
    late 1980s. I was one of the first to use it in production, but one of >>>> my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond >>>> rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination >>>>> in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but
    doing it right might be difficult.

    We do stuff like this all the time, and this case isn't a big deal. Of
    course it will work first time.

    That confession might be held against you. Working right, and working
    well enough that the customers don't notice anything wrong, are rather different levels of performance.

    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz
    either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    No, they are great. We did some ATLC e/m simulations to get a good
    wideband match to the PCB, to get the pads and stackups right. The fat
    center pin isn't ideal but can be corrected for.

    https://www.dropbox.com/scl/fi/vfi56wy5hkwva51bx77z6/SS_SMA_Edge.JPG?rlkey=nbmbyb0f54uslcpc0nh7rs21p&raw=1

    https://www.dropbox.com/scl/fi/dncsaketsakdormve3i45/Edge_alone_3.jpg?rlkey=13i4pozj116gwk474dc3dnmxt&raw=1

    That was interesting. The center pin sims to 100 ohms in free air, not soldered to a board.

    SMA is supposed to be good to 20GHz. A picture of the connector and and
    a printout from an electromagnetic field simulation program isn't any
    kind of evidence of that kind of performace.

    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that
    the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's
    dielectric constant to get a reliable value.

    Silly me, I just measured the impedance of the cable that we stock. My
    old 11802 TDR seems to be pretty good.

    "Close to 75 ohms" isn't any kind of exact value.
    Your attitude is that everything that I do is wrong and that you are
    always smarter. I gently suggest that you reconsider.

    Everything you do is a bit slap-dash, and if you were a bit smarter
    you'd be able to make it less obvious. Making stuff that is just good
    enough to keep your customers happy isn't wrong - it is pretty much
    commercial wisdom - but boasting about it isn't a great tactic.

    A bit of over-design gives you a solution that will last through a
    couple of generations of up-grades and probably save money in the long term.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, April 10, 2026 10:55:23
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines. >>>>>>
    The fine-pitch one that we are using is great. I alternate the fast >>>>>> signals with real or effective grounds and get a really clean 75 ohm >>>>>> transmission line.

    That was standard operating practice at Cambridge Instruments in the >>>>> late 1980s. I was one of the first to use it in production, but one of >>>>> my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond >>>>> rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination >>>>>> in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but
    doing it right might be difficult.

    We do stuff like this all the time, and this case isn't a big deal. Of
    course it will work first time.

    That confession might be held against you. Working right, and working
    well enough that the customers don't notice anything wrong, are rather >different levels of performance.

    As long as we get orders and the checks clear, we are reasonably
    happy. Personally, I just want to design stuff.


    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz
    either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    No, they are great. We did some ATLC e/m simulations to get a good
    wideband match to the PCB, to get the pads and stackups right. The fat
    center pin isn't ideal but can be corrected for.

    https://www.dropbox.com/scl/fi/vfi56wy5hkwva51bx77z6/SS_SMA_Edge.JPG?rlkey=nbmbyb0f54uslcpc0nh7rs21p&raw=1

    https://www.dropbox.com/scl/fi/dncsaketsakdormve3i45/Edge_alone_3.jpg?rlkey=13i4pozj116gwk474dc3dnmxt&raw=1

    That was interesting. The center pin sims to 100 ohms in free air, not
    soldered to a board.

    SMA is supposed to be good to 20GHz. A picture of the connector and and
    a printout from an electromagnetic field simulation program isn't any
    kind of evidence of that kind of performace.

    We wanted to design the PCB footprint and stackup to best match that
    connector. I can share it with anyone who's interested.

    My humble appologies for annoying you with things that don't interest
    you.


    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that
    the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's >>> dielectric constant to get a reliable value.

    Silly me, I just measured the impedance of the cable that we stock. My
    old 11802 TDR seems to be pretty good.

    "Close to 75 ohms" isn't any kind of exact value.
    Your attitude is that everything that I do is wrong and that you are
    always smarter. I gently suggest that you reconsider.

    Everything you do is a bit slap-dash, and if you were a bit smarter
    you'd be able to make it less obvious. Making stuff that is just good
    enough to keep your customers happy isn't wrong - it is pretty much >commercial wisdom - but boasting about it isn't a great tactic.

    E/M simulation isn't slap-dash. I followed that up with a little
    Dremeling to final-tweak the match.


    A bit of over-design gives you a solution that will last through a
    couple of generations of up-grades and probably save money in the long term.

    How is your business doing?


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Saturday, April 11, 2026 16:02:55
    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines. >>>>>>>
    The fine-pitch one that we are using is great. I alternate the fast >>>>>>> signals with real or effective grounds and get a really clean 75 ohm >>>>>>> transmission line.

    That was standard operating practice at Cambridge Instruments in the >>>>>> late 1980s. I was one of the first to use it in production, but one of >>>>>> my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond >>>>>> rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination >>>>>>> in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't
    happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but
    doing it right might be difficult.

    We do stuff like this all the time, and this case isn't a big deal. Of
    course it will work first time.

    That confession might be held against you. Working right, and working
    well enough that the customers don't notice anything wrong, are rather
    different levels of performance.

    As long as we get orders and the checks clear, we are reasonably
    happy. Personally, I just want to design stuff.


    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz >>>>> either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    No, they are great. We did some ATLC e/m simulations to get a good
    wideband match to the PCB, to get the pads and stackups right. The fat
    center pin isn't ideal but can be corrected for.

    https://www.dropbox.com/scl/fi/vfi56wy5hkwva51bx77z6/SS_SMA_Edge.JPG?rlkey=nbmbyb0f54uslcpc0nh7rs21p&raw=1

    https://www.dropbox.com/scl/fi/dncsaketsakdormve3i45/Edge_alone_3.jpg?rlkey=13i4pozj116gwk474dc3dnmxt&raw=1

    That was interesting. The center pin sims to 100 ohms in free air, not
    soldered to a board.

    SMA is supposed to be good to 20GHz. A picture of the connector and and
    a printout from an electromagnetic field simulation program isn't any
    kind of evidence of that kind of performace.

    We wanted to design the PCB footprint and stackup to best match that connector. I can share it with anyone who's interested.

    My humble apologies for annoying you with things that don't interest
    you.

    That's not what you need to apologise for. You should be apologising for tantalsing us with the output from an electromagnetic field simulation
    of half a connector pair, when you should have been simulating the mated
    pair of connectors.

    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in
    this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that >>>>> the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's >>>> dielectric constant to get a reliable value.

    Silly me, I just measured the impedance of the cable that we stock. My
    old 11802 TDR seems to be pretty good.

    "Close to 75 ohms" isn't any kind of exact value.
    Your attitude is that everything that I do is wrong and that you are
    always smarter. I gently suggest that you reconsider.

    Everything you do is a bit slap-dash, and if you were a bit smarter
    you'd be able to make it less obvious. Making stuff that is just good
    enough to keep your customers happy isn't wrong - it is pretty much
    commercial wisdom - but boasting about it isn't a great tactic.

    E/M simulation isn't slap-dash. I followed that up with a little
    Dremeling to final-tweak the match.

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    A bit of over-design gives you a solution that will last through a
    couple of generations of up-grades and probably save money in the long term.

    How is your business doing?

    As you well know, it is totally non-existent.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, April 11, 2026 09:53:32
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    And ribbon cables aren't particularly wonderful transmission lines. >>>>>>>>
    The fine-pitch one that we are using is great. I alternate the fast >>>>>>>> signals with real or effective grounds and get a really clean 75 ohm >>>>>>>> transmission line.

    That was standard operating practice at Cambridge Instruments in the >>>>>>> late 1980s. I was one of the first to use it in production, but one of >>>>>>> my colleagues used in a field fix a little earlier.

    Ribbon cable terminations weren't designed to cope with sub-nanosecond >>>>>>> rise-times, so it wasn't all that great.

    75 is a convenient impedance for PCB traces and for source termination >>>>>>>> in our FPGA.

    https://www.dropbox.com/scl/fi/b9bm19a5u371irmdlas3d/25_mil_rib_TDR.jpg?rlkey=pvz57m7ml42prv4w6hfr10sq6&dl=0

    That's a pretty horrible 100% overshoot, if brief.

    The inductive glitch is from the loop area at the hand-soldered
    transition from the SMA connector into the ribbon cable. That won't >>>>>> happen on a PCB.

    Really? You may be able to make it tidier, and the loop smaller, but >>>>> doing it right might be difficult.

    We do stuff like this all the time, and this case isn't a big deal. Of >>>> course it will work first time.

    That confession might be held against you. Working right, and working
    well enough that the customers don't notice anything wrong, are rather
    different levels of performance.

    As long as we get orders and the checks clear, we are reasonably
    happy. Personally, I just want to design stuff.


    Those $1 chinese edge-launch SMA connectors are not perfect at 20 GHz >>>>>> either, but they are great otherwise, like for 200 ps edges.

    For your usual definition of "great" which seems to be "barely good enough".

    No, they are great. We did some ATLC e/m simulations to get a good
    wideband match to the PCB, to get the pads and stackups right. The fat >>>> center pin isn't ideal but can be corrected for.

    https://www.dropbox.com/scl/fi/vfi56wy5hkwva51bx77z6/SS_SMA_Edge.JPG?rlkey=nbmbyb0f54uslcpc0nh7rs21p&raw=1

    https://www.dropbox.com/scl/fi/dncsaketsakdormve3i45/Edge_alone_3.jpg?rlkey=13i4pozj116gwk474dc3dnmxt&raw=1

    That was interesting. The center pin sims to 100 ohms in free air, not >>>> soldered to a board.

    SMA is supposed to be good to 20GHz. A picture of the connector and and
    a printout from an electromagnetic field simulation program isn't any
    kind of evidence of that kind of performace.

    We wanted to design the PCB footprint and stackup to best match that
    connector. I can share it with anyone who's interested.

    My humble apologies for annoying you with things that don't interest
    you.

    That's not what you need to apologise for. You should be apologising for >tantalsing us with the output from an electromagnetic field simulation
    of half a connector pair, when you should have been simulating the mated >pair of connectors.

    ATLC only does 2D sims. 3D em simularors are a much bigger deal. But
    our concern was to design the best PCB footprint. The PCB end, not the
    coax transition, obvious and wildly dominates. The main gotcha is that
    big fat center pin.

    The em sim was just a shortcut bootstrap in converging on a good PCB
    decal for this connector. The final tuning is the multilayer PCB.


    The original 3M 50-mil pitch ribbon cable is typically 110 ohms in >>>>>> this gnd-sig-gnd config. 110 can get ugly. I was pleased to find that >>>>>> the 25 mil stuff is close to 75 ohms.

    But not pleased enough to find out the exact value. A google search
    threw up 80R and 83R. You probably have nail down the insulator and it's >>>>> dielectric constant to get a reliable value.

    Silly me, I just measured the impedance of the cable that we stock. My >>>> old 11802 TDR seems to be pretty good.

    "Close to 75 ohms" isn't any kind of exact value.
    Your attitude is that everything that I do is wrong and that you are
    always smarter. I gently suggest that you reconsider.

    Everything you do is a bit slap-dash, and if you were a bit smarter
    you'd be able to make it less obvious. Making stuff that is just good
    enough to keep your customers happy isn't wrong - it is pretty much
    commercial wisdom - but boasting about it isn't a great tactic.

    E/M simulation isn't slap-dash. I followed that up with a little
    Dremeling to final-tweak the match.

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    How did you design wideband SMA to PCB edge-launch transitions?

    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.


    A bit of over-design gives you a solution that will last through a
    couple of generations of up-grades and probably save money in the long term.

    How is your business doing?

    As you well know, it is totally non-existent.

    If you still want to design stuff, get out and meet people. But I
    suggest you keep the contempt level not too obvious.





    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, April 12, 2026 14:49:35
    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put
    through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon clothe
    as the top and bottom layers of our six-kayer board and that was back in
    1986.

    A bit of over-design gives you a solution that will last through a
    couple of generations of up-grades and probably save money in the long term.

    How is your business doing?

    As you well know, it is totally non-existent.

    If you still want to design stuff, get out and meet people. But I
    suggest you keep the contempt level not too obvious.

    Few people deserve contempt. Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Sunday, April 12, 2026 08:52:04
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the
    knowledge could be passed on?

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed decisions.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, April 12, 2026 20:22:18
    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Sunday, April 12, 2026 12:32:32
    Bill Sloman <bill.sloman@ieee.org> wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more informative.

    Yes, I've never worked anywhere where there were formal channels, the
    informal one was the coffee break and the canteen and it worked very
    well. The Chief Engineer used to wander around the development
    department having regular chats with the design engineers to make sure everything was running smoothly and to step in if necessary.


    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    That's a good plan - and even going out as a locum service engineer from
    time to time, so you really get the feel for what they have to contend
    with. In one firm I worked for, the designer of a piece of equipment
    was on call to the production line and the repair shop if any of his
    designs caused them problems.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 04:37:17
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put >through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon clothe
    as the top and bottom layers of our six-kayer board and that was back in >1986.

    That might take two months and cost a few hundred times as much.

    This isn't bad at all, for a $2 JLC board.

    https://www.dropbox.com/scl/fi/ra5rrpd31qsk0ps9s8e2v/R100_TDR_Test.jpg?rlkey=xwht2gtvvg06hierj3kzvpe5x&raw=1

    Here's a mixed-dielectric board.

    https://www.dropbox.com/scl/fi/v3gwktrpy51089e9px7lo/MOV02429.MPG?rlkey=hr4m4dakdltgx4wtfw2s78jli&dl=0


    One problem with teflon lams is that the copper adhesion is terrible.
    Vias can be flakey too. Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric. For short traces sending
    logic levels around, an exotic lam isn't worth it. Even crazy fast
    PCIe is done on FR4.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 04:39:16
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the
    knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed
    decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more >informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, April 12, 2026 22:43:31
    On 12/04/2026 9:39 pm, john larkin wrote:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:

    <snip>

    We don't have engineering technicians. We can solder ourselves.

    We had an actual production line. We did solder ourselves, and some of
    my get-it-to-work-as-it-was-designed-to-work changes were allowed to go
    out to customers.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, April 12, 2026 23:07:30
    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash - >>>> it is total incompetence. It makes it perfectly obvious why you needed >>>> to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put
    through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth
    as the top and bottom layers of our six-kayer board and that was back in
    1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive -
    the printed circuit house had had to buy quite a large minimum chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it. Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder.

    If you need good performance, you have to take more care.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, April 12, 2026 23:15:08
    On 12/04/2026 9:32 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the
    knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed
    decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more
    informative.

    Yes, I've never worked anywhere where there were formal channels, the informal one was the coffee break and the canteen and it worked very
    well. The Chief Engineer used to wander around the development
    department having regular chats with the design engineers to make sure everything was running smoothly and to step in if necessary.


    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    That's a good plan - and even going out as a locum service engineer from
    time to time, so you really get the feel for what they have to contend
    with. In one firm I worked for, the designer of a piece of equipment
    was on call to the production line and the repair shop if any of his
    designs caused them problems.

    Cambridge Instruments worked that way too. Between projects the design engineers put in time on "mods" - modifications proposed by the
    production technicians to make boards more reliable or easier to set up.
    About half of them were misconceived, but the other half could get quite interesting, and we did have to talk to the production line technicians
    which was good for informal communications.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 08:01:49
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash - >>>>> it is total incompetence. It makes it perfectly obvious why you needed >>>>> to Dremel the copper on the board to minimise the impedance mis-match. >>>>
    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put
    through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth
    as the top and bottom layers of our six-kayer board and that was back in >>> 1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive -
    the printed circuit house had had to buy quite a large minimum chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late >1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the >dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it. >> Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder.

    You think the PCIe spec is sloppy?

    Use something else in your PC.


    If you need good performance, you have to take more care.

    Or adaptive equalization.



    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 10:47:58
    On Sun, 12 Apr 2026 17:38:43 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin wrote: >|-----------------------------------------------------------------|
    |"We don't have engineering technicians. We can solder ourselves."| >|-----------------------------------------------------------------|

    All engineers are technicians, as all technicians are engineers, by >definitions.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    No. Technicians seldom design things. By definition!

    Engineers seldom do routine production test or repairs.

    Engineers get paid more.

    What do you do?


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Liebermann@3:633/10 to All on Sunday, April 12, 2026 10:55:02
    On Sun, 12 Apr 2026 17:38:43 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin wrote: >|-----------------------------------------------------------------|
    |"We don't have engineering technicians. We can solder ourselves."| >|-----------------------------------------------------------------|

    All engineers are technicians, as all technicians are engineers, by >definitions.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    Methinks you'll find that the salaries of electronic engineers and
    technicians are quite different. From a random AI dust bin of wisdom:

    "In California, the average salary for an electronics technician is approximately $60,000-$66,000 annually ($29-$32 per hour) as of April
    2026, with top earners exceeding $80,000-$90,000."

    "The average salary for an electronics engineer in the U.S. is
    approximately $111,910 to $127,590 per year, according to 2024-2026
    data. Top earners can exceed $140,000 annually..."

    In other words:
    two technicians = one engineer

    --
    Jeff Liebermann jeffl@cruzio.com
    PO Box 272 http://www.LearnByDestroying.com
    Ben Lomond CA 95005-0272 AE6KS 831-336-2558


    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 11:06:45
    On Sun, 12 Apr 2026 10:55:02 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Sun, 12 Apr 2026 17:38:43 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin wrote: >>|-----------------------------------------------------------------|
    |"We don't have engineering technicians. We can solder ourselves."| >>|-----------------------------------------------------------------|

    All engineers are technicians, as all technicians are engineers, by >>definitions.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    Methinks you'll find that the salaries of electronic engineers and >technicians are quite different. From a random AI dust bin of wisdom:

    "In California, the average salary for an electronics technician is >approximately $60,000-$66,000 annually ($29-$32 per hour) as of April
    2026, with top earners exceeding $80,000-$90,000."

    "The average salary for an electronics engineer in the U.S. is
    approximately $111,910 to $127,590 per year, according to 2024-2026
    data. Top earners can exceed $140,000 annually..."

    In other words:
    two technicians = one engineer

    People hired as techs very rarely advance to engineering positions.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Sunday, April 12, 2026 23:43:28
    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 12 Apr 2026 10:55:02 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Sun, 12 Apr 2026 17:38:43 -0000 (UTC), Niocl s P¢l Caile n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin wrote:
    |-----------------------------------------------------------------|
    |"We don't have engineering technicians. We can solder ourselves."|
    |-----------------------------------------------------------------|

    All engineers are technicians, as all technicians are engineers, by
    definitions.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    Methinks you'll find that the salaries of electronic engineers and
    technicians are quite different. From a random AI dust bin of wisdom:

    "In California, the average salary for an electronics technician is
    approximately $60,000-$66,000 annually ($29-$32 per hour) as of April
    2026, with top earners exceeding $80,000-$90,000."

    "The average salary for an electronics engineer in the U.S. is
    approximately $111,910 to $127,590 per year, according to 2024-2026
    data. Top earners can exceed $140,000 annually..."

    In other words:
    two technicians = one engineer

    People hired as techs very rarely advance to engineering positions.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Well, apart from Jim Williams of LTC and Errol Dietz, who started out as
    Bob Pease?s tech and wound up as CTO of National Semi.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.13
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, April 13, 2026 11:36:45
    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash - >>>>>> it is total incompetence. It makes it perfectly obvious why you needed >>>>>> to Dremel the copper on the board to minimise the impedance mis-match. >>>>>
    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put >>>> through mixed signal D-type connectors too. Just to add high end appeal >>>> we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal >>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth >>>> as the top and bottom layers of our six-kayer board and that was back in >>>> 1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive -
    the printed circuit house had had to buy quite a large minimum chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the
    dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it. >>> Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be
    higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 19:10:12
    On Sun, 12 Apr 2026 23:43:28 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 12 Apr 2026 10:55:02 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Sun, 12 Apr 2026 17:38:43 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin wrote:
    |-----------------------------------------------------------------|
    |"We don't have engineering technicians. We can solder ourselves."|
    |-----------------------------------------------------------------|

    All engineers are technicians, as all technicians are engineers, by
    definitions.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    Methinks you'll find that the salaries of electronic engineers and
    technicians are quite different. From a random AI dust bin of wisdom:

    "In California, the average salary for an electronics technician is
    approximately $60,000-$66,000 annually ($29-$32 per hour) as of April
    2026, with top earners exceeding $80,000-$90,000."

    "The average salary for an electronics engineer in the U.S. is
    approximately $111,910 to $127,590 per year, according to 2024-2026
    data. Top earners can exceed $140,000 annually..."

    In other words:
    two technicians = one engineer

    People hired as techs very rarely advance to engineering positions.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Well, apart from Jim Williams of LTC and Errol Dietz, who started out as
    Bob Pease?s tech and wound up as CTO of National Semi.

    Cheers

    Phil Hobbs

    I met Jim once at the Foothill Flea Market. He was very reserved, very
    shy, but shared my affection for the old Tek 500-series scopes.

    His two books on analog design are wonderful.

    You can see from his schematics the lack of cademic engineering,
    especially control theory. He was very intuitive.

    Jim and Pease died about the same time.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, April 12, 2026 19:19:38
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash - >>>>>>> it is total incompetence. It makes it perfectly obvious why you needed >>>>>>> to Dremel the copper on the board to minimise the impedance mis-match. >>>>>>
    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You can put >>>>> through mixed signal D-type connectors too. Just to add high end appeal >>>>> we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal >>>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth >>>>> as the top and bottom layers of our six-kayer board and that was back in >>>>> 1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive - >>> the printed circuit house had had to buy quite a large minimum chunk of >>> the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the
    dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    The deconvolution thing is one of the mathematically "ill-posed
    problems." Which makes it fun to play with.

    I can't see glass weaves in a 20 GHz TDR on a cheap FR4 board.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, April 13, 2026 17:01:35
    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash - >>>>>>>> it is total incompetence. It makes it perfectly obvious why you needed >>>>>>>> to Dremel the copper on the board to minimise the impedance mis-match. >>>>>>>
    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and >>>>>> routed coax cable through a mixed signal 41812 connector. You can put >>>>>> through mixed signal D-type connectors too. Just to add high end appeal >>>>>> we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal >>>>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth >>>>>> as the top and bottom layers of our six-kayer board and that was back in >>>>>> 1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive - >>>> the printed circuit house had had to buy quite a large minimum chunk of >>>> the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible. >>>>> Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late >>>> 1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the
    dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be
    higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    The deconvolution thing is one of the mathematically "ill-posed
    problems." Which makes it fun to play with.

    Deluded nonsense.

    I can't see glass weaves in a 20 GHz TDR on a cheap FR4 board.

    The wavelength of a a 20GHz signal in FR4 is about 1cm. The weave in the
    glass fibre cloth is at about 1mm. It won't be all that obvious -
    perhaps more so if you hit an exact multiple of period of the weave, and
    your board turns into a diffraction grating.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Gerhard Hoffmann@3:633/10 to All on Monday, April 13, 2026 09:55:58
    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to
    the chief engineer and told him what you had done wrong, so that the
    knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs
    to have information passed back up to them, so they can make informed
    decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more
    informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge
    from A to B.

    Gerhard

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Gerhard Hoffmann@3:633/10 to All on Monday, April 13, 2026 10:07:30
    Am 13.04.26 um 04:10 schrieb john larkin:

    ........

    Jim and Pease died about the same time.


    Didn't Pease die in a car accident in his VW Bully
    on the way home from Jim's funeral?

    Even weirder, he had written a publication on how to
    avoid car accidents, IIRC.

    Gerhard

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Gerhard Hoffmann@3:633/10 to All on Monday, April 13, 2026 10:14:31
    Am 13.04.26 um 10:07 schrieb Gerhard Hoffmann:
    Pease die in a car accident

    Ah, Google knows the incident.
    And it was a Beetle, not the small bus.

    from there:
    <
    https://www.edn.com/analog-engineering-legend-bob-pease-killed-in-car-crash/
    >

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 13, 2026 01:40:17
    On Mon, 13 Apr 2026 09:55:58 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to >>>> the chief engineer and told him what you had done wrong, so that the
    knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs >>>> to have information passed back up to them, so they can make informed
    decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more
    informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with
    the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge
    from A to B.

    Gerhard

    I visited the DeLaval turbine plant and was not allowed to turn a
    trimpot on my own controller. I had to tell a union guy which way to
    turn it.

    Unions are self-destructive.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 13, 2026 01:43:20
    On Mon, 13 Apr 2026 10:14:31 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 13.04.26 um 10:07 schrieb Gerhard Hoffmann:
    Pease die in a car accident

    Ah, Google knows the incident.
    And it was a Beetle, not the small bus.

    from there:
    < >https://www.edn.com/analog-engineering-legend-bob-pease-killed-in-car-crash/


    Pease lived on Miraloma street near my house. His front yard and most
    of the parking spaces on the street were full of various rusting VWs.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Monday, April 13, 2026 09:08:56
    john larkin <jl@glen--canyon.com>wrote:
    On Mon, 13 Apr 2026 09:55:58 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to >>>>> the chief engineer and told him what you had done wrong, so that the >>>>> knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs >>>>> to have information passed back up to them, so they can make informed >>>>> decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more
    informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with >>>> the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge >>from A to B.

    Gerhard

    I visited the DeLaval turbine plant and was not allowed to turn a
    trimpot on my own controller. I had to tell a union guy which way to
    turn it.

    I was not allowed to replace a defective capacitor I located in ground equipment in ESA
    when they called me to help with trouble shooting.
    I said: Look we have that capacitor, can replace it now.
    But a whole procedure had to followed.
    Seems it was replaced as thing went OK later!
    Was a dead short coupling capacitor.

    IRC in broadcasting I have cheated by getting parts from the local electronics shop,
    things were also often time critical.
    We had a large parts store, but not always everything in stock.

    But then I also have a paper that says: 'Technician in higher electronics'
    And an other one 'NERG technician'..
    And an other one 'broadcasting engineer'
    etc etc
    That last one from the exams I did after getting a 6 month training in broadcast equipment, satellite systems, audio, video, studio management, what not
    in the school banks .. All payed for by the national network.
    Nice trip to Brussels headquarters after passing the exams, then straight to work.


    Unions are self-destructive.

    No, they protect people.


    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Gerhard Hoffmann@3:633/10 to All on Monday, April 13, 2026 11:49:49
    Am 13.04.26 um 11:08 schrieb Jan Panteltje:
    john larkin <jl@glen--canyon.com>wrote:
    On Mon, 13 Apr 2026 09:55:58 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to >>>>>> the chief engineer and told him what you had done wrong, so that the >>>>>> knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs >>>>>> to have information passed back up to them, so they can make informed >>>>>> decisions.

    If that were the only way information got passed back up to them the >>>>> firm would have foundered very rapidly. In general management doesn't >>>>> want to know and wouldn't have known what it meant if they had been >>>>> told through official channels. Unofficial channels tended to be more >>>>> informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with >>>>> the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge
    from A to B.

    Gerhard

    I visited the DeLaval turbine plant and was not allowed to turn a
    trimpot on my own controller. I had to tell a union guy which way to
    turn it.

    In my case that was not bc of unions. I did not have the annual
    exam / paperwork.


    I was not allowed to replace a defective capacitor I located in ground equipment in ESA
    when they called me to help with trouble shooting.
    I said: Look we have that capacitor, can replace it now.
    But a whole procedure had to followed.
    Seems it was replaced as thing went OK later!
    Was a dead short coupling capacitor.

    IRC in broadcasting I have cheated by getting parts from the local electronics shop,
    things were also often time critical.
    We had a large parts store, but not always everything in stock.

    But then I also have a paper that says: 'Technician in higher electronics' And an other one 'NERG technician'..
    And an other one 'broadcasting engineer'
    etc etc
    That last one from the exams I did after getting a 6 month training in broadcast equipment, satellite systems, audio, video, studio management, what not
    in the school banks .. All payed for by the national network.
    Nice trip to Brussels headquarters after passing the exams, then straight to work.


    Unions are self-destructive.

    No, they protect people.

    Sometimes, it goes over the top. In a previous life, I did sth. for a
    huge Berlin based manufacturer of photo typesetters. The engineers
    were not allowed to do their circuit drawings in Orcad STD themselves;
    that was reserved work for the technical drawing people who knew nothing
    about electronics.

    They went bust in 1993.



    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Monday, April 13, 2026 13:18:32
    Gerhard Hoffmann <dk4xp@arcor.de>wrote:
    Am 13.04.26 um 11:08 schrieb Jan Panteltje:
    john larkin <jl@glen--canyon.com>wrote:
    On Mon, 13 Apr 2026 09:55:58 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to >>>>>>> the chief engineer and told him what you had done wrong, so that the >>>>>>> knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had >>>>>> screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs >>>>>>> to have information passed back up to them, so they can make informed >>>>>>> decisions.

    If that were the only way information got passed back up to them the >>>>>> firm would have foundered very rapidly. In general management doesn't >>>>>> want to know and wouldn't have known what it meant if they had been >>>>>> told through official channels. Unofficial channels tended to be more >>>>>> informative.

    I did make a habit of talking to the service engineers from time to >>>>>> time, when they were back on-site. I didn't have to make an effort with >>>>>> the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge >>> >from A to B.

    Gerhard

    I visited the DeLaval turbine plant and was not allowed to turn a
    trimpot on my own controller. I had to tell a union guy which way to
    turn it.

    In my case that was not bc of unions. I did not have the annual
    exam / paperwork.


    I was not allowed to replace a defective capacitor I located in ground equipment in ESA
    when they called me to help with trouble shooting.
    I said: Look we have that capacitor, can replace it now.
    But a whole procedure had to followed.
    Seems it was replaced as thing went OK later!
    Was a dead short coupling capacitor.

    IRC in broadcasting I have cheated by getting parts from the local electronics shop,
    things were also often time critical.
    We had a large parts store, but not always everything in stock.

    But then I also have a paper that says: 'Technician in higher electronics' >> And an other one 'NERG technician'..
    And an other one 'broadcasting engineer'
    etc etc
    That last one from the exams I did after getting a 6 month training in broadcast equipment, satellite systems, audio, video,
    studio management, what not
    in the school banks .. All payed for by the national network.
    Nice trip to Brussels headquarters after passing the exams, then straight to work.


    Unions are self-destructive.

    No, they protect people.

    Sometimes, it goes over the top.


    I was reading this morning Lufthansa is now hit by big strikes...
    https://www.ard-text.de/mobil/109

    it will be hard for the employers to give in when airplane fuel prices are skyrocketing.

    In a previous life, I did sth. for a
    huge Berlin based manufacturer of photo typesetters. The engineers
    were not allowed to do their circuit drawings in Orcad STD themselves;
    that was reserved work for the technical drawing people who knew nothing >about electronics.
    They went bust in 1993.


    Yes, same here where I worked in The Netherlands, drawing department!
    I provided them with sketches....
    We used an external company to make the PCB layouts, some ISA card stuff back then,
    I tested the circuits on veroboard before that..
    Never a problem.
    Small boards we etched ourselves ..
    Been doing that at home too.
    In that company we worked close with IBM, their office just a mile away.

    I worked for many companies, both here and all around the world, including UK and US.
    And had my own TV repair shop in the nineties.
    That is actually where I got my first computer, a Sinclair ZX80,
    started coding!
    https://panteltje.nl/panteltje/z80/index.html
    Scans of the circuit diagrams, all build on veroboard:
    https://panteltje.nl/panteltje/z80/system14/diagrams/index.html

    I still use veroboard for all projects at home, gamma spectrometer:
    https://panteltje.nl/pub/sc2_sideview_with_probe_connection_img_3269.jpg


    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Monday, April 13, 2026 13:37:57
    Gerhard Hoffmann <dk4xp@arcor.de> wrote:
    Am 13.04.26 um 04:10 schrieb john larkin:

    ........

    Jim and Pease died about the same time.


    Yup, 2011 was a bad year for that. Jim, Bob, Tony Siegman (who posted as
    AES here and in sci.optics ), and Dennis Ritchie.


    Didn't Pease die in a car accident in his VW Bully
    on the way home from Jim's funeral?

    He was still on the property iirc.


    Even weirder, he had written a publication on how to
    avoid car accidents, IIRC.

    A really turgid book on avoiding car accidents, unfortunately (I bought a
    copy and threw it away.)

    Then he died by driving the least crashworthy car in memory into a tree.

    A good guy. May God keep him in memory eternal.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 13, 2026 07:10:38
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>> routed coax cable through a mixed signal 41812 connector. You can put >>>>>>> through mixed signal D-type connectors too. Just to add high end appeal >>>>>>> we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal >>>>>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth >>>>>>> as the top and bottom layers of our six-kayer board and that was back in
    1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive - >>>>> the printed circuit house had had to buy quite a large minimum chunk of >>>>> the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible. >>>>>> Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late >>>>> 1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the >>>>> dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder. >>>>
    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be
    higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Monday, April 13, 2026 11:17:46
    On Mon, 13 Apr 2026 10:07:30 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 13.04.26 um 04:10 schrieb john larkin:

    ........

    Jim and Pease died about the same time.


    Didn't Pease die in a car accident in his VW Bully
    on the way home from Jim's funeral?

    Yes, a Beetle.

    Even weirder, he had written a publication on how to
    avoid car accidents, IIRC.

    He did at that, and I read it. Bought it directly from Pease at a
    lecture in the Boston area.

    He was very big on wearing seat belts, but was unbelted when he
    crashed on the way home from Jim W's funeral.

    My theory is that he drank too much fine wine at the funeral, and
    forgot to buckle up, and may have simply fallen asleep while driving
    home.

    Joe

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 14, 2026 02:40:23
    On 13/04/2026 6:40 pm, john larkin wrote:
    On Mon, 13 Apr 2026 09:55:58 +0200, Gerhard Hoffmann <dk4xp@arcor.de>
    wrote:

    Am 12.04.26 um 13:39 schrieb john larkin:
    On Sun, 12 Apr 2026 20:22:18 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 5:52 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:


    ...Some of my colleagues screwed up from time
    to time, and so did I, but we covered up for one another.

    Wouldn't it have been a better-organised firm if you could have gone to >>>>> the chief engineer and told him what you had done wrong, so that the >>>>> knowledge could be passed on?

    We didn't need to bother. The technicians always knew when you had
    screwed up, and the word got passed around.

    Instructions are passed down the management chain but management needs >>>>> to have information passed back up to them, so they can make informed >>>>> decisions.

    If that were the only way information got passed back up to them the
    firm would have foundered very rapidly. In general management doesn't
    want to know and wouldn't have known what it meant if they had been
    told through official channels. Unofficial channels tended to be more
    informative.

    I did make a habit of talking to the service engineers from time to
    time, when they were back on-site. I didn't have to make an effort with >>>> the technicians - they loved to gossip.

    We don't have engineering technicians. We can solder ourselves.

    I was not allowed to solder a single joint in the stuff that
    I had designed myself that went to space. Not even moving a wire bridge >>from A to B.

    Gerhard

    I visited the DeLaval turbine plant and was not allowed to turn a
    trimpot on my own controller. I had to tell a union guy which way to
    turn it.

    Unions are self-destructive.

    Far from it. But American bosses really don't like them. When I was
    briefly and minimally active as a trade union officer in the UK I got to
    hear a lot about how pathologically nervous American companies with
    British subsiduaries were about any kind of trade union activity in
    those subsiduaries. Most of the stuff I did get involved with was about restraining bureaucratic half-wits in the personnel department from
    bullying employees they didn't like. All the trade union reps did was
    push the disagreement up to the next level of management, who weren't
    all that clever either, but rational enough to recognise irrational
    behavior when it was spelled out for them.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 14, 2026 02:53:57
    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde" >>>>>>>>>>>>>>>>>>>>>>>>>>>>> <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>>> routed coax cable through a mixed signal 41812 connector. You can put >>>>>>>> through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything like ideal >>>>>>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth >>>>>>>> as the top and bottom layers of our six-kayer board and that was back in
    1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously expensive - >>>>>> the printed circuit house had had to buy quite a large minimum chunk of >>>>>> the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible. >>>>>>> Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late >>>>>> 1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the >>>>>> dielectric constant of the substrate changes along the transmission >>>>>> line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder. >>>>>
    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >>>> higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X

    You do seem to be a dummy in this area. I'm not.

    The joys of decomposing a complex repetitive signal into it's component
    sines - the discrete Fourier transform (or if you do it with the minimum
    of arithmetic effort, the fast fourier transform) aren't unknown to me.

    Equalisation is just boosting and shifting the components that have been
    been attenuated and delayed. If you printed circuit board introduces lot
    a of random and frequency dependent little delays it's not easy to find
    the correct correction function.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 14, 2026 03:47:59
    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org> wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote:
    On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote:
    On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote:
    On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote:
    On Thu, 9 Apr 2026 00:00:38 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote:
    On Wed, 8 Apr 2026 16:36:08 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote:
    On Mon, 6 Apr 2026 15:23:01 -0400,
    "Edward Rawde"
    <invalid@invalid.invalid> wrote:
    "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote:
    "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote:
    "john larkin" <jl@glen--canyon.com>
    wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why
    you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions?

    We didn't try. We put SMA sockets on the printed circuit board and
    routed coax cable through a mixed signal 41812 connector. You
    can put
    through mixed signal D-type connectors too. Just to add high
    end appeal
    we used semi-rigid coaxial cable to link everything together

    The final tweaks result from real PCBs not being anything
    like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded
    Teflon cloth
    as the top and bottom layers of our six-kayer board and that
    was back in
    1986.

    That might take two months and cost a few hundred times as much.

    It didn't, even in the UK in 1987. The boards were hideously
    expensive -
    the printed circuit house had had to buy quite a large minimum
    chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and
    they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is
    terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in
    the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means
    that the
    dielectric constant of the substrate changes along the transmission
    line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam
    isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with
    murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be
    higher that 100,000 units per year. You don't seem to design for that
    kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions.
    Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the
    lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X

    You do seem to be a dummy in this area. I'm not.

    The joys of decomposing a complex repetitive signal into it's component
    sines waves - the discrete Fourier transform (or if you do it with the
    minimum of arithmetic effort, the fast fourier transform) aren't unknown
    to me.

    Equalisation is just boosting and shifting the components that have been
    been attenuated and delayed. If your printed circuit board introduces a
    lot a of random and frequency dependent little delays it's not easy to
    find the correct correction function.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 13, 2026 10:49:55
    On Tue, 14 Apr 2026 02:53:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>>>> routed coax cable through a mixed signal 41812 connector. You can put
    through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together >>>>>>>>>>
    The final tweaks result from real PCBs not being anything like ideal >>>>>>>>>> physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth
    as the top and bottom layers of our six-kayer board and that was back in
    1986.

    That might take two months and cost a few hundred times as much. >>>>>>>
    It didn't, even in the UK in 1987. The boards were hideously expensive -
    the printed circuit house had had to buy quite a large minimum chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible. >>>>>>>> Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in the late >>>>>>> 1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the >>>>>>> dielectric constant of the substrate changes along the transmission >>>>>>> line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder. >>>>>>
    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >>>>> higher that 100,000 units per year. You don't seem to design for that >>>>> kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions. >>>>>> Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the >>>>> lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X

    You do seem to be a dummy in this area. I'm not.

    The joys of decomposing a complex repetitive signal into it's component >sines - the discrete Fourier transform (or if you do it with the minimum
    of arithmetic effort, the fast fourier transform) aren't unknown to me.

    Equalisation is just boosting and shifting the components that have been >been attenuated and delayed. If you printed circuit board introduces lot
    a of random and frequency dependent little delays it's not easy to find
    the correct correction function.

    Given signal S and bad comm channel C, the product is ugly signal

    S * C.

    If you work in frequency domain, S has a complex spectrum and C has a
    complex transform and the * above is a complex multiply of the
    spectra.

    If you work in time domain (as I do) S is a waveform and C is the
    impulse response of the channel, and the * operator is convolution.

    In either case, we want an equilizer E such that

    S * C * E = S

    namely C * E = 1

    In frequency domain, you do a complex divide to calculate E, which
    genereally explodes.

    In time domain I have an iterative algorithm to get E. Iterate too
    many times and it explodes too.

    The problem is ill-posed and non-causal, which is what makes it
    interesting.

    Adaptive equalizer chips can input an unrecognizable hairball and
    output a beautiful data stream. Things like fast PCIe wouldn't work
    without adaptive equalizers.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 14, 2026 04:49:27
    On 14/04/2026 3:49 am, john larkin wrote:
    On Tue, 14 Apr 2026 02:53:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400, "Edward Rawde"
    <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org> wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com> wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't slap-dash -
    it is total incompetence. It makes it perfectly obvious why you needed
    to Dremel the copper on the board to minimise the impedance mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>>>>> routed coax cable through a mixed signal 41812 connector. You can put
    through mixed signal D-type connectors too. Just to add high end appeal
    we used semi-rigid coaxial cable to link everything together >>>>>>>>>>>
    The final tweaks result from real PCBs not being anything like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded Teflon cloth
    as the top and bottom layers of our six-kayer board and that was back in
    1986.

    That might take two months and cost a few hundred times as much. >>>>>>>>
    It didn't, even in the UK in 1987. The boards were hideously expensive -
    the printed circuit house had had to buy quite a large minimum chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is terrible. >>>>>>>>> Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency >>>>>>>> substrates, and we used couple of different ones even back in the late >>>>>>>> 1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means that the >>>>>>>> dielectric constant of the substrate changes along the transmission >>>>>>>> line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with murder. >>>>>>>
    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >>>>>> higher that 100,000 units per year. You don't seem to design for that >>>>>> kind of market, and I certainly never did. You can put in a lot of >>>>>> design effort to let you get away with cheapest possible solutions. >>>>>>> Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that. >>>>>>
    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the >>>>>> lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a >>>>> reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X >>
    You do seem to be a dummy in this area. I'm not.

    The joys of decomposing a complex repetitive signal into it's component
    sines - the discrete Fourier transform (or if you do it with the minimum
    of arithmetic effort, the fast fourier transform) aren't unknown to me.

    Equalisation is just boosting and shifting the components that have been
    been attenuated and delayed. If you printed circuit board introduces lot
    a of random and frequency dependent little delays it's not easy to find
    the correct correction function.

    Given signal S and bad comm channel C, the product is ugly signal

    S * C.

    If you work in frequency domain, S has a complex spectrum and C has a
    complex transform and the * above is a complex multiply of the
    spectra.

    If you work in time domain (as I do) S is a waveform and C is the
    impulse response of the channel, and the * operator is convolution.

    In either case, we want an equilizer E such that

    S * C * E = S

    namely C * E = 1

    In frequency domain, you do a complex divide to calculate E, which
    generally explodes.

    It doesn't "explode". Rounding error and random noise wreck the result,
    which is close enough to "explode" for all practical purposes.

    In time domain I have an iterative algorithm to get E. Iterate too
    many times and it explodes too.

    Same problem.

    The problem is ill-posed and non-causal, which is what makes it
    interesting.

    If you don't understand what you are doing, it may look "interesting"

    Adaptive equalizer chips can input an unrecognizable hairball and
    output a beautiful data stream. Things like fast PCIe wouldn't work
    without adaptive equalizers.

    Up to a point. It's a "beautiful data stream" because what you want a
    are ones and zeros at specific data rate - if the transitions between
    bits move around a bit you don't care as long as doesn't move around
    enough to turn a one into a zero

    If you want a clean result, it makes sense to make your transmission
    lines clean and simple - nice homogeneous dielectrics, rather than FR4.
    They won't be as mechanically strong or as cheap, but if you confine
    them to fast buried non-dispersive signalling layers, it can be a
    practical - if not a dirt cheap - solution.

    If you want precision timing, you need to spend the money.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, April 13, 2026 12:21:54
    On Tue, 14 Apr 2026 03:47:59 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org> wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org> >>> wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote:
    On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400,
    "Edward Rawde"
    <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r10a6$2at4a$2@dont-email.me...
    On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r0pp5$28hv3$1@dont-email.me...
    On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com>
    wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com...

    <snip>

    The E/M simulation of the un-mated half of a connector isn't
    slap-dash -
    it is total incompetence. It makes it perfectly obvious why
    you needed
    to Dremel the copper on the board to minimise the impedance
    mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>>> routed coax cable through a mixed signal 41812 connector. You
    can put
    through mixed signal D-type connectors too. Just to add high
    end appeal
    we used semi-rigid coaxial cable to link everything together >>>>>>>>>
    The final tweaks result from real PCBs not being anything
    like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded
    Teflon cloth
    as the top and bottom layers of our six-kayer board and that
    was back in
    1986.

    That might take two months and cost a few hundred times as much. >>>>>>
    It didn't, even in the UK in 1987. The boards were hideously
    expensive -
    the printed circuit house had had to buy quite a large minimum
    chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is
    terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency
    substrates, and we used couple of different ones even back in
    the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means
    that the
    dielectric constant of the substrate changes along the transmission >>>>>> line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam
    isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with
    murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >>>> higher that 100,000 units per year. You don't seem to design for that >>>> kind of market, and I certainly never did. You can put in a lot of
    design effort to let you get away with cheapest possible solutions. >>>>> Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that.

    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the >>>> lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a
    reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X

    You do seem to be a dummy in this area. I'm not.

    You are universally wonderful.


    The joys of decomposing a complex repetitive signal into it's component >sines waves - the discrete Fourier transform (or if you do it with the >minimum of arithmetic effort, the fast fourier transform) aren't unknown
    to me.

    Equalisation is just boosting and shifting the components that have been >been attenuated and delayed. If your printed circuit board introduces a
    lot a of random and frequency dependent little delays it's not easy to
    find the correct correction function.

    The frequency-domain way to calculate the equalizer is to do a complex
    divide of the equivalent FFTs. That tends to blow up with divides by
    small numbers or zeroes.

    There is a world of academic papers on how to work around the FFT
    division crisis, and they turn out to be messy and iterative and
    ill-posed too.

    As the book says, frequency domain and time domain are just ways to
    look at the same things.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, April 14, 2026 16:51:25
    On 14/04/2026 5:21 am, john larkin wrote:
    On Tue, 14 Apr 2026 03:47:59 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 14/04/2026 12:10 am, john larkin wrote:
    On Mon, 13 Apr 2026 17:01:35 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/04/2026 12:19 pm, john larkin wrote:
    On Mon, 13 Apr 2026 11:36:45 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 13/04/2026 1:01 am, john larkin wrote:
    On Sun, 12 Apr 2026 23:07:30 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 9:37 pm, john larkin wrote:
    On Sun, 12 Apr 2026 14:49:35 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 12/04/2026 2:53 am, john larkin wrote:
    On Sat, 11 Apr 2026 16:02:55 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 3:55 am, john larkin wrote:
    On Sat, 11 Apr 2026 03:05:16 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 11/04/2026 1:13 am, john larkin wrote:
    On Sat, 11 Apr 2026 00:06:40 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 7:00 pm, john larkin wrote:
    On Fri, 10 Apr 2026 16:51:21 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 11:21 am, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 03:41:39 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 2:40 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>> On Fri, 10 Apr 2026 01:55:00 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 10/04/2026 1:23 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 16:21:20 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 3:55 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 03:20:55 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:
    On 9/04/2026 2:36 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 9 Apr 2026 00:00:38 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 10:52 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 8 Apr 2026 16:36:08 +1000, Bill
    Sloman <bill.sloman@ieee.org>
    wrote:
    On 8/04/2026 4:39 am, john larkin wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 6 Apr 2026 15:23:01 -0400,
    "Edward Rawde"
    <invalid@invalid.invalid> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r10a6$2at4a$2@dont-email.me... >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 7/04/2026 3:32 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Bill Sloman" <bill.sloman@ieee.org>
    wrote in message news:10r0pp5$28hv3$1@dont-email.me... >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 7/04/2026 2:30 am, Edward Rawde wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "john larkin" <jl@glen--canyon.com>
    wrote in message news:o2i7tk5q0b453cv1ag9jq0ec787n8lu9iu@4ax.com... >>>>>>>>>>
    <snip>

    The E/M simulation of the un-mated half of a connector isn't
    slap-dash -
    it is total incompetence. It makes it perfectly obvious why
    you needed
    to Dremel the copper on the board to minimise the impedance
    mis-match.

    Right, except that it works.

    To your complete satisfaction.

    How did you design wideband SMA to PCB edge-launch transitions? >>>>>>>>>>
    We didn't try. We put SMA sockets on the printed circuit board and >>>>>>>>>> routed coax cable through a mixed signal 41812 connector. You
    can put
    through mixed signal D-type connectors too. Just to add high
    end appeal
    we used semi-rigid coaxial cable to link everything together >>>>>>>>>>>
    The final tweaks result from real PCBs not being anything
    like ideal
    physics models. Affordable FR4 is a wideband mess.

    So why use FR4? We put in two layers of isocyanate bonded
    Teflon cloth
    as the top and bottom layers of our six-kayer board and that
    was back in
    1986.

    That might take two months and cost a few hundred times as much. >>>>>>>>
    It didn't, even in the UK in 1987. The boards were hideously
    expensive -
    the printed circuit house had had to buy quite a large minimum
    chunk of
    the isocyanate bonded Teflon cloth substrate to make our boards, and >>>>>>>> they got the money back over of a handful of boards

    This isn't bad at all, for a $2 JLC board.

    <snipped uninformative pictures>

    One problem with teflon lams is that the copper adhesion is
    terrible.
    Vias can be flakey too.

    Ours were fine. Nowadays there a whole range of high frequency >>>>>>>> substrates, and we used couple of different ones even back in
    the late
    1980's.

    Some of the rigid Isola materials are better,
    if you really need a low-loss dielectric.

    It's not just the low-loss. The glass-fibre mat in FR4 means
    that the
    dielectric constant of the substrate changes along the transmission >>>>>>>> line, and that generate small reflections.

    For short traces sending logic levels around, an exotic lam
    isn't worth it.
    Even crazy fast PCIe is done on FR4.

    Keep the specification sloppy enough and you can get away with
    murder.

    You think the PCIe spec is sloppy?

    It's a mass market product, and the production volumes are going to be >>>>>> higher that 100,000 units per year. You don't seem to design for that >>>>>> kind of market, and I certainly never did. You can put in a lot of >>>>>> design effort to let you get away with cheapest possible solutions. >>>>>>> Use something else in your PC.

    Why would I? It's a cheap mass market product, and it works.
    If I needed something better - and could afford it - I'd buy that. >>>>>>
    If you need good performance, you have to take more care.

    Or adaptive equalization.

    Adaptive equalisation won't get rid of the small reflections from the >>>>>> lumps of glass fibre in FR4.

    Of course it will.

    Given a linearly distorted signal without too much noise, there is a >>>>> reciprocal function that undoes the distortion. It's "the
    deconvolution problem" to find that reciprocal function.

    Word salad.

    Here ya go:

    https://www.amazon.com/Signals-Systems-Dummies-Mark-Wickert/dp/111847581X >>
    You do seem to be a dummy in this area. I'm not.

    You are universally wonderful.

    There a long gap between "not being a dummy in a specific area" and
    being universally wonderful (which is not a state mere humans can
    attain). These discussions are more like Dr. Johnson's "Sir, there is no settling the point of precedency between a louse and a flea".
    Since you do make more money out of selling your electronic expertise
    than I do, you must be the more effective blood sucker.

    The joys of decomposing a complex repetitive signal into it's component
    sines waves - the discrete Fourier transform (or if you do it with the
    minimum of arithmetic effort, the fast fourier transform) aren't unknown
    to me.

    Equalisation is just boosting and shifting the components that have been
    been attenuated and delayed. If your printed circuit board introduces a
    lot a of random and frequency dependent little delays it's not easy to
    find the correct correction function.

    The frequency-domain way to calculate the equalizer is to do a complex
    divide of the equivalent FFTs. That tends to blow up with divides by
    small numbers or zeroes.

    Effectively you have to invert a matrix, and if your matrix is ill-conditioned, most of the entries in your inverted matrix are
    excessively sensitive to noise in your original observations (which can
    be rounding errors in your numerical representations of those observations)
    There is a world of academic papers on how to work around the FFT
    division crisis, and they turn out to be messy and iterative and
    ill-posed too.

    That's one way of putting it.

    As the book says, frequency domain and time domain are just ways to
    look at the same things.

    Not the same things, but the same thing. And the book is just
    reiterating the obvious, which you do have to do when instructing
    dummies.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.14
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)