Advanced Search

There's an old thread here that may give some ideas:

forum.linuxcnc.org/24-hal-components/280...n-cleanup-using-comp

I get the carousel.comp working with the toolchanger.

It homes and couunts correct... spindle orient before lift up to the gear to dont crash.

All sensor stuff is linked in a remaped m6 ngc and communicate with m64 m65 and m66 between ngc and hal and carousel.comp.

There is a and2 fuction which gives the carousel the enable signal.
This and2 swirches when the hardware sensor gets true that tell that the carousel is in disengaged position. This means the carousel is connected with the gear to maindrive and the tool is released from the spindle sk30.



Next step is to make the stuff working with the main drive.. think its some stuff with mux2 and xor2.

The spindle is synced and can orient. Its a full servo spindle.

PCW, thanks for your reply!

Is there any example for this solution with userspace hal component?

thank you very much. I really wanted to multiply the two signals but I didn't know the commands. now I understand and I will try.

something went wrong with the screen shot
 

Hello Chris,

After experiencing issues with other software on my computer, I decided to perform a fresh installation using the current DVD version 2.9.4.
Unfortunately, I'm once again encountering problems with Z-Level Compensation.
After creating the “probe_points.txt” file, I can enable “Z-Comp”, but the value in the “Z_Axis Comp” field does not change as expected. Once “Z_COMP” is turned off, it cannot be reactivated without restarting the program.
Do you have any idea what might be causing this?

With this installation, I also tried the touch plate function. It’s visible that after probing the touch plate, the program sets the Z value to the height of the touch plate before executing the retract. This causes the retract value to be added, and the resulting height above the object is correct.
Unfortunately, the program then subtracts the length of the current tool, which in my case is not useful.
Is it possible to disable this behavior?

Thank you very much for your support.
Best regards,
Klaus

Thanks for your reply.
This is the result on the workpiece
 

So this is my setup:
 

Hello,

For me, he basically does the first (rough measurement) until the step comes back, this is no longer carried out, regardless of whether the workpiece height or tool length and the whole sporadically.
It happens that I finish several parts with the same program and the first or two run through and then it caught or just caught.
If you wait, a timeout comes as described.
At the moment I only come out when I end Linuxcnc, I haven't tried something else yet.
I suspect something swallows in the order.
I have already discharged the trial entrance, but that was also unsuccessful.
I'll try to implement this with the spindle and see what happens.

Until then, greetings to everyone, Frank

For other random probe failures, see also github.com/LinuxCNC/linuxcnc/pull/3537

h_munktell wrote:

[code]Interestingly, G38 moves is not dependent of spindle-at-speed signal, do not know if this is intentional or a bug in linuxcnc code.

[/code]

That does seem inconsistent, but at the same time you almost always _don't_ want the spindle to spin with the probe loaded. Especially if it's a wired probe. 
 

pinterluca wrote:

I'm installing a 20w laser on my CNC and I control the power of laser using the spindle pwm. The software LightBurn use M67 to control the laser power. 

Which of these do you want to use? They aren't really compatible. 

You could use the spindle-override controls indirectly, using a HAL "scale" component to multiply the motion.analog-out.NN pin by halui.spindle.N.override.value
linuxcnc.org/docs/stable/html/man/man9/scale.9.html
linuxcnc.org/docs/stable/html/man/man1/h...l#Spindle%20Override

The xml file from stepperonline is for something else.
You need a xml file that maps the linuxcnc internal "pins" to the drives PDOs.
There are numerous examples if you search for "A6 ethercat-conf.xml" in this forum. You can start with one of these and then adapt to your needs.

check with command "ethercat slaves". Errors show up in syslog.

You can set SDOs permanently with "ethercat download".
There can be a maximum of 10 PDOs in the xml file.

You may be seeing a problem caused by the G-code preview. That runs through the code to draw the lines, but won't update values based on probe results etc (as it doesn't _move_ anything).

The trick here is probably
Which will end the loop early in preview generation.

linuxcnc.org/docs/stable/html/gcode/over...ub:system-parameters

Since it's not realtime, you should be able to make a simple (python?) userspace
hal component using the kernels serial driver.