Are there any "Monitor" statements used in your program. Perhaps at the beginning of the program your trying to step through?
R-J3ic not stepping through TP program correctly
-
JonnyRotten -
November 11, 2009 at 6:42 PM -
Thread is marked as Resolved.
-
-
YEs, there are monitor statements, but I get the same results in programs that do not have them.
-
But have those monitors been started? Try this if you haven't already. Create a new TP,insert several motion instructions. Then try stepping through these to see what results there are.
-
Just tried this, same thing.
I also tried powering it down and trying it again, to make sure some monitor wasn't hanging somewhere as well.Frustrated!
-
It sounds like a software issue I would try new software
-
Do you image backup from another robot you can load? Just to test results. This may sound strange but when running in auto can you see the @ symbol running through the program?
-
If you get the chance check these variables. Please re-post your settings.
Go to variables, goto $SCR.
Scroll down to $singlestep, toggle step button. Variable will should change 0 to 1.
$tpmotnenable should be set to (0)GOTO $SSR
$SSR.$stepstmttyp-I'm thinking this is the one causing you the problem. This should be set to (3), please let us know your setting for future references.
0= Task paused at each statment
1= paused at a motion statement only
2= paused at a karel motion
3= Execution continue in routine$Dummy should be 255
-
I had a chance to go through all of this today.
$singlestep toggles from 0-1 correctly
$dummy7 - 255
$sglsteptask - [14] of BYTE
$steptasknum - 1
$stepstmttyp - 3
$stepsegtype - 0
$bwdstep - 0
$showstmttyp - 0Also, the $singlestep setting was in SSR on my, not in $SCR. In $SCR $tpmotnenable was set to 0 thought.
-
Do you image backup from another robot you can load? Just to test results. This may sound strange but when running in auto can you see the @ symbol running through the program?I can see the @ only when it hits the exact points in the program in auto, it doesn't go line to line. or at least it goes too fast for me to see.
-
Not sure. I tried digging up some more info but fell short on time. I will post any findings but this may be one of those things we all have to live with unless you update software. Sorry.
-
Has anybody come up with a solution to this issue. I have the same issue on 10 new robots (M-10iA and LRMates) with the latest software V8.10P/03.
Single Step stops when a program is called up and won't return to the original program. Called Fanuc and they said they have never heard of this issue
and to check with the integrator. -
I would load the updated software... They are up to 8.10P/16 R30iB... and 8.13P/08 for the R30iB Mates...
Do you have any backgound tasks running? Any KAREL? -
Just got done loading the latest level of software and it did not help. Still can not step through in single step mode. It stops after completing each motion move and I have to arrow down to the next move. If it calls up a sub routine like :open Gripper: it will not return to the main program. I have to select the original program and then arrow down to the next line after it called the subroutine. What a pain. I am working with Fanucs support but not gion?etting anywhere.
Any one have any ideas?
-
Has FWD/BWD been disabled? This will keep you from being able to block through a program.
Press your function key and see if FWD/BWD disable is enabled.
-
After working with Fanuc we found a solution. The automation company had a programming error. They had a programmed a UOP "paused" signal to activate the UOP "stop cycle". When I put a Test pendant enable contact in series with the UOP "paused" input I can now single step forward and backward.
If anyone else has this problem you can test it by going into system config and disabling UOP and then see if you can single step. If yo can then you have a PLC programming issue.
-