Foliver

Hi VernonAzuki, I'm reall sorry that I never post the answer to the problem here. I'll try to remember evrything since it was 10 years ago :) so in the sytem we in the system we were using, Ultra 3000 drive with with 3trd party motor, an Exlar don't remember the exact catalogue number.  the encoder was coming from the motor to a green terminal that was connecting to the drive.  we did all the standard test to fin what was going on, swap encoder cable, test, swap power cable, test, swap drive, test, swap motor, test. we did not find a culprite, so I was pretty lost.  In that period, there was a lot of defective encoder cable coming from allen-bradley. But what I learn latter was that is was not just the cable that was the problem, but the whole communication system in the motor/drive. So basically, wiht a ultra 3000 and an Exlar motor, the system need to have a higher "connectivity" between the drive and the motor than a system with a Allen Bradley motor.    So the real problem was a close to the limit connectivity between the motor and the drive. It was either on the drive or motor side, maybe the green terminal, I am not really sure.  But we fixed the problem by changing the encoder cable from Allen Bradley to Amphenol. here a link (not hte exact cable) : https://www.amphenol.com/node/1034 we started to buy them wiht both ends made in there factory. there was a longer delivery both we never had any problem after that.  later, when we change to kinetix 6500 and 5700, we found that those were a lot more reliable on the connectivity and switch back to cable that we can do the terminal ourself. beacause delivery time and way easier to order a 90 feet cable and cut it than try to find the right length and order it 6 mounth in advance... :)   So If you do have the same problem and did all the test without any result, I would suggest to try an Amphenol cable. There is also a connectivity paste that can be apply to every connection to help, but it doesn't last very long....    

we are not get the module to communicate directly for the drive so we tried couple thing. flash the processor and sercos card in 17 then back in 18, just to be sure that everything been erase in the memory. re try to swap motor and cable from axis 2 to 3. that time the fault goes on drive 3. Put new cable. same thing, put a new motor, same thing. Put the new cable and motor on axis 2, worked fine but still a fault on drive 3. we left that like this for the night. Came back this morning to test while all other motor on site is off to be sure that there is no leak to the ground. A surprise: the error is now on axis #2. I've also overwrites the .CMF file and rebuild again the axis. no change. Sometime the Sercos loop stop at 3 and sometime we have a E07 ( no feedback ) error. the only other thing I thinking of is installing version 19 and see what happen. I also wandering about the BC01 module, if it can cause some voltage drop or if it can messed-up the communication with the other Bm01 module.... Foliver

I seen that before, there a little difference in version 18 and up, it's now a .cmf file and you need a special program to install it on a computer. I've checked that already. but I'm thinking of re-install that and try it. even if I already rebuild the axis group and they are the same motor. So I would think that if the motion data base is in error, it would be on all axis, but from now on nothing make sense anymore. I also tried to flash (again) all drive, trying to kind of reset the drive to factory default. did not change anything. apparently there a way to "see" what motor the drive is seeing with a special cable, I'll try to find that. Foliver

yes that what I meant when it said changing the backplane

Let me describe the system first 1768-L43 Ver.18.11. Mo4se Ver 18.5 , 3 axis with the same motor and the same mechanical setup making the same movement. The system been runing for amlmost 3 years now. we have that system in different location in north america and this is the first place this happen. The customer called us because he had problem with an axis (#2). So as usual we start by changing the cable, then the motor, finally the drive. We also change the sercos card an the optic fiber. after changing the Kinetix backplne, I've call the AB guy. At that time we had an error E07 on the drive 2. From there we tied different thing like, re-re-re verifying all firmware, deleted harmony file, export the program in L5k download, deleted everything linking the the motion group(axis, drive sercos card) and rebuild it. Tried again, now the sercos ring stop at 3, like if the motor is not configure, but it configured exactly as the two other. so we tried to download the program with the axis #2 motor catalog number at "non". The sercos ring goes to 4. Return offline, put the right catalog number, download, the ring stop a 3 again. so we tied again to take our spare motor ( with his own cable) on the axis 3. the spare kit is working fine. we take that, install it on axis 2. not working. Swap drive 2 and 3, the error stay on axis 2 (did not follow the drive). do you have any idea, other than sending a new Plc+drive cabinet? Regards, Foliver

After talking a lot with AllenBradley tech Support, they will wend a guy here to check what is going on with those two drive. i'll send you some news when we will get anwser....

Well in fact it's not the first setup of that system. Ive been installing it about 2 month ago. everything was fine. but they call back because 2 servo drive was going in fault ( e22, e24 ). I was on another contract near of them so i end up here chcking that. Ive try the usaual stuff: changing Cn2 cable with another known as working ( those wire are serie C ), changing the cable going to the breakbox with one working, changing the breakbox, checking the ground system, remove every power cable passing above 6inch of the encoder cable. and the errors always coming from those two drive. we've change the motor, change the drive. Still happen. It can be ok for a day or two. or it can go in error every 1 hour. So i'm searching for something i've miss... It is really a pleasure to work on this, until it stop working! :)

By tthe way, id there anybody who know how to set the Commissioning/Commutation Adjustment in the sercos card in Rslogix 5000 ? Thank

After searching a lot on internet, we have found that the communication between the drive and the communicate by Rs-485. After checking on the encoder pins, there is a 130 oms resistors. But When i'm checking on the drive pin it's giving me 12.3k . So i know tha t485 need his both resistor to work well, unless they have herractic and intermittent problem. have anyone had an idea on that? Thank

Thank !

By any chance, is anyone know another companie that will sell Encoder cable for a GSX30-0605-MTM-AB5-268. I'm kind of tired of changing Ab cable..... Thank

dont think I do not apreciate what you do here, it's just i'm basicly french and sometime i can seem rude but i dont mean it. The thing is that the guy told that to reset that kind of fault you have to remove the control power because it's with that power that the drive keep it fault memory. thank for the advise and by the way i was just trying to be funny... i bet i miss my shot

I've got a problem with two Ultra 3000 drive in the same place ( 6 in total). It's an intermitent problem: it give me an E22 or\and E24 ( over Velocity\OverTemp ). The problem is that the thing is not running and i receive those errors. A motor and a drive have beeen change, the encoder cable is an Serie B made after the recall date from AB. The cable have been ring out and it working. It's not a question of parameter or anything like that because i've been testing the drive during the production all day( making it make long fast stroke whenever the system need that servo). no over temp. no over velocity. The ground have been test. the shield is connected ( both motor and encoder). the main ground of the servo panel is a #8 Awg connected on the main ground of the factory. The main transfo is a delta, but normally that should not do anything to the drive. Thank

What do you use instead?