Codesys 3.5.18.60 – Application Loss and Persistent Data Corruption

rer-code
2025-08-19
2025-08-26
  • rer-code - 2025-08-19

    Hi,

    I’m currently managing over 50 PLCs running Codesys version 3.5.18.60. At seemingly random intervals, some of these devices experience a failure where:

    All persistent variables are lost.
    Attempting to log in results in the message:
    β€œThe application does not exist on device. Do you want to create it and proceed with download?”
    The log shows:
    β€œLoading retain-data/bootproject failed.”
    From what I’ve gathered, this may be due to a corrupted persistent data file, but I’m not entirely sure how to confirm or resolve this issue.

    If anyone has encountered something similar or has suggestions for troubleshooting or preventing this, I would greatly appreciate your input.

    Best regards

     
  • TimvH

    TimvH - 2025-08-26

    Which device do you use? Does this have persistent memory (e.g. NVRAM) available?
    Maybe first ask your PLC vendor about the possibilities and how they advice to use persistent variables?
    If you have no NVRAM available, CODESYS will store the variables in a file when the device gracefully shuts down. But on an abrupt power failure, this is not possible. If you have no NVRAM and you want to use persistent variables, then consider using a UPS. In this case when the power is lost, the UPS can keep the power on the PLC which then can gracefully shut down.

    Alternatively use the Persistence Manager to store the variable values in a file e.g. only on change.
    See:
    https://content.helpme-codesys.com/en/CODESYS%20Application%20Composer/ac_pm_overview.html

     

Log in to post a comment.