Operaghost
Member
This thread has been around for ages now. You might consider starting a new message in its own thread.
Anyways, remember that the MOV actually copies the data. It does not remove it from the source. As long as the rung is true, the MOV will be triggered.
So, for example, if there are no conditions (inputs) ahead of the MOV it would move the data on each scan. If I had a source of 1000 and a destination of Timer.PRE then 1000 would get moved into the preset over and over and over. Each scan.
If I had an input ahead of the MOV and the input was true. The same thing would happen. If I only wanted the data moved a single time when that input was triggered I would add a one-shot ONS instruction.
Just as another possibility, you could make the Program tag an Alias to the Controller tag. Then you would not need the MOV.
OG
Anyways, remember that the MOV actually copies the data. It does not remove it from the source. As long as the rung is true, the MOV will be triggered.
So, for example, if there are no conditions (inputs) ahead of the MOV it would move the data on each scan. If I had a source of 1000 and a destination of Timer.PRE then 1000 would get moved into the preset over and over and over. Each scan.
If I had an input ahead of the MOV and the input was true. The same thing would happen. If I only wanted the data moved a single time when that input was triggered I would add a one-shot ONS instruction.
Just as another possibility, you could make the Program tag an Alias to the Controller tag. Then you would not need the MOV.
OG