-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Specified port, COMX, does not exist (Windows) #84
Comments
Thanks for the report, that is definitely strange. Can other serial programs (pyserial) open it when it is If you have any more information about how this might be resolved please let me know. |
I had actually tried it in pyserial just before I changed the port number and it opened it without error. It works on port numbers below COM10 and fails for everything COM10 and above. This must be some common Microsoft problem because I have seen it from other vendors in the past. Edit: For some reason for port number above 9 you must use this notation "\.\COM10". But this notation also works for ports below 9. So if you start having this problem possibly just change the constructor to append "\." to portname. |
Just a confirmation over here: bakercp/ofxSerial#5 (comment) @wjwwood Seems like the solution would be to take @anderwm 's approach and append "." in the win impl. |
what I used: learned that \ removes following char. thanks @bakercp |
fix handling of COM ports over 10 on Windows, fixes #84
I reproduced this and fixed it in #84, thanks guys! |
Just an FYI. There seems to be some port number, beyond which the Serial constructor throws a IO Exception on Windows. When my device was enumerated at COM20 (with -e in test_serial), trying to connect to it throws. When I changed to COM2 it worked as expected. I have had this problem with Windows software before so I knew to try that...I can't remember the root cause.
The text was updated successfully, but these errors were encountered: