SECI Troubleshooting - ISISComputingGroup/ibex_developers_manual GitHub Wiki
Items we wish to capture for troubleshooting SECI.
Motor stops before Limit for no Reason (has had IBEX on)
If an axis stops moving under SECI at a certain place which is not near the limits it is possible that the soft limits have got set in the controller. These can be set by IBEX so if you have swapped back from IBEX it is worth checking these.
To clear the limits:
- open the low motor table
- select tools and the motor in question
- click "clear axis limits"(approximate wording).
This should allow the motor to go the whole range.
SECI failing to start-up
There are a number of reasons as to why SECI might fail too start-up. One issue that we have seen is that a configuration might have become corrupted somehow, and it is causing the control system to crash when loading it. One work around for this is to set the AutoloadLastConfigflag to false and restart the control system. The flag can be found in the file ~\Program Files (x86)\STFC ISIS Facility\SECI\SeciUserInterface.exe.config on the instrument.
Beam Status not updating
The beam status is taken from http://beamlog.nd.rl.ac.uk/jsbeam.txt which is updated by a jsbeam.py script on the server which is run as a cron job. The beam status may not be updating because the script has failed to update the file, which causes it to be empty.
For most instruments including CRISP and HIFI this jsbeam.txt file is read by dataweb at http://dataweb.isis.rl.ac.uk/IsisPPP/BeamCurrents.aspx and this dataweb page is displayed in SECI. On SURF, however, the jsbeam.txt values seemed to be read by SECI and then SECI built the graphs.
VIs slow and unresponsive
This may be caused by one or more MOXA NPort boxes associated with an instrument losing their network connections. VIs which communicate through a working box may be affected by other VIs being unable to open ports on a non-working box.
Verify that all MOXA NPort boxes are functioning normally and have valid network connections. Their front panels don't always show a network problem, so check the rear LAN socket for connection and activity. If it is convenient to do so, also power-cycle the box to re-establish communications.
Configuring Blocks Causes an issue of DataGridViewComboBoxCell value is not valid
This has been seen on HIFI and is likely due to some odd state of blocks and groups. The issue has not been fixed and the block xml must be edited manually.