Homemade CNC Plasma - hypertherm, Mesa, gear drives, nema 34.

Thanks PCW.

I'll try an reconnect the ohmic to a different encoder A pin.

Also need to work on the air scribe next.

Its been a very busy few days. slowly getting tools dialed in for the new machine. Still a long way to go with ohmic sensing and the air scribe, but I'm happy with how everything is moving. the factory hypertherm cut charts are about 1000mm/min off what is actually working.

so working away and everything is going great, until. went to cut some plate today for the air scribe, turn everything on and then, she no connect. Worked fine a few days ago.

This is the error and i can't find a fix. Help

$ linuxcnc
LINUXCNC - 2.9.3-125-g62642dde63
Machine configuration directory is '/home/cnc/linuxcnc/configs/T19'
Machine configuration file is 'T19.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./T19.hal

identityKinematicsSetup: coordinates:XYYZ
   Joint 0 ==> Axis X
   Joint 1 ==> Axis Y
   Joint 2 ==> Axis Y
   Joint 3 ==> Axis Z
identityKinematicsSetup: Recommend: kinstype=both

hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 10.10.10.10: Connection refused
hm2_eth: rtapi_app_main: Connection refused (-111)
./T19.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./T19.hal:9: /usr/bin/rtapi_app exited without becoming ready
./T19.hal:9: insmod for hm2_eth failed, returned -1
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: unloading
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal



 

I would guess you changed the IP on the PC ....
That error is almost always due to PC having the IP set at 10.10.10.10 (or 192.168.1.121), set it to anything else for the last 2 (or 3) digits:
10.10.10.11 is fine
192.168.1.100 is fine
etc.
Edit:
check with
ip a

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp3s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 78:7b:8a:b4:e1:b9 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.10/0 brd 255.255.255.255 scope global noprefixroute enp3s0f0
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether a8:be:27:c0:1f:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.102/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
valid_lft 4044sec preferred_lft 4044sec
inet6 2401:d006:d001:9301:b2bb:20c1:e292:519/64 scope global dynamic noprefixroute
valid_lft 539sec preferred_lft 539sec
inet6 fe80::5009:8b29:227e:d171/64 scope link noprefixroute
valid_lft forever preferred_lft forever

RNJFAB wrote:

2: enp3s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 78:7b:8a:b4:e1:b9 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.10/0 brd 255.255.255.255 scope global noprefixroute enp3s0f0
valid_lft forever preferred_lft forever

Yup, exactly, set to 10.10.10.10.
If you used the Network Manager to configure the PC, use it again to change it to 10.10.10.11 or 10.10.10.100 , save, disconnect and connect again.
If you edited the /etc/networks file, edit it there.