Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  30 Apr 2024, Luigi Vigani, Bug Report, Params not initialized when starting sequencer midas_sequencer_ok.pngmidas_sequencer_buggy2.png
    Reply  03 May 2024, Zaher Salman, Bug Report, Params not initialized when starting sequencer 
       Reply  03 May 2024, Stefan Ritt, Bug Report, Params not initialized when starting sequencer param_test.mslfunctions.mslSequencer.jsonScreenshot_2024-05-03_at_09.19.29.pngScreenshot_2024-05-03_at_09.20.47.png
       Reply  03 May 2024, Luigi Vigani, Bug Report, Params not initialized when starting sequencer seq1.PNGseq2.PNGseq3.PNG
          Reply  03 May 2024, Zaher Salman, Bug Report, Params not initialized when starting sequencer 
             Reply  03 May 2024, Stefan Ritt, Bug Report, Params not initialized when starting sequencer 
                Reply  03 May 2024, Zaher Salman, Bug Report, Params not initialized when starting sequencer 
                   Reply  03 May 2024, Stefan Ritt, Bug Report, Params not initialized when starting sequencer Screenshot_2024-05-03_at_18.19.52.png
                      Reply  10 May 2024, Zaher Salman, Bug Report, Params not initialized when starting sequencer 
                         Reply  13 May 2024, Luigi Vigani, Bug Report, Params not initialized when starting sequencer 
Message ID: 2756     Entry time: 03 May 2024     In reply to: 2755     Reply to this: 2757
Author: Stefan Ritt 
Topic: Bug Report 
Subject: Params not initialized when starting sequencer 
Ahh, that rings a bell:

1) JS opens start dialog box
2) User enters parameters and presses start
3) JS writes parameters
4) JS starts sequencer
5) Sequencer copies parameters to variables

Now how do you handle 3) and 4). Just issue two mjsonrpc commands together? What then could happen is that 4) is executed before 3) and we get the garbage.
You have to do 3) and WAIT for the return ("then" in the JS promise), and only then issue 4) from there.

Stefan
ELOG V3.1.4-2e1708b5