EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: RE: Serial port COM10: not work?
From: Mark Rivers <rivers@cars.uchicago.edu>
To: "'Eric Norum'" <eric@norum.ca>
Cc: "EPICS Tech-Talk \(tech-talk@aps.anl.gov\)" <tech-talk@aps.anl.gov>
Date: Wed, 30 Sep 2015 17:31:01 +0000

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

 

 

From: Eric Norum [mailto:eric@norum.ca]
Sent: Wednesday, September 30, 2015 11:14 AM
To: Mark Rivers
Cc: EPICS Tech-Talk (tech-talk@aps.anl.gov)
Subject: Re: Serial port COM10: not work?

 

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:

            drvAsynSerialPortConfigure(“L10”, “\\\\.\\COM10”, ……..)

 

On Sep 30, 2015, at 5:24 AM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

 

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.

 

-- 
Eric Norum
eric@norum.ca




 


Replies:
Re: Serial port COM10: not work? Eric Norum
RE: Serial port COM10: not work? Heesterman, Peter J
References:
Serial port COM10: not work? Heesterman, Peter J
Re: Serial port COM10: not work? Jack
RE: Serial port COM10: not work? Mark Rivers
Re: Serial port COM10: not work? Eric Norum

Navigate by Date:
Prev: RE: Serial port COM10: not work? Heesterman, Peter J
Next: Re: Serial port COM10: not work? Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: Serial port COM10: not work? Eric Norum
Next: Re: Serial port COM10: not work? Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020