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: 2022-06-29 11:18 AM
I know thta defining variables (which are assigned USINT values by defaut) under the "Alarms" folder acivates the Alarm icon on the top left of the display if the variable is set to 1, for example AL00 := 1; will turn the alarm icon ON and will show "PMOT" on the AL menu accesible with the SET button.
I´ve also discovered by chance that if you do: AL00 :=2; the alarm icon will blink instead.
So I load these variables memory addresses to an array with a task at Init like this : Alarm[0].MemAddress := ?AL00; and then for example "Alarm[6].@MemAddress := TO_USINT(CompressorAlarmId.b0)"; will turn the compressor motor alarm ON if the output bit from compressor alarm management turns to ON.
My question is: is there anyway to access "Short Names" programmatically as well ? Can they be changed on the fly without re-programming the PLC ?
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: 2022-06-30 11:51 PM
Hello,
the scope of Alarm folder defined in the M171O projects is to automatically create a dynamic Alarm menu (Set-->AL) on the M171O local display.
Alarm folder is present on other project targets just for porting reason.
Basically if an alarm variable has value 1 (assumed as active alarm) or 2 (assumed as alarm which can be reset), the related short name will be visible in the AL folder, if it is 0 it will be hidden.
The Alarm icon is on if at least an alarm variable has value 1.
The Alarm icon blink if at least an alarm variable has value 2 and all other have value 0.
Short name can't be changed runtime.
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: 2022-06-30 11:51 PM
Hello,
the scope of Alarm folder defined in the M171O projects is to automatically create a dynamic Alarm menu (Set-->AL) on the M171O local display.
Alarm folder is present on other project targets just for porting reason.
Basically if an alarm variable has value 1 (assumed as active alarm) or 2 (assumed as alarm which can be reset), the related short name will be visible in the AL folder, if it is 0 it will be hidden.
The Alarm icon is on if at least an alarm variable has value 1.
The Alarm icon blink if at least an alarm variable has value 2 and all other have value 0.
Short name can't be changed runtime.
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: 2022-07-01 03:48 AM
Thank you.
May the short name be read sowehow (other than physically reading it on the Set/Al menu I mean) ? I am using an alarm system which makes use of the "OverwriteLocalDisplay" Function to automatically display the alarm on the screen as it happens, it would be nice if I did not have to two tables synced manually.
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.
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