Threading problem
- brianbonedoc
- Offline
- Junior Member
-
Less
More
- Posts: 33
- Thank you received: 2
04 Dec 2015 15:12 #66386
by brianbonedoc
Replied by brianbonedoc on topic Threading problem
It's the Z index pulse in the Hal file.
The following user(s) said Thank You: Iron-Man
Please Log in or Create an account to join the conversation.
04 Dec 2015 15:33 #66388
by PCW
Replied by PCW on topic Threading problem
If you have a spindle encoder, using the encoder velocity hal pin is a better way to get spindle
velocity than the index pulse (which will be too short to sense on a high resolution encoder)
velocity than the index pulse (which will be too short to sense on a high resolution encoder)
The following user(s) said Thank You: Iron-Man
Please Log in or Create an account to join the conversation.
04 Dec 2015 16:08 #66392
by Iron-Man
PCW thanks, I do have a high resolution encoder (2000ppr x4). I repaired it and changed it for differential output . I believe that I now have the correct hal pin set to velocity. I just need to connect the correct function to the pathpilot GUI. Threading is working but, shows no change in the RPM window.
I followed the example on NYC CNC, NYC CNC Hopefully I can sort this out later today.
Thanks,
Iron-Man
Replied by Iron-Man on topic Threading problem
If you have a spindle encoder, using the encoder velocity hal pin is a better way to get spindle
velocity than the index pulse (which will be too short to sense on a high resolution encoder)
PCW thanks, I do have a high resolution encoder (2000ppr x4). I repaired it and changed it for differential output . I believe that I now have the correct hal pin set to velocity. I just need to connect the correct function to the pathpilot GUI. Threading is working but, shows no change in the RPM window.
I followed the example on NYC CNC, NYC CNC Hopefully I can sort this out later today.
Thanks,
Iron-Man
Please Log in or Create an account to join the conversation.
07 Dec 2015 21:51 #66586
by Iron-Man
I will give it another try tonight. Everything seem to be working, threading, CS speed etc, except I do not see any RPM in the read-out.
Thanks,
Iron-Man
Replied by Iron-Man on topic Threading problem
It's the Z index pulse in the Hal file.
I will give it another try tonight. Everything seem to be working, threading, CS speed etc, except I do not see any RPM in the read-out.
Thanks,
Iron-Man
Please Log in or Create an account to join the conversation.
- brianbonedoc
- Offline
- Junior Member
-
Less
More
- Posts: 33
- Thank you received: 2
07 Dec 2015 22:18 #66587
by brianbonedoc
Replied by brianbonedoc on topic Threading problem
I have an issue if the RPM is too high (>1700) i don't get a readout either. Maybe due to the speed of my Proximity switch used for the index pulse?
I have not bothered to investigate as mostly I am below that speed.
I have not bothered to investigate as mostly I am below that speed.
Please Log in or Create an account to join the conversation.
08 Dec 2015 13:39 - 08 Dec 2015 13:40 #66617
by Iron-Man
Replied by Iron-Man on topic Threading problem
I believe that this is the proper line in the post-gui hal file:
# spindle RPM during program execution comes from encoder
net spindle-velocity => tormach.spindle-speed-out
Threading is working, just no RPM display during active gcode running. When program stops, then the rpm shows in the window. Will dig deeper into the code and find out why rpm not showing.
I will move on to connect limit switches etc.
Will post some simple video and pictures.
Iron-Man
# spindle RPM during program execution comes from encoder
net spindle-velocity => tormach.spindle-speed-out
Threading is working, just no RPM display during active gcode running. When program stops, then the rpm shows in the window. Will dig deeper into the code and find out why rpm not showing.
I will move on to connect limit switches etc.
Will post some simple video and pictures.
Iron-Man
Last edit: 08 Dec 2015 13:40 by Iron-Man. Reason: sentence structure.
Please Log in or Create an account to join the conversation.
- brianbonedoc
- Offline
- Junior Member
-
Less
More
- Posts: 33
- Thank you received: 2
03 Jan 2016 21:03 - 03 Jan 2016 21:05 #67774
by brianbonedoc
Replied by brianbonedoc on topic Threading problem
I finally got to figuring out my RPM issue. As you recall I could view accurate RPM up to about 1700. Above that then the display wouldn't read properly. At first I thought it had to do w/ the index pulse or proximity sensor that I was using for the index pulse. This was incorrect as I am using the ENCODER pin for the velocity as Peter stated (hm2_5i25.0.encoder.00.velocity).
The issue was my filter setting. Here is the original HAL area:
# as per Peter Wallace to reduce encoder errors from noise
# use the 'raw' interface to set the encoder filter higher to ignore more noise
# this sets how long an encoder signal needs to be stable to be accepted
# register 0x3400 is QfilterRate decimal 13312
# count rate is ClockLow/(QfilterRate + 2)
# ClockLow is 33 MHz
# setting the filter to 38 (decimal) will allow the encoder to function well past 100 kHz
# lathe encoder is 1024 pulses per rev, 3000 RPM is 60 kHz
#
setp hm2_5i25.0.raw.write_address 13312
setp hm2_5i25.0.raw.write_data 38
setp hm2_5i25.0.raw.write_strobe TRUE
Because my encoder is 4x that of the original tormach one (1024) I figured the FILTER to 38 would have to come down a bit.
So I changed the 38 ---> 19 (arbitrarily) and Now I get accurate readings >2400.
(setp hm2_5i25.0.raw.write_data 19)
The issue was my filter setting. Here is the original HAL area:
# as per Peter Wallace to reduce encoder errors from noise
# use the 'raw' interface to set the encoder filter higher to ignore more noise
# this sets how long an encoder signal needs to be stable to be accepted
# register 0x3400 is QfilterRate decimal 13312
# count rate is ClockLow/(QfilterRate + 2)
# ClockLow is 33 MHz
# setting the filter to 38 (decimal) will allow the encoder to function well past 100 kHz
# lathe encoder is 1024 pulses per rev, 3000 RPM is 60 kHz
#
setp hm2_5i25.0.raw.write_address 13312
setp hm2_5i25.0.raw.write_data 38
setp hm2_5i25.0.raw.write_strobe TRUE
Because my encoder is 4x that of the original tormach one (1024) I figured the FILTER to 38 would have to come down a bit.
So I changed the 38 ---> 19 (arbitrarily) and Now I get accurate readings >2400.
(setp hm2_5i25.0.raw.write_data 19)
Last edit: 03 Jan 2016 21:05 by brianbonedoc.
Please Log in or Create an account to join the conversation.
Time to create page: 0.289 seconds