Jeff thanks so much. I think everything is ok. The ping
worked fine. The routes are all set up ok. The broadcast
address on the sun is:
hector:/home/keck/opt>/usr/sbin/ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
2
inet 137.78.170.167 netmask ffffff00 broadcast 137.78.170.255
On both VxWorks CPUs it is the same. I am running Tornado 1 kernels.
The casr 2 command returns:
btSeq>casr 2
Channel Access Server V4.8
No clients connected.
Client Name="", Client Host="", V4.0, Channel Count=0
TId=0X16836C8, Protocol=UDP, Socket FD=14
Secs since last send 64380.70, Secs since last receive 228.62
Unprocessed request bytes=0, Undelivered response bytes=0
Client's DNS Host Name histrionic:55292 State=up
32928 bytes allocated
There are currently 308320 bytes on the server's free list
7 client(s), 512 channel(s), and 512 event(s) (monitors)
The server's resource id conversion table:
Bucket entries in use = 0 bytes in use = 16404
Bucket entries/hash id - mean = 0.000000 std dev = 0.000000 max = 0
Channel Access Address List
137.78.170.255:5065
value = 20 = 0x14
It looks very much the same for the other CPU with the PMAC motor
control.
Any other suggestions are greatly appreciated.
Thanks,
Len
Jeff Hill wrote:
>
> 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
> > ____________________________________________________
--
____________________________________________________
Leonard J. Reder
Jet Propulsion Laboratory
Interferometry Systems and Technology Section 383
Email: [email protected]
Phone (Voice): 818-354-3639
____________________________________________________
- References:
- RE: Problem talking CA across two CPUs in same crate??? Jeff Hill
- Navigate by Date:
- Prev:
RE: Problem talking CA across two CPUs in same crate??? Jeff Hill
- Next:
Re: Problem talking CA across two CPUs in same crate??? Ernest L. Williams Jr.
- 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:
RE: Problem talking CA across two CPUs in same crate??? Jeff Hill
- Next:
Re: Problem talking CA across two CPUs in same crate??? Ernest L. Williams Jr.
- 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
|