- Posts: 153
- Thank you received: 0
Servo Spindle motor encoder Mesa 7i76e
PCW wrote: Can you post you hal and ini files?
Here they are. ini file is set to text file for uploading.
Attachment not found
Attachment not found
Please Log in to join the conversation.
or "watch" on these three pins should help track down the issue:
near.0.in1
near.0.in2
near.0.out
Please Log in to join the conversation.
blazini36 wrote: Since you are not using a timing belt you should spin your spindle by hand and let it drive your motor then you can estimate the difference, how accurate you get is all in how thorough you are. Spin the spindle exactly 1 time and look at how many counts feed back from the motor,
A better way would be to set up a halmeter to count the encoder counts, then zero the encoder and rotate the spindle by hand exactly 20 times (or 50 times if you are very patient). Then divide the total counts by 20. The number you get is the number of motor encoder counts per spindle rotation, and that should be accurate enough for most purposes.
Please Log in to join the conversation.
Erikcnc wrote: i got in my hal file near.0.scale 1.50 now, still no green light.
also near.0.difference value is 3.333333)
Have a look at the inputs of the near component with a couple of halmeters. You might see that one is RPM and one is RPS, or possibly one is positive and one is negative.
Please Log in to join the conversation.
andypugh wrote:
blazini36 wrote: Since you are not using a timing belt you should spin your spindle by hand and let it drive your motor then you can estimate the difference, how accurate you get is all in how thorough you are. Spin the spindle exactly 1 time and look at how many counts feed back from the motor,
A better way would be to set up a halmeter to count the encoder counts, then zero the encoder and rotate the spindle by hand exactly 20 times (or 50 times if you are very patient). Then divide the total counts by 20. The number you get is the number of motor encoder counts per spindle rotation, and that should be accurate enough for most purposes.
I'll agree with you on that, average over 20 would certainly be more precise. Same idea either way though.
Please Log in to join the conversation.
PCW wrote: I don't see anything obvious wrong in the hal file but using halmeter
or "watch" on these three pins should help track down the issue:
near.0.in1
near.0.in2
near.0.out
after some other projects i can now continue on the lathe again.
first of all, i hope everyone is doing okay in this situation.
now,
i checkt in hal show the following pins.
only on near.0.in1 i got no respons.
Please Log in to join the conversation.
Are you actually controlling spindle speed from G-code?
Does Halmeter show the spindle speed on the motion.spindle-speed-out-rps pin?
Everything looks like it should work.
Please Log in to join the conversation.
andypugh wrote: Your HAL
Code:net spindle-vel-cmd-rps <= motion.spindle-speed-out-rps net spindle-vel-cmd-rps-abs <= motion.spindle-speed-out-rps-abs net spindle-vel-cmd-rpm <= motion.spindle-speed-out net spindle-vel-cmd-rpm-abs <= motion.spindle-speed-out-abs ... net spindle-vel-cmd-rps => near.0.in1 net spindle-vel-fb-rps => near.0.in2 net spindle-at-speed motion.spindle-at-speed <= near.0.outAre you actually controlling spindle speed from G-code?
Does Halmeter show the spindle speed on the motion.spindle-speed-out-rps pin?
Everything looks like it should work.
also at motion.spindle-speed-out-rps nothing
in my programs i use g97.
Please Log in to join the conversation.
also at motion.spindle-speed-out-rps nothing.
Is the spindle controlled by M3 / M4 and S?
I am failing to see how the spindle can be controlled by the motion.spindle pins but for there to be no output on one of those pins.
Which version of LinuxCNC are you using?
Please Log in to join the conversation.
andypugh wrote:
also at motion.spindle-speed-out-rps nothing.
Is the spindle controlled by M3 / M4 and S?
I am failing to see how the spindle can be controlled by the motion.spindle pins but for there to be no output on one of those pins.
Which version of LinuxCNC are you using?
yes. only thing is that its waiting for the part at a threading cycle. before i switched the encoder it worked fine. excapt that spindle position wasn't correct.
im using 2.4.17
Please Log in to join the conversation.
