Perfect, I think I found the error and can release a new version as RC this week. Could you please test it then?

Could you check also the log file: `cat /var/log/revpipyloadapp`?

It looks like the program crashes, the outputs from the program itself are in the file `revpipyloadapp`, I forgot to mention in the last post, sorry.

And it's running now? Are the sections [MQTT], [XMLRPC], etc. also double in your configuration file? If so, please delete the duplicate occurrences completely. The value `plcprogram_watchdog = 1` is not good! The number is the timeout in seconds. If you activate the software watchdog, it must also ...

Please check the `autostart=1` parameter in /etc/revpipyload/revpipyload.conf. It must be `1`.

Checkout `plcuid` and `plcgid` maybe you have to change the values, if you need your script running as root.

https://revpimodio.org/en/revpipyplc-2/revpipyload/

Regards
Sven

Hi Alex! It could really be that `shared_procimg=True` cause that problems. I just have a similar problem report with the flag on GitHub. If you do not need the `shared_procimg=True` because no other Python processes access the process image, I would ask you to remove it / set it to False. If you co...

Hi Alex!

The use of RevPiModIO looks just right. You are probably using a single instance for your entire program, which is recommended.

For me, it would be important to know which parameters you use in the instance (autorefresh, shared_procimg, etc.).

Gruß
Sven

Hi kimgama! You are using the "Memory-Values", which just define the type of your analog inputs. Just change your Code like this: # Change RTD_Value_* to AIn_* ai_value = rpi.io['AIn_1'].value / 10 ai_value2 = rpi.io['AIn_2'].value / 10 Now you get the temperature with a decimal place. Gre...

Hi mcww_rd

After copying a new piCtory configuration, did you reset the driver of the piBridge - or restart the Revolution Pi?

When a new config.rsc is created, e.g. `piTest -x` must be called so that the driver read and applies the new configuration.

Greeting
Sven

Hi waisha. It looks like a resource problem on the RevPi. Of course, when the CPU is busy and the system starts to be unoperable, revpimodio2 can of course no longer maintain the cycle time and these warnings are issued. We now have to find out what is happening there. - In the command line, for exa...

Hi waischa. Did I understand you correctly that your Python program does not contain any GUI elements, so it could actually run on the command-line? Then you would have the possibility to use RevPiPyLoad. The service starts your program automatically and also monitors it. If it crashes, it can be re...