I know it's obvious, but do you have the menu/system/config : "force message" enabled?
Posts by moln4r
-
-
we use 3 for injection molding machines. so yes.
-
sent you a pm
-
try this:
SRVO--156 SERVO IPMAL alarm (Group:%d Axis:%d)
Cause: IPM module has trouble.
Remedy: Replace the IPM mudule. Refer to the maintenance manual for detail.
-->
(68)SRVO–156 IPMAL alarm (Group : i Axis : j)
(Explanation) Abnormally high current flowed through the main
circuit of the servo amplifier.
(Action 1) Turn off the power, and disconnect the power cable
from the servo amplifier indicated by the alarm
message. (And disconnect the brake cable (CRR64
on the servo amplifier) to avoid the axis falling
unexpectedly.) Supply power and see if the alarm
occurs again. If the alarm occurs again, replace the
servo amplifier.
(Action 2) Turn off the power and disconnect the power cable from
the servo amplifier indicated by the alarm message, and
check the insulation of their U, V, W and the GND lines
each other. If there is a short–circuit, replace the power
cable.
(Action 3) Turn off the power and disconnect the power cable
from the servo amplifier by the alarm message, and
measure the resistance between their U and V, V and
W and W and U with an ohmmeter that has a very low
resistance range. If the resistances at the three places
are different from each other, the motor, the power
cable is defective. Check each item in detail and
replace it if necessary.
-
Hello all, did someone found out how to fix this? Just installed V9_Rev.G on windows 10, and I got the same error.
EDIT:
Logged in with an admin profile, started up one cell, after this everything works fine on normal user profiles.
solved.
-
Just an idea, but have you checked the payload settings?
-
+1 to HawkME
anyway what you posted means that your robot in GROUP 1 reached the end position on AXIS 5
-
Hello,
We have 2 LRMate 200iD arms one with R30iB Mate controller and the other is R30iB Mate Plus. Can we swap the two controllers if the mechanical arms have the same TYPE: A05B-XXXX-XXXX number? I found some info here on the forum that they need to be re-mastered after a controller swap. That's not a problem, but is there anything else I need to know?
thanks.
-
Once we had similar issue. After re-teaching the user frame, all our positions shifted. I investigated for a few hours than found out that the tool frame was initialized, and re-configured and there was a p=(-180) missing. So it was not the user frame after all...
-
first just try to change the system variable $IO_AUTO_CFG to True and perform a cold start.
-
how about creating a short bg logic code with the pos sysvars to trigger the do on a position or range?
($SCR_GRP[1].$MCH_POS_X/Y/Z/W/P/R)
-
So JimFc uncovered that you have a variable for that. The next question is that your robot has BG Logic or not? If it has, than you can monitor this easily.
-
exactly.
find the line where this program called. it has to be something like this:
CALL PROG_NAME_X(8,9,0,0,0,0) ;
in this case AR[1]=8 AR[2]=9
-
-
to move the robots with offsets we use a small program with ARs to keep the main programs clean as possible.
In this case you need 1 position and 1 position register, and call the "set_offs" program before you move, to set PR[100] with argument registers.
5: ! move to press position 9 ;
6: ;
7: CALL SET_OFFS(0,(-50),5,0,0,0) ;
8:L P[1] 150mm/sec CNT60 Offset,PR[100] ;
9: CALL SET_OFFS(0,0,5,0,0,0) ;
10:L P[1] 150mm/sec CNT50 Offset,PR[100] ;
11:L P[1] 50mm/sec FINE ;
and the called set_offs program is:
1: !---------------------- ;
2: ! SET OFFSET IN PR[100] ;
3: !---------------------- ;
4: ! ;
5: PR[100,1]=AR[1] ;
6: PR[100,2]=AR[2] ;
7: PR[100,3]=AR[3] ;
8: PR[100,4]=AR[4] ;
9: PR[100,5]=AR[5] ;
10: PR[100,6]=AR[6] ;
so you can set the value of PR[100] directly with AR[1-6]
just my 2cents
-
You can also turn on write protection on your programs, most of the people never find out how to turn it off... at least here
-
This is all about it in the manual
SRVO--310 SERVO
Cause: Internal alarm
Remedy: Contact the service personnel.
-
Hello, all our mate controllers have external IO racks like this:
just something to start with.
-
Cause: The ready signal of the servo amplifier corresponding to the displayed group and axis was
turned off.
Remedy:
1. Refer to those cause/measures when the alarm history is confirmed and other alarms have
occurred at the same time.
2. If this alarm occurred after add axis or modification of axis' setup, confirm whether a set content
is correct. If the mistake is found, modify it. Especially, confirm whether to find the mistake in
the FSSB line number, the amplifier axis number, and the amplifier type.
3. Confirm the setting of the machine lock for the multi group.
• Advance to measures 4 when all motion groups machine lock are released.
• Release the machine lock of the robot when the robot (six axis amplifier) is a machine
lock. Note: When six axis amplifier is made a machine lock, the amplifier subordinate
to this turns off and SRDY is turned off.
4. If this alarm cannot be reset, refer to the Controller Maintenance Manual for more information.
Note
1. When six axis amplifier is made a machine lock, the amplifier subordinate to this turns off and
SRDY is turned off.
2. There is a possibility when the specification of the teach pendant is not correct compared with
the controller. For instance, when the teach pendant of the RIA/CE specification is used in the
controller of non-RIA/CE specification, this alarm might occur. Connect the correct teach
pendant corresponding to the controller.
-
Fanuc has roboguide, wich is basically the same as robotstudio. 1 month trial available