Argonne National Laboratory

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  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017 
<== 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: Sun, 4 Oct 2015 17:32:17 +0000
> — and since the IOC shell treats backslashes separately:
> drvAsynSerialPortConfigure(“L10”, “\\\\.\\COM10”, ……..)

I just determined that your example above is not what the iocsh does.  If the string is inside quotes the iocsh does not treat backslashes separately, but without the quotes it does:

drvAsynSerialPortConfigure("L0",\\\\.\\COM1,0,0,0)
drvAsynSerialPortConfigure("L0","\\.\COM1",0,0,0)

Both of the above pass \\.\COM1 to the driver.
drvAsynSerialPortConfigure("L0","\\\\.\\COM1",0,0,0)

passes \\\\.\\COM1 to the driver.

Mark


________________________________
From: Eric Norum [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<mailto: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<UrlBlockedError.aspx>.

--
Eric Norum
eric@norum.ca<mailto:eric@norum.ca>






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? Mark Rivers
Next: RE: EPICS Collaboration Meeting Andrew C. Starritt
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017 
Navigate by Thread:
Prev: RE: Serial port COM10: not work? Mark Rivers
Next: RE: Serial port COM10: not work? Heesterman, Peter J
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·