1. Forum
  3. Search

Advanced Search

Search Results (Searched for: 7i76e)

  • Jocman
  • Jocman
Yesterday 17:50
Replied by Jocman on topic MAC address not retrieved (after 2 years stop)

MAC address not retrieved (after 2 years stop)

Category: Driver Boards

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:
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:
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
  • PCW
  • PCW's Avatar
14 Jan 2026 18:50
Replied by PCW on topic Custom large scale 4 axis wire cutter and a retrofit of an existing CNC

Custom large scale 4 axis wire cutter and a retrofit of an existing CNC

Category: CNC Machines

1. Suggested pullup is 2.2K 1/2w for 24V. The only disadvantage of the pullup is the wiring nuisance.
10K will not work.

2. Enable on simple step/dir drives is not of much value safety wise as it's very unlikely to have a runaways
without the control generating step/dir pulses (and step generation will stop on a LinuxCNC or communication fault)

3. Its important that the default state of 7I76EU outputs be the safe state as all outputs will return to the power up state on
communication loss. This initial state is all outputs open circuited (this is true even if the outputs were set to push-pull mode)
  • Avion
  • Avion
14 Jan 2026 16:32
Custom large scale 4 axis wire cutter and a retrofit of an existing CNC was created by Avion

Custom large scale 4 axis wire cutter and a retrofit of an existing CNC

Category: CNC Machines

Hey everyone, 

1.5 years ago i bought a CNC mill. It was a used portal cnc (barely used) with chineese base and german splindle, table, controller and linear rails upgrade by a manufacturer in Germany. It was based on CNC Graf and I always had issues with it. Either Fusion to cnc gcode was faulty, did not execute all commands etc. etc. etc. 
I grew and also wanted to build a large scale foam cutter for 1:1 RC plane replicas. So i said its the perfect time to retrofit the old cnc and to build the new 4 axis foam wire cutter and build it with linuxcnc and on the base of mesa7176EU. 
I bought all parts for the wire cutter and some upgrades for the existing cnc (touch probe, hand wheel, two tool measure sensors). 

This is the wire cutter design i made. 
https://imgur.com/a/XOdKh2n
File Attachment:


I had so many issues even getting linuxcnc up and running for the mesa ...  Of course due to my limited experience with debian but also since there are so many unknowns on the mesa world as well.
I thought I will share my project (s) here and also post the wiring diagram and the configuration as i am continuing. 
Right now i finally got the motors spinning and hal machine enabled properly and am working on setting up the limit switches for the axis. 

The first questions that are right now open are in this direction. I will post later the configuration right now for the portal CNC. The wire-cutter is build in parrallel but priority has of course the retrofit of the portalCNC to get at least one thing back online. Wirecutter:
  1. How do I configure multiple Y and Z axis in axis configuration for wire. I have two L legs basically so i need to control 4 Axis. In the linuxCNC setup i only saw the configuration for the XZY and XZYA. It should in the end basically have two heads ;).
