Message display

[TTCSR]

That is helpful, however, it still won't work for my application as there will still be times that an error message will be displayed for a brief moment, every five seconds.  I will definitely use this for future programs on other projects.

I do have another question.  I have a sequence that advances every 1 second unless an error occurs.  Is there a way to monitor the sequence and set a bit on if the sequence does not advance for more than a second?  If there is a way, it will totally solve my issue since I can use that bit in my HMI to change screens when that bit turns on.

[support]

You can use a 1 second clock pulse to trigger a custom function which is used to advance a sequencer counter if there is no error. If an error is detected (that is determined by your software) then the custom function can stop advancing the sequencer or set an alarm bit which is monitored by another custom function for actions.

[garysdickinson]

I would suggest the use of a TIMER.

Gary d

[TTCSR]

My sequence is advanced by each cutom function via an IF THEN ELSE statement (shown below).  Each completion of a test sets the CTRPV to the next sequence for the next test, hence, I cannot use a clock pulse for advancement.  However, I am not sure how I could use a timer though?

IF TESTBIT (INPUT[1],1) THEN
   IF INPUT[1]+INPUT[2]+INPUT[3]+INPUT[4]+INPUT[5] & &HFFFD THEN    'CHECK IF ANY OTHER INPUT #1 TO #16) IS ON
      CALL 2:
      SETLCD 2,1,D$+"A3 &"      
      CALL 8:
   ELSE
      IF CTRPV[1]=1 THEN
         CTRPV[1]=2
         SETLCD 0,0,CHR$(1)
      ELSE
         CTRPV[3]=10
         SETLCD 0,0,CHR$(1)
      ENDIF
   ENDIF
ENDIF

[garysdickinson]

I'm sorry, but I can not help you.

I think that your coding style has limited your options.

You might consider throwing more hardware at the problem.  Add another PLC to manage the display.  

I know that this adds extra cost to your project but if you can't change your coding style then a second PLC gives you the opportunity to manage the display of messages independently of the execution of your test sequence.

Gary d

[TTCSR]

I figured it out with a timer.  I placed a timer on each test.  If the test remains active for longer than 2 seconds, the timer bit triggers an output bit that I use to enable a display on my HMI.  I had to create 50 timers, one for each test, but it works perfectly.  

I agree the coding has limited my options, however, it was necessary due to the application.

Thank you for all the input and feedback!