Conveyor tracking error handling?
Have my first working conveyor tracking setup, but the manual does´nt discuss error handling, would it be enough to catch the following two errors 50174 and 50221. in an error handler like this:
ERROR
IF ERRNO=174 OR ERRNO=221 THEN
DropWObj wobjcnv1;
DeactUnit CNV1;
bFelConv:=TRUE;
ENDIF
And use the boolean "bFelConv" as a "start at beginning of conveyor tracking routine"?
Kind regards
Mikael
Comments
-
Hi,
the errors 50174 and 50221 from the error logging can not be handled by using the number 174 and 221 in the error handler, because these are different concepts.
Error number 50174 means you have no conveyor connected and you have to use thr instruction "WaitWobj" before you exucete amove instruction bases on the conveyor work object.
/BR
Micky
0 -
so how would you handle these errors? the thing that happened was that the robot could'nt keep up so it connected the workobject, but the workobject reached the max distance Before the robot was finished which caused the error, we solved it be adjusting the speeds, but which solution should i use to Catch this error.
0 -
Im testing the following solution right now, maybe it will work...
PROC initCnvTrk()
CONNECT nCnvTrackError WITH T_CnvTrk_Error;
! 50174 Wobj not connected
IError COMMON_ERR\ErrorId:=174,TYPE_ALL,nCnvTrackError;
ENDPROC
TRAP T_CnvTrk_Error
DropWObj wobjcnv1;
DeactUnit CNV1;
bFelConv:=TRUE;
ENDTRAP
0
Categories
- All Categories
- 5.5K RobotStudio
- 396 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 250 ScreenMaker
- 2.8K Robot Controller
- 316 IRC5
- 61 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 801 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 5 Job listings