Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  29 May 2026, Zaher Salman, Info, ODBvalue timeout 
    Reply  29 May 2026, Stefan Ritt, Info, ODBvalue timeout 
       Reply  29 May 2026, Zaher Salman, Info, ODBvalue timeout 
          Reply  29 May 2026, Stefan Ritt, Info, ODBvalue timeout 
             Reply  29 May 2026, Zaher Salman, Info, ODBvalue timeout 
Message ID: 3226     Entry time: 29 May 2026     In reply to: 3225     Reply to this: 3227
Author: Stefan Ritt 
Topic: Info 
Subject: ODBvalue timeout 
> Dear all, I implemented an optional timeout for the wait ODBvalue command. The way it works is similar to the standard wait command:
> 
> WAIT ODBvalue, /Equipment/HV/Variables/Measured[3], <, 100, timeout, 60
> 
> where the "timeout" keyword start a countdown in seconds. If the ODB condition is not met after 60 seconds the sequencer moves on to the next line.
> 
> To use this feature you must recompile the msequencer, delete /Sequencer/State and start the freshly compiled msequencer. This will add two ODBs to the /Sequencer/State: "Timeout value" (the countdown) and "Timeout limit" (the limit given in the wait command).
> 
> I suggest that we add something similar to the pysequencer using the same ODBs.

How can the MSL code figure out if the wait succeeded or timed out?

Stefan
ELOG V3.1.4-2e1708b5