Advanced Search

Okay thank you all this info helps a lot. But simply moving the w3 from down to up will not change the board address to 10.10.10.10 alone. Do I basically have to do step 3 like in this post here to change the board address to 10.10.10.10? forum.linuxcnc.org/12-milling/44860-sett...on-a-mesa-card-7i76e

There was a time you had to know about networks but now its all dumbed down via DHCP.
Sounds like you need to watch my video wich goes through this about 16 minutes in

Maybe the Mesa card manuals (if anyone reads them) needs to state that the computer & Mesa card must have different addresses. Or something along these lines. It keeps coming up from time to time.

I don't know much about networking but when I type "hostname -I"into the terminal to check my computer's IP address I get 192.168.1.121 so they are the same I see now.

Probably the same address on the PC, so that might return "connection refused".
Change the 121 at the end to 100.

What's the IP address of the computer and is the ethernet cable known to be good ?

I am not using a network switch and the jumpers are at default position. This is how I have the board connected in the attached.

RMJ wrote:

hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 192.168.1.121: Connection refused

Debug file information:
Note: Using POSIX realtime hm2_eth: Itapi_app_main: Connection refused (-111)

I would guess the Mesa is wired to a network switch and there is something else there with the same IP address, as i have never ever seen a "connection refused" from a Mesa board.
So how is the Mesa wired to the PC? It should be directly wired, not switch or hub or router.
What is the jumper settings on Mesa regarding the IP address?
Did you check the manual?

Hey everyone! This is my first post and first time installing and configuring Linuxcnc with a Plasma Table that has four Clearpath servo motors and a MESA 7i76e and THCAD-10. I have reinstalled multiple different versions of Linuxcnc trying to solve my problems. So far the 2.7 stretch version of Linuxcnc connects to the 7i76e just fine and I am able to jog the motors but this version missing the slave axis functions I need for my machine's gantry with two motors. Every single later version of Linuxcnc 2.8 and 2.9 give me network configuration problems but has the slave axis(tandem axis) functions my machine needs. I decided to go with the newest version of Linuxcnc 2.9.2 I went through the pncconf and made a base configuration with IP address 192.168.1.121 now when I open the configuration I get stuck on getting Linuxcnc to start due to this error:

Print file information: RUN_IN_PLACE=nO
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/ust/bin
LINUXCNC_TCL_DIR=/ust/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/ust/lib/linuxcnc/modules
LINUXCNC CONFIG DIR=
LINUXCNC_LANG_DIR=/usI/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HAL CMD=halcmd
LINUXCNC_EMCSH=/ust/bin/wish8.6
LINUXCNC - 2.9.2
Machine configuration directory is '/home/rolando/linuxcnc/configs/my_LinuxCNC_machine'
Machine configuration file is "my_LinuxCNG_machine ini"
INIFILE=/home/rolando/linuxcnc/configs/my_LinuxCNC_machine/my_LinuxCNC_machine.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY-gmoccapy
COORDINATES=XYYZ
KINEMATICS=trivkins coordinates=XYYZ kinstype=B0TH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvi
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): -/my_LinuxCNC_machine.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script

identityKinematicsSetup: coordinates:XYYZ
Joint 0 ==> Axis X
Jount 1==> AKIS Y
Joint 2 ==> Axis Y
Joint 3 ==> Axis Z

hm2: loading Mesa HostMot2 driver version a.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 192.168.1.121: Connection refused
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: Itapi_app_main: Connection refused (-111)
/my_LinuxCNC_machine.hal:9: waitpid failed /ust/bin/tapi_app hm2_eth
_/my_LinuxCNC_machine.hal:9: /ust/bin/rtapi_app exited without becoming ready
-/my_LinuxCNC_machine.hal:9: insmod for hm2_eth failed, returned -1
1718
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

forum.linuxcnc.org/24-hal-components/329...i76e?start=40#295082

You can look here. My psb also works but requires 5v source without ripples.

To check for an EMI issue, you could monitor
hm2_7i76e.0.packet-error-total in the watch tab of
halshow to get an indication of how often packets
are dropped.

Also you might try pinning the Ethernet IRQ to the
last CPU (the one LinuxCNC uses for real time) 
This requires that you isolate the last CPU with
an isolcpus statement in your grub file
(isolcpus=3 for a 4 core CPU for example)
And then pinning the Ethernet IRQ to that CPU

 

The "Watchdog has bit" error typically indicates major latency issues on the host

What are your ping times if you ping the 7I76E?

ping -i .2 -c 4 10.10.10.10
sudo chrt 99 ping -i .001 -q 10.10.10.10

The first command populates the ARP cache so the ARP lookup doesn't add time to the first ping
The second command should be run for a few minutes (and the stopped with a control C)
 

Hallo Andi,
krankheitsbedingt muss ich leider meine beiden Mesa Karten 7i76e und 7i85 abgeben.
beide sind neu und unbenutzt
bei Interesse bitte ich um Kontaktaufnahme mit mir
Gruß Michael

Try Portugal at www.eusurplus.com, they should have 7i96S
And there is no 7i96E but there is 7i76E.

thanks for your help. i have now comment one more line to use the io tool-prepared.

when i now push the button after M6 Tx it justfires a small pulse to the atc_zylinder and then it shows the correct toolnumber in linuxcnc.


BUT the small pulse is to short to insert the tool / unclamp. I think that pushing the button fires the tool changed and then tool-change is not active anymore.

Maybe a way could be to watch the button rising and falling edge??
or could it makes more sense to tr the hal component "manualtoolchange" out?