The configuration at P08:
haspp08: p08/ads/sps2 192.168.34.164 haspp08sltvh.desy.de p08/slt/exp.03 p08/ads/sps2 chan 0 slt2hleft p08/slt/exp.04 p08/ads/sps2 chan 1 slt2hright p08/slt/exp.05 p08/ads/sps2 chan 2 slt2vgap p08/slt/exp.06 p08/ads/sps2 chan 3 slt2voffs haspp09: p09/slt/exp.07 p09/ads/sps1 chan 0 slt1vgap (used by P08) p09/slt/exp.08 p09/ads/sps1 chan 1 slt1voffs (used by P08)
At P08 and P09 we have the situation that the 192.168.34.163 PLC controls 4 axes which move 2 slits of different beamlines. The way how we deal with it is to define all 4 channels of 192.168.34.163 on haspp09 and refer to p09/slt/exp.07 and p09/slt/exp.08 in haspp08:/online_dir/online.xml. Likewise the file haspp09:/online_dir/online.xml ignores p09/slt/exp.07 and p09/slt/exp.08.
Here is the interesting part of haspp08:/online_dir/online.xml. Notice how slt1vgap and slt1voffs are to device servers that run on haspp09.
<device> <name>slt1vgap</name> <type>stepping_motor</type> <module>spk</module> <device>p09/slt/exp.07</device> <control>tango</control> <hostname>haspp09:10000</hostname> </device> <device> <name>slt1voffs</name> <type>stepping_motor</type> <module>spk</module> <device>p09/slt/exp.08</device> <control>tango</control> <hostname>haspp09:10000</hostname> </device> <device> <name>slt2left</name> <type>stepping_motor</type> <module>spk</module> <device>p08/slt/exp.03</device> <control>tango</control> <hostname>haspp08:10000</hostname> </device> <device> <name>slt2right</name> <type>stepping_motor</type> <module>spk</module> <device>p08/slt/exp.04</device> <control>tango</control> <hostname>haspp08:10000</hostname> </device> <device> <name>slt2vgap</name> <type>stepping_motor</type> <module>spk</module> <device>p08/slt/exp.05</device> <control>tango</control> <hostname>haspp08:10000</hostname> </device> <device> <name>slt2offs</name> <type>stepping_motor</type> <module>spk</module> <device>p08/slt/exp.06</device> <control>tango</control> <hostname>haspp08:10000</hostname> </device>