DamianInRochester
Lifetime Supporting Member
There has got to be a better way than what I have been doing.
Say for example I have a PV+ talking with a SLC5/03 via DF1.
I want to make a Screen that shows the state of the inputs.
I don't want to send over every single input on a separate tag, so I copy the Input status to an N integer in the PLC.
On the FTView end, I create an internal tag called {InputCard3} that points to the N integer.
Why Rockwell decided not to allow you to simply reference a bit of that tag like this "{inputCard3}.5" is beyond me.
So I have been skinning this cat by using these expressions for each instance of my bits.
{InputCard3} & 1 <> 0
{InputCard3} & 2 <> 0
{InputCard3} & 4 <> 0
{InputCard3} & 8 <> 0
{InputCard3} & 16 <> 0
{InputCard3} & 32 <> 0
etc.
There has to be a better way right?
What am I missing?
And yes, you can do bit shifts but this is just bad and probably less efficient behind the scenes.
Say for example I have a PV+ talking with a SLC5/03 via DF1.
I want to make a Screen that shows the state of the inputs.
I don't want to send over every single input on a separate tag, so I copy the Input status to an N integer in the PLC.
On the FTView end, I create an internal tag called {InputCard3} that points to the N integer.
Why Rockwell decided not to allow you to simply reference a bit of that tag like this "{inputCard3}.5" is beyond me.
So I have been skinning this cat by using these expressions for each instance of my bits.
{InputCard3} & 1 <> 0
{InputCard3} & 2 <> 0
{InputCard3} & 4 <> 0
{InputCard3} & 8 <> 0
{InputCard3} & 16 <> 0
{InputCard3} & 32 <> 0
etc.
There has to be a better way right?
What am I missing?
And yes, you can do bit shifts but this is just bad and probably less efficient behind the scenes.