Troubleshooting

Some typical situations were observed to trigger a False property isOK state, and could not be easily fixed from hardware side, e.g. by increasing the exposure time of a diagnostics camera:

  • Analogues typically fluctuate, and their value can overshoot and/or undershoot the region of accepted values.

    Possible solution: Enlarge the region of accepted values if possible. Also, increasing size of the running average sample should reduce the sensitivity to outlayers.

  • During a specific experiment a monitored parameter varies sizable due to modifications of the running condition of an experiment, e.g. changing periodically the number of PPL pulses while monitoring the intensity of the laser beam. Ideally using a normalized signal would be ideal to handle this kind of situations, but unfortunately a Karabo device with this functionality is not present at the moment.

    Possible solution: Disable the monitoring of that property during those specific running conditions.

  • After preparing the setup for a new experiment the Overview devices start showing the monitored properties in bad state. This could be due to different running conditions in the experimental area, resulting in the monitored parameters being outside of the expected range.

    Possible solution: Reload new reference values from the system by clicking the button “Update References”.

  • During a new experiment some properties, or even an entire Overview device (checking a specific section of the experimental area, no more in use) should not be monitored, but they will be need in the future. A similar situation can also appear when the connection of Karabo to a section of experimental area is broken, due e.g. to hardware or infrastructure failures.

    Possible solution: Those properties (or Overview device) can be easily disabled from the monitoring, letting the Overview monitoring the system while disregarding those properties. Saving online the new system configuration allows to recover the new setting in case of restart of devices.

  • If a device, working during commissioning, hangs in the initialization state when restarted, then some needed connections to devices (to monitor the properties) cannot be established.

    Possible solution: Check that the needed devices are actually online.