Advanced Search

papagno-source wrote:

If I command m3 s1000 and after g33.1 z-50 k1, the tapping is not performed correctly, the spindle turns in m3, the z reaches -50 and no longer returns to z +, I send back with the spindle rotating.

 

Do you mean that Z makes an unsynchronized move to -50 and then just sits there?  Does the spindle reverse?

Have you checked the spindle-at-speed signal/pin during the improper tapping process?

I'm interested in your problem as I (and others) have noticed some issues with spindle synchronized moves.  Mine has cleared up somewhat from my first tests, but I suspect that LCNC's code for spindle synchronized moves (G33, G33.1, G76) do not calculate the appropriate spindle angular position for the start of synchronized movement.  There may be other problems, too.

Unfortunately, I'm not able to critique (or really understand) LCNC's trajectory planner code for tapping/threading - I've no real programming experience.  But a review of old github issues and threads on the Developers' mailing list indicates this may be a old - but still present - issue.

Here are a couple of recent threads you might be interested in reviewing:
forum.linuxcnc.org/38-general-linuxcnc-q...pping-problem#319620

forum.linuxcnc.org/38-general-linuxcnc-q...es-with-speed#317088

If you can offer any insights I'm all ears.

I have an old lathe that I run using linuxcnc with gmoccapy as the display.
I am trying to get the speed display working but it wont start and gives the error 'pyvcp_options.hal:16: Pin 'pyvcp.spindle-speed' does not exist'
If I '#' out that line and another one that gives the error 'pyvcp_options.hal:24: Pin 'pyvcp.spindle-at-speed-led' does not exist' then it starts and works as needed but I don't have the speed displayed.
I used stepconf to create the files and am using LinuxCNC 2.9.4 [Debian 12 Bookworm PREEMPT-RT ISO]
Can anyone point in the direction of a fix please?

loadrt not count=2
addf not.0 servo-thread
addf not.1 servo-thread
net my-input-signal-1 <= not.0.in hm2_7i92.0.encoder.03.input-index
net inverted-signal-1 => not.0.out min-y

net my-input-signal-2 <= not.1.in hm2_7i92.0.encoder.04.input-index
net inverted-signal-2 => not.1.out max-z

Two mistakes there, one mine as i forgot to tie the signals together and yours = do not add or remove stuff randomly, xxxxx does not exist as a pin or function or parameter or anything.
Is the above easier to follow?

Found the problem, as for my VFD pwmgen output has to be inverted (setp hm2_7i95.0.pwmgen.00.out0.invert_output true), after that scale started to work in right direction.