OAC server talks to UMACs for motor control in Potsdam AGWs, but not for MODS.
azcamserver.mountain.lbto.org for reading CCD images. azcamserver gets the images from the PCI fiber interface on agw#-cam.mountain.lbto.org (# is the agw number 1, 2, 3, 4, 7, 8) and mods#-cam.mountain.lbto.org (# is the MODS number 1, 2). (Beware: azcamserver software runs on the local machines for PEPSI AGWs, and not on azcamserver.mountain.lbto.org.)
How things mashup
GCS (Guiding Control Subsystem) talks to oac (oacserver) and to azcamserver
OAC server commands the UMACs -> probes (home, x/y position etc)
azcamserver talks to the other agw#-cam & mods#-cam, which are connected to the WFS and Guider camera controllers via direct fiber link and get the actual data.