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=UNOFFICIAL]
From: "BUTTON, David" <dbu@ansto.gov.au>
To: Carsten Winkler <carsten.winkler@helmholtz-berlin.de>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 6 Nov 2013 13:41:53 +0000
Hello Carsten,   

Thank you for your reply. Could you please confirm for me that this is done by adding the environment variable to windows via the Windows Advance System Properties > Environment Variables, or is there another configuration file located somewhere that the CALab vi's refer to?

I have also got the extra problem that there are PV's on different IOC's which I want to access but they have all been setup to different ports.  Can you list multiple ports, or do you have to manipulate the variable dynamically in code to change the port number for each IOC?

Kind Regards,

David

From: Carsten Winkler [carsten.winkler@helmholtz-berlin.de]
Sent: Wednesday, 6 November 2013 7:05 PM
To: BUTTON, David; tech-talk@aps.anl.gov
Subject: Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNCLASSIFIED:For-Official-Use-Only]

Hello Dave,

please set the environment variable EPICS_CA_SERVER_PORT for all systems with running CA Lab clients and they will connect.
You're right, CA Lab runs only on Windows and Linux PCs but not on real-time controllers.
God luck with the EPICS IO Server.

Regards,
Carsten

Am 06.11.2013 08:26, schrieb BUTTON, David:

Hello,

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.

Thanks in advance,

Dave





Helmholtz-Zentrum Berlin für Materialien und Energie GmbH

Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.

Aufsichtsrat: Vorsitzender Prof. Dr. Dr. h.c. mult. Joachim Treusch, stv. Vorsitzende Dr. Beatrix Vierkorn-Rudolph
Geschäftsführung: Prof. Dr. Anke Rita Kaysser-Pyzalla, Thomas Frederking

Sitz Berlin, AG Charlottenburg, 89 HRB 5583

Postadresse:
Hahn-Meitner-Platz 1
D-14109 Berlin

http://www.helmholtz-berlin.de

Replies:
Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNOFFICIAL] Martin L. Smith

Navigate by Date:
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] Martin L. Smith
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] Andrew Johnson
Next: Re: LabVIEW EPICS Communication on ports other than 5064? [SEC=UNOFFICIAL] Martin L. Smith
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 ·