Need Help!- Mazatrol T-3

[robind]

I need to find an FX-331 board or get the one I have fixed. Does anyone have an idea where to find one?

[bigbobomb]

Originally Posted by robind I need to find an FX-331 board or get the one I have fixed. Does anyone have an idea where to find one?

MITSUBISHI

[chippy1]

How do you know that the FX331 you have is defective? What's the symptom and how did you diagnose that the FX331 was the problem?


Regards,


Chippy

[robind]

My service tech guy spent about 6 hrs. trouble shooting and testing the control with different boards. The FX331 is the only one he did not have a spare of. The control when turned on would after a few seconds give an error of x axis lag excess. He turned a couple of pots on the board to change the droop on the dagnotics screenbut the drive just ran away and showed the same error. This service tech is not a shade tree sort of tech. He is the tech guru at a large machine shop nearby. Mitsubishi will rebuild the board for about $800.00. I just thought there might be one around out there for less money.

Thanks,

robind

[chippy1]

Typicaly this board is not a problem. What led up to the x-axis lag. Did you just come in one day, power up and you got x-axis lag.

Your CNC guru, what all did he try? Did he swap top cards on the amps? If the servo's power up and when you initially give it a manual command to move, can you see the position move but physically the axis doesn't move then the base is not moving the motor and the amp maybe the problem. Did he swap drives? Did you move resolvers or tachs? If the tach is turned 90 degress you will get a lag during power up. The axis will jump.

Please tell me more before you send the PCB to Mitsubishi.


Regards,

Chippy

[ccs007]

I have encounter x-axis vibrated with a little bit noise and confirmed that the servo drive was faulty. I don't know whether same with your problem?

[robind]

The problem started one morning when starting machine. I started to home the Z axis and the lag on Z error came up. As for the drive boards, we did move them and the problem did not move or change. The other boards in the bottom the tech had spares except for the fx331. We put the spares in and it had no change. The lag error is not just the one axis. It is either one, you try to move first. The tech tried to change the droop setting in the diagnostic mode. This did not help. When the droop number got close to -45 it seemed to runaway, but the axis did not physically move.

[chippy1]

Thanks for giving more information.

Based on your last post, and the problem being in both axis now, I would say that your problem is in the DU30 unit which supplies the P & N voltage to your servo amplifiers. If you look closely for the wires that go to P/N on the AMP, trace them back to the DU unit. Its location is usually at the bottom of the cabinet. It will have a large white ceramic glass fuse and two or three indicator fuses. It also has a small green PCB which is called a TR15 card I believe. Look to see if any red LED's on this card. This unit is most likely your problem. Make sure the breaker is not tripped. Usually if it is the CNC will tell you so.


Regards,

Chippy

[mazaksa]

Originally Posted by robind My service tech guy spent about 6 hrs. trouble shooting and testing the control with different boards. The FX331 is the only one he did not have a spare of. The control when turned on would after a few seconds give an error of x axis lag excess. He turned a couple of pots on the board to change the droop on the dagnotics screenbut the drive just ran away and showed the same error. This service tech is not a shade tree sort of tech. He is the tech guru at a large machine shop nearby. Mitsubishi will rebuild the board for about $800.00. I just thought there might be one around out there for less money. Thanks, robind

For this old controls it's better look for old machines on where the owners need to be dispos. Take whole control out of that machine and use the cards what you need

[robind]

Thanks to all who tried to help. I broke down and sent the board in to be fixed. Got it back in 2 days. It's up and running with no more problems.

robind