Richard, Patrick

Last week I found what turned out to be the cause of the issue I had with reading the pressure from the BPG402 gauges at end X when we tried to move them from h1ecatx1 to h0veex (alog 26198). It turned out that there was a type mismatch between the IO variable for the gauge pressure and the PLC variable I linked it to. The IO variable is defined as a REAL and the PLC variable I had defined as a LREAL. Last week I updated the script that generates the code to change the PLC variable to a REAL and committed it into svn. Today Richard moved the gauges back to the h0veex vacuum chassis. I did an svn update on h0veex, recreated the target code and ran it. The reading of the pressure still remained flat 0 in the system manager, but reported valid values in the IOC. I am calling this success.

I did a scan for devices, and the solar powered gauge and second fiber to ethercat converter is not seen. I disabled them in the system manager. Richard says that the fiber cable may be damaged.

The channels for these gauges still exist on h1ecatx1. The next task will be to remove these.

I also installed the necessary software to run medm on h0veex. I installed Xming-6-9-0-31 and EPICS Win32 Extensions 1.40. I also installed python-2.7.11 to generate the medm screens from a template substitution script I wrote.

I had to add the following system environment variable to get medm to run:
DISPLAY localhost:0

When medm started it gave messages for finding each process variable on both the CDS NIC and Beckhoff EtherCAT NIC. I tried adding the EPICS_CAS_INTF_ADDR_LIST system environment variable, setting it to 10.1.0.60 and restarting medm, but the same messages appeared, so I removed it. I then set the following system environment variables and restarted medm again:

EPICS_CAS_AUTO_BEACON_ADDR_LIST NO
EPICS_CAS_BEACON_ADDR_LIST 10.1.255.255

The messages changed to finding each channel on both 10.1.0.60 and h0veex (10.1.0.60 is the IP address for h0veex). I'm not sure why this is, but it seems to be working, so I am leaving it with this configuration for now.

To access the medm screens after a reboot it is currently necessary to start Xming, then start medm, then open H0_VAC_MENU_CUSTOM.adl in C:/SlowControls/TwinCAT3/Vacuum/MEDM/LHO/Target.