-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect _COMMTIMEOUTS struct in serial_windows.go #7
Comments
Hi @dmnef, thanks for the report. Both COMMTIMEOUTS and SERIAL_TIMEOUTS show the same field order, with the Multipliers before the Constants. The comments on COMMTIMEOUTS did not make it any clearer. I would like to run a few tests on my Windows system to see if the fields seem to be swapped, and if so, I will make the change. |
Ok, my story: I tried to communicate with a bootloader residing in an MCU connected via standard FTDI-based USB-to-serial converter. Problem was solved by swapping mentioned fields. |
Hi @dmnef, I added For read_constant=500, read_length=10 and read_multiplier=100, I get:
...as expected. If the fields were backwards, I expect the timeout to happen at 5100ms. Could you try this example in your environment and see if you get different results? |
I tried. Got exactly same results. Sorry for misleading. Although the problem i've mentioned still exists. |
The correct field order should be like this:
See comments there: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363190%28v=vs.85%29.aspx
The text was updated successfully, but these errors were encountered: