@har Hi har,

This error is related to the timing issue of the 'data_collect' task. The task takes longer to complete than the allotted time. Based on the image, I would guess that the Python block will take the most time to execute. In your case, I would inspect the timing of the whole project and also the diagnostics of task (Target ->Diagnostics -> data_collect and select the Task tab as shown bellow).

Cheers,
Jan

@har Hi Har,

I'm sorry, but we are not able to debug third-party Python code for you.

If you made it work under plain Python, then you can send the data to REXYGEN using the REST API. Have a look at "0302-03 REST API Python Bash etc", which sends data to REXYGEN using Python.

Kind regards,
Tomas

@MikeyH Hi Mike,

This is related to the communication timeout - inspect data length with respect to baudrate and timeouts.

All REXYGEN error codes here in Docs: https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BRef_ENGap3.html#x488-487000C

Cheers,
Tomas

@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