|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
29 May 2026, Zaher Salman, Info, ODBvalue timeout
|
29 May 2026, Stefan Ritt, Info, ODBvalue timeout
|
29 May 2026, Zaher Salman, Info, ODBvalue timeout
|
29 May 2026, Stefan Ritt, Info, ODBvalue timeout
|
29 May 2026, Zaher Salman, Info, ODBvalue timeout
|
29 May 2026, Stefan Ritt, Info, ODBvalue timeout
|
|
|
Message ID: 3229
Entry time: 29 May 2026
In reply to: 3228
Reply to this: 3230
|
| Author: |
Zaher Salman |
| Topic: |
Info |
| Subject: |
ODBvalue timeout |
|
|
> > >
> > > How can the MSL code figure out if the wait succeeded or timed out?
> > >
> > > Stefan
> >
> > You get a message, something like:
> > 17:52:12.293 2026/05/29 [Sequencer,INFO] WAIT ODBValue timeout after 10.0 seconds: /Equipment/Test/Variables/V < 1 not satisfied
> >
> > Do we need something else?
> >
> > Zaher
>
> I mean how can the following code determine the timeout?
My intention with this was dealing with something like setting a cryostat temperature or any non-critical parameter. If it is not reached within a given timeout we give up and move on with the plan rather than sitting and wasting a whole night of beam. If your ODBvalue is "mission critical" then the wait command should not be used with a timeout. If you do use the timeout option then you will have to check in the following lines what is the state of your ODBvalue (very easy). To me this is the simplest and most useful way for our use case. |