This is the second time my 6042 has fried it's X motor. Last time was about 2 months ago. It starts out as giving random X CURRENT errors after a job is done as it goes to park the carriage at the origin. Never during a job. This motor gave the error 2 times before then burning out.
Any ideas what it could be?
The motor connects to the mainboard on CN14, encoder is on CN15. None of the wires or connectors look bad. If the MOSFET bridge on the mainboard that pulses the motors were stuck or bad it would never work. The chances of it randomly sticking after all this time are low.
Power supply voltages are in range on both power supplies for the +35v lines. But I think it's only the main supply that powers the X motor anyway.
I am going to clean and oil the side rails, and also clean out all the grease on the linear bedscrew the X motor drives. Then relube it with Mobilux EP1. My thinking is as the X motor rehomes the carriage it's either hitting a tough spot or getting some resistance near the end deceleration, which is either causing it to overdrive the motor or make regenerative power. Hence the X CURRENT error only on that spot.
Additionally, I may move the origin down the bed 3 inches to prevent the carriage from having to travel on that part of the rail if there is a rough spot. Wouldn't prevent the hard deceleration though.
Firmware is 1.9, looks like ChatGPT claims v 2.4 fixed a deceleration issue so maybe this was a known bug. Of course Mimaki in their infinite wisdom does let us mere mortals have access to such things like service manuals for their unsupported models so I'll stay at 1.9.
I have another spare motor, power supply, and mainboard ordered in any case. My plan is after cleaning put a new motor in and jumper the cables to a voltmeter and just leave it running to see what voltage happens. Motor is rated at 24V so anything appearing on the lines over gives a clue. If that fails again all I can think is change the mainboard/power supply.
Any ideas what it could be?
The motor connects to the mainboard on CN14, encoder is on CN15. None of the wires or connectors look bad. If the MOSFET bridge on the mainboard that pulses the motors were stuck or bad it would never work. The chances of it randomly sticking after all this time are low.
Power supply voltages are in range on both power supplies for the +35v lines. But I think it's only the main supply that powers the X motor anyway.
I am going to clean and oil the side rails, and also clean out all the grease on the linear bedscrew the X motor drives. Then relube it with Mobilux EP1. My thinking is as the X motor rehomes the carriage it's either hitting a tough spot or getting some resistance near the end deceleration, which is either causing it to overdrive the motor or make regenerative power. Hence the X CURRENT error only on that spot.
Additionally, I may move the origin down the bed 3 inches to prevent the carriage from having to travel on that part of the rail if there is a rough spot. Wouldn't prevent the hard deceleration though.
Firmware is 1.9, looks like ChatGPT claims v 2.4 fixed a deceleration issue so maybe this was a known bug. Of course Mimaki in their infinite wisdom does let us mere mortals have access to such things like service manuals for their unsupported models so I'll stay at 1.9.
I have another spare motor, power supply, and mainboard ordered in any case. My plan is after cleaning put a new motor in and jumper the cables to a voltmeter and just leave it running to see what voltage happens. Motor is rated at 24V so anything appearing on the lines over gives a clue. If that fails again all I can think is change the mainboard/power supply.
