Codesys Persistent Variables

Hi everyone,

I’m trying to declare several setpoint variables as persistent so they’ll retain their values after a power loss.

I’ve used the PERSISTENT and RETAIN keywords in the variable declarations. These variables correctly hold their values through warm and cold resets in the CODESYS IDE, but when I physically remove power from the controller and plug it back in, they all revert to zero.

I’ve already created a Persistent Variables object and mapped the instance paths to my variables. I also tried implementing the Persistence Manager module to handle them, but when I did, the controller became unreachable after deployment and required a factory reset.

Has anyone successfully gotten persistent variables to survive a full power cycle on a groov RIO running CODESYS 3.5.20.10?
Is there a recommended approach (or configuration setting) to make these values truly nonvolatile?

Any insight would be greatly appreciated.

Thanks,
Jon

The groov RIO does not have the battery backed NV RAM, so it does not support persistence. If you need variables to be persistent on a power cycle you would need to use the EPIC. You could potentially use the Recipe Manager to store data on the RIO using Codesys.