Advanced Search

Hi Phil,

Thank you. I checked the HAL pins and it looks like the feed reduction pin is connected to the motion pin. I will bring it up in advanced configuration, hopefully that gives us some clarity.

Love your work !

Cheers, Peter

Hmmm, I don't understand what is going on. This is what you should see:


It may be worth asking in a different forum section as a M67 issue, either Basic Configuration or Advanced Configuration as more folk will probably notice it. I am fairly certain that there is nothing we do which would affect M67 operations. In the meantime I will keep experimenting but not being able to replicate the issue makes it difficult.

Hi Phil,

Same result on the motion.analog-out-03 pin.

Cheers, Peter

The feed-reduction pin should be directly connected to motion.analog-out-03 which should be switched by the M67 E3 Qn g-code commands.

Could you look at motion.analog-out-03 with HAL Meter and see what it does.

They do change state correctly here.

Hi Phil,

I had a chance to make up a video with HAL Meter and the feed reduction stays at 60% except for the last leg.

Cheers, Peter

could you use Switchable kinematics ?

for example you can run the millturn configuration - it rotates the Z axis on 90 degrees.

linuxcnc.org/docs/html/motion/switchkins.html
linuxcnc.org/docs/html/man/man9/millturn.9.html

 
 

Could try this change and remove the resume (line 21).
I might need to make a separate resume pin for you for this case.
or add some logic to convert the pause/resume pins to one pin that is true for pause and false for resume.

The halui.pause nad halui.resume are coming from the xhc-whb04b-6.hal file.

I'm not sure how to change those entries.

17 # program related signals
  18 net pdnt.program.is-idle                  whb.halui.program.is-idle             halui.program.is-idle
  19 net pdnt.program.is-paused                whb.halui.program.is-paused           halui.program.is-paused
  20 net pdnt.program-is-running               whb.halui.program.is-running          halui.program.is-running
  21 net pdnt.program.resume                   whb.halui.program.resume              halui.program.resume
  22 net pdnt.program.pause                    whb.halui.program.pause               halui.program.pause
  23 net pdnt.program.run                      whb.halui.program.run                 halui.program.run
  24 net pdnt.program.stop                     whb.halui.program.stop                halui.program.stop
 

谢谢，已经研究明白了

Mark - you're running a LCNC version pre-joint/axis?

EDIT:

I'm not familiar with pre-joint/axis configs, but one thing I noticed in your HAL files is that it looks like there's a mismatch between the INI and HAL axis numbers.

Vertical:
INI - Y is axis_1
INI - Z is axis_2
HAL - Y is axis_1
HAL - Z is axis_2

Horizontal
INI - Z is axis_1
INI - Y is axis_2
HAL - Z is axis_2
HAL - Y is axis_1

Make sense?

It is looking a bit ugly but it seems to do what you need:

加我QQ：304394405我远程给你配置

Do you have halui.pause or resume pin connected somewhere?
from the docs:

If using the Spindle lift option, HALUI can not be used to pause/resume the program. There is a pin, QtDragon.external-pause available to pause/resume from an external source. You must also enable external offsets. In the setting tab check use external offsets

also for qtdragon_hd line 41 should be un commented

The files real name is .axisrc (note the leading dot which makes it a hidden file) and it goes in the users home directory. If it does not exist then create it.
Both commands will work from ~/.axisrc and will be applied to every LinuxCNC config.
 

I understand, but I didn't identify any file called axisrc, just create it? Does it need to be in a specific folder? Will the root_windows command you mentioned be inside this file too?