Just curious how everyone is using these blocks in regards to having the blocks reset to default values when the code is loaded onto a new blank controller.
For example,
Think of a program that has some runtime modifiable parameters stored in memory dynamics that should be set to some standard values when the code is first programmed onto the controller. Assume the memory on the controller is uninitialized therefore the memory dynamics will have random values at first boot up.
I don't want to have to run through all the values and set the defaults manually using the service tool, so I used the Memory Dynamics with default. I setup the standard default values along each memory dynamic, and tied a control signal to each that will set the default value and write that to memory.
The question is how to get the controller to decide when to set everything to default? So i have two ideas:
-Use service tool or the display UI to trigger the set to default. Only problem is that a service tech might forget to do this step and bad things could happen when they start the equipment.
-Add a couple memory dynamics with 'key' values and if they don't match what they should, reset all memory dynamics to default values. This seems like a sound idea but for some reason its not setting well with me.
Has anyone else run into this and how did you handle it?
Tyler
