Advanced Search

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
 

The 7I76EU is compatible with 7I76E hal/ini files, so you can
just select "7I76E" in pncconf.

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.

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)

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 parameterin 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!

djdock99 wrote:

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

Never smart to do that to machines.

djdock99 wrote:

.... 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 ?

djdock99 wrote:

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

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.

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......


 

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)

You have setup 2 networks on the same 1'st physical network card, the 2'nd network card has nothing set.
WHY????
That will not work, so start new and use this:
forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards

If mesaflash reported that error, update mesaflash
(instructions on the git site or above in this thread)

github.com/LinuxCNC/mesaflash

If LinuxCNC reported the issue, you need t o update LinuxCNC.

(You don't actually have to update LinuxCNC as it will work fine but will complain about the card every time you start LinuxCNC)
 

I'm having the exact same problem, has anyone figured out what's going on?

Tks

Estley wrote:

I swapped computers for a i5 and now it all works fine, thanks!!

Perfect!

I swapped computers for a i5 and now it all works fine, thanks!!

It's not a laptop, it's an i3 mini PC, I'll swap it for a i5 I have laying around and see what happens.

I'm a huge fan of your videos, I was actually watching one of them when you replied!!