Hi Mark,
Just a separate suggestion, while we’re on the subject of Windows serial port naming.
I wondered if it might be appropriate to provide ‘translation’ from /dev/ttyS<n> to \\.\COM<n+1>, in order to hide the operating system dependency?
Thanks,
Peter.
The code in question is in the Windows-specific driver file (drvAsynSerialPortWin32.c), so it is already Windows-specific. We are not adding OS-specific code
to a generic driver.
I don’t like users having to put 6 backslash characters into the device name, where everywhere else in Windows they just say COM10.
I agree with Peter’s suggestion that we don’t need a special case for COM1-COM9.
I propose the following:
-
If the device name passed to drvAsynSerialPortConfigure starts with ‘\’ then assume the user has used a device name, and use it directly.
-
If the device name does not begin with ‘\’ then prepend “\\.\”.
Mark
I’m not convinced that burying windows-specific code like that into the configure command is a good idea.
What’s so hard about just noting in the documentation that COM ports above 9 require special naming — and since the IOC shell treats backslashes separately:
That may depend on which version of asyn you are using. The upcoming R4-27 release contains the following in the release notes:
*******************************************
Fix to automatically prefix COM port names larger than COM9 (e.g. COM10, COM11, etc.) with "\.\". This is needed for all ports except COM1-COM9. Thanks to Freddie Akeroyd for this fix.
*******************************************
If you are running the master branch from github you already have this fix. If not then I think you can work around the problem by using the full path name to the port when you open it, i.e. \\.\COM10.
