Is there any benefit to using ALMD instructions in a Studio 5000 project when the HMI is using FTView ME?
We are currently triggering our alarms with the bits of dints and all the messages are set up in the ME project. We were looking into moving over to a PV5000 or an SE machine, which made me start researching the ALMD instruction and the tag based alarming in the newer PLCs, but due to a lack of features in the PV5000, and the exorbitant cost of standalone SE Station machines, we've decided to stick with the PV7+.
But our alarm code still needs a lot of clean up, and if I'm already in there, I'd like to have it ready for migration when we do eventually have to go to PV5000 or SE.
I know that ME won't get the message out of the ALMD instruction, but is there anything else useful in the ALMD instruction that ME can use?
I'd also love any tips for efficient programming with ALMD instructions if anyone has them. I've already discovered that you cannot create an array of ALMD tags. I really wish I could use tag based alarms with ME.
We are currently triggering our alarms with the bits of dints and all the messages are set up in the ME project. We were looking into moving over to a PV5000 or an SE machine, which made me start researching the ALMD instruction and the tag based alarming in the newer PLCs, but due to a lack of features in the PV5000, and the exorbitant cost of standalone SE Station machines, we've decided to stick with the PV7+.
But our alarm code still needs a lot of clean up, and if I'm already in there, I'd like to have it ready for migration when we do eventually have to go to PV5000 or SE.
I know that ME won't get the message out of the ALMD instruction, but is there anything else useful in the ALMD instruction that ME can use?
I'd also love any tips for efficient programming with ALMD instructions if anyone has them. I've already discovered that you cannot create an array of ALMD tags. I really wish I could use tag based alarms with ME.