Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84522members
353757posts

TM171 Alarms

Machine Automation Forum

A forum addressing machine automation solutions for the complete machine lifecycle. Including offers like Machine Advisor, Modicon PLC/PacDrive, Lexium or Preventa. Discuss and share knowledge on offers relating to cloud-based service platforms, machine localization and monitoring, industrial operations control, motion products as well as safety function!

Solved
otrotabi
Lieutenant
Lieutenant
0 Likes
3
236

TM171 Alarms

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 ? 

 

alarms.jpg

 

 

 

 

 


Accepted Solutions
FedericoM
Lieutenant Lieutenant
Lieutenant
0 Likes
2
192

Re: TM171 Alarms

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.

See Answer In Context

3 Replies 3
FedericoM
Lieutenant Lieutenant
Lieutenant
0 Likes
2
193

Re: TM171 Alarms

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.

otrotabi
Lieutenant
Lieutenant
0 Likes
1
182

Re: TM171 Alarms

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.

Tags (1)
FedericoM
Lieutenant Lieutenant
Lieutenant
0 Likes
0
177

Re: TM171 Alarms

Unfortunately it is not possible...

Tags (1)