Hello, all. New user here. Trying to use a 'condition' monitor program within a looping section of RSR...in teach, stepping through program, when i force the DI change of what I'm monitoring, the condition program calls the assigned macro and changes accordingly, the data register I'm using in a job called within the RSR and the data register logic I have set up in the called job responds correctly...when i run the press and robot in auto, all stops at the line where 'monitor' starts and I get a syntax fault....does this have to do with condition program naming? I'm using an identical setup with another condition program and monitor without any issue...any input will be appreciated...Cheers!
How to use 'monitor' program within program?
-
Tech4484 -
May 8, 2013 at 4:28 AM -
Thread is marked as Resolved.
-
-
Tech,
If you were CALLing the condition handler that would happen.
Condition handlers have to be started with the MONITOR_[program name] command.Could you post your programs to see more?
-
Kind thanks for the feedback...going to try, instead, doing the monitor in 'system' instead, as the state I'm trying to monitor comes from the injection moulding press that the robot is servicing...have logic in running demould program intended to 'reject' the first 2 finished parts anytime the press is taken out of auto operation state...usually, the op aborts the rsr on the demould robot and calls it again, which restarts the 'scrap part' logic, but we had an incident a couple of weeks ago where a short shot part made it to the end of the line, which leads me to believe that the op just skipped a line and started all back up, in the looping section of the rsr, with no active logic to reject the first 2 parts....i think doing it at the system level will prevent this from happening again and keep everyones' head on....Cheers! !
-
You called the program a function CALL or RUN? Can you please show the code. And how you resolved your problem?