You are not logged in.
Pages: 1
Topic closed
Hi,
Is there a way to save parameters that are changed by a HMI? For example, when I change a parameter whilst in watch mode, I get the option to save the changes made. If I make a change in a HMI, I don't get the same promt next time I go into watch mode; I thought I had found the answer with the 'Check Parameter Changes' function in Draw, but it didn't seem to work. Is this possible?
Cheers,
Adam
Offline
Hi Adam,
do I understand it correctly that your goal is to transfer the parameter changes into the .mdl source files? I.e. this would happen in development phase.
Or is your question about permanently stored user-defined parameters? I.e. this would happen in production phase. E.g. when the user wants to enter a setpoint for room temperature controller and this value should be kept after power failure?
Best regards,
Jaroslav
Monarco HAT for Raspberry Pi - Lightweight I/O for monitoring, archiving and control.
Raspberry Pi in industrial automation!
Offline
Hi Jaroslav,
This would be in a production/use phase. For example, I have set the system up and running and have provided a HMI for users to monitor things and set what setpoints they want for each of the rooms the system is controlling. If I have to make a modification to the system at a later date, when I redownload the modified program to the device, I will overwrite and loose any parameters/setpoints the user may have changed since my original download. I am looking for a way of saving these parameter/setpoint changes by the user, so I can include them in my modified program.
Cheers,
Adam
Offline
Hi Adam,
I see your point. You can achieve this using persistent memory. More information about persistent memory can be found in RexDraw documentation: https://www.rexcontrols.com/media/doc/P … df#page=13
Just be careful when redownloading the modified configuration to the device where the parameters are already stored. Redownload will not erase the persistent memory. If you want to erase it for some reason, use Expert mode in Download dialog.
In the current version (REX 2.50.5) persistent parameters are stored with respect to GUID. GUID is unique ID of each function block. Therefore if you erase (accidentally) a function block with persistent parameter and replace it with the same function block using the same name it will not be paired with the persistent data already stored in your target device. We have already come up with fix but it will be part of next release.
If you have any questions feel free to ask. I will do my best to help you.
Regards, Tomas
Offline
Thank you Tomas, that did exactly what I was looking for.
Adam
Offline
Glad I could help, Adam.
Good luck with your automation project.
Cheers, Tomas
Offline
Pages: 1
Topic closed