- Posts: 6803
- Thank you received: 2181
QTDragon operation notes
2.8 is the current officially released version.
2.9 is close ish - it certainly can be used reliably.
I think you might be missing a library that pops up a message dialog.
If you run linuxcnc/qtdragon from a terminal, it might tell you the library names.
Something like package python-dbus.mainloop.pyqt5
Probing error - that should be a linuxcnc (not qtdragon) problem - sounds like your Z axes acceleration is low. Strange it would be different with AXIS.
There is another probe gcode 38.4 that moves away from the work piece and trips on loss of contact. so probe g38.2 down, then probe 38.4 up, then rapid up. probably more accurate too.
linuxcnc.org/docs/2.9/html/gcode/g-code.html#gcode:g38
There is no guarantee that the line numbers displayed are exact in linuxcnc.
often they are right, but not always.
It's possible to trick linuxcnc to do jog while paused with external offsets - it's a bit advanced but it still doesn't allow origin changes while in auto mode.
We almost had proper built in Jog while paused... but that was a long time ago.
What distribution of linux are you using? Debian? The floating error messages should work in 2.8 - probably just missing the package.
If you could run linuxcnc from the terminal and post the output, maybe I could see the problem.
Chris
Please Log in or Create an account to join the conversation.
2.8/2.9 is the linuxcnc version.
2.8 is the current officially released version.
2.9 is close ish - it certainly can be used reliably.
I think you might be missing a library that pops up a message dialog.
If you run linuxcnc/qtdragon from a terminal, it might tell you the library names.
Something like package python-dbus.mainloop.pyqt5
I'll look into the above when I'm back in the workshop...
Probing error - that should be a linuxcnc (not qtdragon) problem
I'm still working out where the demarcation lines are...
sounds like your Z axes acceleration is low. Strange it would be different with AXIS.
Oops! I didn't mean to mislead. I only switched to AXIS to get the error line number. When I found it was the G0 Z2 code, I found a workaround by playing with the Feedrate & Rapidmove override controls...
I can see how the G38.4 would help. I'll give it a go next time.
We almost had proper built in Jog while paused... but that was a long time ago.
Maybe that can be put back on the table.
What distribution of linux are you using? Debian? The floating error messages should work in 2.8 - probably just missing the package.
If you could run linuxcnc from the terminal and post the output, maybe I could see the problem.
I'm using Debian Buster (as supplied in the LinuxCNC ISO).
I do get the floating error messages.
I will run it again from the terminal to check its current state., when I get back to workshop.
I'm not a Debian guru. OpenSUSE is my flavour - either Leap or Tumbleweed.
I have done the odd Raspberry PI with Debian. But the last one I did was with Leap 15.
Kind regards
Pedro
Please Log in or Create an account to join the conversation.
Apart from the Error about the Basic Probe macro, I can't see any issues... Do you?
Kind regards
Pedro
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Some more notes:
I began to translate some MACH3 code to LinuxCNC, but I’ve hit more issues with the QTDragon GUI. There are some unknown g-codes, so I get this Error Message “unknown g-codes”, but I don’t get the line number nor the bad gcode… Not even a hint of where to look!
The horizontal slide G-code panel doesn’t allow for long lines, therefore, lines truncated.
How do I get LinuxCNC/ QTDragon to save the Fixture on exit, and restore it when restarting?
How do I get LinuxCNC/ QTDragon to save the last job folder, and restore it when restarting?
Does anyone know how to fix these issues?
Kind regards
Pedro
Please Log in or Create an account to join the conversation.