Advanced Search

You can link both sense0 and strobe with something like:

Though I think that strobe defaults to high, so can often be left unconnected.

Thank you for the helpful hal commands.  Here are the contents of the before and after home text files.

You might want to insert the carousel in one of these loops.
(depending on the style of the toolchanger)

Often you will have
This is not always the case, though.
The tool-prep handshake is typically used with random toolchangers, where there is a tool swapper. If you need to put away the current tool first, then tol-prep will be looped, and the logic will be in the tool-change handshake.

You should probably toggle "tool changed" from your tool-change ngc file. That ensures that the system stops if there is a failure in the tool change routine.

The issue is in the hal... i delete the hal with failures ... not that someone use it and wondering...

I will try both,  thank you! Ill post about the results and those files. 

i have only sense 0 and sense 1 linked. sense 0 is index and sense 1 is the sensor on the slotted disc. i use index configuration.

strobe is everytime high. i dont know to what i need it to llink. sense 1 and strobe together?!

Failures in ngc.. i delete

Ich kann Deutsch lesen

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

Are you sure that EVAL[.....] is valid? Is that documented somewhere?

I don't recognise it as one of the documented unary functions, but can see examples of its use on the forums. I know that py and pyrun exist (I can see them in the source code, they may not be documented) but eval has me stumped.

I'm going to open it up under the Elastic License 2.0. The repo isn't public yet because the internal API is a mess and running it locally is not trivial. So for those that are wary of web services I'll also include a script to make running it locally easy.