I don't have the tab with "7i76 I/O,

 

You should get a screen like this:

 

If not. it may be that you have hit a locale bug in pncconf and may have to
temporarily set the locale language to  en_US to work around the issue.

Hallo,
ich bin gerade am Umbau einer ISEL CPM3020 von IMC4 auf MESA 7i76EU. Die Kommunikation von LinuxCNC zur Karte funktioniert.
Aktuell hänge ich an der Konfiguration der Referenz- und Endschalter fest. Ich versuche via Pncconf die Pins festzulegen, finde aber im Menu "Mesa Karte 0" nur Zuordungen für TB2/TB3, P1 und P2. Bei P1/P2 könnte ich die Schalter zwar anlegen, dann bekomme ich aber Pin Nummern die m.E. mit den Field I/Os nichts zu tun haben sondern nur mit den I/O Expansion connectoren. Ich habe trotzdem mal darüber die Schalter konfiguriert, das Ergebnis sieht in der HAL Datei dann wie folgt aus (Leerzeilen entfernt):# externe Signaleingänge
# --- MIN-HOME-X ---
net min-home-x     <=  hm2_7i76e.0.gpio.017.in
# --- MAX-X ---
net max-x     <=  hm2_7i76e.0.gpio.018.in
# --- MIN-HOME-Y ---
net min-home-y     <=  hm2_7i76e.0.gpio.019.in
# --- MAX-Y ---
net max-y     <=  hm2_7i76e.0.gpio.020.in
# --- MIN-Z ---
net min-z     <=  hm2_7i76e.0.gpio.021.in
# --- MAX-HOME-Z ---
net max-home-z     <=  hm2_7i76e.0.gpio.022.in


Eine Konfigurationsseite für TB5 oder TB6 zur Konfiguration der Field I/Os kann ich nicht finden. Wo ist mein Denkfehler? 

I just did this for my CNC. Here are the HAL bits I used.  Amusingly, I can't find where <axis>-fault is connected, but I *do* get following errors when I hit things.  More testing required...

addf and2.3 servo-thread
addf and2.4 servo-thread
addf and2.5 servo-thread
addf and2.6 servo-thread
addf and2.7 servo-thread
addf timedelay.0 servo-thread

setp timedelay.0.on-delay 1
setp timedelay.0.off-delay 0

net machine-is-on => timedelay.0.in
net enable-faults <= timedelay.0.out

net x-enable  => hm2_7i76e.0.7i76.0.0.output-08 # TB5 leftmost output
net y-enable  => hm2_7i76e.0.7i76.0.0.output-09
net y2-enable => hm2_7i76e.0.7i76.0.0.output-10
net z-enable  => hm2_7i76e.0.7i76.0.0.output-11
net a-enable  => hm2_7i76e.0.7i76.0.0.output-12

# HLFB is true when enabled *and* following
net hlfb_x  hm2_7i76e.0.7i76.0.0.input-16-not # TB5 leftmost
net hlfb_y  hm2_7i76e.0.7i76.0.0.input-17-not
net hlfb_y2 hm2_7i76e.0.7i76.0.0.input-18-not
net hlfb_z  hm2_7i76e.0.7i76.0.0.input-19-not
net hlfb-a  hm2_7i76e.0.7i76.0.0.input-20-not

net hlfb_x        => and2.3.in0
net enable-faults => and2.3.in1
net x-fault       <= and2.3.out

net hlfb_y        => and2.4.in0
net enable-faults => and2.4.in1
net y-fault       <= and2.4.out

net hlfb_y2       => and2.5.in0
net enable-faults => and2.5.in1
net y2-fault      <= and2.5.out

net hlfb_z        => and2.6.in0
net enable-faults => and2.6.in1
net z-fault       <= and2.6.out

net hlfb_a        => and2.7.in0
net enable-faults => and2.7.in1
net a-fault       <= and2.7.out
 

I have had loong time before network tunning done this ... it is basic stuff for latency reduction at any hardware

I will do the kill of EEE and I will share the resaults in comming weeks .. thanks for hint !

regards 

I did not get a working stepper configuration out of MesaCT with a 7i76eu. I have posted the output and my working config here forum.linuxcnc.org/configuration-tools/5...erated-configuration

The output was supposed to be on the 02 stepper but it was connected to the 00 stepper. The feedback loop was not closed and it was not set to be in velocity mode. Look at the two configurations.

You might post a link to this thread on the MesaCT topic

Here is a generated HAL file X axis configuration.

This is what I had to change it to in order to make it work properly.

7i76eud.bin firmware did the trick. Interesting this firmware does not show up in the MesaCT list when using the Configuration Tool. It was in the /lib/firmware/hm2/ folder but it was not showing up in the drop down list.

It could be that I am an imbecile. However when I used MesaCT as installed per the instructions here using apt  gnipsel.com/linuxcnc/mesact/install.html#install-with-apt . I did not get an anywhere near working configuration out of the tool. The stepper configurations were very incomplete. The feedback loop was not closed in fact the PID output was not even sent to the mesa stepper driver. 

I will post up my configuration files from the output shortly. 

If you don't have an added parallel daughtercard, you should normally not change the
installed firmware.

The default 7I76EU firmware is 7i76eud.bin, to re-install:

mesaflash --device 7i76eu --addr [card_ip_address] --write 7i76eud.bin --reload

where [card_ip_address]  is either 192.168.1.121 or 10.10.10.10 depending on how you
have the card setup.

 

I have a 7i76eu that I am using on a new lathe conversion. I must have something wrong with firmware or something on the 7i76eu. The configuration is set up with 3 encoders is what it says. I only have one encoder connected to the 7i76 on tb3. It is configured as single ended jumpers w11 w12 and w16 all set to the left position (up in my case). When I look at the inputs in halshow the A signal is showing up as the A signal on encoder 0, the B signal is showing up as the A signal on encoder 1 and the index signal is showing up as the A signal on encoder 2.

What do I have incorrect here. My mesa setup is a 7i76eu with just a 7i73 pendant smart serial card. I have one spindle drive, one encoder that I am using on the 7i76 two steppers and several io.

I downloaded the firmware pack from Mesa. I installed one that just had the 7i76in the name but no other cards. Which firmware should I use in this case? 

Not sure if this is a config or a firmware mismatch issue. Any help would be appreciated.

Working through this,

irqbalance was not installed by default in Debian since Debian 9 Stretch because the kernel now does its own rebalancing. In some case irqbalance has caused  instabilities. Accordingly any advice about irqbalance is obsolete. If you have installed it, you should purge it
sudo apt purge irqbalance

Also cpufrequtils is deprecated in Trixie and has been replaced by the  linux-cpupower package. to set your governor to performance, use ( I think)

Also, I did not see where you are disabling Energy Efficient Ethernet.  It is supposed to be disabled by default but this is not always the case. There are some flags that can be set in GRUB but they are driver specific. eg. igb.EEE=0 

I have not tested this but This is a robust way to ensure EEE is disabled on every boot. Create a new systemd service file:
sudo geany /etc/systemd/system/disable-eee.service

1. Add the following content, replacing enp6s0 with your interface name. This service will run ethtool after the network is up.

1. Save and close the file.

Reload the systemd daemon:
Enable and start the service:

Yes, i read thier manual 1k times.. it is pretty solid extraction of what we all need...

Yes I am recompiling everytime to native NIC driver as common e1000e or rtl8190too ... It works pretty solid for 8khz thread 
8190too are basically free stuff on the market right now it cost few bucks

There are native drivers for beckhoff too but I have never tried them yet ... 

I am not expert in this drivers ..but if it will improve my latency i need them all ...