Protoconv (as of at least version 1.3.2) assumes serial devices are full duplex, and persistently reads from the device. This blocks any writes from accessing the device (at least when hardware flow control is enabled).
Some thought should probably be given to making the serial interface handling more generic/configurable, and the assumptions should be documented, and supported serial modes/physical configurations enumerated in the docs.
Currently it's unclear, and untested, if the current architecture is appropriate for non-flow-controlled half-duplex serial (2-wire rs485 for example).
Protoconv (as of at least version 1.3.2) assumes serial devices are full duplex, and persistently reads from the device. This blocks any writes from accessing the device (at least when hardware flow control is enabled).
Some thought should probably be given to making the serial interface handling more generic/configurable, and the assumptions should be documented, and supported serial modes/physical configurations enumerated in the docs.
Currently it's unclear, and untested, if the current architecture is appropriate for non-flow-controlled half-duplex serial (2-wire rs485 for example).