@MikeyH Hi Mike,

This error is related to the timing issue of the Modbus Driver. It means that the Modbus Driver exceeded the allotted time 800x from the executive start for some reason. In your case, I would inspect the timing of the whole project and also the diagnostics of tasks related to the Modbus driver.

Without knowledge of your project, communication frame and timing, I'm not able to provide more details.

Cheers, Tomas

@MikeyH Hi Mike,

This error is triggered when something is preventing Studio from writing to the Project location. Do you have all related folders available for read and write?

If the issue persists, can you share a minimal project with us? Thanks

Cheers, Tomas

Hi har,
Check if RexCore is running. I see that you are solving the Python code in another thread. It is possible that your code is not only causing the error, but also causing the entire RexCore to crash. Try connecting to the Raspberry via SSH and enter the command:

systemctl status rexcore

Cheers,
Jan

@har Hi har,

Thanks for the additional info. We are not able to provide free support on this since it's your custom Python script. The error is not related to the Rexygen ecosystem. It seems that the CPU dispatcher is being initialised multiple times.

Tomas

@har Yes, the issue is in initialisation of the Python Block. If you wait a second with the mouse on the message
it will show you more instead of "..." which might help you to find the issue easier.

Cheers,
Tomas

Hi har,

thanks for your question. Please, can you share System Log? There should be some error which is preventing RexCore from running.

Cheers, Tomas

Hi Phil,

Thanks for your question. Please, have a look at example "0305-01 Hour Meter" - it should do the job or point you in the right direction.

Let us know if it helped.

Cheers,
Tomas

@stepan-ozana
The problem is caused by a large value in the parameters tn and tp. The change occurs, but it is very slow. For a faster transition between values, set lower parameter values. For an immediate change, set 0.

@stepan-ozana Hello,
thank you for your report.

Please, what version of REXYGEN are you using? I've tested it now on 3.0.4.17197 and everything seems to work. I'm attaching a printscreen and the project.
myproject_exec.mdl myproject_task.mdl

Best regards,
Jan

Hello Štěpán,

Thanks for the detailed summary — that’s really helpful!

Regarding the first experiment with the SETPS command:
The reason the CNSTEST1:scv parameter wasn’t updated is due to the SETF parameter of the SETPS block being set to "on". In this configuration, the value is only updated on a rising edge at the SET input.
To allow the value to be updated continuously, set SETF to "off". This way, the parameter will be updated in each cycle regardless of input transitions.

As for the issue with setting the CNA:filename parameter:
The filename specified here is not part of the application on the target device. Instead, the file resides on the host PC, and its contents are imported into the project during compilation.
That’s why the filename parameter cannot be changed online — it only serves as a reference for the compiler, not as a runtime variable.
Similarly, updating the nmax parameter isn't possible either, because REXYGEN does not support dynamic arrays — both the size and content of arrays are fixed during compilation.

As a general rule, parameters that can be modified online via SETP blocks are the same ones you can manually change in Watch mode — in other words, those that are not greyed out in the parameter list. If a parameter is greyed out, it means it’s read-only during runtime and cannot be changed programmatically either.

Cheers,
Jan