MAC address not retrieved (after 2 years stop)

More
9 months 2 weeks ago #341365 by Jocman
Hi.
After 2 years I went to my home made hobbystic cnc to realize a project.
When used last time, the machine worked perfectly.
But today, starting LinuxCNC, I got a message error then LinuxCNC quit.

Here you can find the message (only the Print File Information section):

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.7.14
Machine configuration directory is '/home/joccnc/linuxcnc/configs/Prova01'
Machine configuration file is 'Prova01.ini'
INIFILE=/home/joccnc/linuxcnc/configs/Prova01/Prova01.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./Prova01.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: 10.10.10.10: Could not retrieve mac address
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=2058
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments


As I can see, the problem should be the Mesa board MAC address.
I didn't make any change (configuration, setup or else) last time I used the system (2 years ago), so I don't understand what happens.
Honestly, I made a first try with ChatGPT (I know, not the best idea but at the moment maybe.... - moreover it looks to me AS - Artificial Stupidity - more than AI - Intelligence....), but its suggestions were totally useless (some changes to ini and hal files), so I resumed my original files (attached).

Currently, LinuxCNC keep quitting; LinuxCNC correctly connects to the MESA Board.

My OS is LinuxCNC 2.7.14 + MESA 7i76e (Hybrid stepper drivers)

Can anyone help me to fix it?

Thanks

Andrea

Please Log in or Create an account to join the conversation.

More
9 months 2 weeks ago #341372 by PCW
Whats does the command:

ip a

report?

What happens if you:

ping 10.10.10.10

?

 

Please Log in or Create an account to join the conversation.

More
9 months 2 weeks ago #341385 by rodw
did you turn on power to the Mesa card before starting linuxcnc?

Please Log in or Create an account to join the conversation.

More
9 months 2 weeks ago #341434 by Jocman
did you turn on power to the Mesa card before starting linuxcnc?

yep, first thing I tried (a lot of times I got an error then I realized I forgot to switch on the machine)


Whats does the command:
ip a
report?
What happens if you:
ping 10.10.10.10


This is what I get with "ip a" and giving a ping:
Code:
joccnc@JocCnc:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 scope host lo        valid_lft forever preferred_lft forever     inet6 ::1/128 scope host        valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000     link/ether e8:4e:06:84:dc:c9 brd ff:ff:ff:ff:ff:ff     inet 192.168.1.245/24 brd 192.168.1.255 scope global dynamic eth0        valid_lft 863950sec preferred_lft 863950sec     inet6 fd59:b8bd:be6f:0:6bdd:2ca7:6e73:aa7b/64 scope global noprefixroute dynamic        valid_lft 7152sec preferred_lft 3552sec     inet6 fe80::6ed6:c856:a0cb:2db8/64 scope link        valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000     link/ether 70:85:c2:6a:f0:3d brd ff:ff:ff:ff:ff:ff     inet 10.10.10.11/8 brd 10.255.255.255 scope global eth1        valid_lft forever preferred_lft forever     inet6 fe80::8ede:25a1:ff4d:99b4/64 scope link        valid_lft forever preferred_lft forever joccnc@JocCnc:~$ ping 10.10.10.10 PING 10.10.10.10 (10.10.10.10): 56 data bytes 64 bytes from 10.10.10.10: icmp_seq=0 ttl=64 time=0.779 ms 64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.418 ms 64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.402 ms 64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.424 ms 64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.365 ms


eth0 is my second network card, I use it to reach my NAS, my LAN and the WEB
eth1 is the integrated network card, used by Mesa

giving the ping 10.10.10.10 I get response from Mesa
I just don't understand why eth1 report IP 10.10.10.11, when my hal file is set 10.10.10.10, and ping to 10.10.10.10 works.

BTW, after these tests I tried to start LinuxCNC, I get again an error message, but this time no mention about the MAC (is correctly reported), now the error is about HM2 registration:
Code:
Print file information: RUN_IN_PLACE=no LINUXCNC_DIR= LINUXCNC_BIN_DIR=/usr/bin LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc LINUXCNC_SCRIPT_DIR= LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules LINUXCNC_CONFIG_DIR= LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs INIVAR=inivar HALCMD=halcmd LINUXCNC_EMCSH=/usr/bin/wish8.6 LINUXCNC - 2.7.14 Machine configuration directory is '/home/joccnc/linuxcnc/configs/Prova01' Machine configuration file is 'Prova01.ini' INIFILE=/home/joccnc/linuxcnc/configs/Prova01/Prova01.ini PARAMETER_FILE=linuxcnc.var TASK=milltask HALUI=halui DISPLAY=axis Starting LinuxCNC... Starting LinuxCNC server program: linuxcncsvr Loading Real Time OS, RTAPI, and HAL_LIB modules Starting LinuxCNC IO program: io Starting HAL User Interface program: halui Found file(REL): ./Prova01.hal hm2: loading Mesa HostMot2 driver version 0.15 hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2 hm2_eth: 10.10.10.10: Hardware address: 00:60:1b:10:45:59 hm2_eth: discovered 7I76E-16 hm2/hm2_7i76e.0: Smart Serial Firmware Version 43 Board hm2_7i76e.0.7i76.0.0 Hardware Mode 0 = standard Board hm2_7i76e.0.7i76.0.0 Software Mode 0 = io_spin Board hm2_7i76e.0.7i76.0.0 Software Mode 1 = io_ana_spin Board hm2_7i76e.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv board fails HM2 registration Shutting down and cleaning up LinuxCNC... Running HAL shutdown script Killing task linuxcncsvr, PID=1208 hm2: unloading Removing HAL_LIB, RTAPI, and Real Time OS modules Removing NML shared memory segments

Please Log in or Create an account to join the conversation.

More
9 months 2 weeks ago - 9 months 2 weeks ago #341437 by PCW
The host address of 10.10.10.11 is fine, it must be different than the FPGA card
(but in the same subnet)

A failed HM2 registration usually means dropped packets, so there is something marginal
with the Ethernet connection.

What does:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10

report?

(it will run 1 minute before printing statistics)
 
Last edit: 9 months 2 weeks ago by PCW. Reason: sp

Please Log in or Create an account to join the conversation.

More
9 months 1 week ago #341647 by Jocman
sorry for being late in my answer, but job and family demand their time too.....This is what i get : joccnc@JocCnc:~$ sudo chrt 99 ping -i.001 -c 60000 -q 10.10.10.10
[sudo] password for joccnc:
PING 10.10.10.10 (10.10.10.10): 56 data bytes
--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.246/0.395/0.733/0.032 ms

Please Log in or Create an account to join the conversation.

Moderators: PCW, jmelson
Time to create page: 0.224 seconds
Powered by Kunena Forum