g+
g+ Communities
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  <20132014  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
<== Date ==> <== Thread ==>

Subject: Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNCLASSIFIED:For-Official-Use-Only]
From: Andrew Johnson <anj@aps.anl.gov>
To: "BUTTON, David" <dbu@ansto.gov.au>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 6 Nov 2013 10:46:37 -0600
Hi David,

On 11/06/2013 01:26 AM, BUTTON, David wrote:
Locally our EPICS control system has been modified so that the several
IOC servers which are running of the computer we call control have had
their EPICS_CA_SERVER_PORT variable set to values other than 5064, ie
49200 and 49212...  Needles to say that both the EPICS IO Server native
to LabVIEW is now unable to access the PV's, and likewise the CALab vi's
can no longer access them either.  I am unable to discover if there is a
way to change the "port number" so that I can get either the NI or
CALabs vi's working again. The native I/O server is important as it runs
on the real-time controllers where I believe the CA Lab vi’s can only
run on a windows application.  I am only recently started down this path
of LabVIEW EPICS communications, and would greatly appreciate input.

If you can't change those IOCs back to using port 5064 like Carsten suggested then you can tell your CA clients which ports to talk to by setting their EPICS_CA_ADDR_LIST environment variable to a space-separated list of <hostname or ip-address>:<port number> entries, for example:

setenv EPICS_CA_ADDR_LIST "ioc1:49200 192.168.70.7:49212"

Doing this will not stop the regular broadcasts to port 5064, so you only need to add the exceptions. Of course this could become a bit of a management nightmare if you keep adding exceptions so I would recommend trying to undo the port change, but it might be acceptable for a smaller system.

HTH,

- Andrew
--
Advertising may be described as the science of arresting the human
intelligence long enough to get money from it. -- Stephen Leacock

References:
LabVIEW EPICS Communication on ports other than 5064? [SEC=UNCLASSIFIED:For-Official-Use-Only] BUTTON, David

Navigate by Date:
Prev: Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNOFFICIAL] Martin L. Smith
Next: CAEN HV SY2527 : "undefined reference" for EPICS Sanguk Won
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
Navigate by Thread:
Prev: Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNCLASSIFIED:For-Official-Use-Only] Carsten Winkler
Next: RE: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNOFFICIAL] BUTTON, David
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·