Experimental Physics and Industrial Control System
I have a simple Ethernet network.
Let's say that I have 2 computers on the same network link (no gateway).
I run several IOCs on both computers.
For IOC#1 on cpu#1, I set
EPICS_CA_SERVER_PORT=5066
EPICS_CA_REPEATER_PORT=5067
For IOC#2 on cpu#1, I set
EPICS_CA_SERVER_PORT=5068
EPICS_CA_REPEATER_PORT=5067 ? <- same for all IOC running on this cpu
For IOC#1 on CPU#2, I set
EPICS_CA_SERVER_PORT=5070
EPICS_CA_REPEATER_PORT=5069
For IOC#2 on CPU#2, I set
EPICS_CA_SERVER_PORT=5071
EPICS_CA_REPEATER_PORT=5069
and on my OPI
EPICS_CA_AUTO_ADDR_LIST=NO
EPICS_CA_ADDR_LIST="cpu#1:5067 cpu#2:5069"
<- i.e. ADD_LIST link to repeater instead of individual server ports?
How are IOCs aware of the presence of PVS in other IOCs?
Can I use records to link IOCs between each other (ex
sequencer/fanout/dfanout/etc. records that interact with PVS from
separated IOCs)?
Thanks for your input,
--
Emmanuel Mayssat
Cell: 650/793-0626
Lyncean Technologies, Inc.
"See the invisible"
- Replies:
- RE: EPICs repeater, beacon,address list, and server port Jeff Hill
- Navigate by Date:
- Prev:
RE: Sequencer intro needed ! Emmanuel Mayssat
- Next:
RE: EPICs repeater, beacon,address list, and server port Jeff Hill
- 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: Floating point exception running ArchiveEngine Kay-Uwe Kasemir
- Next:
RE: EPICs repeater, beacon,address list, and server port Jeff Hill
- 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