exception: FlexScript exception: MAIN:/project/exec/globals/Debugger/onUpdate

[ozawa_shinya]

[ FlexSim 23.0.8 ]

Hi,

The attached model executes the stop command in the process flow. The OnRunStop trigger executes command1, which executes reset and print. When I run this model I get the following error and FlexSim is frozen so I have no choice but to end the task from Task Manager.

exception: FlexScript exception: MAIN:/project/exec/globals/Debugger/onUpdate

Why does this happen?

reset-command-in-user-commands.fsm

Thanks in advance.

[joerg_vogel_HsH]

You are imitating a model run dashboard by commands. A stop call stops a model run, but pending commands are still in an event pipeline. It is similar to expecting an action after switching off main power of a computer and telling him to do still something that needs power of this system. You need for this a system console that is running always in FlexSim. That does not exists in FlexSim. This exists in your windows system. You can run a windows system process, that executes windows button commands of a FlexSim model run dashboard.

[joerg_vogel_HsH · Accepted solution]

Please investigate an event list on or around stop time instead of setting a debug point. A stop call terminates a model run execution instantly. I’am not sure how something can resume a suspended model run of a debug point that had terminated a model run.

[ozawa_shinya]

Since we can not say anything definitive about the behavior of breakpoints after the model is terminated with stop(), does that mean you do not recommend to use breakpoints in this case?

[joerg_vogel_HsH]

@Shinya O, yes. A breakpoint stops an execution of a FlexSim model run. A call of stop() or reset, what does a sequence of some similar actions, is not able to resume any events.