D
damianmandan
During my tests with SerialPort component I discovered that setting
RtsEnable to new value causes a series of IOCTLs to the driver. I
suppose that a DCB is read, modified and set.
That is somewhat complicated and for the MS Com (serial.sys) driver
little too much: BeginWrite/EndWrite stops to work due to the driver
holding the output.
A lightweight EscapeCommFunction would server my purpose much better. Is
there a way to use it? (I used this with C++ and it works fine in
similar application).
Background: while sending data via the port I change the RTS pin. I use
a loop back connector so I can check the reaction on that change (CTS)
during heavy load. Setting the Rts (probably in this implementation DCB
with baud rate, Handflow, Chars and so on -> PortMon) causes the data
sending to stop after short while. After closing port a reopen is
impossible. Only Disable/Enable port with Device Manager can make it
available again.
Any suggestion?
Damian
RtsEnable to new value causes a series of IOCTLs to the driver. I
suppose that a DCB is read, modified and set.
That is somewhat complicated and for the MS Com (serial.sys) driver
little too much: BeginWrite/EndWrite stops to work due to the driver
holding the output.
A lightweight EscapeCommFunction would server my purpose much better. Is
there a way to use it? (I used this with C++ and it works fine in
similar application).
Background: while sending data via the port I change the RTS pin. I use
a loop back connector so I can check the reaction on that change (CTS)
during heavy load. Setting the Rts (probably in this implementation DCB
with baud rate, Handflow, Chars and so on -> PortMon) causes the data
sending to stop after short while. After closing port a reopen is
impossible. Only Disable/Enable port with Device Manager can make it
available again.
Any suggestion?
Damian