Task #1142
openChange "Green monster" to use remex for communication to DAQ crates
0%
Description
In past experiments, we have used the "Green monster" tool as a slow-control interface to the DAQ crates, for instance to change the VQWK module integration settings or to mark the datastream with the scandata/cleandata words. The back-end of this was a socket-server running on each DAQ crate (cfSock) which then had sub-calls to the other VxWorks libraries to actually control the settings.
For the CODA3 Linux ROCs, Bryan recommended using the "remex" system (Remote Execution Client/Server Library). Each active ROC registers itself with the platform and the remex command run from another machine is able to access any variable or execute any function which is compiled into the ROC's active readout list.
This does make the interface a bit easier on both sides.
Paul has created a simple header-only library to support the scandata/cleandata words and tested remex communication to the VME linux ROC in the hall, moller12vme1.
The cfSock verison of "green monster" is available at /adaqfs/home/moller-onl/integrating/devices_vxwrks/PyGreenMonster on the adaq systems. We will need to make a new version that uses remex instead of using cfSock.
The beam modulation control script was built using PyGreenMonster as a starting framework, but is fully independent. We would need to go through the same sort of adaptation to use remex for it. A reference copy of teh BMod system is available at /adaqfs/home/apar/pking/PyGreenMonster_20200220
No data to display