Ask our Experts
Didn't find what you are looking for? Ask our experts!
New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Support Forum for HVAC and pumping machines, Modicon M17x and EcoStruxure Machine Expert HVAC software for chillers, AHU, CRAC units for datacenters or process chillers applications - from design, implementation to troubleshooting and more, by Schneider Electric.
Search in
Please select a country to continue with beta search.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-24 05:52 AM
I am aware of the Video_GetParam and Video_SetParam functions on how to read and set PLC variables from an HMI in procedures. However I guess we will all agree that it would be best if we could simply use @LocalParameters.variable format instead and I guess there must be quite powerful reasons why this is not implemented this way.
Other than quite cumbersome, my main concern is that this procedure is not at all robust: in case you start working with the PLC program and for some reason you either delete or re-assign the variable to another memory position, the HMI logic will not even notice.
There seems to exist or at least existed, but do not seem to work any longer, a couple of different approaches to this issue:
1) Use the generated .exp file and link it to the HMI, and then use this variables in the HMI (although I am not sure if they maybe used in procedures or only in pages)
2) According to this post -which is fairly recent-, it should be possible to use the Par_Adr() function but I get "Unknown function" if I try to use it in a procedure.
So my questions are : 1) Is the .exp file still useful ? If so, how do you use it ? and 2) is the Par_Adr() function deprecated ?
Regards,
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-24 06:29 AM
Hello,
PAR_ADR() works:
In the coming future the Display part will be improved and also this part will become simpler
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-24 06:29 AM
Hello,
PAR_ADR() works:
In the coming future the Display part will be improved and also this part will become simpler
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-24 09:24 AM
Ok, I figured it out. The HMI compiler is case sensitive, so Par_Adr() does not work, only PAR_ADR() does.
For anyone else interested, search for @LocalParameters does not exist,do not expect the EEPROM or Status variables to be listed after writing the dot.
So, what other tools or functions are available for HMI and where can we find information about them ?
Regards
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-25 02:03 AM
Hello,
LocalParameters is the default name assigned to the tab of the window HMI Var and Parameters which includes the list of Parameters and Status of the of the local PLC
The list of advanced function for HMI are listed in the help on line:
Most of them are used by the compiler.
Let's say that the ones that are often used in the scripts are:
Video_GetParam()
Video_SetParam()
Video_SendEvent()
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-08-27 03:56 AM
Many thanks. Regards.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.