QTDragon operation

qtdragon does not support 5 axis yet. I'm working on it.

Thanks Rod!

In this case, as cmorley just confirmed, it's probably a 5 axis problem, so I will wait for this exciting work to get a little farther along. (I guess I'm going to break out some manual macros for now).

Sorry about the confusion on the pendant, it doesn't have anything to do with extra axis... I only meant that my configuration is complex enough because I have a pendant hal file on top of the basics that I might well have caused my own problem.

Also, I tried the "linuxcnc -l" trick... but because it crashed before it could start, when I use that command I get the last working configuration, which doesn't have these helpful error messages.

So in this case  I had to try the full command with the path to the .ini file, and the contents of that terminal window is attached. The log files didn't show up where the messages in the terminal said they would be. 
 

I just pushed to 2.9/master, modifications to qtdragon (not hd) for displaying/screen jogging 5 axis.
axis 4 and 5 can be any axis (besides XYZ)
I have included sample configs for xyzab and xyzac,
I've only tested basic moving/homing in simulation- I don't have a 5 axis machine.

If anyone tests please give feedback.

I'm having an error pop up, but if I click close, everything seems fine.

So it's a low priority... but... what the heck is it?

When I click the ESTOP - Set button, or the ESTOP - Rest button, or the Machine On button (but not the Machine Off button, ie, I'm turning it from On to off) I get a small modal window message: Operator Error, Bad Character 0 used. There are three button options: Show Last Five, Clear, and Close. If I Close or Clear the message box closes, and if I'd clicked Clear then the next time the message box appears, there's only one "bad character 0" line.

I'm on LinuxCNC ver: 2.9.0~pre1.1076.gcb0aa52ce, & Debian 12

Is this a sample config or your own ?

Do you have an 'on_abort' file in the config folder. it would be called in those button situations - maybe there is an O instead of a zero somewhere.

reading the terminal text after running from a terminal may give a clue.

I have pushed the work to fix the buttons of the 4th and 5th axis.

It is my own.

I do have an "on_abort.ngc" file, copied from the QTDragon install page, and located in the configuration subdirectory nc_subroutines.

Though that error appears, the machine so far seems to be operating (ie, it's jogging), but I'm still trying to set up and use the probe routines.

First question might need to move to the tool/probe thread: I've been able to get the basic tool probe motion motion to work: Go to Tool Tab, click the tool and load it with M61 On, then click Touch Plate... it goes through the proper motions, but it doesn't fill the Z offset for the tool. I have the touch plate height filled in, I would have thought the tool offset would be the absolute Z minus the touch plate height. I'm still trying to sort out what I'm missing there.

Second question (it's a set) because in the process of getting to the first question, I've found more errors, I haven't been able to sort these out either:

1. From the Tool Probe screen, when I click the option to "Go To Tool Setter" I get the Operator Error: "Probe Routine: Missing toolsetter setting: z_max_clear"    (I haven't found that yet)
2. When I go to Offsets tab, the Tool Sensor X/Y location is not the one I put in the .ini file, so I put it in.
3. After that, when I press "Go To Sensor" my machine times out... is there a place to change the CALL_MDI_WAIT timeout? Is that advisable? Sometimes the log file says the timeout was 5 seconds, and sometimes it was 10 seconds. Why two different times?

(I have a very strangely shaped machine: super tall and long, so this 'timeout' thing makes sense to happen to few other people)

I'm attaching the terminal log, the .ini file, and the .hal files.

Thanks for any help.

(Sorry it took me so long to respond, it's been hurricane prep her in sunny southern California. wow. )