-
Notifications
You must be signed in to change notification settings - Fork 73
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
Incompatibility with baudrate-less serial drivers on Windows #137
Comments
There is already a "dev" gensio that I believe does what you want. So instead of serialdev, use dev. |
Using dev instead produces the same error. It looks like the DCB configuration is overconstraining the driver causing it to error out.
|
Hmm. If you use dev, it shouldn't be calling that code. It seems that the device is advertising itself as a serial port, and that the windows code I have here is just trusting it; the information about whether it's "dev" or "serialdev" is not passed in. Fortunately, that can be solved pretty easily. |
Ok, I have pushed up a patch to the gensio repository that should solve this. Unfortunately, I cannot ultimately test it, as I don't have any hardware like that. Can you give it a try? |
Any news on this? I'd like to get a release out for a different issue, but I'd like to make sure this is fixed, too. |
Sorry I don't have the compilation setup right know so I won't be able to test it. I went developing an alternative using Golang and https://github.com/bugst/go-serial I can try a prerelease or the release you want to publish. |
Ok, I went ahead and did a release of gensio 2.8.12 and ser2net 4.6.4. If you could test it, that would be great. I think I got everything, but I can't test and be sure. Sorry this didn't work out of the box for you. |
Like explained here for another software, some drivers requires that no baudrate is set for the serial port, otherwise the driver can crash an output an error, and ser2net is not usable.
Here is the error from the underlying gensio:
This is the case for ublox F9x devices when using the integrated USB interface.
Proposed solution : allow to set the baudrate to None to be compatible with those specific drivers.
The text was updated successfully, but these errors were encountered: