Advanced Search

Search Results (Searched for: 7i76e)

  • Todd Zuercher
  • Todd Zuercher's Avatar
24 Feb 2026 16:02
7i76EU+7i85+7i84U was created by Todd Zuercher

7i76EU+7i85+7i84U

Category: Driver Boards

First time using a Mesa Ethernet board and I'm trying to set up a new install.  I think I've flashed the right firmware to the 7i76eu.  But I can't seem to see the 7i84u card that I have plugged into the first serial connector on the 7i85.  The encoders seem to be working on the 7i85, but I can't seem to make the 7i84u work.  On the 7i85u CR2 and CR7 are on yellow and CR5 is on red.  Not sure what I'm doing/have done wrong.

Here's the output of mesaflash --device 7i76eu  --addr 10.10.10.10  --readhmid
twincnc@twincnc:~$ mesaflash --device 7i76eu  --addr 10.10.10.10  --readhmid
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I76
  FPGA Size: 20 KGates
  FPGA Pins: 256
  Number of IO Ports: 3
  Width of one I/O port: 17
  Clock Low frequency: 100.0000 MHz
  Clock High frequency: 160.0000 MHz
  IDROM Type: 3
  Instance Stride 0: 4
  Instance Stride 1: 64
  Register Stride 0: 256
  Register Stride 1: 256

Modules in configuration:

  Module: DPLL
  There are 1 of DPLL in configuration
  Version: 0
  Registers: 7
  BaseAddress: 7000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: WatchDog
  There are 1 of WatchDog in configuration
  Version: 0
  Registers: 3
  BaseAddress: 0C00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: IOPort
  There are 3 of IOPort in configuration
  Version: 0
  Registers: 5
  BaseAddress: 1000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: StepGen
  There are 5 of StepGen in configuration
  Version: 2
  Registers: 10
  BaseAddress: 2000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: MuxedQCount
  There are 6 of MuxedQCount in configuration
  Version: 4
  Registers: 5
  BaseAddress: 3600
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: MuxedQCountSel
  There are 1 of MuxedQCountSel in configuration
  Version: 0
  Registers: 0
  BaseAddress: 0000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: SSerial
  There are 1 of SSerial in configuration
  Version: 0
  Registers: 6
  BaseAddress: 5B00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 64 bytes

  Module: LED
  There are 1 of LED in configuration
  Version: 0
  Registers: 1
  BaseAddress: 0200
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for on-card -> 7I76
Pin#                  I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

TB2-4,5                 0   IOPort       StepGen          0        Dir/Table2      (Out)
TB2-2,3                 1   IOPort       StepGen          0        Step/Table1     (Out)
TB2-10,11               2   IOPort       StepGen          1        Dir/Table2      (Out)
TB2-8,9                 3   IOPort       StepGen          1        Step/Table1     (Out)
TB2-16,17               4   IOPort       StepGen          2        Dir/Table2      (Out)
TB2-14,15               5   IOPort       StepGen          2        Step/Table1     (Out)
TB2-22,23               6   IOPort       StepGen          3        Dir/Table2      (Out)
TB2-20,21               7   IOPort       StepGen          3        Step/Table1     (Out)
TB3-4,5                 8   IOPort       StepGen          4        Dir/Table2      (Out)
TB3-2,3                 9   IOPort       StepGen          4        Step/Table1     (Out)
Internal-Field-IO      10   IOPort       SSerial          0        TXData0         (Out)
Internal-Field-IO      11   IOPort       SSerial          0        RXData0         (In)
TB3-18,19              12   IOPort       SSerial          0        TXData1         (Out)
TB3-16,17              13   IOPort       SSerial          0        RXData1         (In)
TB3-13,14              14   IOPort       MuxedQCount      2        MuxQ-IDX        (In)
TB3-10,11              15   IOPort       MuxedQCount      2        MuxQ-B          (In)
TB3-7,8                16   IOPort       MuxedQCount      2        MuxQ-A          (In)

IO Connections for P1
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                     17   IOPort       SSerial          0        RXData6         (In)
14                     18   IOPort       SSerial          0        TXData6         (Out)
 2                     19   IOPort       SSerial          0        RXData5         (In)
15                     20   IOPort       SSerial          0        TXData5         (Out)
 3                     21   IOPort       SSerial          0        RXData4         (In)
16                     22   IOPort       SSerial          0        TXData4         (Out)
 4                     23   IOPort       SSerial          0        RXData3         (In)
