I have a discrete 2-state device function block set up controlling a motor with 5 i/o. ProgCommand, FB0, FaultAlmUnlatch, Out, and FaultAlarm. Starting yesterday the block started throwing an alarm as soon as the motor started. Looking through the manual it says the alarm will trip when the feedback doesn't match the command state after FAULTIME (set at 2 seconds) or if the feedback suddenly reports a different state than the commanded state. I put a trend on the tags involved and this is what I am seeing.
TIME ProgCommand FB0 FaultAlarm
00:00:00.000 0 0 0
00:00:00.010 1 0 0
00:00:00.060 1 1 1
Just 0.050 of a second after commanding the drive "ON", the feedback comes back saying the drive is "ON" and it sets the Alarm bit.
Any one have any idea what it trowing the fault?
Thanks
TIME ProgCommand FB0 FaultAlarm
00:00:00.000 0 0 0
00:00:00.010 1 0 0
00:00:00.060 1 1 1
Just 0.050 of a second after commanding the drive "ON", the feedback comes back saying the drive is "ON" and it sets the Alarm bit.
Any one have any idea what it trowing the fault?
Thanks