J3 is an 8P8C jack (commonly RJ45) for IEEE P802.3bz 2.5GBASE-T communications, backward compatible with Gigabit and Fast EthernetThe “what” was of course not Ethernet.
I didn't learn this until this year...
So it's really not uncommon to have manufacturers make something thing that a different company is known for. I think it's basically just luck that Molex got the credit for it
Edit: just realized you were maybe referring to the LEMO F-Series compatible connectors. Sometimes a company just designs a new connector. The F-series stuff gets used on stuff like instrumentation that may or may not be ingress protected, and has a need for extremely small size and potentially getting mated/unmated often in service. My assumption is that LEMO found that there wasn't a connector on the market that did this well, and spun up a niche.
Is Mate-n-Lok perhaps a compatible product from a competitor?
1: https://community.intel.com/cipcp26785/attachments/cipcp2678...
Like "Kleenex" means any facial tissue that is meant to be sneezed on.
(Both uses are wrong, but both also tend to promote efficient communication.)
I think "extruded" in this context comes from CAD terms, wherein: One builds the 2D cross-section of whatever complexity is entailed, and then mashes the "Extrude" button to add a third dimension to the shape.
I don't think the term, as-used, has anything at all to do with extrusion as a manufacturing process.
https://www.reddit.com/r/electronics/comments/ioc6sf/i_final...
It took a few tries to get it right, but it's amazing that PoE is even an option given how far it is outside of the scope of what the cables and connectors were designed for. I've heard of locations that use it for power, instead of 120 V outlets, because it's cheaper and safer and most portable high-current appliances use batteries, while fixed high-current appliances use 240 V outlets.
Hot plugging is always a challenge, especially with direct current, and negotiation prevents that from being a problem while making a connection, but I never considered that unplugging isn't negotiated first. I wonder if IEC has ever considered using a locking latch, like an EV charger.
I have a PoE camera that I sometimes unplug to restart it, when it freezes up and I can't restart it from the web interface. I'll be sure to turn that port off first, before unplugging it.
Right, in your average 2020s home or office, "Ethernet" is almost certainly 8P8C (commonly known as RJ-45). In decades past it was more ambiguous – in the 1990s, coax – ThinNet/10Base2 – was still reasonably common; even the older ThickNet/10Base5 would still occasionally be encountered. So to some extent, being specific is a bit of an "old timer" trait–a habit picked up decades ago when it was still important, now maintained when it is rarely still necessary.
But even in the 2020s – in a factory, it could easily be M12 instead. Or even a mix of both – 8P8C in the offices, but M12 on the factory floor.
Honestly, even in a home environment, I hate how fragile and easily unplugged 8P8C connectors are (the worst part is when they get slightly pulled out, so they still look like they are plugged in, but the connection is dead or flaky). I've thought about using M12 at home before, but it probably wouldn't be very practical.
In the 1990's they were extremely uncommon and ethernet was rare.
People had dial-up if they had anything at all and only a tiny fraction of people even had that.
Dialup internet (or any internet access at all) was uncommon but LANs were popular, and they very rarely ran IP.
IP didn’t typically come until later in the decade, when the need to share an internet connection arose.
A low to mid spec PC cost around $2000, and an NE2000 clone was around $50. RG-58 coax was about 20 cents a foot from Radio Shack.
Windows for Workgroups made the setup pretty trivial, and there was a plethora of folks out there (like me) repairing PCs and setting up LANs for small businesses.
The simple equation was that setting up a network did not look like it would make those companies money. And in the Windows for Workgroups era, running CAD on Windows was a massive performance hit.
Don’t ignore the capital cost of buying Windows versions of Cad software…potentially thousands of dollars per seat. Don’t ignore the cost of graphics cards…the high performance card might not have Windows drivers and every machine might have a different card bought at a different time.
And don’t ignore the cost of a file server that inspires confidence. In an environment where contracts are five to seven figures, the local PC repair shop is not the most enticing risk.
Your suggestion that the existence of businesses installing something is evidence the thing is uncommon, is illogical
As the other commenter pointed out already, the vast majority of Netware networks used Ethernet. I knew what Token Ring was, but I don't think I ever actually saw it, my knowledge of it was purely from books and magazines. My dad's work (a pharmaceutical manufacturing plant) was somewhat of an IBM shop in that their main computer was an AS/400 that ran the whole factory, but I interned in their IT department for two weeks in 1997 (I think I'd just turned 15) and I don't remember seeing any Token Ring, or hearing it even mentioned.
And this is the thing, I was a teenager in the 1990s, I was there. I saw Ethernet (and Acorn Econet too, which is much more obscure). I saw it at my school. I saw it at my dad's work. I remember one of my school friends had Ethernet in his house (not in the walls, they just had 2-3 computers in the family room connected to a hub/switch). I was trying to convince my dad to buy Ethernet cards but he wasn't sold on the idea–he was familiar with it from work (his field was chemistry and pharmaceutical manufacturing not computing, but he was technical enough to know what it was), but at home he was happy with Laplink. We had dial-up Internet before we had Ethernet; we had multiple computers, more than one of them had a modem, and my siblings and I would fight over who would use the dial-up since only one of us could use it at once. I remember around 1998 I was invited to a LAN party at a church, but I didn't go.
"the world were most people actually lived" is a bit meaningless, because then we are talking about what was happening in rural villages in Africa at the time. In the world in which I lived, my 1990s, Ethernet was widespread, first in school/work settings, and by the end of it, it was really taking off in home settings too. Maybe your 1990s were different from mine (different country/geography, different social milieu), or maybe you weren't actually there to experience it firsthand.
I was firmly into adulthood when they began, I worked at ordinary small businesses, and was often involved in technology purchasing decisions.
Where I was working in 1997, I set up the company’s Yahoo email…one address for the whole office which went to the receptionist’s computer. Which was fine because important communication was done by phone or fax and if you needed to reach someone out of their office you probably called their pager…though cell phones were around, most business people could not justify the expense and cell phone culture did not exist yet.
The office moved files with floppy disks via courier or USPS. Backups were to Qic tape and files moved within the office via sneaker net…cd burners were still uncommon, large, SCSI, slow, and expensive. So Zip disks were more common.
To put it another way, I spent all 10 years of the 1990’s using computers for work. It was a very different life.
I suspect your experiences were in part a product of which industry you were in, and which end of that industry - in another comment you mentioned DOS-based CAD software, in the early 1990s some big firms (especially in aerospace, defence, automotive) were still using IBM mainframe-based CAD systems running on IBM 7437s and 5080s (and if you could afford that fiendishly expensive kit, you could afford networking and likely already had it); as the 1990s progressed, mainframe-based CAD increasingly moved to UNIX workstations, for which Ethernet was very standard. And DOS-based CAD software and networking were not mutually exclusive-NetWare worked fine with DOS, and my high school had a CAD lab running the DOS version of Bentley MicroStation (IIRC, the DOS version we used was still branded Intergraph not Bentley), but all the machines were connected to Ethernet and we logged in to them using NetWare. Similarly, at my dad’s work almost all PCs ran Windows 3.x, but there were a few DOS-only machines connected to various pieces of laboratory or manufacturing equipment for which the software was DOS-only (and had issues running under a Windows 3.x DOS box) - and they connected those machines to NetWare too, because NetWare had no problem with DOS-only clients.
Token Ring was rare outside of IBM shops. Only commonly found in places like banks.
100% guilty here, ouch.
also never saw a 8P8C "keyed, real rj45" connector in person.
Why wouldn't you say RJ45?
https://www.govinfo.gov/content/pkg/CFR-2000-title47-vol3/pd...
Unfortunately, the “RJ45” part of these codes has become a metonym for the unkeyed version of the miniature eight-position jack and plug, now widely used for Ethernet and other purposes, but strictly speaking, RJ45 refers to a different connector with totally incompatible wiring.
Pedantically speaking, RJ45 (as first defined by AT&T internally[1], and later by the FCC's 47 CFR part 68) is not that. The RJ45 socket is a keyed 8P8C modular jack, not a regular 8P8C modular jack. Here is a photo: https://commons.wikimedia.org/wiki/File:RJ45_female_connecto...
[1]: The "RJ45" designation was originally an AT&T "USOC" (Universal Service Order Code). In the '70s, the FCC told AT&T that they had to allow interoperability from other companies, so the FCC had to publish a bunch of specifications; the meaning of "RJ45" became publicly specified in Bell System Communications' Technical Reference PUB 47101 "Standard Plugs And Jacks" (1979, though I think there might be an older number/revision from the early '70s that I haven't been able to track down). That (in combination with a few other technical references, such as PUB 47102), later became part of the Code of Federal Regulations, as 47 CFR part 68.
Closer is RJ38X, which is a series 8-position jack, not a normal 8-position jack. ("Series" means that the jack shorts pint 1 to pin 4 and pin 5 to pin 8 when there's not a cable plugged in to it; you would be able to fit an "Ethernet" connector into it, but even so it's probably not what you want.)
AFAICT (skimming 47 CFR part 68, and the historical AT&T documents that became 47 CFR part 68), there is no RJ-number for a normal 8-position jack.
Because of the size being different? Surely a keyed female plug will take a male connector with or without the key. Or did you mean you couldn't fit a RK45 connector into a Ethernet plug because then the key would interfere?
The regular ethernet 8P8C connector was defined by both an ANSI and ISO spec, neither of which gave the connector an actual name as it covers modular connector designs. :/
RJ11, RJ14 and RJ25 all used the same 6P housing though, making them 6P2C, 6P4C and 6P6C connectors, respectively.
Things sold as RJ11 is often 6P4C, making for another error. The rule of thumb is that anything referred to as RJ-something is likely wrong.