Service diagram for positioner
Posts by Lemster68
-
-
I am looking for a manual.
-
Find where the motor power cables connect.
-
Do you have the manual for that positioner or electrical drawings?
-
No, do not disconnect.
-
Maybe, I can't quite tell, the cover is off. Those look like SMB cables, but there has to be somewhere the connections for motor power and control signals.
-
Is there an extra brake release on the box which connects the SMB and motor power/signal cables? Exercise caution when releasing brakes!
-
What do you mean by "in standby"? Powered down?
-
-
It happens sometimes. Hopefully you have a backup from after the newer changes were incorporated. If so, then you should do a restore.
-
You could also check into TriggL and TriggCheckIO.
-
Try using the optional argument /Conc with your move instruction and get back to me with results. Also, look into your event logs, under motion, and look for "corner path failure" warning. It will tell you exactly where the offending line is. I use it as feedback to tell me where I am doing something stupid like programming a z50 with a following Waittime, which will always generate that warning. Of course I would not do that, just about the best example, though. Those warning will cause your motion event to fill quickly, flushing out the more important events. It is possible to turn those off in the system parameters, but only advised after you use them to improve your path programming.
As far as the program pointer advance, it used to be said that it would be three lines. Since IRC5 was introduced, I have the opinion that it is more. There are parameters to change that will change the read ahead, but they are not for the inexperienced or faint of heart.
Then moveSync should work about the same way with the WaitDi instruction.
A hacky kind of way is to do an IF DI=desired state THEN
Move with big zone
ELSEIF DI=undesired state THEN
Move with Fine point, or /conc with zone
ENDIF
-
Here is another:
Code
Display MoreIF stDate<>CDate() THEN MotionSup\On\TuneValue:=125; ELSE MotionSup\On\TuneValue:=100; ENDIF TPErase; stTime:=CTime(); stHour:=StrPart(stTime,1,2); stMinute:=StrPart(stTime,4,2); bOk := StrToVal(stHour,nTimeCurrentHour); bOk := StrToVal(stMinute, nTimeCurrentMin); IF nTimeCurrentHour <> nTimeLastHour OR (nTimeCurrentMin > nTimeLastMin +10) THEN MotionSup\On\TuneValue:=125; ELSE MotionSup\On\TuneValue:=100; ENDIF
The thing that you need to keep in mind is do not try to set a specific time unless you know that the robot will be available to run it or else you will rarely ever do bullseye. Set a time window when it can do it, between welding jobs.
-
-
-
Have you set the correct payload? By default, I think that all are set to maximum. Is it operating near singularity or close to robot end of work envelope?
-
Try to just shut it down, not restart. Leave power off for quite a while, then power back up
-
So did you or did you not enter the command xdelete image.bin?
-
You could manually edit the values in the data for workobject, or reteach if you have some fixed reference position/pointers for where it had been taught originally.
-
While it is possible to change it, just about every programmer just uses the default, "main". If you were to change it, you would have to remember to change that parameter every time that you update robotware or have to reinstall the system, for some reason.