Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Fri, 24 Aug 2001 17:13:58 -0600

> Very good thank you much.  I set the EPICS_CA_ADDR_LIST variable
> in VxWorks and the PVs in the sequencer appear to be connecting.

So this mystery remains: why is the CA broadcast address
not seen by CPU2, but the CA unicast in your EPICS_CA_ADDR_LIST 
is? I am guessing that your CPU1 is sending all of its traffic 
to a router that is configured to not forward IP packets with 
a broadcast destination address. Type routeShow to see if
this is the case.

Perhaps you have the "gateway IP" set in the vxWorks boot 
parameters. This results in an odd route auto-configured by WRS
that sends all IP packets to the router even if the destination 
is on the attached LAN. This can be fixed by using the routeDelete
command followed by the routeAdd command.

Jeff

> -----Original Message-----
> From: Leonard J. Reder [mailto:[email protected]]
> Sent: Friday, August 24, 2001 4:53 PM
> To: Ernest L. Williams Jr.
> Cc: EPICS Tech-Talk
> Subject: Re: Problem talking CA across two CPUs in same crate???
> 
> 
> Very good thank you much.  I set the EPICS_CA_ADDR_LIST variable
> in VxWorks and the PVs in the sequencer appear to be connecting.
> 
> Thanks,
> 
> Len
> 
> "Ernest L. Williams Jr." wrote:
> > 
> > Hi,
> > 
> > Given that two IOCs need to talk with each other they could each  "CA
> > client" just as your SUN workstation becomes a client.
> > 
> > Now you must define for the IOC the EPICS_CA_ADDR_LIST environment variable.
> > 
> > This could be done in the resource.def file as follows:
> > # add the following line
> > EPICS_CA_ADDR_LIST      DBF_STRING     <IP Address of the IOC you want to
> > talk to>
> > 
> > OR
> > you could add a putenv statement in your st.cmd file as follows:
> > putenv (" EPICS_CA_ADDR_LIST  = <IP Address of the IOC you want to talk to>
> > ")
> > 
> > Hope this helps.
> > 
> > Thanks,
> > *******************************************
> > Ernest L. Williams Jr.
> > SNS Control Systems Group, ORNL
> > 701 Scarboro Rd., MS 6473
> > Oak Ridge, TN 37830
> > Phone 865-241-9071
> > e-mail: [email protected]
> > Fax 865-241-6739
> > ******************************************
> > ----- Original Message -----
> > From: "Leonard J. Reder" <[email protected]>
> > To: "EPICS Tech-Talk" <[email protected]>
> > Sent: Friday, August 24, 2001 12:41 PM
> > Subject: Problem talking CA across two CPUs in same crate???
> > 
> > > Hello,
> > >
> > > I am using EPICS R3.13.3 and I am using the sequencer.  There are
> > > two Motorola PPC boards in my configuration.  One of which has
> > > a sequencer within it (call it CPU1) and the other has PMAC
> > > motor control (call it CPU2).  It appears that the sequencer
> > > works fine with recorders within CPU1.  But for some reason
> > > the sequencer process variables that are associated with
> > > recorders in CPU2 cannot connect.  Both CPUs are plugged into
> > > the same network also.
> > >
> > > Are there any ideas what could be wrong with my configuration.
> > >
> > > Oh yes I can get to all the process variables via the client
> > > Sun workstation using caget, caput and camonitor calls.
> > >
> > > All replies would be greatly appreciated.
> > >
> > > Len
> > >
> > > --
> > > ____________________________________________________
> > > Leonard J. Reder
> > > Jet Propulsion Laboratory
> > > Interferometry Systems and Technology Section 383
> > > Email: [email protected]
> > > Phone (Voice): 818-354-3639
> > > ____________________________________________________
> > >
> 
> -- 
> ____________________________________________________
> Leonard J. Reder
> Jet Propulsion Laboratory
> Interferometry Systems and Technology Section 383
> Email: [email protected]
> Phone (Voice): 818-354-3639
> ____________________________________________________

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System