Some instructions to help out when replacing your drives and restoring the Fanuc beta drive parameters. With Beta series drives the parameters are stored in the drive so if you
replace the drive the parameters will go with it. MRO Electric and Supply maintains a comprehensive stock of new and used FANUC Robotics Drives parts. If you need a replacement part, please call 800-691-8511 or email email@example.com.
To save and restore Power Mate CNC Manager parameters to Beta Servo Drives:
This is required when replacing a Beta drive and applies to the following
controls. 16iA,18iA,21iA,16iB,18iB,21iB,20i,16,18,21,0i,Powe rate-iD and Powermate-iH.
1. Make NC PRM 960.3 (PMN) = 0 (Enables PMM function).
2. Select where parameters are to be saved (to save to memory card on i series controls make PRM 960.2
(MD2) = 0 and PRM 960.1 (MD1) = 1, to save as a part program make PRM 960.1 = 0).
3. Set parameter 8760 to the program number you want the parameters to be stored as. Note 1.
4. Press the SYSTEM button then the RIGHT CHAPTER button until the Power Motion Manager screen is displayed.
5. Press the SYSTEM soft key.
6. Press the PARAM soft key.
7. Press the OPRT soft key.
8. Press the RIGHT CHAPTER button. READ and PUNCH soft keys will be displayed.
9. Select EDIT mode.
10.To save parameters from Beta drive to CNC press the READ soft key, press the ALL soft key then the EXEC soft key.
11.To restore the parameters from the CNC to the Beta drive press the PUNCH soft key, press the ALL soft key, then the EXEC soft key.
Recently we had a customer who was working on troubleshooting a FANUC CNCPower Supply alarm that he had on a machine. He was wondering what the different codes stood for, so we wanted to go ahead and list the different alarm codes for this series. These codes apply to power supplies that start with the following prefixes. The “X”s after the H will be numbered, so an example part number is A06B-6087-H130.
Answer: The 140CPU651xx and 140CPU671xx controllers can only be programmed with the Unity Software. The 140CPU671xx will require UNITY Version 2.0
The existing 140CPU43412A and 140CPU53414A can be programmed with Unity once the kernel and executive firmware have been updated with the Unity OS Loader. (These controllers require a minimum of PV04 for the Unity upgrade.)
As both the 140 CPU 434 12A and 534 14A Quantum CPUs are compatible with Concept or ProWORX software, they can be upgraded to be compatible with the Unity Pro software without any hardware modification. This process of migrating from Concept to Unity Pro is achieved by updating the CPU operating system. This update is performed with the aid of the OS-Loader tool included with Unity Pro. The 2 upgraded processors (140 CPU 434 12U/534 14U) are then equivalent to the corresponding Unity processors.
MRO Electric and Supply maintains a comprehensive stock of new and used Modicon Quantum parts including Quantum CPUs. If you need a replacement part, please call 800-691-8511 or email firstname.lastname@example.org.
On Unidrive Classics, when a UD7x Unidrive option module error trip occurs,
the display will show the trip code as “tr__”. The trip number
can also be read in Unidrive parameter #10.20 or UD70
virtual parameter #88.01, and the line number where the trip
occurs in parameter #17.03, though only if the program was
compiled with debugging information.
When an error occurs in the UD70, the DPL program will
immediately stop. Also, depending on the cause of the trip
and the setting of the Trip enable parameters, the Unidrive will
trip on the “tr__” code. Optionally, an ERROR task may have
been defined which would be executed whenever a run-time
error occurs. MRO Electric and Supply maintains a comprehensive stock of new and used Control Techniques Unidrive and Control Techniques Unidrive Classic SP parts. If you need a replacement part, please call 800-691-8511 or email email@example.com.
Code Description Action
40 Unknown error Always trips
41 Parameter does not exist Trips if #17.14=1
42 Parameter read only Trips if #17.14=1
43 Parameter write only Trips if #17.14=1
44 Parameter value over range Trips if #17.14=1and #17.17=1
45 Virtual access failed – e.g. IOLink not running Trips if #17.14=1 (access)and
#17.15=1* (all time)
46 Stack Overflow Always trips
47 Internal error Always trips
48 Internal error Always trips
49 The wrong system loaded Always trips
50 DPL Maths fault – e.g. divide by zero, overflow etc Trips if #17.14=1
51 DPL array index out of range Trips if #17.14=1
52 User-generated trip from control word Always trips *
53 DPL Program incompatible Always trips
54 DPL Overload – Clock tick too short Trips if #17.14=1
55 RS485 trip – Mode 3 Trips if #17.14=1
56 Option board and system incompatible Always trips
57 Illegal OSCall Always trips
58-59 Internal Error Trips if #17.14=1
60-69 Option generated trip Trips if #17.14=1 *
Prc2 *Watchdog Trip.See the DPL command WDOG for information
Note: The watchdog trip can be disabled by setting #17.18 to 0.
CTTG128.doc V1.0 2 04/12/05
*When a trip occurs, all tasks of the DPL program will be halted (real-time tasks will
first complete) and any ERROR task is executed. The only exception to this is with trip 45, trip
52, trip 60 with certain option cards, the Watchdog trip (Prc2) and any other normal drive trips.
The line number is only available when the program was compiled with debugging information.
Any other trip numbers that appear are either generated by the drive itself or the DPL program.
Last week we had a customer who was running an RNC 16 STAR 1990 vintage machine which failed so he decided to replace the main A16B-1010-0280 motherboard. His original problem was that he was receiving a 401 [VRDY Off] Error which then led to a 911 Error. When he replaced the A16B-1010-0280 motherboard, the machine would go directly to the 911 Error.
The first thing we checked for was to make sure that he transferred over all of the EEPROM modules from his original board to the replacement board, which he did. Since that wasn’t the issue, we double checked on the 911 Error, which shows as a RAM PARITY ERROR in the manual. The main cause of this error is an issue with the memory in the unit, which is caused by the memory board failing or losing the parameters in the system.
To check to see if the memory board was causing it or not, you can turn the control off, reset it, and delete the parameters. If this clears the alarm, the control would come up with a different series of servo alarms meaning that the parameters need to be reloaded. If the Fanuc 911 Error comes back it would mean that there is a problem with the memory board which needs to be replaced. Before trying any of this, be sure to confirm that you have all of the parameters saved so you can load them back in. Check out our article on IT and Robotics here.
Once the 911 Error was cleared, the customer was able to load the parameters back on to get the machine up and running.