g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

<19941995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  Index <19941995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014 
<== Date ==> <== Thread ==>

Subject: CA WAN/gateway extensions notes
From: watson@cds002.cebaf.gov
Date: Sun, 10 Apr 94 15:24:16 -0400
  
  Marty, Jeff, Bob, & John:
      Here's my notes (finally) from our discussion at LANL (blurred somewhat
  by time) on the subject of extending CA beyond a single subnet:
  
      1. Extension should support the possibility of read/write or read-only
         to remote PV's without administrative overhead (that is, it should
         be possible without having to edit a gateway PV list).
  
      2. Read-only, read/write, and no-access mix in both directions.
  
      3. (Optional -- this idea was considered not important during
         discussions) Possibility of imposing access control by a simple
         list.
  
      4. No remote subnet message for local PV's (that is, the first broadcast
         must be constrained to the local subnet if desired).
  
      5. CA able to handle one or more local networks on the first broadcast
         (needed for OPI's with multiple network interfaces)
  
      6. User configurable list of subnets or addresses, with control over
         which addresses are used in the first broadcast.
  
      7. Must be ready by June 1, preferably earlier for beta test.  (This
         constraint was requested by CEBAF to support end station to accelerator
         data exchanges during commissioning).
  
  It was agreed that 7 precludes developing a full blown name server.  Jeff's
  idea (developed by the group) was for CA to support a list of addresses
  to contact for PV's.  These addresses could be either subnet broadcast
  addresses, or IP addresses of specific IOC's.  The list would be user
  specifiable at run time (not compiled in), with a delimiter to indicate
  which addresses are used on the first try.  E.g. a list might be of the
  form:
  
  	ip1, ip2; ip3; ip4, ip5
  
  In this case, the initial broadcast is sent to ip1 and ip2.  After a timeout,
  it is sent to ip1, ip2 and ip3.  On the next timeout it would be sent to all
  five.  Other discussion also suggested that the time interval between
  retries also be run-time configurable.
  
  Just think:  you could make an OPI display which showed the up status of
  all EPICS collaboration IOC's !!!
  
  Chip

Navigate by Date:
Prev: Re: Ascii file formats and the use of EDIF watson
Next: CA WAN/gateway extensions notes mrk
Index: <19941995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014 
Navigate by Thread:
Prev: EPICS drivers for CAN and RS232 / TCP/IP Matthias Clausen DESY -MKV2/KRYK-
Next: CA WAN/gateway extensions notes mrk
Index: <19941995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·