HVAC and Pumping Forum
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.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-13 03:47 AM
According to the online help, expressions can make use of PLC variables:
|
I tried to define the expression the same way I would do it inside PLC programming and by using @LocalParameters."plcvariablename" format as used when defining edits on the HMI screens
Actually what I am trying to accomplish is to show a static test "Config.Err" or an enumerative corresponding to a USINT variable enumerative on the same place on the screen.
So, how do you do that ? Is it necessary to create a .parx file in the PLC and import it in the HMI ?
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: 2024-10-14 02:45 AM
Hello,
@syntax is not supported by expressions.
My suggestion, also for data exchange optimization, is to pack boolean info into words (in the programming part), read them in the global script of the HMI and finally unpack them into global hmi variables.
These variables can be used in the expressions...you can find an example in the Parametric AHU template included with ESME HVAC setup
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: 2024-10-14 02:45 AM
Hello,
@syntax is not supported by expressions.
My suggestion, also for data exchange optimization, is to pack boolean info into words (in the programming part), read them in the global script of the HMI and finally unpack them into global hmi variables.
These variables can be used in the expressions...you can find an example in the Parametric AHU template included with ESME HVAC setup
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: 2024-10-15 03:46 AM
Thanks Federico. So the information is not completely accurate then - though it is not wrong -. You still need to use the Video_getParam to import the variables into local variables to use them in the local HMI.
I also tried another approach, by choosing a variable in the visibility field, and then adding "NOT" before the variable. It compiles fine but does not work as expected
Where can I have more information regarding .xml .parx files ? They are mentioned in the literature but since there are no examples I am not sure how to use 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: 2024-10-15 11:50 PM
@syntax is supported in the Visible field, but you can use just variable, you cannot write expressions directly in the field.
Parx file is automatically created inside each project and contains the description of Parameters and Status Variables (the tab LocalParameters shows the info of the related parx files).
I haven't documentation for it...but creating different type of parameters and status, the file structure will become quite clear
Link copied. Please paste this link to share this article on your social media post.
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.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of