sthays10
Member
This is the first project I've configured in FactoryTalk View ME. I have experience programming in InTouch, so trying to figure out the way alarming works in FT is frustrating.
I have my alarms set up in RSLogix 500. The alarm condition (either a comparing instruction or a digital bit) will turn on a B15/x bit. This bit will seal itself in until the PLC receives the HMI Acknowledge bit.
When I configure the Alarm in FT, I have the tag TANK_PSI_HIHI with a device address of B15/x. I have the alarm trigger set to this tag, with a trigger value of 1. When I run my application, I get a message: {ALARMS\TANK_PSI_HIHI}: This trigger has been disabled as its data type is not supported by Bit or LSBit triggered alarms.
Does this mean that FTView can not alarm off of binary bits? All the examples I see from a Google search and a forum search use mapping the digital bits into an N Alarm word... is this the only way? I would prefer not to do this (since I have already set up all my binary alarm bits), so if there is a work around, I'd love to hear it.
Thanks for your attention.
Steve
I have my alarms set up in RSLogix 500. The alarm condition (either a comparing instruction or a digital bit) will turn on a B15/x bit. This bit will seal itself in until the PLC receives the HMI Acknowledge bit.
When I configure the Alarm in FT, I have the tag TANK_PSI_HIHI with a device address of B15/x. I have the alarm trigger set to this tag, with a trigger value of 1. When I run my application, I get a message: {ALARMS\TANK_PSI_HIHI}: This trigger has been disabled as its data type is not supported by Bit or LSBit triggered alarms.
Does this mean that FTView can not alarm off of binary bits? All the examples I see from a Google search and a forum search use mapping the digital bits into an N Alarm word... is this the only way? I would prefer not to do this (since I have already set up all my binary alarm bits), so if there is a work around, I'd love to hear it.
Thanks for your attention.
Steve