EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: Windows EPICS problem
From: "Jeff Hill" <[email protected]>
To: "'Andrew Johnson'" <[email protected]>, "'Mark Rivers'" <[email protected]>
Cc: "'EPICS tech-talk'" <[email protected]>
Date: Thu, 10 Apr 2008 08:36:28 -0600
Hi Mark,

I am also surprised by this behavior.

There is probably something going on with the routing tables. 

I would type "route print" into a dos box to find out what up. The
"ipconfig" command is also useful on windows.

Jeff

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Andrew Johnson
> Sent: Wednesday, April 09, 2008 8:11 AM
> To: Mark Rivers
> Cc: EPICS tech-talk
> Subject: Re: Windows EPICS problem
> 
> Hi Mark,
> 
> Mark Rivers wrote:
> >
> > - CA clients on that Windows machine can see PVs on all other machines
> >  on the network
> > - CA clients on other machines on the network can see PVs on the
> >  Windows machine
> >
> > So the problem is only that local Windows clients can not see the PVs
> >  from a soft IOC running on the same computer.  This is only happening
> >  on this computer, not other Windows computers running the same IOC
> >  binary. (They are not running at the same time, so it is not a
> >  duplicate PV name problem).
> >
> > None of the EPICS environment variables are set except:
> > EPICS_CA_MAX_ARRAY_BYTES=10000000
> > EPICS_DISPLAY_PATH=P:/epics/adl
> >
> > The Windows Firewall is not running, nor is any other firewall that I
> >  am aware of.
> 
> Very strange.  Have you tried setting EPICS_CA_ADDR_LIST to localhost
> (127.0.0.1) or even the PC's own IP address (which of course may change
> for your demo) to force it to search itself?
> 
> My guess is it's probably something to do with DLL versions somewhere
> since the problem is only on this machine - do you have two versions of
> ca.dll installed, maybe one from Win32 extensions and another that came
> with the IOC code?
> 
> - Andrew
> --
> When a distinguished but elderly scientist states that something is
> possible, he is almost certainly right.  When he states that something
> is impossible, he is very probably wrong.  -- Arthur C. Clarke


References:
Windows EPICS problem Mark Rivers
Re: Windows EPICS problem Andrew Johnson

Navigate by Date:
Prev: Re: MEDM CA Exception Limit Emmanuel Mayssat
Next: RE: MEDM CA Exception Limit Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Device support for Keyence LK-G CCD Laser Displacement Sensor Kurt Goetze
Next: RE: Windows EPICS problem Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·