EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Channel Access/Linux/R3.13.7
From: "Garrett D. Rinehart" <rinehart>
To: tech-talk
Date: Mon, 2 Dec 2002 10:19:28 -0600 (CST)
I get no channel access at all. I'm running John's build on a RedHat 7.3 box. 
Network functions seem normal (ping, telnet, ssh, etc all work). I've checked 
that the CA ports 5064 and 5065 are not blocked. My linux box and iocs are all 
on a private network with no routers between them. Even setting 
"EPICS_CA_ADDR_LIST" as John mentions does nothing. Medm screens stay white. 
Tcl/tk scripts cannot connect to channels. Caget/caput commands eventually time 
out. I get no errors other than "invalid channel name" responses from 
caget/caput.

I don't even have any more ideas what to look for. If anyone has any ideas at 
all, please let me know.

Thanks.

Garrett Rinehart
Control and Data Acquisition System Manager
Accelerator Operations Group
Intense Pulsed Neutron Source
Argonne National Laboratory
9700 S. Cass Ave
Argonne, IL  60439
(630)252-6561


> Subject: Channel Access/Linux/R3.13.7
> To: 'EPICS Tech-Talk' <[email protected]>
> MIME-version: 1.0
> List-Help: <http://www.aps.anl.gov/epics/mail.php>
> 
> We are in the process of upgrading from EPICS 3.13.5 and R3.13.7.
> Everything works fine on solaris but on Linux I do not get any channel
> communication from IOCs unless I specify EPICS_CA_ADDR_LIST.  This did work
> on R3.13.5 without this specification.  My 3.13.5 distribution came from a
> tar.gz file from APS.  My 3.13.7 came directly from APS CVS.  Is there a
> difference in settings in config files that can cause this.
> 
> John Hammonds


Navigate by Date:
Prev: Re: device support routines for RS232 Garrett D. Rinehart
Next: Re: Channel Access/Linux/R3.13.7 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  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: Channel Access/Linux/R3.13.7 Andrew Johnson
Next: RE: Channel Access/Linux/R3.13.7 Garrett D. Rinehart
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·