And as far as your question goes, maybe you can find an ABB robot model which has matching kinematic model.
Posts by Lemster68
-
-
I approved your post, but removed links. Please upload your pictures inside your post rather than link to external sites.
-
DS186's answer is entirely correct. Moreover, there is a system parameter setting that you can change to avoid this event in the future. Open the control panel, navigate your way to controller, Auto Condition Reset. Select AllDebugSettings, make it TRUE. When switching to Auto, it will unsimulate all IO, return the PP to Main if the calling heirarchy is not based on Main (someone set PP to routine other than main) and set the speed override to 100% if it has been reduced.
-
Ummm, why did you not just turn on do416 in your program?
-
You are correct, especially that you realize to remove the individual signals also. Termination should be at the end of the bus.
-
-
You can edit the eio for the broken welder, removing the unit. Then it might work if there are no further network hardware issues. You might then need to also disconnect that broken one. You might have to change the topography and termination.
-
You can find it now in the manuals sub forum.
-
Service Manual for IRBP B_D
-
How much do these gears weigh? If you are talking a couple kilograms the percentage of the robot's handling capacity will be so small that the robot would hardly notice. Now if you are talking tens, twenty or more, then sure.
-
There may be a stopmove active from one of the background tasks.
-
The motor on lamp on the robot is powered by the brake release circuit. If there was a short there you would get a different error regarding brake release circuit voltage, short circuit.
-
One time that happened to me. I was easy on the electricians, I swapped out the main computers and told them to peel off the stickers from the outside of the controllers and swap them. You could also juust swap out the SD cards.
As far as the contactors activation error, I see no way that the mismatch could cause that. Unfortunately I cannot help too much there, but I know a guy, Skooter who is the best.
-
You did not mention the controller version. Nevertheless, it could be a) collision detection is turned off, or b) the sensitivity is turned way up. Larger number = less sensitive, smaller = more.
-
Is it that the joint move is near the end point and is followed by a linear? Sometimes the error is not the current move , but the subsequent move. It is looking ahead and stopping the motion short with the fault.
-
If you crashed the tool, then only the TCP should be affected. Why redo your uframes? They should remain the same.
-
You have the PC interface option. It is active or inactive depending on whether or not you are using it. It is simply there for you to use if you need to.
I would contact that supplier to see if they have a similar product which works with the older robotware. Otherwise, you could look for a different product that says that it will do what you need it to do.
-
Is the cell controlled by a PLC? Or is this robot standalone?
-
-
Changing the main computer would probably result with compatibility issues with the other hardware in the controller. If you talk to ABB about it I expect that they would tell you to upgrade the entire controller. Is it really that necessary to upgrade to the newest? If so, why?