We had the best luck with the Keyspan USA-19HS adapters, but there is just some programming software out there that can't fathom a port not named COM1 at $3F8 or COM2 at $2F8. I worked in that industry for a while as well. Most of the time on newer equipment they work fine, if your serial device is expecting to see all of the older handshaking business that happened with serial than it may not work correctly. The only time I have ever experienced any issues was when I was dealing with very dedicated machinery (like a Allen-Bradley PLC, or a old Simplex fire alarm system). The virtual serial port name /dev/cu.UC-232AC was created and this port name needed to be defined in our software.Īdditionally we found we had to do a kextload command.Most of the time they work just fine. This is described in their documentation. The SIIG required two drivers to be installed in macOS in order for the serial port to be fully functional. User reported they used the port name cu.USA19Hfd13P1.1 in our software.Ī customer reported that using a serial to USB adaptor that used the FTDI FT232R chip created a device name of tty.usbserial-A104PFUI. The Keyspan macOS driver creates a virtual serial port as per the example below: This section documents any information we have about the use of these adapters.
With a virtual serial port you should be able to test all is working as described in our troubleshooting article.
These adapters allow a serial device to be plugged into a USB port and a driver is used to created a 'virtual' serial port in the system that can be defined and used as though it was a real serial port. Most modern systems do not come with serial (RS232) ports so in order to use serial touch devices in these cases you'll need to use a USB to serial adapter.
0 kommentar(er)
