LinuxCNC not connecting to 7i96S on 2.9.1
20 Dec 2023 18:07 - 26 Dec 2023 18:55 #288684
by rowow
LinuxCNC not connecting to 7i96S on 2.9.1 was created by rowow
FIXED*** When installing the linux cnc OS I had the ethernet port connected to the internet. When doing a new install with it disconnected it worked. Some errors come up (see page 5 of thread), but try to get through them and it works.
Ive installed linuxcnc before successfully with my mesa card, but recently changed to a new computer and after a fresh install of 2.9.1 and following the exact same steps I did before to get my mesa controller running it now puts out the following when launching
[/code]
Ive installed linuxcnc before successfully with my mesa card, but recently changed to a new computer and after a fresh install of 2.9.1 and following the exact same steps I did before to get my mesa controller running it now puts out the following when launching
Debug file information:
Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
./Mill.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./Mill.hal:9: /usr/bin/rtapi_app exited without becoming ready
./Mill.hal:9: insmod for hm2_eth failed, returned -1
1818
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
Pinging 10.10.10.10 works great
[code]PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.585 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.354 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.385 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.358 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.383 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.375 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.370 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.371 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.283 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.351 ms
^C
--- 10.10.10.10 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9219ms
rtt min/avg/max/mdev = 0.283/0.381/0.585/0.073 ms
while reading through dozens of forum posts I used a command which got the mesa board information and pins through the terminal and it listed all its information successfully. I however forgot the command I used to be able to do again and post the results.
Last edit: 26 Dec 2023 18:55 by rowow.
Please Log in or Create an account to join the conversation.
20 Dec 2023 18:33 #288686
by PCW
Replied by PCW on topic LinuxCNC not connecting to 7i96S on 2.9.1
Usually the "resource unavailable" issue is something wrong
with the host setup or link status. Its often temporary after
making some change in the network settings.
To read the card info:
mesaflash --device 7i96s --addr 10.10.10.10 --readhmid > pins.txt
(and post pins.txt here)
Possibly unrelated but your ping times are quite long.
If you have an Intel Ethernet chip, you should disable
IRQ coalescing as described in the hm2_eth manual page:
man hm2_eth
You can try disabling this with a terminal command but
the setting will revert to the defaults after reboot so its
best to disable the IRQ coalescing in the interfaces file
as described in the hm2_eth manual page.
To disable IRQ coalescing on the command line:
sudo ethtool -C [Your_Ethernet_Device_Name] rx-usecs 0
Note that you may need to install ethtool on Debian
with the host setup or link status. Its often temporary after
making some change in the network settings.
To read the card info:
mesaflash --device 7i96s --addr 10.10.10.10 --readhmid > pins.txt
(and post pins.txt here)
Possibly unrelated but your ping times are quite long.
If you have an Intel Ethernet chip, you should disable
IRQ coalescing as described in the hm2_eth manual page:
man hm2_eth
You can try disabling this with a terminal command but
the setting will revert to the defaults after reboot so its
best to disable the IRQ coalescing in the interfaces file
as described in the hm2_eth manual page.
To disable IRQ coalescing on the command line:
sudo ethtool -C [Your_Ethernet_Device_Name] rx-usecs 0
Note that you may need to install ethtool on Debian
Please Log in or Create an account to join the conversation.
20 Dec 2023 18:52 #288687
by rowow
Replied by rowow on topic LinuxCNC not connecting to 7i96S on 2.9.1
reading the card info does not do anything.
and for disabling IRQ the ethernet_device_name would be enp1s0 or the custom name I gave it
and for disabling IRQ the ethernet_device_name would be enp1s0 or the custom name I gave it
Please Log in or Create an account to join the conversation.
20 Dec 2023 19:04 #288688
by PCW
Replied by PCW on topic LinuxCNC not connecting to 7i96S on 2.9.1
mesaflash --device 7i96s --addr 10.10.10.10 --readhmid > pins.txt
Will create a file "pins.txt" that you can post here
Also the results of the command
ip a
May be helpful
Will create a file "pins.txt" that you can post here
Also the results of the command
ip a
May be helpful
Please Log in or Create an account to join the conversation.
20 Dec 2023 19:08 #288689
by rowow
Replied by rowow on topic LinuxCNC not connecting to 7i96S on 2.9.1
found the output of pins.txt in the home directory. Attached it to this comment
this is the output of "ip a"
this is the output of "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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 54:ab:3a:de:23:19 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.11/24 brd 10.10.10.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::56ab:3aff:fede:2319/64 scope link
valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 6a:36:20:e7:46:71 brd ff:ff:ff:ff:ff:ff permaddr 7c:5c:f8:f3:05:c0Please Log in or Create an account to join the conversation.
20 Dec 2023 19:18 #288690
by PCW
Replied by PCW on topic LinuxCNC not connecting to 7i96S on 2.9.1
All looks OK, you might try disabling IRQ coalescing and see if that helps
sudo ethtool -C enp1s0 rx-usecs 0
sudo ethtool -C enp1s0 rx-usecs 0
Please Log in or Create an account to join the conversation.
20 Dec 2023 19:30 #288691
by rowow
Replied by rowow on topic LinuxCNC not connecting to 7i96S on 2.9.1
Did "sudo ethtool -C enp1s0 rx-usecs 0" no output,
Still error when starting linux cnc
Still error when starting linux cnc
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/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.1
Machine configuration directory is '/home/rowow/linuxcnc/configs/Mill'
Machine configuration file is 'Mill.ini'
INIFILE=/home/rowow/linuxcnc/configs/Mill/Mill.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
COORDINATES=XYZ
KINEMATICS=trivkins coordinates=XYZ
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
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./Mill.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
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: INFO: Hardware address (MAC): 00:60:1b:16:84:e8
hm2_eth: discovered 7I96S
hm2/hm2_7i96s.0: Low Level init 0.15
hm2/hm2_7i96s.0: Smart Serial Firmware Version 43
board fails HM2 registration
hm2_eth: in hm2_eth_reset
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
./Mill.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./Mill.hal:9: /usr/bin/rtapi_app exited without becoming ready
./Mill.hal:9: insmod for hm2_eth failed, returned -1
2930
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtimePlease Log in or Create an account to join the conversation.
20 Dec 2023 19:37 #288692
by PCW
Replied by PCW on topic LinuxCNC not connecting to 7i96S on 2.9.1
Did the ping times improve?
What is your servo thread period?
What is your servo thread period?
Please Log in or Create an account to join the conversation.
20 Dec 2023 19:43 #288693
by rowow
Replied by rowow on topic LinuxCNC not connecting to 7i96S on 2.9.1
Ping times did not improve.
Attached servo thread jitter screenshot
Attached servo thread jitter screenshot
Please Log in or Create an account to join the conversation.
20 Dec 2023 19:46 - 20 Dec 2023 19:47 #288694
by PCW
Replied by PCW on topic LinuxCNC not connecting to 7i96S on 2.9.1
What is LinuxCNC's servo thread period?
If the ping times did not improve, there is something preventing good
Ethernet latency. What is the host machine hardware?
If the ping times did not improve, there is something preventing good
Ethernet latency. What is the host machine hardware?
Last edit: 20 Dec 2023 19:47 by PCW.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.089 seconds