Advanced Search

Maybe the real sensors have a different polarity to your bench test setup?
Halscope should help understand what is going on, if you scope the inputs and the carousel.0.state (with reference to:
github.com/LinuxCNC/linuxcnc/blob/2.9/sr...s/carousel.comp#L309

No feedback from other users so far but the workaround disconnecting the 'joint.n.index-enable' (where n is the joint for the caxis) certainly worked for me.
Note though that I have since dismantled my test setup, so no further testing has been done on my part.

[edit]
I have now filed an issue on git:
github.com/LinuxCNC/linuxcnc/issues/3556

The docs are quite clear that 1,2,3 is valid for a home sequence. But just as a test, can you try 0,1,2 ?
(Though it's all a bit odd, as the files show that homing has completed) 

 

yes strobe is always high thats why i never connect it. now i hae connect it with sense-01 which is the counter.

the stuff about linking into tool-prep stuff i would done when everything works... but fromm there i am far away.. on the table with switches it works.. on the machine... it shoots over.. or stops in the middle ... cant discribe .. its terrible... thats why i was thinking to debounce via hardware like its original.. original control works flawless.

cmorley wrote:

I'm curious, Why aren't people working on the version in linuxcnc?
github.com/LinuxCNC/linuxcnc/tree/master...n-panels/versa-probe

Well, until 3 days ago it was GTK2. 

I can't remember why I chose to work with a different version, except that I think I assumed that PSNG was enhanced relative to VersaProbe. 
 

You can install Mate on Debian as easy as:
sudo apt update
sudo apt install mate-desktop-environment mate-desktop-environment-extras lightdm lightdm-gtk-greeter
log out, choose Mate for desktop environment, log in . This needs to be done only once if you want to continue using Mate. If you want to go back to XFCE, log out, change, log in.

scotth wrote:

 Watching what happens with an AC vent hitting the top of a machine with a laser will drive you crazy.
 

Skunkworks implemented temperature compensation on his (large) mill a long time ago. 



 

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