OWEN.DAVID
Member
We have an input map that executes at the top of every scan.
In most cases we are using the MOV instruction to copy the input data into a human referenceable tag of the same data type. For example,
MOV(IO_AB_Node2:11:I.Ch6Data,AI_Winch_Pressure)
However, in some cases the AI_... tag has been been created as an alias of the same input.
Does this mean that the Alias tag will be updated once by the MOV instruction and then again if/when the data refreshes at input card? Such that a reference to this tag later in the scan could retrieve a different value?
If so, this seems to be nullify the benefit of the input map, i.e. data doesn't change during the scan.
What is best practice for a project using an input map?
*use MOV to copy input data only to a BASE tag
*use MOV to copy input data to an ALIAS tag for some benefit?
Or is it more nuanced than this?
In most cases we are using the MOV instruction to copy the input data into a human referenceable tag of the same data type. For example,
MOV(IO_AB_Node2:11:I.Ch6Data,AI_Winch_Pressure)
However, in some cases the AI_... tag has been been created as an alias of the same input.
Does this mean that the Alias tag will be updated once by the MOV instruction and then again if/when the data refreshes at input card? Such that a reference to this tag later in the scan could retrieve a different value?
If so, this seems to be nullify the benefit of the input map, i.e. data doesn't change during the scan.
What is best practice for a project using an input map?
*use MOV to copy input data only to a BASE tag
*use MOV to copy input data to an ALIAS tag for some benefit?
Or is it more nuanced than this?