Advanced Search

where can i find it ?

You would load the 7I76eu firmware that includes PKTUart support

7i76eu_7i76x1_pktv3d.bin

This file is in the 7i76eu.zip archive downloaded from Mesa's store (in the specifications tab)

You program it with mesaflash, something like:

mesaflash --device 7i76eu --addr 10.10.10.10 --write 7i76eu_7i76x1_pktv3d.bin --reload

 

Hi andypugh,
i dont know how to flash the pktUART, i dont know how to download it, i want to use it to control mr-je driver from Mitsubishi
 

AdelRTP wrote:

thanks a lot Tommy,
i’m trying to control two servo drives (Modbus RTU) with a Mesa 7i76EU in LinuxCNC, but I can’t use Classic Ladder or PktUART

Have you spotted the new Modbus / PktUART driver? It's more flexible that mesa_modbus. (but only exists in the dev version of LinuxCNC) 

linuxcnc.org/docs/devel/html/man/man1/mesambccc.1.html
linuxcnc.org/docs/devel/html/man/man9/hm2_modbus.9.html
 

Moved to "driver boards" section.

thanks a lot Tommy,
i’m trying to control two servo drives (Modbus RTU) with a Mesa 7i76EU in LinuxCNC, but I can’t use Classic Ladder or PktUART

Use the latest version of mesaflash
github.com/LinuxCNC/mesaflash
Scroll down for info on how to install.

Using  with a Mesa 7i76EU (IP ). Ping works, but:mesaflash --device 7i76eu --addr 192.168.1.121 --readhmid
Unsupported ethernet device 7I76EU at 192.168.1.121
No 7I96S board found
Also tried with IP  after moving jumper W14 up
mesaflash --device 7i76eu --addr 10.10.10.10 --readhmidIs the 7i76EU supported? How to fix "Unsupported device"? 

I finally found the real cause.

Today i got the amplifier fault on another joint (joint 0) and I found that it the problem happened whenever I turned on the spindle.

After several attempts to measure the ground connections the machine stopped in a position where I found the machine frame was not grounded.

The reason: The spindle connector got loose. The machine frame was grounded through the spindle cable, and that cable had become loose.

All I had to do was tighten the screw of the connector. Ground connection works reliably again and the machine runs well. Phew.

So, has there been any progress on getting this sensor to market? 