17                     24   IOPort       SSerial          0        TXData3         (Out)
 5                     25   IOPort       SSerial          0        RXData2         (In)
 6                     26   IOPort       SSerial          0        TXData2         (Out)
 7                     27   IOPort       MuxedQCountSel   0        MuxSel0         (Out)
 8                     28   IOPort       MuxedQCount      0        MuxQ-A          (In)
 9                     29   IOPort       MuxedQCount      0        MuxQ-B          (In)
10                     30   IOPort       MuxedQCount      0        MuxQ-IDX        (In)
11                     31   IOPort       MuxedQCount      1        MuxQ-A          (In)
12                     32   IOPort       MuxedQCount      1        MuxQ-B          (In)
13                     33   IOPort       MuxedQCount      1        MuxQ-IDX        (In)

IO Connections for P2
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                     34   IOPort       None           
14                     35   IOPort       None           
 2                     36   IOPort       None           
15                     37   IOPort       None           
 3                     38   IOPort       None           
16                     39   IOPort       None           
 4                     40   IOPort       None           
17                     41   IOPort       None           
 5                     42   IOPort       None           
 6                     43   IOPort       None           
 7                     44   IOPort       None           
 8                     45   IOPort       None           
 9                     46   IOPort       None           
10                     47   IOPort       None           
11                     48   IOPort       None           
12                     49   IOPort       None           
13                     50   IOPort       None      
  • Stormbird
  • Stormbird
23 Feb 2026 13:49
Replied by Stormbird on topic looking for Mesa 7I76E card

looking for Mesa 7I76E card

Category: User Exchange

I have one unused, never connected, bought from Mesa in California in 2017, been sitting in a drawer in my desk ever since. Oxford, UK for £150 please
  • Christian
  • Christian
21 Feb 2026 12:20
Replied by Christian on topic Mesa 7i76EU - how to enable mode 2?

Mesa 7i76EU - how to enable mode 2?

Category: Computers and Hardware

Hello everyone,
First of all, thanks to PCW for pointing out that `sserial_port_0=20000000` in the driver config **should enable Mode 2**:

> In the driver config string will set the mode to 2 which will enable both the MPG encoder inputs and analog inputs.  
> Note that the encoder inputs are intended for MPG use and are fairly slow and do not support index.  
> You would normally use the 7I76EU high speed encoder input for the spindle (TB3 pins 7..15).

I have a **brand new Mesa 7I76EU** for my Maho MH400 mill and I want to use **Mode 2**:
- Inputs 16–19 for an **MPG handwheel (ABZ encoder)**  
- Inputs 00–03 as **analog inputs** for feedrate and spindle override

**What I have tried so far:**  
- In the `.ini` under `[HOSTMOT2]` I set:

[HOSTMOT2]
DRIVER=hm2_eth
BOARD=7i76eu
CONFIG="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=20000000"


- In the HAL, the card is loaded like this:

loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=20000000"
setp [HMOT](CARD0).watchdog.timeout_ns 5000000


- LinuxCNC detects the card correctly:

hm2_eth: discovered 7I76EU
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


**Problem / Open Questions:**  
- Despite this configuration, the card **does not automatically operate in Mode 2**.  
- I want to use the analog inputs and the MPG handwheel simultaneously, and monitor the spindle with an ABZ encoder, but the Mode 2 functionality does not seem active yet.  
- Is it possible that the mode must be **physically set via jumpers**, or is there another driver/firmware parameter I am missing?  
- Attempts to flash a Bitfile did **not work**.

Any advice on how to reliably activate Mode 2 without LinuxCNC entering a fault state would be greatly appreciated.

Thanks in advance!  
Christian
  • DerKlotz
  • DerKlotz
21 Feb 2026 12:09 - 21 Feb 2026 12:51
Replied by DerKlotz on topic Add Buttons in Probe Basic

Add Buttons in Probe Basic

Category: QtPyVCP

You mean that led at the attached photo? I can´t find a probe section in QT Designer or do i need to be in Probe Basic Development modus instaed of stable?

And can you help me here -> 
However, I don't know how to link the light switch to the output of my Mesa 7i76e. I tried to implement "net light => hm2_7i76e.0.7i76e.0.0.output-02 <= qtpyvcp.light" in my postgui_hal. Unfortunately, that didn't work.

 
  • DerKlotz
  • DerKlotz
20 Feb 2026 11:45 - 20 Feb 2026 14:41
Replied by DerKlotz on topic Add Buttons in Probe Basic

Add Buttons in Probe Basic

Category: QtPyVCP

