New config not launching LinuxCNC
07 Aug 2023 03:55 #277192
by PCW
Replied by PCW on topic New config not launching LinuxCNC
Yes adding /24 to the ip address is the same as a 255.255.255.0 netmask
Also the ping times are really long...
Does mesaflash work?
Also the ping times are really long...
Does mesaflash work?
Please Log in or Create an account to join the conversation.
07 Aug 2023 04:16 #277194
by smplc
Replied by smplc on topic New config not launching LinuxCNC
I tried:
auto enp86s0
iface enp86s0 inet static
address 10.10.10.1/24
hardware-irq-coalesce-rx-usecs 0
and
auto enp86s0
iface enp86s0 inet static
address 10.10.10.1
netmask 255.255.255.0
hardware-irq-coalesce-rx-usecs 0
Powered-off/on the control box and the NUC after each edit and before attempting to launch LinuxCNC but the same error occurred again.
auto enp86s0
iface enp86s0 inet static
address 10.10.10.1/24
hardware-irq-coalesce-rx-usecs 0
and
auto enp86s0
iface enp86s0 inet static
address 10.10.10.1
netmask 255.255.255.0
hardware-irq-coalesce-rx-usecs 0
Powered-off/on the control box and the NUC after each edit and before attempting to launch LinuxCNC but the same error occurred again.
Please Log in or Create an account to join the conversation.
07 Aug 2023 04:21 #277195
by smplc
Replied by smplc on topic New config not launching LinuxCNC
However, the ping did show packets transmitting. Yes, it'd appear that mesaflash is working.
I still don't know why LinuxCNC isn't launching.
I still don't know why LinuxCNC isn't launching.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 18563
- Thank you received: 6219
07 Aug 2023 11:10 #277223
by tommylight
Replied by tommylight on topic New config not launching LinuxCNC
Hal and ini?
The error reports no network connection, is the Mesa board wired directly to the PC?
If the PC has more than one ETH port, make sure Mesa is wired to the configured one.
Check the hal file, might have the wrong addres in the loadrt line.
Is Mesa set for 10.10.10.10?
Do the LED's blink on Mesa and PC connectors?
Try another cable.
Check the 5V going to Mesa, it can be 4.75-5.25V, anything under or over is not good.
The error reports no network connection, is the Mesa board wired directly to the PC?
If the PC has more than one ETH port, make sure Mesa is wired to the configured one.
Check the hal file, might have the wrong addres in the loadrt line.
Is Mesa set for 10.10.10.10?
Do the LED's blink on Mesa and PC connectors?
Try another cable.
Check the 5V going to Mesa, it can be 4.75-5.25V, anything under or over is not good.
Please Log in or Create an account to join the conversation.
07 Aug 2023 15:24 - 07 Aug 2023 15:31 #277244
by smplc
Replied by smplc on topic New config not launching LinuxCNC
• Yes, the 7i96s card RJ45 Cat5e is connected to the RJ45 NUC mini PC.
• The NUC12WSHi3 only has one ethernet port and presently not using B-key SATA.
• The hal file loadrt line has a 192.168.1.121 address. This is the same address that matches the 7i96s_d card in the PnCConf Wizard.
• Yes, the 7i96s LED's CR11-CR14 blinks green when pinging 10.10.10.10 . Closing ping CR11 remains lit. The CR8 steady lit yellow. The RJ45 lit green and orange. The NUC RJ45 only green lit.
• Another cable hasn't been tried yet because the same one used with BRIX 1900, Debian 10, launched LinuxCNC 2.8.0, a configured profile and automation operable.
• The 7i96s has it's own 5VDC power supply and the multi-meter reads 4.97VDC.
I don't remember if I did something outstandingly different with the BRIX than the NUC and the Mesa and LinuxCNC configuration yet. I probably disconnected the BRIX Wi-Fi terminal in case any issue with the ethernet. However, the BRIX and NUC are different mini PC's. The BRIX has Deb 10 and the NUC Deb 12.1. I haven't tried Deb 12.0 yet. I can try comparing the BRIX and NUC .pncconf file's but the NUC chucker_no_spindle profile closely matches the BRIX sherline_lathe_chucker profile. I guess I could copy the sherline_lathe_chucker folder, paste it in the NUC /configs folder and try launching it profile with LinuxCNC.
• The NUC12WSHi3 only has one ethernet port and presently not using B-key SATA.
• The hal file loadrt line has a 192.168.1.121 address. This is the same address that matches the 7i96s_d card in the PnCConf Wizard.
• Yes, the 7i96s LED's CR11-CR14 blinks green when pinging 10.10.10.10 . Closing ping CR11 remains lit. The CR8 steady lit yellow. The RJ45 lit green and orange. The NUC RJ45 only green lit.
• Another cable hasn't been tried yet because the same one used with BRIX 1900, Debian 10, launched LinuxCNC 2.8.0, a configured profile and automation operable.
• The 7i96s has it's own 5VDC power supply and the multi-meter reads 4.97VDC.
I don't remember if I did something outstandingly different with the BRIX than the NUC and the Mesa and LinuxCNC configuration yet. I probably disconnected the BRIX Wi-Fi terminal in case any issue with the ethernet. However, the BRIX and NUC are different mini PC's. The BRIX has Deb 10 and the NUC Deb 12.1. I haven't tried Deb 12.0 yet. I can try comparing the BRIX and NUC .pncconf file's but the NUC chucker_no_spindle profile closely matches the BRIX sherline_lathe_chucker profile. I guess I could copy the sherline_lathe_chucker folder, paste it in the NUC /configs folder and try launching it profile with LinuxCNC.
Last edit: 07 Aug 2023 15:31 by smplc. Reason: Cable model.
Please Log in or Create an account to join the conversation.
07 Aug 2023 15:34 #277246
by PCW
Replied by PCW on topic New config not launching LinuxCNC
"The hal file loadrt line has a 192.168.1.121 address"
That needs to be 10.10.10.10
That needs to be 10.10.10.10
Please Log in or Create an account to join the conversation.
07 Aug 2023 16:03 #277248
by smplc
Replied by smplc on topic New config not launching LinuxCNC
The hal file I replaced the 192.168.1.121 with 10.10.10.10 . LinuxCNC launched the chucker_no_spindle profile. The GUI has latency issue now. 7i96s CR6 is lit red. I suppose try a latency-test and update it the chucker_no_spindle.ini file at SERVO_PERIOD.
Please Log in or Create an account to join the conversation.
07 Aug 2023 16:18 #277250
by PCW
Replied by PCW on topic New config not launching LinuxCNC
The servo period should be 1 ms (1000000 ns)
or perhaps even longer as the ping times were quite slow
or perhaps even longer as the ping times were quite slow
Please Log in or Create an account to join the conversation.
07 Aug 2023 16:30 #277251
by smplc
Replied by smplc on topic New config not launching LinuxCNC
The latency retested at 22675 ns. I tried that value at the SERVO_PERIOD and the error again. The SERVO_PERIOD is now at 1000000 and LinuxCNC Axis lathe launches without error. X and Z axes are jogging. The sherline_lathe_chucker.ini was at SERVO_PERIOD = 1000000 too. Thanks.
Please Log in or Create an account to join the conversation.
Time to create page: 0.082 seconds