RS232: Difference between revisions
Jump to navigation
Jump to search
m (→rs232 over ip) |
|||
| Line 23: | Line 23: | ||
== piping to an external program == | == piping to an external program == | ||
=== linux === | |||
=== windows === | |||
== driver issues == | == driver issues == | ||
handling of DTR and RTS seems to be completely missing. rs232dev_set_status, rs232dev_get_status, rs232dev_set_bps apparently are not called by the layer above | handling of DTR and RTS seems to be completely missing. rs232dev_set_status, rs232dev_get_status, rs232dev_set_bps apparently are not called by the layer above | ||
Revision as of 18:31, 25 July 2019
here i will track some things regarding rs232 emulation, and perhaps fix things while at it Gpz (talk) 19:29, 25 July 2019 (CEST)
using a real RS232 port
linux
/dev/ttyUSB0
this worked out of the box
windows
COMx[:][baud=b][parity=p][data=d][stop=s][to={on|off}][xon={on|off}][odsr={on|off}][octs={on|off}][dtr={on|off|hs}][rts={on|off|hs|tg}][idsr={on|off}]
- finding out what COM port the usb adapter ended up might be tricky, you can use a tool like "Keyspan Serial Assistant"
rs232 over ip
linux
windows
piping to an external program
linux
windows
driver issues
handling of DTR and RTS seems to be completely missing. rs232dev_set_status, rs232dev_get_status, rs232dev_set_bps apparently are not called by the layer above