Portal CNC
  1. We have NPN NO sensors and are connecting them to a mesa board that has “sinking inputs”. I understand that a pull up resistor is required for it to work, but is it the “good way” or would it be better and safer to use a PNP NC Sensor.  Bear in mind that our sensor is a limit and homing switch for each axis. And if a pullup resistor is okay to go with, then will the difference between 2kOhm and 10kOhm  be important for accuracy ?
  2. Stepper driver DM556 ENA+ and ENA - with mesa 7i76eu.
    The default for them is to be left not connected when using different controls(STEP+- and DIR+-), but are there any long term downsides to it? any way to use them for improving safety of cnc operation.
  3.  If I understand correctly, reversing inputs/outputs in HAL makes changes operational only when the linux cnc terminal is operational and connected to the mesa board, in any other state the outputs will be “as they are” not “as set up” ? Or some of the configuration (In systems like(PC(Linuxcnc) - ethernet - mesa) is stored on mesa? If so, then what are the good practices about what should be done hardware wise and what can be safely done software side.
  • Jocman
  • Jocman
14 Jan 2026 13:43
MAC address not retrieved (after 2 years stop) was created by Jocman

MAC address not retrieved (after 2 years stop)

Category: Driver Boards

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
  • rodw
  • rodw's Avatar
13 Jan 2026 21:12
Replied by rodw on topic Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help

Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help

Category: Installing LinuxCNC

This video of mine explains how to set up the network.


if you type man hm2_eth it explains how to edit the network file to set a fixed Ip address for the 10.10.10.1 IP address on the PC (after you review the output from the IP a command tommy mentions
  • tommylight
  • tommylight's Avatar
13 Jan 2026 15:55
Replied by tommylight on topic Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help

Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help

Category: Installing LinuxCNC

Can you post what
ip a
in a terminal returns?
  • geostu34
  • geostu34's Avatar
13 Jan 2026 04:51
Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help was created by geostu34

Need help setting up Mesa 7I76EU and Linux CNC, I will pay $100 if someone help

Category: Installing LinuxCNC

I need help setting up my Mesa Card. I believe I have an issue with setting up the IP Address in the computer. I can load Linuxcnc but can get the card to connect. I will pay $100 to someone to walk me through it on the phone or connect directly to my computer. I know nothing about Linux. I want to get this setup asap

george
  • PCW
  • PCW's Avatar
06 Jan 2026 17:45 - 06 Jan 2026 18:29
Replied by PCW on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

If you wish to test the inputs, disconnect all external devices from the inputs
and test each input by connecting it to field power (+24V in your case)
Note the touching the screw on the connector is not reliable unless the screw is tight

If the NPN limit switch outputs are not very close to ground in one state,
you still have a wiring error.
  • Bendandsend
  • Bendandsend
06 Jan 2026 17:07
Replied by Bendandsend on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

I rewired my psu input from psu > wagos > mesa input > field to psu > mesa > field > wagos but no change sadly.

Oddly enough, I can jump between gnd and input pins 13 and 12 and get a change of state using showpin, but nothing down to pin 8. And thats without a resistor on any input except for 8.
  • PCW
  • PCW's Avatar
06 Jan 2026 15:35
Replied by PCW on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

Those voltage values indicate a wiring issue.

With NPN sensors, one state should be very close to GND  (<1V)
How high the voltage is in the other state depends on the pullup resistance
which may be infinite (no pullup) or some intermediate voltage depending on the
pullup resistance (some NPN proximity switches have built in weak pullups)

Because the low levels are not close to GND, it sounds like the the NPN proximity
switch common is not connected to the field power common.

 
  • jimmyrig
  • jimmyrig
06 Jan 2026 15:00
Replied by jimmyrig on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

Had the same issue, double check your wiring of the orange block. If it's wrong it won't power up and you'll get the issue your are seeing.
  • Bendandsend
  • Bendandsend
06 Jan 2026 06:00
Replied by Bendandsend on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

Thank you so much for the response, I have been going through a trial and a half with this install :') I bought some 2.2k 1/2W resistors just for this project, and have been battling to get a result

In halshow, none of the inputs change state, even the estop. But watchpin in the terminal shows clearly that estop, probe and for whatever reason, Z max (Home) limit switch change state even though it currently doesn't have a pullup. I only get a reaction from Z max when sensor is active.

I currently have a pullup on my X min, but can't get any reaction out of it no matter what state the proximity switch is in (on/off or jumper to GND) when using watchpin.

Just for reference as to wiring, I have all +wires > COM+> +WAGO fed by +FIELD, same setup for GND. Then individually connected sensor wires to MESA inputs. Pretty obvious, but just in case, I figured I best note it.

Also, I figured I will include multi readings in both states for all inputs with sensors on and off. X max excluding as I have found it to be dead. I will be replacing all of these anyway with PNP when they arrive. But was hoping to atleast get it running.

Readings are as follows:

X max DEAD
X min 3.9 off, 7.8 on
Y max 14.7 off, 18.4 on
Y min 12.3 off, 8.3 on
Z max 8.0 off, 14.9 on
Z min 12.4 off, 9.0 on

Readings might be telling or maybe not?

My GUI is also massive and a PITA, so I have mostly been doing my stuff through SSH. No matter what commands I send, I cant get the GUI to scale properly :( that's everything on the screen though, for whatever reason, my mini pc with Debian 12 cant seem to recognize the screen through HDMI. Any suggestions there would be absolutely amazing!
  • tommylight
  • tommylight's Avatar
05 Jan 2026 15:30
Replied by tommylight on topic MESA 7i76eu Firmware

MESA 7i76eu Firmware

Category: Driver Boards

Already replied on the other topic.
  • PCW
  • PCW's Avatar
05 Jan 2026 14:32
Replied by PCW on topic 7i76EU GPIO inputs completely frozen - not updating in real-time

7i76EU GPIO inputs completely frozen - not updating in real-time

Category: Driver Boards

7I76EU inputs are sinking inputs, that is, they detect a positive voltage
relative to field power ground. They will read "low" in hal until there are at
~60% of field voltage (~+14.4V at +24V field voltage)

If you use proximity switches, they should be PNP (sourcing) type.
NPN type switches would need a pullup (say 2.2K 1/2W) resistor to
+24V to work.
  • Bendandsend
  • Bendandsend
05 Jan 2026 10:11
Replied by Bendandsend on topic MESA 7i76eu Firmware

MESA 7i76eu Firmware

Category: Driver Boards

Hey Tommylight — thanks for the reply just to close the loop on that earlier issue

I did get past the firmware/install side in the end. After a few messy attempts, I wiped everything and went with a fresh Debian 12 install, then installed LinuxCNC separately (rather than relying on bundled firmware paths). That got the 7i76EU fully detected, firmware loaded cleanly, and all stepgens running perfectly.

Where I’m stuck now is further downstream: the limit/prox inputs. The board, smart-serial, and motion side are all behaving exactly as expected, but the GPIO inputs appear frozen and don’t update in HAL even when shorted directly to GND.

So the original “missing firmware” problem is solved — this is a new issue on the input side, which is what I’m trying to chase down now.

I created a fresh topic on it to try and nail it down as its hopefully my final port of call for a while.
Displaying 1 - 15 out of 543 results.
  1. Forum
  3. Search
Time to create page: 0.361 seconds
Powered by Kunena Forum