Fanuc RoboGuide SysRdy UOP Signal

    Hello everyone,

    I'm trying to create toolpaths and generate programs using RoboGuide. Everything seems to be working fine except when I try to move the Tool Center Point with my mouse. Whether I offset it in a direction +/- or just grab the little TCP dot and move it, RoboGuide pauses for about 3-4 seconds with a little pop-up menu stating "Waiting for SysRdy UOP signal". The robot arm "ghost" will then move to the TCP briefly and then the TCP will move back to where it was originally. When I created my station I used a very recent backup of the files (not an image). Our real robot has a bunch of safety interlocks in place that prevent certain things from running unless certain conditions are met (doors are closed such that prox sensors activate, spindle needs to be warmed up, robot @ home position, etc). I'm not sure if that could be contributing to the issue but it might help. I've noticed that cycle restarting the controller makes it behave briefly, a few moves maybe, before the issue resurfaces. Any suggestions to help resolve this issue would be greatly appreciated, thanks!

    Quote from rpgemployee

    Hello everyone,

    I'm trying to create toolpaths and generate programs using RoboGuide. Everything seems to be working fine except when I try to move the Tool Center Point with my mouse. Whether I offset it in a direction +/- or just grab the little TCP dot and move it, RoboGuide pauses for about 3-4 seconds with a little pop-up menu stating "Waiting for SysRdy UOP signal". The robot arm "ghost" will then move to the TCP briefly and then the TCP will move back to where it was originally. When I created my station I used a very recent backup of the files (not an image). Our real robot has a bunch of safety interlocks in place that prevent certain things from running unless certain conditions are met (doors are closed such that prox sensors activate, spindle needs to be warmed up, robot @ home position, etc). I'm not sure if that could be contributing to the issue but it might help. I've noticed that cycle restarting the controller makes it behave briefly, a few moves maybe, before the issue resurfaces. Any suggestions to help resolve this issue would be greatly appreciated, thanks!

    Reserialize the robot and remove all safety options like the DCS one, you can also add the IRProgrammer option if you want in order to modify the program on a more easy way if you want to also code logic (it's a web interface like the TP that allow you to write instructions directly and more things instead of adding them through the TP menu)


    That's what I do every time I create a cell from a backup, so I don't have problems with the controller requesting me to validate dcs or putting them in bypass.

    To reselialize the robot, click on the robot mechanical unit item, then open properties and select the reserialize option.

    A new screen will open where you will be able to modify the robot options, change them, and then you will be warned the system will be modified. Just accept and a new system will be created and your old one will be replaced.

    Take into account that you will lose the posibility to see the DCS zones on roboguide if you disable the dcs option, but this should not be a problem if you plan to use it only to adjust offline paths.

Advertising from our partners