Hi Mark, Eric, Freddie,
If I understand Microsoft's documentation correctly, it is OK to specify e.g. COM1: as \\.\COM1 - I think there's no need to make a separate case for ports 1..9.
Cheers,
Peter.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Mark Rivers
Sent: 30 September 2015 13:24
To: Jack; [email protected]
Subject: RE: Serial port COM10: not work?
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.
Mark
From: [email protected] [[email protected]] on behalf of Jack [[email protected]]
Sent: Wednesday, September 30, 2015 4:50 AM
To: [email protected]
Subject: Re: Serial port COM10: not work?
Hi Peter,
I'm using asyn/stream with ports 10 and 11 without troubles.
HTH,
-Mauro
On 9/29/2015 8:04 PM, Heesterman, Peter J wrote:
<!--
@font-face
{font-family:"MS Mincho"}
@font-face
{font-family:"MS Mincho"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
-->
Hi,
The devices (pump controllers) are named TT01, TT02, TT03, TT04, NT07 and NT10, respectively.
These were attached to COM1, COM2, COM3, COM4, COM7 and COM10 (only in the interests of matching the number scheme, above).
When I installed the software, the first five worked perfectly.
But the last one was unable to connect.
On a hunch, we re-mapped the last comport to COM8:, in the operating system.
Now all 6 work perfectly.
I wondered if there is a single-numeric-digit constraint, on the serial port number?
Thanks,
Peter.
--
________________________________________________________________________
Mauro Giacchini
Controls System Specialist
Istituto Nazionale di Fisica Nucleare - Laboratori Nazionali di Legnaro V.le dell'Universita', 2
35020 LEGNARO (PD) - ITALY
Phone: +39.049.8068558
EPICS _at_ LNL http://www.lnl.infn.it/~epics/
...the first EPICS installation to the project SPES realized from the scratch in ITALY is in production since begin 2010!!
________________________________________________________________________
This email has been checked for viruses by Avast antivirus software.
www.avast.com
- References:
- Serial port COM10: not work? Heesterman, Peter J
- Re: Serial port COM10: not work? Jack
- RE: Serial port COM10: not work? Mark Rivers
- Navigate by Date:
- Prev:
Re: Serial port COM10: not work? Eric Norum
- Next:
RE: Serial port COM10: not work? Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Serial port COM10: not work? Mark Rivers
- Next:
caQtDM new major version Mezger Anton Christian (PSI)
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|