Closed jwoodwardtfx closed 8 years ago
Thanks for the bug report. Clearly a regression from 1.x. Can you let me know what chipset you use and if it's easily available for my own testing?
It's a USB cellular modem (u-blox TOBY L210) that enumerates as a number of COM ports.
Probably not easy to get hold of for you to test, but if you have any changes you want me to try then just let me know...
That sounds a lot like the issue I had back along... Try opening direct
Can you try applying this patch if this fixes your problem? I don't have my equipment with me to test.
0001-Fix-exception-on-Windows-for-serial-drivers-that-don.patch.txt
Yep, that fixes it (it's the same as the fix I've made locally :p).
Thanks.
When calling SerialPortStream.cs:Open() on a serial port whose driver does not support clearing the serial break state an exception is generated and the port cannot be opened.
There is an attempt to catch this exception when setting the "BreakState" in SerialPortStream.cs:Open() but the exception is actually first generated before this point by the call to "m_NativeSerial.SetPortSettings()" (towards the end of this function the break state is set or cleared, causing the exception to be generated).