Hello,I've been working on this for the last few days and now understand how to add switches graphically under user_buttons/template_main/template_main.ui (see attached photo).However, I don't know how to link the light switch to the output of my Mesa 7i76e, for example. I tried to implement net light => hm2_7i76e.0.7i76e.0.0.output-02 <= qtpyvcp.light in my postgui_hal. Unfortunately, that didn't work. What am I overlooking as a newbie? 
And in addition i´d like to have a nice looking Led right to the button. Red = off, green = on. I could not find one in QT Designer. Alternatively, the button itself could change from red to green.

Translated with DeepL.com (free version)
  • summat
  • summat
19 Feb 2026 16:49

Mini PC for LinuxCNC/CPU Realtime Performance

Category: Computers and Hardware

I'll hijack this thread, as my use-case is a "mini PC" NUC gen-11 i3, modest performance but which should more than adequate for LinuxCNC. Running 2.9.0 (though able to update... however same behaviour verified with another user here with standard desktop and 2.9.8).

With a Mesa 7i76e (other user: 7i92) - just observing HAL pins, whilst rebuilding an old Boxford 160 set-up I noticed that the HAL Write.Time pin was bubbling around 10,000-12,000 (so, 10us-12us) - which looked quite respectable given that the HM2 is scheduled on servo thread at 1ms. The hm2.read, however, was around 800,000-900,000 (verified on other user's 7i92 also), That, to my uneducated mind is getting a bit close to the limits of the 1ms servo thread. Do other people see similar performance / behaviour with Mesa cards?

I'll dig deeper and Wireshark the set-up. I should say that my particular environment the NUC wired interface is hooked to the Mesa, and I use WiFi for internet. Other user is dedicated wired interface to the machine without internet.
  • DerKlotz
  • DerKlotz
16 Feb 2026 14:10
Add Buttons in Probe Basic was created by DerKlotz

Add Buttons in Probe Basic

Category: QtPyVCP

Hello,
i need some buttons in Probe basic which activates outputs from my Mesa 7i76e. The attached photo show what i need. 
I found /user_buttons/template_user_buttons/template_user_buttons.ui (attached). Would that a nice place add the buttons. But so far i don´t know how to start the ui ind Probe Basic GUI.

Best regards
 
  • PCW
  • PCW's Avatar
15 Feb 2026 03:06

Mesa 7I76EU – Fixing „Unsupported ethernet device – No 7I76EU board found” Error

Category: Driver Boards

The 7I76EU is compatible with 7I76E hal/ini files, so you can
just select "7I76E" in pncconf.
  • Pupy1993
  • Pupy1993
15 Feb 2026 02:13

Mesa 7I76EU – Fixing „Unsupported ethernet device – No 7I76EU board found” Error

Category: Driver Boards

Hello. 
I'm new in this form. I couldn't config my Mesa Card 7i76EU, the PncConf doesn't show the 7i76eu. I'm using Linux CNC 2.9.8. Thanks in advance.
  • PCW
  • PCW's Avatar
14 Feb 2026 20:07
Replied by PCW on topic Mesa 7i76EU - how to enable mode 2?

Mesa 7i76EU - how to enable mode 2?

Category: Computers and Hardware

sserial_port_0=20000000

In the driver config string will set the mode to 2 which will enable both
the MPG encoder inputs and analog inputs.

Note that the encoder inputs are intended for MPG use and

1. Are fairly slow
2. Do not support index

You would normally use the 7I76EU high speed encoder input for the
spindle (TB3 pins 7..15)
  • Christian
  • Christian
14 Feb 2026 09:37
Mesa 7i76EU - how to enable mode 2? was created by Christian

Mesa 7i76EU - how to enable mode 2?

Category: Computers and Hardware

Hello everyone,I’m looking for some help with my MESA 7i76EU configuration.I would like to use Mode 2. According to the manual, in this mode inputs 16–19 can be used for the encoder signals of an MPG handwheel, and inputs 00–03 are converted into analog inputs. I would like to connect potentiometers to these analog inputs to override the feed rate and spindle speed.At the same time, I would like to use the encoder interface of the MESA with an ABZ encoder to monitor the spindle speed. As far as I understand, the 7i76EU is designed for exactly this purpose.My question:
How do I switch the MESA to Mode 2?So far I have tried setting the parameter
sserial_port_0=20000000
in the .hal file.
I also tried flashing a new bitfile that should change the mode, but that didn’t work either.Maybe it’s much simpler and the MESA detects analog signals automatically?
Or does the mode have to be changed via jumpers?At the moment I’m a bit stuck with my research (manual, internet, and AI didn’t get me any further), so I would really appreciate any advice or hints.Thanks a lot!
  • tommylight
  • tommylight's Avatar
07 Feb 2026 17:54
Replied by tommylight on topic Maho mh800w retrofit

Maho mh800w retrofit

Category: Milling Machines

.... i can manually latch relay 19k1 by holding on the contactor with a screw driver.

Never smart to do that to machines.

.... but the x and z servos are rotating slowly but smoothly.

This means that LinuxCNC has no control over the servo drives, usually incorrect or missing wiring, like are the encoders wired to Mesa and do they work correctly counting up/down on the LinuxCNC DRO ?

Then when i update the hal file to electronically latch 19k1 with f2 it will not hold and drops relays straight away.

What error does LinuxCNC show when that happens?
I would bet it shows "joint.n.following-error" as noted on my second reply.
-
You are working on a complicated machine, so it is imperative to follow instructions strictly and as listed in priority.
See this for wiring and testing:
forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77
And for network and WiFi to work at the same time, see here
forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards
  • NWE
  • NWE's Avatar
02 Feb 2026 22:43 - 02 Feb 2026 23:07

MAC address not retrieved (after 2 years stop)

Category: Driver Boards

Jocman post=342013 userid=24026
As I've 2 lan cards (the onboard and a second PCI board), I tried to launch
ip a
when connected to both, and this is what I get:
connected to Mesa (onboard card):

joccnc@JocCnc:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
-- snip --
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 10.10.10.11/8 brd 10.255.255.255 scope global eth0
-- snip --
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 70:85:c2:6a:f0:3d brd ff:ff:ff:ff:ff:ff
joccnc@JocCnc:~$

and pinging  my router:

joccnc@JocCnc:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sending packet: Network is unreachable



connected to WEB:

joccnc@JocCnc:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
-- snip --
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
-- snip --
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 70:85:c2:6a:f0:3d brd ff:ff:ff:ff:ff:ff
joccnc@JocCnc:~$

and pinging my router:

joccnc@JocCnc:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.651 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.488 ms

[\quote]

 

Going by your most recent answer I interpret the above:

It appears to me you have two network configurations "Web" and "Mesa 7i76e" In both configurations you appear to have the first network port selected. This means, when you click on the "Mesa 7i76e" network, the pc tries to connect to the Mesa card via the network port that is connected to your LAN.

To fix, right-click on the network icon, click "edit connections", click on "Mesa 7i76e", click on the little gear at bottom "edit the selected connection", click on the "Device" dropdown, and select the correct device, click on "IPv4 Settings" tab, make sure the "Gateway" field is empty. click "Save", close the network edit window, and try reconnecting to both networks. On my system, I have both networks connected at the same time.

Don't change settings for the "Web" connection, from what I see, that one is likely configured correctly.
  • Jocman
  • Jocman
01 Feb 2026 17:27 - 01 Feb 2026 17:29

MAC address not retrieved (after 2 years stop)

Category: Driver Boards

It'5 days i'm away for work, hopefully tomorrow evening i can come back to my cnc.
Anyeway, to give an answer to tommilight and nwe.
I've 2 phisical lan cards. The 1st (let say A) is the MB's onboard lan card, the 2nd (let say B ) is a separate PCI card.
A is connected directly to mesa card. B is connected to my domestic LAN (then to my router). 2 different phisical cables. This because, if I remember, mesa cards don't love to be connected via router.
Untill 2 years ago, when I worked with my cnc, I used to connect to A (I don t remember if eth0 or eth1), that case my cnc worked perfecly, but i didn't have any access to the web or to my nas.
Then, if I connected to B (in case I need to access the web or my Nas) obviusly the cnc wasn't available.
But I remember I hade 2 different networks (eth0 and eth1).
This year something happened (I didn't do anything but start the pc), so if I connect to the web, i can access internet,but if I connect to mesa (and linux tell me "you're connected to mesa 7i76e) linuxcnc gives me errors.
Now, ok i can try to setup again the network as tommylight suggests, but could it be better to phisically remove the PCI card (B )? I do not need internet or access to my nas whe I use my cnc (that pc is exclusively dedicated  to the cnc machine), I can easily use a normal usb pendrive to transfer the cnc files (I design and program my jobs on another pc),I just care about having my cnc working......


 
  • PCW
  • PCW's Avatar
30 Jan 2026 14:59 - 30 Jan 2026 15:00

OMRON Yaskawa controllers, what I/O board would you choose

Category: Driver Boards

For step/dir, Mesa 7i96S is the right choice, and if you do need more IO add Mesa 7i84 with 32 inputs and 16 outputs and wires to 7i96S with a simple cut down LAN cable.

If need more I/O than a 7I96S can provide, a 7I76EU is a one card solution (basically a 7I96S+7I84U on one card)
Displaying 31 - 45 out of 514 results.
Time to create page: 0.561 seconds
Powered by Kunena Forum