Advanced Search

Unfortuately HALUI doesn't integrate well with guis.
Overrides changes in HALUI will show in QtDragon but not HALUI jog speed.
There has been some work on this recently but it hasn't made it in linuxcnc yet.

It's possible to add custom code/pins to qtdragon to help with integration.
Can you be specifics about what you need?

Looks fantastic in pics! haven't trued it yet.

Always interested in contructive feedback good or bad - really am.
But stuff like this makes me shake my head a bit.

Compiling problems aren't usually QtDragons fault - you didn't  mention what system you are compiling in so no one could help or evaluate the problem.

I'm sorry Qtdragon didn't suit you out of the box, but there is quite alot you could change.
For instance based on your pic, you could turn on the machine and home it, then the colors change from disabled to enabled and look like this:

 

Qtdragon has optional stylesheets to easily change colors, there are several built in.

If fonts are a problem you can change them too.
linuxcnc.org/docs/stable/html/gui/qtdragon.html#_stylesheets

If you asked nice I bet someone would have even helped you get something that works better for your eyes.

Or don't use it at all. Choice is yours. 
 

Look on the start page, should be a checkbox for 'advanced pages'
check that box on, then extra pages will be shown in sequence.

In my script, with G59.3, after I do those three lines, the only other thing I do is a quick G43 (no H needed) to reload the just-modified table entry.

If this is a 7I96 and not a 7I96S, you would need 7i96_inmd.bit firmware installed.
has this been done?
 

 Thank You for you input, I copied and made a separate tool_change.ngc for testing this tool probe in G59.3 somehow I was able to get that to probe and go back to previous WCS but my measure is still off tool tip about 9.5mm below Z0. My question is do I remove #<tool_length> = [#<spindle_setter_z> - #<setter_touch_machine_z>]p, li { white-space: pre-wrap; }hr { height: 1px; border-width: 0; }li.unchecked::marker { content: "\2610"; }li.checked::marker { content: "\2612"; }and update ; Write the measured length to the selected tool-table entry.G10 L1 P#<selected_tool> Z#<tool_length>p, li { white-space: pre-wrap; }hr { height: 1px; border-width: 0; }li.unchecked::marker { content: "\2610"; }li.checked::marker { content: "\2612"; }with G10 L1 P[#<_selected_tool>] Z[#5403 + #5063]

just want to be clear
Thankyou


 

Thank you for all the help over the years you have given me.

Thank you for all the contributions you have made here on the forum over the years.

Your support has been excellent!

Hello,
I am trying to set up my LinuxCNC control system with a Mesa 7I96 using pncconf. I’ve seen in several threads that there is an "external controls" page in pncconf where you can configure things like handwheels. However, I am unable to access this "external controls" page. What am I doing wrong? Could someone help me find it?
Thanks,
Hans

Hello,
i have install LCNC with a 7I96 for a lathe. There a two mpgs connected the first mpg on pin 0 + 1 and the other mpg on pin 2 + 3 from connector
TB3. Is there a sample for the hal-file to use the mpgs for nturning in manual mode?
Thanks
Hans

Thank you for approving it, tommylight - and for being upfront about it being paid software. That's exactly how I wanted to present it.

If anyone has questions, finds a bug, or thinks a cycle behaves wrong on their machine, please post here - I'll answer and fix what I can.

I have approved this, it is for payed software with a trial version, so if anyone has anything against it, let me know.
Thank you.

chattr +i foo.hal

That prevents linux itself from modifying the file (even as root) until you -i it.
But as Rod said, once you start manually editing it, you can't use the wizards any more.

I've got some general observations which you may or may not already know, and some specifics from my setup which does basically the same thing.  Note: I'm not an expert, I just spent a lot of time trying to wrap my head around how this all works

Remember that #5063 is in the current WCS coordinate system, NOT the machine coordinate system, and not always G54.  To get the machine Z, you need to undo this correctly. Also note that the current location after a probe hit is NOT the same as the location stored in #5061 et al.  The probe needs some time to stop, so it's always past the probe point when you read "current position".
As for probing for tool length, it turns out you don't need ANY of that.  All you have to do is probe the toolsetter, and offset the tool length by the amount the probe is off by, in a known coordinate system.  I dedicate G59.3 to be "where the toolsetter is" and, in G59.3, do this:If you don't want to do that, you need to know the machine Z of the toolsetter (which you do) and do the math to undo the probe point (undo the WCS offset and tool offset), then set the tool length to be the offset from where you expected the toolsetter to be.
Remember that "machine Z" = "probe hit Z" + "WCS Z" + "tool offset Z" so you need to know which WCS and tool offset is in effect when you probe.  Yes, keeping track of which way to apply the offsets can be tricky.  Remember that offsets are always added to where you want, to get where the machine goes.  A longer tool as a more positive (usually "bigger") tool offset to move the spindle more in the +Z direction ("up").
Remember that you're not always in G54.  You can use #5220 to compute a parameter for the current WCS.  Your current WCS Z is #[ 5200 + #5220 * 20 + 3 ]
I use G70 and G72 to save and restore the machine's modal state during tool changes, so I don't mess up a running program by changing something important and not setting it back.
Also, you most certainly CAN probe the toolsetter with the 3d probe to calculate its length.  I do this all the time.  You just have to make sure the probe "hits" when either probe is tripped, as one will trip before the other but you don't know which.  You don't need to use the 3d probe's length in your tool length offset, the 3d probe is just another tool.  Reference off a known fixed location in machine space (your spindle_setter_z), not some other tool's arbitrary offset.  The 3d probe has its own tool offset when it's loaded, just like any other tool.