QTDragon run from line dialog when not enabled
18 Aug 2021 02:09 - 18 Aug 2021 02:10 #218030
by coredump
QTDragon run from line dialog when not enabled was created by coredump
Hello. I am using the latest git master version for Linuxcnc and qtdragon_hd. I got everything setup but for some reason, when running a file generated by pcb2gcode I started getting the run from line dialog on tool changes (the dialog I am saying is the one where you can set spindle version and etc).
I tried enabling and disabling the run from line stuff but to no avail. I think it may be something related to how the pcb2gcode stuff is made, or a config I haven't found yet.
I am attaching the NGC in case. It usually happens after all the probing is done, and it asks to run from line 87
I tried enabling and disabling the run from line stuff but to no avail. I think it may be something related to how the pcb2gcode stuff is made, or a config I haven't found yet.
I am attaching the NGC in case. It usually happens after all the probing is done, and it asks to run from line 87
Last edit: 18 Aug 2021 02:10 by coredump.
Please Log in or Create an account to join the conversation.
18 Aug 2021 02:41 #218032
by cmorley
Replied by cmorley on topic QTDragon run from line dialog when not enabled
I can't run your program in sim but i don't see anything crazy in it.
Would you say it's after the M0 codes that this happens?
Do you see on the tool change dislaog, a button for jogging while paused?
If you press that button a run from line dialog will pop.
Would you say it's after the M0 codes that this happens?
Do you see on the tool change dislaog, a button for jogging while paused?
If you press that button a run from line dialog will pop.
Please Log in or Create an account to join the conversation.
18 Aug 2021 04:07 #218036
by coredump
Replied by coredump on topic QTDragon run from line dialog when not enabled
So how it goes is it finishes probing, and then goes through asking me to change tool (I see the message). I think all the pop ups appear at the same time? As in the Change tool message, the change tool dialog and behind it the one that has an option to turn on the spindle CW or CCW and speed. When I click everything the code just hangs there even if I press the Resume button
Same code ran fine on gmoccapy.
Same code ran fine on gmoccapy.
Please Log in or Create an account to join the conversation.
18 Aug 2021 04:56 #218037
by cmorley
Replied by cmorley on topic QTDragon run from line dialog when not enabled
Does it do it with any other program?
Please Log in or Create an account to join the conversation.
18 Aug 2021 05:10 #218039
by cmorley
Replied by cmorley on topic QTDragon run from line dialog when not enabled
According to your program there should be a stop between the probe and toolchange - Does that happen? Do you resume from pause? does the dialogs come after that?
Please Log in or Create an account to join the conversation.
18 Aug 2021 19:26 - 18 Aug 2021 19:27 #218088
by coredump
Replied by coredump on topic QTDragon run from line dialog when not enabled
I tried another run today and I got the same problem. I am attaching the screenshots from what happened, and I tried to pay more attention to see if I could see anything different. I am a dumbass and took a screenshot with the screenshot app on screen, but behind it it's the 'spindle speed CW CCW' screen. It pops up without me doing anything, together with the 'manual tool change request', and I didn't click the pause for jogging button.This is what the machine status log has:
And that happened on this part of the code (I could see the red/yellow line jumping around on the code window:
Wed18 15:04 Started program from line 1
Wed18 15:04 Attach the probe tool
Wed18 15:07 Detach the probe tool
Wed18 15:08 Change tool bit to mill diameter 0.12679mm
Wed18 15:08 tool change paused for jogging; launched run-from-line
Wed18 15:08 Run timer stopped at 00:02:55
Wed18 15:08 Tool 4: HQMASTER V-Bit 0.1 30 dgAnd that happened on this part of the code (I could see the red/yellow line jumping around on the code window:
G0 Z5.000 ( Move Z to safe height )
(PROBECLOSE) ( Close the probe log file )
( Probing has ended, each Z-coordinate will be corrected with a bilinear interpolation )
(MSG, Detach the probe tool)
M0 ( Temporary machine stop. )
G00 Z25.00000 (Retract to tool change height)
T4
M5 (Spindle stop.)
G04 P1.00000 (Wait for spindle to stop)
(MSG, Change tool bit to mill diameter 0.12679mm)
M6 (Tool change.)
M0 (Temporary machine stop.)
M3 ( Spindle on clockwise. )
G04 P1.00000 (Wait for spindle to get up to speed)
G04 P0 ( dwell for no time -- G64 should not smooth over this point )
G00 Z5.00000 ( retract )
Last edit: 18 Aug 2021 19:27 by coredump. Reason: formatting
Please Log in or Create an account to join the conversation.
19 Aug 2021 12:46 #218139
by hottabich
Replied by hottabich on topic QTDragon run from line dialog when not enabled
In linuxcnc 2.8.1everything works. Checked in the simulator (through Probe sim). After probing the workpiece, we change the tool and work is in progress.
Please Log in or Create an account to join the conversation.
19 Aug 2021 17:21 #218163
by cmorley
Replied by cmorley on topic QTDragon run from line dialog when not enabled
Yes master tool change dialog is different l, to facilitate pausing for jogging.
I can't get this error to show in sim so am having problems figuring out what to change.
I can't get this error to show in sim so am having problems figuring out what to change.
Please Log in or Create an account to join the conversation.
21 Aug 2021 18:55 #218339
by cmorley
Replied by cmorley on topic QTDragon run from line dialog when not enabled
I can't get this problem to show.
can you post the file dialog_widgets.py ?
and/or a program that shows the problem with out probing.?
Are you using a compiled version or buildbot version?
can you post the file dialog_widgets.py ?
and/or a program that shows the problem with out probing.?
Are you using a compiled version or buildbot version?
Please Log in or Create an account to join the conversation.
22 Aug 2021 22:52 - 22 Aug 2021 22:55 #218445
by coredump
Replied by coredump on topic QTDragon run from line dialog when not enabled
I just tried again using a fresh install with Debian Buster ISO install and the buildbot version from Master (linuxcnc-uspace 1:2.9.0~pre0.4478.ga2e0d30a6) via apt.
At this point I am thinking that it must be something wrong on my configs somewhere, because the only thing intact between my last try and now is the linuxcnc configuration directory. I say that because no matter how many times I reinstall I still getting the Jump List on the file browser to show the same items (and keep giving me errors because a directory that I had 4 installs ago is still on the jumplist and I can't find where to delete that).
I am uploading the program that I was trying to run to this gist , and after the probing sequence it did the same thing: pops up the tool change screen + the spindle CCW/CW one from Run from Line that is not enabled.
I also tried using MDI to do a simple T0 then M6, and then different T numbers followed by M6 and all the times it works fine, showing the change tool prompt but with the 'Pause for jogging' button disabled/greyed out.
I algo got this on the machine log for that run:
And this is the debug log on qtvcp:
As you can see it gets to line 353 that is the end of the probing routines, and then it pauses so I can disconnect the probes, then after resuming it runs until the dialog for changing tool appears, but at that point the 'Button pressed is' is on the log, but I haven't clicked anything really (aside from the RESUME to continue after disconnecting the probe clips).
All the dialogs show at the same time. After that no matter what I do the program is just dead (no led on RUN PROGRAM or RESUME or anything).
On this run I clicked the 'pause for jogging' to see if I could continue after setting the speed on the other dialog, but even so the spindle turns on and then stays there without moving and the program is just stopped/not running/dead.
My configs are up to date on my github.
At this point I am thinking that it must be something wrong on my configs somewhere, because the only thing intact between my last try and now is the linuxcnc configuration directory. I say that because no matter how many times I reinstall I still getting the Jump List on the file browser to show the same items (and keep giving me errors because a directory that I had 4 installs ago is still on the jumplist and I can't find where to delete that).
I am uploading the program that I was trying to run to this gist , and after the probing sequence it did the same thing: pops up the tool change screen + the spindle CCW/CW one from Run from Line that is not enabled.
I also tried using MDI to do a simple T0 then M6, and then different T numbers followed by M6 and all the times it works fine, showing the change tool prompt but with the 'Pause for jogging' button disabled/greyed out.
I algo got this on the machine log for that run:
Sun22 18:28 Loaded program file : /home/coredump/linuxcnc/nc_files/PCB-i2c/ALelectronics-B_Cu_gbr_iso_combined_cnc.ngc
Sun22 18:28 Loaded file /home/coredump/linuxcnc/nc_files/PCB-i2c/ALelectronics-B_Cu_gbr_iso_combined_cnc.ngc
Sun22 18:28 Started program from line 1
Sun22 18:33 tool change paused for jogging; launched run-from-line
Sun22 18:33 Run timer stopped at 00:04:26
Sun22 18:33 Tool 1: 1/4 Bottom Cleaning
Sun22 18:33 tool change paused for jogging; launched run-from-line
Sun22 18:33 Need tool prepared -Txx- for toolchangeAnd this is the debug log on qtvcp:
2021-08-22 18:32:53,102 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 353
2021-08-22 18:32:53,103 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 353
2021-08-22 18:32:53,104 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - Line changed: 353
2021-08-22 18:33:04,964 - QTvcp.QTVCP.QT_ACTION - DEBUG - resume
2021-08-22 18:33:04,990 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 393
2021-08-22 18:33:04,991 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 393
2021-08-22 18:33:05,038 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - Line changed: 393
2021-08-22 18:33:05,291 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 394
2021-08-22 18:33:05,292 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: highlight line 394
2021-08-22 18:33:05,293 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - Line changed: 394
2021-08-22 18:33:06,735 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Button pressed is: Pause For Jogging
2021-08-22 18:33:06,798 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:06,799 - QTvcp.QTVCP.WIDGETS.TOOL_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:06,800 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:06,800 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Saving ToolChangeDialog-geometry data from widget to file.
2021-08-22 18:33:07,085 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: got external hilight 0
2021-08-22 18:33:07,087 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - editor: got external hilight 0
2021-08-22 18:33:45,412 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Button pressed is: Pause For Jogging
2021-08-22 18:33:45,464 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:45,464 - QTvcp.QTVCP.WIDGETS.TOOL_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:45,464 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - message returned:{'NAME': 'RUNFROMLINE', 'LINE': 397, 'NONBLOCKING': True, 'RETURN': None}
2021-08-22 18:33:45,465 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Saving ToolChangeDialog-geometry data from widget to file.
2021-08-22 18:33:51,940 - QTvcp.QTVCP.QT_ACTION - DEBUG - MDI_WAIT_COMMAND= s15000 M3, maxt = 5
2021-08-22 18:33:51,990 - QTvcp.QTVCP.QT_ACTION - DEBUG - MDI_COMMAND: s15000 M3
2021-08-22 18:33:57,516 - QTvcp.QTVCP.QT_ACTION - DEBUG - MDI_WAIT_COMMAND= s15000 M3, maxt = 5
2021-08-22 18:33:57,566 - QTvcp.QTVCP.QT_ACTION - DEBUG - MDI_COMMAND: s15000 M3
2021-08-22 18:34:21,626 - QTvcp.QTVCP.WIDGETS.GCODE_EDITOR - DEBUG - Line changed: 0
2021-08-22 18:34:26,848 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Button pressed is: &Yes
2021-08-22 18:34:26,852 - QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET - DEBUG - Value of pressed button: 16384
2021-08-22 18:34:26,896 - QTvcp.QTVCP.QT_MAKEGUI - DEBUG - Calling handler file Closing_cleanup__ function.
2021-08-22 18:34:26,940 - QTvcp.QTVCP.WIDGETS.BASIC_PROBE - DEBUG - Saving Basic Probe data to preference file.
2021-08-22 18:34:26,970 - QTvcp.QTVCP.QT_MAKEPINS - DEBUG - Saving Main Window geometry to preference file.
2021-08-22 18:34:26,971 - QTvcp.QTVCP.QT_MAKEPINS - DEBUG - search for widget closing cleanup functions
2021-08-22 18:34:26,975 - QTvcp.QTVCP.QT_MAKEPINS - INFO - Closing cleanup on: originOffsetDialog_
2021-08-22 18:34:26,979 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - Saving __dialogOffsetViewWidget data to file.
2021-08-22 18:34:27,013 - QTvcp.QTVCP.QT_MAKEPINS - INFO - Closing cleanup on: offset_table
2021-08-22 18:34:27,015 - QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW - DEBUG - Saving offset_table data to file.
2021-08-22 18:34:27,037 - QTvcp.QTVCP.QT_MAKEPINS - INFO - Closing cleanup on: filemanager_usb
2021-08-22 18:34:27,041 - QTvcp.QTVCP.QT_MAKEPINS - INFO - Closing cleanup on: filemanagerAs you can see it gets to line 353 that is the end of the probing routines, and then it pauses so I can disconnect the probes, then after resuming it runs until the dialog for changing tool appears, but at that point the 'Button pressed is' is on the log, but I haven't clicked anything really (aside from the RESUME to continue after disconnecting the probe clips).
All the dialogs show at the same time. After that no matter what I do the program is just dead (no led on RUN PROGRAM or RESUME or anything).
On this run I clicked the 'pause for jogging' to see if I could continue after setting the speed on the other dialog, but even so the spindle turns on and then stays there without moving and the program is just stopped/not running/dead.
My configs are up to date on my github.
Last edit: 22 Aug 2021 22:55 by coredump. Reason: This post editor is garbage
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.088 seconds