- Posts: 44
- Thank you received: 8
Can't run first job with qtdragon_hd
- ucancallmebob89
- Offline
- Senior Member
-
Less
More
4 years 10 months ago - 4 years 10 months ago #229821
by ucancallmebob89
Replied by ucancallmebob89 on topic Can't run first job with qtdragon_hd
Last edit: 4 years 10 months ago by ucancallmebob89.
Please Log in or Create an account to join the conversation.
- ucancallmebob89
- Offline
- Senior Member
-
Less
More
- Posts: 44
- Thank you received: 8
4 years 10 months ago #229823
by ucancallmebob89
Replied by ucancallmebob89 on topic Can't run first job with qtdragon_hd
Ok so my previous post isn't right, that tab is just displaying descriptions of various gcodes from ~/linuxcnc-dev/lib/python/qtvcp/lib/mdi_text.py.
But I'm still pretty sure it has something to do with my toolchange configuration.
But I'm still pretty sure it has something to do with my toolchange configuration.
Please Log in or Create an account to join the conversation.
- ucancallmebob89
- Offline
- Senior Member
-
Less
More
- Posts: 44
- Thank you received: 8
4 years 10 months ago #229827
by ucancallmebob89
Replied by ucancallmebob89 on topic Can't run first job with qtdragon_hd
www.forum.linuxcnc.org/21-axis/42888-how...axis?start=10#213214
This fixed it. Looks like it was a problem with the dialog. This is the tool change section in my postgui file now:
Troubleshooting this only took 3 days, but hey, that's linux for you I guess.
This fixed it. Looks like it was a problem with the dialog. This is the tool change section in my postgui file now:
Troubleshooting this only took 3 days, but hey, that's linux for you I guess.
The following user(s) said Thank You: hottabich
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
Less
More
- Posts: 7368
- Thank you received: 2181
4 years 10 months ago #229851
by cmorley
Replied by cmorley on topic Can't run first job with qtdragon_hd
So loading the tool_dialog is not necessary - it's included in the screen code.
I seem to remember you have multiple entries for tool change - some commented out.
I also fixed the LED color problem - the limits were like that too.
I seem to remember you have multiple entries for tool change - some commented out.
I also fixed the LED color problem - the limits were like that too.
The following user(s) said Thank You: ucancallmebob89
Please Log in or Create an account to join the conversation.
- ucancallmebob89
- Offline
- Senior Member
-
Less
More
- Posts: 44
- Thank you received: 8
4 years 10 months ago #229883
by ucancallmebob89
Replied by ucancallmebob89 on topic Can't run first job with qtdragon_hd
Yeah I think all the LEDs in the qtdragon_hd.ui file were green on and green off.
I did have the toolchange HAL settings in a few different places but I'm pretty sure I only ever had one set of them active. I've been trying to cobble together this config from a few different reference sources so I'm not 100% sure where the best place to put everything is. What file are you referring to for the "screen code"?
I did have the toolchange HAL settings in a few different places but I'm pretty sure I only ever had one set of them active. I've been trying to cobble together this config from a few different reference sources so I'm not 100% sure where the best place to put everything is. What file are you referring to for the "screen code"?
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
Less
More
- Posts: 7368
- Thank you received: 2181
4 years 10 months ago #229924
by cmorley
Replied by cmorley on topic Can't run first job with qtdragon_hd
By screen code I mean the files that produce the screen. qtdragon - usually hidden from the user.
Qtvcp's builtin component is smart enough to check to see if the other toolchanger component is loaded - it will give a warning in the terminal about it but will use the previously loaded one.
Yes I understand it's hard to piece together a config from examples and best practices change over time.
in the file qtvcp_postgui.hal was the appropriate location to connect the signals for toolchanging. it's called after the qtdragon screen has initialized and added it's HAL pins.
Some sparse information here:
linuxcnc.org/docs/devel/html/gui/qtdragon.html#_hal_pins
Qtvcp's builtin component is smart enough to check to see if the other toolchanger component is loaded - it will give a warning in the terminal about it but will use the previously loaded one.
Yes I understand it's hard to piece together a config from examples and best practices change over time.
in the file qtvcp_postgui.hal was the appropriate location to connect the signals for toolchanging. it's called after the qtdragon screen has initialized and added it's HAL pins.
Some sparse information here:
linuxcnc.org/docs/devel/html/gui/qtdragon.html#_hal_pins
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 1.788 seconds