- Joined
- Jun 10, 2019
- Messages
- 539
I'm having an issue with my Prototrak where the Y-axis slows down when moving in a Y-minus direction only. My question is somewhat platform independent, however.
I confirmed the the DRO functions correctly and there isn't any problem moving the table manually in either Y direction. I looked for loose or suspect wiring in the controller plugs, within the end-cap of the servo, etc.. I then swapped all leads between X and Y axis (power, DRO, comms) in an attempt to isolate the problem to the Servo vs. Cables/brains. However, the Prototrak will not operate normally if you do this (the axis will start to move, but then immediately show a fault code; I assume because it's expecting a certain rate given the axis input and swapping everything results in the maths not working for that axis...just a guess? this is true of both X and Y). My next brute-force debug will be to physically swap the servos.
Anyway: I first just wanted to know if the slow-down behavior for only one direction tends to be generally be a symptom of the servo, wiring, or controller. My knowledge is elementary but I generally am thinking its most likely the servo. My first though is that the encoder in the servo may not be functioning correctly in only 1 direction. Is that likely? Are there other more likely culprits?
The symptom is easily reproduced with a jog in the Y-minus direction. The servo sound like it spools up to max feed rate for a fraction of a second (you can hear it), but then immediately reduces to a slower feed and maintains that slow feed during the jog. e.g. at 100% (100 IPM), the feed drops to something relatively high (60-70%)...it doesn't continue to drop during that 1 jog operation. If you keep re-trying new jog ops, the reduced speed eventually will get slower and slower. It may be worth nothing that if the the "slowed" speed is still relatively high (set 100%, but runs at 60%), if you drop the feed 50%, then the moves will work for a while (set 50%, runs at 50%). But eventually the problem starts to occur even if the set feed rate is 50% (e.g. it will run lower than 50%). It does eventually get as low as 10%. The numbers in my example are not exact...the slow speed will be all sorts of random, slower feed rates.
This problem will occur on immediate start-up of a cold mill and affects all operations (mill, circle, arc, etc…) whether its singular or a compound move. Y-plus moves work perfectly fine all the time.
I confirmed the the DRO functions correctly and there isn't any problem moving the table manually in either Y direction. I looked for loose or suspect wiring in the controller plugs, within the end-cap of the servo, etc.. I then swapped all leads between X and Y axis (power, DRO, comms) in an attempt to isolate the problem to the Servo vs. Cables/brains. However, the Prototrak will not operate normally if you do this (the axis will start to move, but then immediately show a fault code; I assume because it's expecting a certain rate given the axis input and swapping everything results in the maths not working for that axis...just a guess? this is true of both X and Y). My next brute-force debug will be to physically swap the servos.
Anyway: I first just wanted to know if the slow-down behavior for only one direction tends to be generally be a symptom of the servo, wiring, or controller. My knowledge is elementary but I generally am thinking its most likely the servo. My first though is that the encoder in the servo may not be functioning correctly in only 1 direction. Is that likely? Are there other more likely culprits?
The symptom is easily reproduced with a jog in the Y-minus direction. The servo sound like it spools up to max feed rate for a fraction of a second (you can hear it), but then immediately reduces to a slower feed and maintains that slow feed during the jog. e.g. at 100% (100 IPM), the feed drops to something relatively high (60-70%)...it doesn't continue to drop during that 1 jog operation. If you keep re-trying new jog ops, the reduced speed eventually will get slower and slower. It may be worth nothing that if the the "slowed" speed is still relatively high (set 100%, but runs at 60%), if you drop the feed 50%, then the moves will work for a while (set 50%, runs at 50%). But eventually the problem starts to occur even if the set feed rate is 50% (e.g. it will run lower than 50%). It does eventually get as low as 10%. The numbers in my example are not exact...the slow speed will be all sorts of random, slower feed rates.
This problem will occur on immediate start-up of a cold mill and affects all operations (mill, circle, arc, etc…) whether its singular or a compound move. Y-plus moves work perfectly fine all the time.