dalporto
Lifetime Supporting Member
See code at the bottom.
Hi all.
For the story, this is my first complete project using a Rockwell PLC, I've been mostly working with Unity Pro for the last 15 years.
So, I was planning a remap for about 40 analog values. You'll see that I use the value, a signal quality bit (which show #BAD on the HMI when the quality bit is off), and a signal fail which drive the alarm.
The SIM_ON (Simulator On) internal bit, when toggled, will mostly clear every alarm and place the PLC in a state of ready to start, and then I can use the other SIM values to test / FAT.
With a Schneider PLC, I have a block that I disable when the SIM_ON is true, giving me the opportunity to toggle whatever I want on the "output" side, so I can test every bit / value individually without having to double every tag I need, that don't look possible with Rockwell
Now, with that setup, I just figured out that I cannot force anything to individually test the _QUAL and the _F bit except for the local .Fault, which is useless as it is. This is mainly to prove that the right tag goes at the right place on the HMI/SCADA. When I turn off the SIM_ON, I have all alarm / statuses coming at once, which is useless.
The only thing I'm seeing right now would be to double the SIM tags, which I'm trying to avoid since I usually try to remove the feature before to give it to the customer, it's taking a lot of room and it's kind of busy work to do.
So, what's your take on that? I'm pretty sure some people had to do that kind of thing at some point. Basically, what would you do in that situation?
Thanks.
Hi all.
For the story, this is my first complete project using a Rockwell PLC, I've been mostly working with Unity Pro for the last 15 years.
So, I was planning a remap for about 40 analog values. You'll see that I use the value, a signal quality bit (which show #BAD on the HMI when the quality bit is off), and a signal fail which drive the alarm.
The SIM_ON (Simulator On) internal bit, when toggled, will mostly clear every alarm and place the PLC in a state of ready to start, and then I can use the other SIM values to test / FAT.
With a Schneider PLC, I have a block that I disable when the SIM_ON is true, giving me the opportunity to toggle whatever I want on the "output" side, so I can test every bit / value individually without having to double every tag I need, that don't look possible with Rockwell
Now, with that setup, I just figured out that I cannot force anything to individually test the _QUAL and the _F bit except for the local .Fault, which is useless as it is. This is mainly to prove that the right tag goes at the right place on the HMI/SCADA. When I turn off the SIM_ON, I have all alarm / statuses coming at once, which is useless.
The only thing I'm seeing right now would be to double the SIM tags, which I'm trying to avoid since I usually try to remove the feature before to give it to the customer, it's taking a lot of room and it's kind of busy work to do.
So, what's your take on that? I'm pretty sure some people had to do that kind of thing at some point. Basically, what would you do in that situation?
Thanks.