Extremely confused - Nonworking limit switches
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17538
- Thank you received: 5126
30 Sep 2025 01:09 #335594
by PCW
Replied by PCW on topic Extremely confused - Nonworking limit switches
Can you post the two configurations?
Are you dropping packets?
That is, what is:
hm2_7i96s.0.packet-error-total
Sounds like something very basic is broken
Are you dropping packets?
That is, what is:
hm2_7i96s.0.packet-error-total
Sounds like something very basic is broken
Please Log in or Create an account to join the conversation.
- ffffrf
- Offline
- Senior Member
-
Less
More
- Posts: 51
- Thank you received: 2
30 Sep 2025 01:26 - 30 Sep 2025 01:29 #335595
by ffffrf
Replied by ffffrf on topic Extremely confused - Nonworking limit switches
Hopefully I am using the correct terminology, by config I just mean associated hal / ini files
so my taig (config 2) represents the second machine using (mesa2) and my MODLATHE (config 1) was paired with my mesa1 board
Typing halcmd show param hm2*packet* only brings up error-decrement (value 1), error-increment (value 2), error-limit (value 10) and read-timeout (value 80), I do not see a total packet error parameter
so my taig (config 2) represents the second machine using (mesa2) and my MODLATHE (config 1) was paired with my mesa1 board
Typing halcmd show param hm2*packet* only brings up error-decrement (value 1), error-increment (value 2), error-limit (value 10) and read-timeout (value 80), I do not see a total packet error parameter
Last edit: 30 Sep 2025 01:29 by ffffrf.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Offline
- Moderator
-
Less
More
- Posts: 21121
- Thank you received: 7216
30 Sep 2025 01:27 #335596
by tommylight
Replied by tommylight on topic Extremely confused - Nonworking limit switches
@LangdonS, he has 2 of Mesa 7i96S, so why are you suggesting he use parallel port testers?
Not helpful, just confusing.
-
@ffffrf
trying to clear things a bit, so you have
1 single PC
2 of Mesa 7i96S
2 of separate machines
Is that correct? Assuming yes
From that, PC works properly with Mesa1, machine works properly with Mesa1, correct? Assuming yes
That same PC with the Mesa 2 works for steppers but IO does not work, right? Assuming yes
-
Do you need to run both Mesa/machines at the same time? Assuming no
I am pretty sure 2 Mesa can be run, but not two instances of LinuxCNC, although there was some talk about that.
-
Assuming all of the above is correct:
-There is no need to change Mesa board address, nor change PC address at all to use both cards, but not at the same time. Leave the PC at 10.10.10.11 and both Mesa at 10.10.10.10. That reminds me, the networking on your PC is not set correctly despite working intermittently as it has two different names assigned to the same interface, and this must be corrected for reliable connection.
-regarding non working IO, i suspect you might have changed the serial ports on the PncConf wizard, but again, this is my assumption and as such might be wrong.
-easiest way = make a new config, do not change serial ports numbers, see if that works
or
-open both hal files, for Mesa1 and Mesa2 with a text editor (do not use office stuff) and check the "loadrt" lines at the top of the files, see if they are the same and if the sserial string is the same
-
Just in case, you can make as many config as you like, you can have several configs for the same machine with say different speeds or different accelerations or different limits or.... so feel free to make new configs till you get things working as you like them to.
Wow this was long....
Not helpful, just confusing.
-
@ffffrf
trying to clear things a bit, so you have
1 single PC
2 of Mesa 7i96S
2 of separate machines
Is that correct? Assuming yes
From that, PC works properly with Mesa1, machine works properly with Mesa1, correct? Assuming yes
That same PC with the Mesa 2 works for steppers but IO does not work, right? Assuming yes
-
Do you need to run both Mesa/machines at the same time? Assuming no
I am pretty sure 2 Mesa can be run, but not two instances of LinuxCNC, although there was some talk about that.
-
Assuming all of the above is correct:
-There is no need to change Mesa board address, nor change PC address at all to use both cards, but not at the same time. Leave the PC at 10.10.10.11 and both Mesa at 10.10.10.10. That reminds me, the networking on your PC is not set correctly despite working intermittently as it has two different names assigned to the same interface, and this must be corrected for reliable connection.
-regarding non working IO, i suspect you might have changed the serial ports on the PncConf wizard, but again, this is my assumption and as such might be wrong.
-easiest way = make a new config, do not change serial ports numbers, see if that works
or
-open both hal files, for Mesa1 and Mesa2 with a text editor (do not use office stuff) and check the "loadrt" lines at the top of the files, see if they are the same and if the sserial string is the same
-
Just in case, you can make as many config as you like, you can have several configs for the same machine with say different speeds or different accelerations or different limits or.... so feel free to make new configs till you get things working as you like them to.
Wow this was long....
Please Log in or Create an account to join the conversation.
- tommylight
-
- Offline
- Moderator
-
Less
More
- Posts: 21121
- Thank you received: 7216
30 Sep 2025 01:35 #335597
by tommylight
Replied by tommylight on topic Extremely confused - Nonworking limit switches
Ok i just saw the attachments,
this is on Taig new
net min-x <= hm2_7i96s.0.gpio.001.in
while this is on Modlathe
net min-home-x <= hm2_7i96s.0.inm.00.input-00-not
not the same pins, and i do not mean the number, probably choosing the pins on the wrong page of the wizard ???
Damn, i am making a lot of assumptions tonight, i better go sleep, it is 3:33AM here!
this is on Taig new
net min-x <= hm2_7i96s.0.gpio.001.in
while this is on Modlathe
net min-home-x <= hm2_7i96s.0.inm.00.input-00-not
not the same pins, and i do not mean the number, probably choosing the pins on the wrong page of the wizard ???
Damn, i am making a lot of assumptions tonight, i better go sleep, it is 3:33AM here!
Please Log in or Create an account to join the conversation.
- ffffrf
- Offline
- Senior Member
-
Less
More
- Posts: 51
- Thank you received: 2
30 Sep 2025 01:40 #335598
by ffffrf
Replied by ffffrf on topic Extremely confused - Nonworking limit switches
Your assumptions are all correct
and yes aware I cannot run two instances of linuxcnc at the same time, I only ever run one of them, and only one mesa is ever connected to the same pc.
I am looking at both of the hal/ini of both machines and there is no obvious changes within the starting portions of the hal file, and I also built pncconf of my second machine based on my settings of the first machine and just confirmed most of it is identical (minus one being a lathe and one being a cnc mill)
and yes aware I cannot run two instances of linuxcnc at the same time, I only ever run one of them, and only one mesa is ever connected to the same pc.
I am looking at both of the hal/ini of both machines and there is no obvious changes within the starting portions of the hal file, and I also built pncconf of my second machine based on my settings of the first machine and just confirmed most of it is identical (minus one being a lathe and one being a cnc mill)
Please Log in or Create an account to join the conversation.
- tommylight
-
- Offline
- Moderator
-
Less
More
- Posts: 21121
- Thank you received: 7216
30 Sep 2025 01:45 #335599
by tommylight
Replied by tommylight on topic Extremely confused - Nonworking limit switches
Can i assume you missed my last post? 
Also, the Mesa IP is 10.10.10.11 on one of those hal files, should be 10.10.10.10 on both files.
Also, the Mesa IP is 10.10.10.11 on one of those hal files, should be 10.10.10.10 on both files.
Please Log in or Create an account to join the conversation.
- ffffrf
- Offline
- Senior Member
-
Less
More
- Posts: 51
- Thank you received: 2
30 Sep 2025 01:48 - 30 Sep 2025 02:34 #335600
by ffffrf
Replied by ffffrf on topic Extremely confused - Nonworking limit switches
Hey, so the gpio difference was from when i was debugging, after pncconf, both show the same input-00 pin (most recently i tried wiring it to input-01 to see if any difference would occur so this file snippet shows input 01, but again has not fixed it
- the mesa boards were both originally 10.10.10.10 (via IP in terminal and via hal/INI and in PNCCONF) same issue persisted, even after trying all sorts of gpio input changes, reboots, etc. I only changed one to 10.10.10.11 to see if it would resolve the issue
yes sorry your last post came in when i was writing the above - it is unfortunately the same, I just accidentally sent the config in the middle of trying to debug by changing it to gpio001 or gpio000
edit: i will go back now and put mesa2 as 10.10.10.10 as it originally was so i can start debug from square 1
edit2: I feel like when i look back at everything ive tried, the following thing seems to be pointing to wher something is going wrong (below)
back when all boards were 10.10.10.10, all pnc confs for both machines were the same, all inputs were the same for limit switches, etc and i had not changed anything, the following would occur:
mesa2 running config1 (for machine1) WOULD show the limit switches working in axis GUI under the watch section of hal config, however, when I closed config1, and instead ran config2 (for machine2), suddenly the EXACT SAME PINS would NOT show a status change when I press on the limit switch while watching in hal configuration tab of axis gui
but in BOTH cases, the limit switch is shown working in halmeter of pncconf
edit3: I just reverted mesa2 back to 10.10.10.10 and I am able to recreate the above issue, and again the issue persists. I am able to open config1 on mesa2 and I see in the halconfig the status of my input-01 pin changing, but when i close it and open up config2, it no longer works. I also juist tried literally copy pasting the initial HAL file portion over to machine1 config hal (taig), minus the spindle components which I deleted, and the same issue persists and is recreated!!!
edit4: I know everyone is probably asleep but I wanted to post one more thing that I think might be helpful. I just did something crazy - I went into pncconf for config1, which was a lathe, and had a working limit switch with my mesa 2 board about 10 seconds ago. I went into this pncconf config1, and changed it to an XYZ mill, and had to change the X axis to stepgen 3 but left everything else alone...now when I ran this, the limit switch DOES NOT WORK
- the mesa boards were both originally 10.10.10.10 (via IP in terminal and via hal/INI and in PNCCONF) same issue persisted, even after trying all sorts of gpio input changes, reboots, etc. I only changed one to 10.10.10.11 to see if it would resolve the issue
yes sorry your last post came in when i was writing the above - it is unfortunately the same, I just accidentally sent the config in the middle of trying to debug by changing it to gpio001 or gpio000
edit: i will go back now and put mesa2 as 10.10.10.10 as it originally was so i can start debug from square 1
edit2: I feel like when i look back at everything ive tried, the following thing seems to be pointing to wher something is going wrong (below)
back when all boards were 10.10.10.10, all pnc confs for both machines were the same, all inputs were the same for limit switches, etc and i had not changed anything, the following would occur:
mesa2 running config1 (for machine1) WOULD show the limit switches working in axis GUI under the watch section of hal config, however, when I closed config1, and instead ran config2 (for machine2), suddenly the EXACT SAME PINS would NOT show a status change when I press on the limit switch while watching in hal configuration tab of axis gui
but in BOTH cases, the limit switch is shown working in halmeter of pncconf
edit3: I just reverted mesa2 back to 10.10.10.10 and I am able to recreate the above issue, and again the issue persists. I am able to open config1 on mesa2 and I see in the halconfig the status of my input-01 pin changing, but when i close it and open up config2, it no longer works. I also juist tried literally copy pasting the initial HAL file portion over to machine1 config hal (taig), minus the spindle components which I deleted, and the same issue persists and is recreated!!!
edit4: I know everyone is probably asleep but I wanted to post one more thing that I think might be helpful. I just did something crazy - I went into pncconf for config1, which was a lathe, and had a working limit switch with my mesa 2 board about 10 seconds ago. I went into this pncconf config1, and changed it to an XYZ mill, and had to change the X axis to stepgen 3 but left everything else alone...now when I ran this, the limit switch DOES NOT WORK
Last edit: 30 Sep 2025 02:34 by ffffrf.
Please Log in or Create an account to join the conversation.
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17538
- Thank you received: 5126
30 Sep 2025 02:53 #335601
by PCW
Replied by PCW on topic Extremely confused - Nonworking limit switches
Is it possible you have a bad version of LinuxCNC?
(since it seems to be a quite old version when master was 2.9)
but in BOTH cases, the limit switch is shown working in halmeter of pncconf
Did you mean halmeter or pncconf?
(since it seems to be a quite old version when master was 2.9)
but in BOTH cases, the limit switch is shown working in halmeter of pncconf
Did you mean halmeter or pncconf?
Please Log in or Create an account to join the conversation.
- ffffrf
- Offline
- Senior Member
-
Less
More
- Posts: 51
- Thank you received: 2
30 Sep 2025 03:40 #335603
by ffffrf
Replied by ffffrf on topic Extremely confused - Nonworking limit switches
*in both cases the switch is clearly working in pncconf
- I am totally stumped - i guess it could be a bad version of linuxcnc? I havent had any issues with it since setting it up for the first time, only now with this second mesa board. You recommend I update linuxcnc? Will try to do so tomorrow morning
- I am totally stumped - i guess it could be a bad version of linuxcnc? I havent had any issues with it since setting it up for the first time, only now with this second mesa board. You recommend I update linuxcnc? Will try to do so tomorrow morning
Please Log in or Create an account to join the conversation.
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17538
- Thank you received: 5126
30 Sep 2025 17:41 #335634
by PCW
Replied by PCW on topic Extremely confused - Nonworking limit switches
As a data point, your config1 and config2 (MODLATHE and taig_new)
works as expected with LinuxCNC 2.9 and Master with a 7I96S
and I can alternate running MODLATHE and taig_new without
issue.
That is, the inm inputs work properly on both.
works as expected with LinuxCNC 2.9 and Master with a 7I96S
and I can alternate running MODLATHE and taig_new without
issue.
That is, the inm inputs work properly on both.
Please Log in or Create an account to join the conversation.
Time to create page: 0.138 seconds