QTdragon home switches do not work
- Calysto
- Offline
- Senior Member
-
Less
More
- Posts: 43
- Thank you received: 6
04 Dec 2023 18:24 - 04 Dec 2023 18:30 #287209
by Calysto
QTdragon home switches do not work was created by Calysto
I've switched from Axis to QTdragon. Nice interface!! But... my home-switches do not work anymore. The machine just goes on and on when I press the home-all button. Scary... As far as I know the config file is the same as before, accept some [display] settings.
The other thing is that I can always (If the corresponding pin om my mesa card is high or low) press the on-screen e-stop button and then the machine on button. Machine just goes on. In Axis and Gmocappy I first had to make sure there is no e-stop pressed. Is that normal in QTdragon?
I'm using the 2.9.1 image on a RPI4
Tomorrow I will post my config-files.
The other thing is that I can always (If the corresponding pin om my mesa card is high or low) press the on-screen e-stop button and then the machine on button. Machine just goes on. In Axis and Gmocappy I first had to make sure there is no e-stop pressed. Is that normal in QTdragon?
I'm using the 2.9.1 image on a RPI4
Tomorrow I will post my config-files.
Last edit: 04 Dec 2023 18:30 by Calysto.
Please Log in or Create an account to join the conversation.
- JohnnyCNC
-
- Offline
- Platinum Member
-
Less
More
- Posts: 543
- Thank you received: 100
04 Dec 2023 23:45 #287227
by JohnnyCNC
Replied by JohnnyCNC on topic QTdragon home switches do not work
I'm using QTDragon_HD on a regular PC and the Home All function works as expected. By "on and on" do mean it crashes at the physical limit of travel of travel?
If either of my physical E-Stop buttons is pressed, the screen E-Stop will not show the green dot and the machine will not turn on. I have to release the pushed E-Stop first. Working as expected.
If either of my physical E-Stop buttons is pressed, the screen E-Stop will not show the green dot and the machine will not turn on. I have to release the pushed E-Stop first. Working as expected.
Please Log in or Create an account to join the conversation.
- Calysto
- Offline
- Senior Member
-
Less
More
- Posts: 43
- Thank you received: 6
05 Dec 2023 07:45 #287247
by Calysto
Replied by Calysto on topic QTdragon home switches do not work
Thank you! Bij on and on I mean that the motors do not stop, de home switch (inductive sensors) are ignored.
Well, and the e-stops are ignored too I guess... so it looks like that all inputs are skipped. Looks like a config problem. I will go to my machine today and copy the config files.
Well, and the e-stops are ignored too I guess... so it looks like that all inputs are skipped. Looks like a config problem. I will go to my machine today and copy the config files.
Please Log in or Create an account to join the conversation.
- Calysto
- Offline
- Senior Member
-
Less
More
- Posts: 43
- Thank you received: 6
05 Dec 2023 15:19 - 05 Dec 2023 15:21 #287285
by Calysto
Replied by Calysto on topic QTdragon home switches do not work
Attached my configs.
Calysto file is a working file based on axis, e-stop not connected yet. I use this config file for testing purposes.
Qtdragon is the one I can't get to work. Qtdragon starts, I can push the e-stop and machine start, it does not matter if my e-stop physical knob is pressed or not.
Homeing goes wrong, Qtdragon does not react on home-switches. The motors keep turning until they hit the end of the ball-screws and then go into error.
I skipped the qtvcp directory in the zip file to make the zip smaller.
My Machine:
PrintNC, 1540x1540 cutting area. Mesa 7c80 board, with RPI4 4GB.
JMC 180W Servo motors on X/Y/Y2, and a closed loop stepper on Z.
2005 ball screws.
Analogue controled 2,2KW spindle, I couldn't get RS485 to work, will try that again later.
No endstops, only inductive home switches. Software endstops.
Calysto file is a working file based on axis, e-stop not connected yet. I use this config file for testing purposes.
Qtdragon is the one I can't get to work. Qtdragon starts, I can push the e-stop and machine start, it does not matter if my e-stop physical knob is pressed or not.
Homeing goes wrong, Qtdragon does not react on home-switches. The motors keep turning until they hit the end of the ball-screws and then go into error.
I skipped the qtvcp directory in the zip file to make the zip smaller.
My Machine:
PrintNC, 1540x1540 cutting area. Mesa 7c80 board, with RPI4 4GB.
JMC 180W Servo motors on X/Y/Y2, and a closed loop stepper on Z.
2005 ball screws.
Analogue controled 2,2KW spindle, I couldn't get RS485 to work, will try that again later.
No endstops, only inductive home switches. Software endstops.
Attachments:
Last edit: 05 Dec 2023 15:21 by Calysto.
Please Log in or Create an account to join the conversation.
- Aciera
-
- Offline
- Administrator
-
Less
More
- Posts: 3960
- Thank you received: 1714
05 Dec 2023 17:57 #287299
by Aciera
Replied by Aciera on topic QTdragon home switches do not work
Seems your endstop signals do not match in your 'QTdragon_Linuxcnc.hal':
You have this for the input:
# --- Endstops ---
net home-z <= hm2_7c80.0.inmux.00.input-00-not
net home-x <= hm2_7c80.0.inmux.00.input-01-not
net home-y <= hm2_7c80.0.inmux.00.input-02-not
net home-y2 <= hm2_7c80.0.inmux.00.input-03-not
But further on you use different signal names, hence linuxcnc will not see the actual state of the switches:
# ---setup home / limit switch signals---
net x-home-sw => joint.0.home-sw-in
net x-neg-limit => joint.0.neg-lim-sw-in
net x-pos-limit => joint.0.pos-lim-sw-in
# ---setup home / limit switch signals---
net y-home-sw => joint.1.home-sw-in
net y-neg-limit => joint.1.neg-lim-sw-in
net y-pos-limit => joint.1.pos-lim-sw-in
# ---setup home / limit switch signals---
net y2-home-sw => joint.2.home-sw-in
net y2-neg-limit => joint.2.neg-lim-sw-in
net y2-pos-limit => joint.2.pos-lim-sw-in
# ---setup home / limit switch signals---
net z-home-sw => joint.3.home-sw-in
net z-neg-limit => joint.3.neg-lim-sw-in
net z-pos-limit => joint.3.pos-lim-sw-in
You have this for the input:
# --- Endstops ---
net home-z <= hm2_7c80.0.inmux.00.input-00-not
net home-x <= hm2_7c80.0.inmux.00.input-01-not
net home-y <= hm2_7c80.0.inmux.00.input-02-not
net home-y2 <= hm2_7c80.0.inmux.00.input-03-not
But further on you use different signal names, hence linuxcnc will not see the actual state of the switches:
# ---setup home / limit switch signals---
net x-home-sw => joint.0.home-sw-in
net x-neg-limit => joint.0.neg-lim-sw-in
net x-pos-limit => joint.0.pos-lim-sw-in
# ---setup home / limit switch signals---
net y-home-sw => joint.1.home-sw-in
net y-neg-limit => joint.1.neg-lim-sw-in
net y-pos-limit => joint.1.pos-lim-sw-in
# ---setup home / limit switch signals---
net y2-home-sw => joint.2.home-sw-in
net y2-neg-limit => joint.2.neg-lim-sw-in
net y2-pos-limit => joint.2.pos-lim-sw-in
# ---setup home / limit switch signals---
net z-home-sw => joint.3.home-sw-in
net z-neg-limit => joint.3.neg-lim-sw-in
net z-pos-limit => joint.3.pos-lim-sw-in
Please Log in or Create an account to join the conversation.
- cmorley
- Away
- Moderator
-
Less
More
- Posts: 7761
- Thank you received: 2055
06 Dec 2023 04:36 #287328
by cmorley
Replied by cmorley on topic QTdragon home switches do not work
My guess here is you built the qtdragon config with pncconf but without home switch inputs,. after you then copy pasted the home switch code from the other file.
Pncconf will add default signals even if you don't choose home or limit switches.
These default signals did not match the copied in signals - as Aciera showed.
Pncconf will add default signals even if you don't choose home or limit switches.
These default signals did not match the copied in signals - as Aciera showed.
Please Log in or Create an account to join the conversation.
- Calysto
- Offline
- Senior Member
-
Less
More
- Posts: 43
- Thank you received: 6
07 Dec 2023 17:50 #287469
by Calysto
Replied by Calysto on topic QTdragon home switches do not work
Yes I did... ... ........ It's working now!!!! 
) Up to the next 'problem'....
) Up to the next 'problem'.... Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.069 seconds