Twitch

"...create a new PLC tag (HMI_Startup); add a HMI startup macro to energize HMI_Startup " Thanks kaiser_will, I think this is a terrific idea and will give it a try!   AndrewG: thanks for helping.  Your idea would definitely work for some types of alarms but some I'm having trouble with are 'over-current' sensors, and for these I would like to alarm ASAP as to save hardware from damage.

Hi, I am using Factory Talk View ME v8.1 with RS Studio 5000 v24 on a 1769-L33ER controller. I have a project that exhibits some strange behavior. With the PLC up and running normally I now fire up the HMI and it will sometimes immediately trigger an alarm. The alarm message is configured to display the failing measured numeric and the test limit values being used, and so it is obvious that there is bogus data (large negative numbers) in those tag values when the alarm triggers.  But when I watch the tags in RS Studio I can see that they are stable and correct where used in the scaling math during the HMI boot.  Once the HMI is active they behave properly as can be proven through alarm testing.  It seems that there are transient values being used as the HMI boots up? Through the history of this HMI development I've seen the problem move to a different alarm, disappear, reappear on a different alarm, and now disappear again as new HMI builds are generated. Can anyone explain what might be happening or especially suggest how to prevent it? Tim