Advanced Search

i had debounce the proxmitiy sensors in the HAL with debounce.. value is 5.

then i think we need to talk about my toolchange.ngc.
do you want it in english or german... because i wrote all comments in german).

thanks andy

It might be worth debouncing the proximity sensor signals in HAL. (there is a "debounce" component.

The "strobe" pin is an indication that the position inputs are valid. During positioning of a binary or gray-coded carousel there may be transient values on the inputs (caused by the sensors not all seeing new edges at the same time) that would indicate incorrect positions. The "strobe" pin is a shorter pulse that indicates that the position encoder sensors are centred on their targets and will be reporting the true position. It will also indicate that the carousel is correctly aligned on an actual pocket.

In that case the fix should be in the just-released 2.9.5 release. (so you probably won't have to build from source again)

There may be some info here: www.forum.linuxcnc.org/48-gladevcp/28429...-hot-keys-on-widgets

But skimming it doesn't look particularly promising.

I haven't made helical gears, but I am sure I could if I wanted to. It's just a matter of increasing the hob angle and adding in a proportion of the feed distance into the gear blank angular position.

Some links: My first YouTube video (filmed with a potato) where I explain the concept.



The current, much improved setup:



A screenshot of my (written just for me, so not very pretty) GUI. Of note is the top left section that calculates gear parameters based on entries in any gear system (mod, dp, cp). You will see that helix angle is included in the settings, but is currently not implemented.

wiki.linuxcnc.org/uploads/Screenshot.png

And all the files that are used are here:
wiki.linuxcnc.org/uploads/hobbing.zip