Experimental Physics and
Industrial Control System

Emmanuel Mayssat <[email protected]> · Wed, 23 Aug 2006 12:44:23 -0700

Chris,

> First off, I'm no ethereal expert, but have used it in attempts to diagnose
> possible CA network problems. Any add-on or plug-in specific to CA packets
> would seem to be a great addition.

I personally do not want to be a CA network expert ;-)
But I have CA errors reported by my IOCs, I hope ethereal could help me
here.

> The reasons for these non-standard ports aside, I have a question about how 
> the CA packets will be recognized. Will it be purely based on 
> source/destination port, or some other header in the packet? If it will be

Yes, by default.
But you can decode packets coming and leaving from non default ports
with a specific protocol.
You can definitely do this through the ethereal GUI. I am not sure if it
is possible from the command line or a config file.

> based solely on ports, do you foresee the ability to customize the ports 
> associated with the CA protocol in the proposed CA ethereal plug-in?
> 
> As a side note, do other labs use non-standard CA ports, or are we on our own
> here?

I use different ports for several iocs running on same computer.
This is particularly convenient in R&D mode, where you can have 1 IOC
per connected device (or rather 1 IOC per small group of devices).
They are issues with port usage. I believe some records needs to have
linked PVs in the same IOC (IN_DBLINK? such as INP of CALC record?).

-- 
Emmanuel Mayssat
Cell: 650/793-0626
Lyncean Technologies, Inc.
"See the invisible"

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System