Len,
Type "ping <CPU2's IP>, 10" on CPU1. If you don't get
a response then there are low level problems with cabling,
hubs, switches, arp, routes, etc. You can look at the routes
by typing routeShow if you are familiar with this sort of thing.
The routes on your sun can be seen for comparison purposes
with "netstat -r". Your network sysadmin should be able to
assist with this type of trouble.
Type ifShow on your CPU1. Verify that the broadcast
address listed for the LAN (not the loopback) interface
matches what you see with "netstat -i" on your Sun.
Next type "casr 2". You should see the above broadcast address
in the CA address list diagnostic. If not, then your CA
configuration is wrong or your version of EPICS is not
compatible with Tornado II (the WRS SENS IP kernel).
I believe that R3.13.3 _is_ compatible with Tornado 2.
If the above check out ok then let me know and I will
send you some additional diagnostics to try.
Jeff
> -----Original Message-----
> From: Leonard J. Reder [mailto:[email protected]]
> Sent: Friday, August 24, 2001 10:42 AM
> To: EPICS Tech-Talk
> 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
> ____________________________________________________
- Replies:
- Re: Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- References:
- Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- Navigate by Date:
- Prev:
Re: mbbiDirect/mbboDirect - why only 16 bits ? Brian McAllister
- Next:
Re: Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
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:
Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- Next:
Re: Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|