not the best solution, but if ALL of your positions shifted, than you can modify the tool offset, and with this you shift all your positions.
Posts by moln4r
-
-
Yep we also checked the optical cable, but there was no problem with it...maybe that solved our problem too
-
I also say bglogic is the best for this (for background tasks).Trigger it with a flag in your main program when needed.
-
Just like Atinder said.Create a joint point, but be careful joint movements can cause collisions easily, check it in slow speed first.
-
Just has the same problem with an m6i last week "Fanuc Servo Serial Bus" disconnect...We also doesn't find any problem.It happened in the same position all the time.After I slowed down that movement the problem doesn't come back again.It was maybe a broken cable or connector on the mechanical part...but i'm not sure.Try to slow down the robot and if the problem still exist check your cables and connections.
-
Hi guys,Is possible rotate tool of 180 of robot standing in a wait position?
Robot go to position A to C, but I want to create a B position in which robot rotate tool of 180°. I see is the X Axis.Thanks
The question is:
Do you want to rotate the axis in every cycle? or just sometimes?
Doesn't understand exactly...if you just want to rotate the axis why don't you just teach a new point? or just offset an existing one. -
-
If you have bglogic than you can do something like this for example:
If R[1]=1 than
Do1=on
EndifIf R[1]=0 than
Do1=off
EndifNow you control the do with R1
-
I don't hink i'm exatly understand what you mean, but you maybe can use SELECT [R*]
-
If you have bglogic I'm sure you can monitor some sysvar and count with a register...
-
Check menu-->system-->config there is an option to continue the program when the controller was restarted.Doesn't remember the exact name of it, but you gonna find it.
How they abort all the programs?They hit fnct-->abort all? -
Next time change the batteries while the controller is on.
Now it's may not a problem because probably you already lost the pulse coder data so you need to master the robot anyway.
but if it's already running in production and you remove the batteries while it turned off than you need to re-teach all your positions.
But i'm sure the tp issue is not because of that. -
I'm not sure on the RJ2, but on later controllers you can turn off the force message setting in the system config. When it is true, it forces the user screen up whenever the MESSAGE command is hit.Yes you can try to turn this setting off (if it's in RJ2) than the screen not changes to the user screen automatically.But I'm also not sure if it's in rj2 or not.
So check
Menu-->System-->Config
And search for force user message, or force message or something similar.If you turn it off (if it's there) than the messages only show up only if you manually select the user page. -
AND!!?
What was the problem? -
No idea....
Maybe you can try to modify the program like this:! Wait Till Mold Fully Open;
WAITTMOUT=x(more than your imm cycle time in ms)
WAIT DI [7: Mold Fully Open] = ON, TIMEOUT LBL [10]If you got the [Robot Not Home] message, than no matter what you see on the tp, the robot doesn't got he signal...or may you need to check your waittimeout settings in the system menu.but just guessing.
-
So is this right? -->
1:
first cycle:
you start the IMM than the robot.
Mold opens, but the robot just hangs there waiting for the mold to open.2:
Fault out the robot with the key switch....3:
2nd cycle:
You reset the robot and sends it home, reset the IMM and restart the cycle than start the robot again and when the mold opens it moves into the mold.Am I understand it right?
Write down what exatly happens. -
Just guessing but you need to check all your programs for the messages, because may you see this program if you press the edit button but maybe a program is already running in the background...Check your programs for the RUN command if you see that, than that program is also running.
About the init...it must be also a program, may it has a different name.Where the cell is initialized. -
How you exactly fault it out?
-
Quote
43: CALL ALLARM ;
It's calling a program called "ALLARM"
May your user screen messages are there...check it.
There must be a program what's controlling the user screen messages.Are U checked all the programs?May your main program RUNs it at the start or init.
-
Are you using a crossover cable?