3 ms·
He doesn't mention it's a RS485 I/O card meant to fit into an CEC expansion box in a Z14 mainframe. Might be helpful terms to search if you're looking to find
by tyingq 2y ago
He doesn't mention it's a RS485 I/O card meant to fit into an CEC expansion box in a Z14 mainframe. Might be helpful terms to search if you're looking to find very similar parts...since there might be run on this one specifically. Found part number 98Y6848 looking this way, which seems like an updated (or maybe just renumbered) version of this.
- trollbridge 2y agoRS-485 is pretty much the standard to communicate with SDLC to another device. Think of this board as a serial port for a mainframe. Looks like the same card is intended for use in IBM POWER hardware too, running OS/400 or AIX (or Linux). Of course, an open question is who on earth is still using SDLC over RS-485 these days, but then again I still see new Dell servers fitted with RS-232 ports.
- MisterTea 2y agoI hope serial never goes away. It's a time tested communications interface that is simple to implement and not a patent minefield.
- evoke4908 2y agoWe've been using RS232 since 1960. I have 100% confidence that in a thousand years there will still be engineering terminals in starships emulating a VT100
- Aloha 2y agoThere will at least - in 75 years be something internally, a minimum layer of abstraction that looks a whole lot like VT100 escape codes in a character stream. It's probably one of the stickiest API's that I can think of.
- numpad0 2y agoRS-232/422/485 are better than surprise USB-C port that require outdated specific Rust compilers and random 32bit ARM binary and an archive.org copy of random repository along cryptic code comments in it to make it work. Obsoleting RS-* ports could very well trigger that event.
- f_devd 2y agoWhat is this a reference to? I'm guessing an rlib was required without them considering ABI stablility, but I can't figure out the rest.
- anyfoo 2y agoThe problem though is that while serial is indeed much more commonplace than you might think (look at any device in your household, chances are high that it contains at least one internal serial port that was used for development), it’s all 3.3V or less with no negative voltages now. We don’t really use the RS-232 physical interface much anymore, it’s very unwieldy. (We also seldomly connect anything but the tx and rx lines, which is a bit of a shame for flow control, but often sufficient for what the ports are actually used for.) So if you interface with those “modern” incarnations of serial ports today, your built in RS-232 COM port is useless most of the time anyway, and you already resort to a small, cheap USB serial adapter board that does the same thing at nowadays non-insane signal levels.
- trollbridge 2y agoMy favourite is connecting to some piece of embedded hardware’s USB service port and finding it’s a bog standard FTDI chipset… complete with the vendor’s drivers being a repackaged version of ftdibus.sys And for even more fun, multiple vendors with multiple, incompatible versions of the FTDI drivers required.