QTdragon Tool Probe X & Y Offsets

More
2 years 6 months ago #299353 by garja
I'm using QTDragon for tool probing. The probing works great. The issue I'm dealing with is when I specify where the sensor is located, such as x0.3493 and y0.5298 in the user interface, and select Go To Sensor, it always goes to x0.0137 and y0.0208. Regardless of where I tell it the sensor is located, it always goes to the same X & Y location. I've searched through all the files to see if I could find somewhere it would allow me to change the settings. I cannot find where it is getting the location it's going to. I can find in the qtdragon.pref where my settings x0.3493 and y0.5298 are located but changing them never results in getting to the right location when select go to sensor. Any help?

Please Log in to join the conversation.

More
2 years 6 months ago #299373 by cmorley
What version of linuxcnc and how did you get it?

Is your machine imperial based? There was a fix for (what sounds like) this, that has not been released yet.
It looks like the position is out by about 25.4 times.

Please Log in to join the conversation.

More
2 years 6 months ago #299403 by garja
Thank you Chris for your reply. I am using Imperial. I downloaded Debian Bookworm Preempt-RT ISO 12.4 from the Linuxcnc website. The Linux version is 2.9.2I believe the Debian version. I've tried to make various changes based on percentages ext but regardless of what I change the numbers to, when the machine locates to the X and Y, it always goes to x0.0137 and y0.0208.

Please Log in to join the conversation.

More
2 years 5 months ago #299437 by cmorley
in 2.92 this is the python code called:
Code:
    # offsets tab     def btn_goto_sensor_clicked(self):         x = float(self.w.lineEdit_sensor_x.text())         y = float(self.w.lineEdit_sensor_y.text())         if not STATUS.is_metric_mode():             x = x / 25.4             y = y / 25.4         ACTION.CALL_MDI("G90")         ACTION.CALL_MDI_WAIT("G53 G0 Z0")         command = "G53 G0 X{:3.4f} Y{:3.4f}".format(x, y)         ACTION.CALL_MDI_WAIT(command, 10)

The bug fix:
Code:
    def btn_goto_sensor_clicked(self):         x = float(self.w.lineEdit_sensor_x.text())         y = float(self.w.lineEdit_sensor_y.text())         if STATUS.is_metric_mode():             x = INFO.convert_machine_to_metric(x)             y = INFO.convert_machine_to_metric(y)         else:             x = INFO.convert_machine_to_imperial(x)             y = INFO.convert_machine_to_imperial(y)         ACTION.CALL_MDI("G90")         ACTION.CALL_MDI_WAIT("G53 G0 Z0")         command = "G53 G0 X{:3.4f} Y{:3.4f}".format(x, y)         ACTION.CALL_MDI_WAIT(command, 10)

But either way if you change the 'Tool Sensor Location' in the offsets tab it should at least go to a different place.
I will just point out it's a G53 move so machine/absolute coordinate system not G5x.

We could try a temporary fix to test if this is the problem.

Please Log in to join the conversation.

More
2 years 5 months ago #299956 by garja
Thanks Chris. I'm so sorry I have not responded until now. I've been swamped trying to meet a work related deadline that has had me putting in some long hours.

The code you provided, do I change that in the python file? I don't think I'll have any trouble updating it.

Again... thanks so much Chris!

Please Log in to join the conversation.

More
2 years 5 months ago #299986 by cmorley
it's in the qtdragon_handler.py file
If you load qtdragon in the INI with this:

DISPLAY = qtvcp -i qtdragon

and run from the terminal, it will tell you were the file is located.

Please Log in to join the conversation.

More
2 years 5 months ago #300587 by garja
Fantastic! Thanks again for your time.

Please Log in to join the conversation.

Time to create page: 0.351 seconds
Powered by Kunena Forum