I'm trying to get a laser machine built, but, this is one of the toughest issues I'm facing.  I have a MESA 7i76EU that I have been trying to interface a BCL-AMP output to.  I have the BCL-AMP connected to a Raytools BT210S002A cutting head sitting on the bench with a chunk of steel in front of it and grounded to the case of the Raytools cutting head.  Between the BCL-AMP and the 7i76EU, I have a TI SN74HCS74DR dual Schmidt Trigger Flip Flop that I'm using to divide the BCL-AMP output frequency by 2 and "clean it up" at the same time.  However, it's just not very stable.  The velocity measured by the 7i76EU jumps around about 600-700 hz.  The velocity range only seems to be around 6500 hz from 0-10mm (3/8") sensing distance, so, my positional sensitivity sucks at around 0.1 inches.  Just for giggles, I ran the signal through 4 Flip Flops to see if the 'jumping around' would decrease.  It didn't.  Which leads me to believe the instability is introduced somewhere in my circuitry or wiring.  I even tried connecting Q and Q not outputs into the MESA card as differential signals and twisted the wires.  No help.

Anyhow, This CV2 height sensing device sounds very promising.  

Based on what im reading, it does seem ill need a larger card to handle all the limit switches and 3 encoders, one for each hand-wheel. I will prob go RJ45 as the parallel ports are less and less these days.

Thinking this guy, not cheap but one stop shop correct?
store.mesanet.com/index.php?route=produc...id=399&search=7I76EU

Hello everyone. 
I know there are plenty of other threads about this topic, and I think I read them all, still I struggle to solve the issues that I am having.

My setup is:

• Dell Wyse 5070 with Celeron J4105 4-core cpu THIN CLIENT
• realtek onboard NIC
• fresh Linuxcnc 2.9.3 install
• brandnew Mesa 7i76eu, flashed with pktUART firmware

I experience issues when I startup Linuxcnc / probebasic.
Most of the time the system errors out right after startup with "error following read...". Sometimes I am "lucky" and it works for maybe 5minutes before it errors out. 

What I did so far (after reading in this forum for 2 nights):

• I ran sudo chrt 99 ping -1.001 -q 10.10.10.10 to get some statistics. Here is the result:
  
  179555 packets transmitted, 179555 received, 0% packet loss, time 180656ms
  rtt min/avg/max/mdev = 0.052/0.065/8.974/0.036
  
• disabled all BIOS options regarding power management, hyperthreading, ... etc
• Installed R8168-dkms driver (sudo apt-get install r8168-dkms)
  While searching in this forum, I found that some people had to install linux headers first. I did not do that. 
  When I run a script to identify the used drivers (JCW posted this somewhere a while ago), i get the followig result:
  ./edriver.txt
  xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
  enp1s0 : r8169
  wlp0s12f0 : iwlwifi
  
  Is this result "expected? Or did the driver installation not work?
  Other people posted that they had to install linux-headers and purge the old driver... 
  
• then I found a script that JCW posted in another thread that pins the IRQ somewhere (I honestly dont really understand whats behind this, but still this is the output):
  cnc@linuxcnc:~/gcodes$ sudo ./pinirq.txt enp1s0
  Cores: 4
  Old CPU Mask: f
  Set device enp1s0 IRQ 122 CPU mask to 8
  
  However, it did not improve my ping / latency at all. Do I need to do anything prior to that? Isolating something?

What I have not done yet:

• editing the kernel parameters in grub customizer (quiet isolcpus= 3 pcie.aspm=0 r8168.eee_enable=0 pcie_aspm=off idle=poll).
  I dont really understand what this does, therefore I hesitated to run it. 
• .... 

Another question... almost all other threads regarding this issue link to a tutorial / troubleshooting file that was hosted by @rodw on google drive, but the link is dead. Could someone provide this file?

regards and thx.
Sebastian
 

So, I've done a lot of progress . After I changed the usb  to RS232 cable( don't buy low quality RS232 to usb cable) I've been able to connect to my driver and configure the external enable and the internal disengage of the motor brake(you need to power the io from external 24v source with Leadshine) . After all this i wired a 24v Finder relay for the motor enable commanded by the mesa,when i launch the program the mesa power  the relay and enable all the drivers. Now  I'm able to move the axis from linuxcnc, but i think I'll change the basic Axis gui with probebasic for more userfriendly interface. For the motor wiring I have to thank the Leadshine tech support, they reply very fast, and for mesa i refered to this guy video  (very helpfull, the 7i76EU version it's same wiring confirmed by Mesa tech support , for shematics and 3d support prototipe refer to this  and official 7i76E pdf ). So now i've to do some tests and project all the electrical supply for all that stuff, and i have to adapt the motors to the mecanical part with new mounting plates(i think i will design them with Fusion 360 and buy them from PCBway machining or other). That's all.

Also are the drives enabled?

Typically servo drives would have an enable input that must be connected to operate
(with default setup parameters)

Note that if LinuxCNC cannot communicate with the 7I76EU, LinuxCNC will not start.

I wired all the the motors, but i can't move with linuxcnc and the mesa board , i've done the basic configuration and followed the this post  because the configurator couldn't find the mesa but after following the instruction the mesa is recognised. My issue now is that i can't command the motors from mesa and motion control of leadshine can't find the driver(i've contacted the even  the techsupport of leadshine , and no solution finded). For the wiring i followed this  and the official pdf. The wiring should be good, i don't think i've done something wrong . A the moment i've some doubts if linuxcnc can communicate with the mesa, but if i unplug the ethernet cable in linuxcnc it's reported an error so i think they are talking. I share the photo's of my wiring. 
Has anyone experienced a similar problem? Is there a way to further test the Mesa board’s output, or any diagnostics I can run in LinuxCNC? Any advice would be greatly appreciated!