Advanced Search

Yes, 7I76E hal and ini files will work with a 7I76EU.

The added 7I76EU features (output modes and spindle mode)
would not be supported, but these are just controlled by parameters
that  can be setp'ed in the hal file.

The firmware files are however different

Appreciate the prompt action, I also got a reply from the Mesa folks that you can select and build configs with 7i76E as well.

-Aren

Thanks for that.
I believe that what Rodw wrote is the reason why i could not anymore open the shared folder, but its funny that in short time this stopped working, as well as the internet browser and also OneDrive setup on wheezy.

The solution is to edit the SMB policy on your windows box and it works perfectly.

I am not expecting that you write me a tutrorial how to get it work, but if you have a simple tutorial, please send me a link. If the new radeon vga will not solve the latency problem, but i will know that i can setup samba on wheezy, then i will do it. If not, i buy the mesa 7i92TF or 7i76e.

7i76EU has been added to Mesa CT just now. I've not tested the configuration yet.

JT

Is there any readme on how to add .bin files for a new board to this? I have the Mesa 7i76eu, successor to the 7i76e, and have downloaded the firmware files from the mesa site but am unsure of how to add them to the configuration tool.

Any help is appreciated,
-Aren

I think its unlikely that you would need so much DPLL pre-trigger so I don't think
increasinh this timr to 250 usec is going to help

I would check hm2_7i76e.0.packet-error-total to see if you have dropped any packets

You might try plotting the following error and perhaps tuning by adding a little
FF2 (say .0003 to start) to the PID loop (using the calibrate menu so you can do this live)

Hello again!
Today, I tried my machine out with a new .ngc file for a part to mill, and while testing in the air, although with reduced G0 to 5500mm/min, I got the "motor-0-position error" again.
So, I changed the setp hm2_7i76e.0.dpll.01.timer-us -200 to 250. The next run comes without the error. But i am sceptical - how far can I go with this or should I change othere settings too?
WHat about the min Ferror - i had 0,01mm is this too much, should i go to 0,1?

Thanks for any answer!
Kind regards,
Hanno

Thanks for your reply Tommylight.
On tomorrow or in 2 days i will tell you the exact version, but i remember it was Kernel 6.3. rt something..
Hypethreading option is not available in Bios. 
This PC was working perfectly fine with Wheezy and Linuxcnc 2.8.x . I also remember that i reinstalled wheezy and tested the machine after first latency problems on Debian12 and there were not problems. So, problems started 100% since Debian12.

I can not justify breaking a perfectly working machine for OneDrive even with a gun pressed to my head

100% right, but i was forced to do so, because my SSD card broke. I remember that Linux didnt started anymore, from one day to another. 

Short history:
At the beginning of my cnc experience i used a USB stick to tranfer files, but someday i got the ethernet working (it was maybe 2018 or so). Since then i used Email or if i had a lot of files then i used USB stick because i remember that the Browser was very slow, which was very annoying for multiple files.
I did it that way for couple of years (its a hobby machine, not using it every day)until i thought that it would be a lot more comfortable and quicker to have them on a server or share the files on the windows pc. I dont know if i used Samba to setup file sharing, but i believe so. This has worked mabye for 1-2 month. Suddenly it did not work anymore and i could not fix it. Then i thought about OneDrive, because i have used it already for other things. I managed to get it working and i had a OneDrive folder on the Desktop, so i somehow installed it on Linux. This worked super well, but also just for couple of month. From one day to another it stopped working. Browser did also not anymore work. It was not supported anymore or so. Of course i have tried to fix it by installing a different browser, but nothing worked and shortly after my SSD broke. No joke.
So, i think you can imagine how pissed off i was. The amount of time i have already spent with fixing linux problems is unimagineable , so i am already a bit allergic to it. 
It is like this:
1. You try installing a different browser for Linux, so you google it with the correct Linux version/kernel version.
3. You find a tutorial and first step says: Open Terminal and copy past this "xadsasddadqd" command.   
4. FAIL, because xxxx1 is missing.
4. You look for a tutorial to install xxxx1
5. For this you unfortunately need also "xxxx2"
6. .... and so on
This is how it was with the wheezy version. Problems after problems and i just wanted to use Linuxcnc, have one app like mousepad and ethernet browser or some kind of file sharing setup. But just for those things i had to make a lot of fixing work. 
I believe with Debian12 there are not this kind of problems anymore, but now my LATENCY is fuxxed up.. 
The funny thing is, i always loved to do some computer fixing stuff, solving problems, tweaking etc. but Linux managed to make me hate such things. 

***FOR ALL BEGINNERS WHO ARE READING THIS:  Its not about LinuxCNC! LinuxCNC is working perfectly and always was working perfectly, also i have LinuxCNC on my Lathe with Mesa 7i76e and its working perfectly!   If i would start my Linuxcnc experience from Debian 12, i would now only need to get the Latency fixed, nothing else. The previous versions i had (wheezy) were for sure versions specific for Linuxcnc, with only those things installed that are needed to start LinuxCNC, thats why i had so many problems and bad experience.

Okay, enough for today. I wait for the Radeon VGA and try then if it works. If not, i think i just buy the Mesa card, because going back to wheezy is, i believe, no option for me. Maybe its possible to get file sharing to work on wheezy, but i dont want to even anymore tried it, because if i do, i will again sit 12 hours in the workshop trying to install Samba, and the 127 other things that are needed  while my hands are freezing. (someone i always have Linux problems in wintertime)

(Debian 12,   2 Parallel port cards / 2 BOBs,   isolcpus=5,     bios settings are correct - as they worked perfectly on wheezy)
Hello,
i have already wrote a thread a couple of month ago about my problems since debian 12.

I upgraded from 2.8 (wheezy) to 2.9x on Debian 12, just because i could not anymore connect to OneDrive, not even through website and upgrading browser did not help. (i am using 2 BOBs and 2 LPT cards for this CNC XYYZ Router machine)
Current Base thread: cant get it below 28.000 intervall and jitter is below 8000

I thought that i managed to get it to work properly, but with slower Axis speeds due to higher latency. A couple days ago i had to cut suspension mounting plates for my car project and found out that the Y-axis (2 motors on Y) is loosing steps. Yesterday i have tried hundreds of different BIOS settings for about 7h (mainly cpu/ram settings), but i always loaded the same G code, not trying other codes (so maybe the code is making problems?), but after stopping the code midway or when the program ends, i see that the Y Axis has lost steps when going to Y0, X0.

Now i am looking for a solution that does not require a lot of time, because to be honest, i have enough of fixing linux problems.
1 Solution (best for me): Fix the Latency problems and continue to use the same pc.
- my last hope might be the IRQ Script, but i remember i have tryed to make it work but couldnt and also i am not sure if that script is only for people who use e.g. a Mesa Ethernet card.

2. Buying a different PC: one that works with good latency on Debian 12 without latency problems
- if you have Debian 12 or any other newer Debian (where OneDrive works) with good latency then PLEASE let me know your exact Hardware!!!

3. Buying a Mesa 7i76e:  will that solve the latency problems on Debian 12?
- i am ready to go that route if that will solve the problems, but i dont see the sense of doing it if people have also problems with Mesa cards on Debian 12.

4. Going back to Wheezy: 
100% solves the latency problems, but this means i need to use again a USB stick for gcode files, because OneDrive does not work on wheezy. (not through browser and not through installed/setup OneDrive because its not supported anymore)

In about 1-2 hours i go to my workshop and the first thing i try is to start a different G-Code and then check if the Y-Axis looses steps. If it does, then the next thing i will try is the IRQ Script, but as i wrote earlier, i am not sure if thats just for people with Mesa cards.
If the script will be "active" but not fix the problem, then i will shut down the pc, do other things and hope that someone here has a solution. 

If i would knew that a Mesa 7i76e would fix the problems, then i believe i would have already ordered it on yesterday, but i dont see the sense of doing so if i still need to fix some IRQ problems, especially when it costs almost 300 €.

Thanks in advance for your help.

This can be done with custom firmware
and some kind of daughter card on one of
the 7I76Es parallel expansion connectors

If the signals are 5V a daughter card may
not be needed but some protection from voltage
spikes like  220 ohm series resistors on the inputs
is advisable.

Another possibility is for me to add a software index pin for the stepgen/encoder
in LinuxCNC's driver so you could connect say a 7I76E field I/O pin to the software
index pin in hal.

This function could be built from hal components but it's a bit complex.

 

Hallo,
I have a linuxcnc 2.9 installation with Mesa 7i76e controlling 
​​​​4 leadshine el7 rs servos via step dir. The encoder input of the 7i76e is used for the spindle.
Homing without index is working perfect.
Is it possible with current hardware to home with index.
I can read the short index signal with Hal Scope. For a & b i have no inputs left.
I tried with software encoder in hal but homing ignores the index and axis moves on.
Do i need a firmware update for the 7i76e like a read a lot with stepgen and index homing?
Thank you

 

Hello,
I am a fairly new LinuxCNC User. I am using a Mesa 7i76e with the probe basic UI.

So far everything works fine but I am having one "issue" or inconvenience.
Whenever I load a gcode, I get the following message: (Header) 3d plot (message) Error in ...ngc line -1 Cannot Probe with zero feedrate.

It still works, I can start the gcode and it runs without any issues but I would like to know why this message comes up.

I will attach my config files and a pic of the error as well as the gcode that was loaded when I took that picture.

If someone knows where this is coming from, please share your wisdom!

Thanks in advance!

I have received the additional Mesa boards and am putting some thought into the system and wiring.

I was thinking that I would use the encoder signals to generate commutation signals to output to the Ultra3000 drives. The drives have inputs for Commutation Channel S1, Commutation Channel S2, Commutation Channel S3. 

The question I have is: do I need to worry about torque ripple if I am providing the drives with only commutation pulses in this manner? If so, should I be outputting something else from LinuxCNC to the drives such as quadrature encoder pulses generated from the encoder signals? 

Trying to avoid getting this all wired up and then having to change it. 

As you can guess from my earlier reply, honestly I do not know.

It switches off all moves. And it makes the E-stop button on Axis GUI (General User interface?) greyed out.
On my mill this is the E-stop! I wired the E-stop-mushroom switch in series with the E-stop input to the VFD, so this tells the drive to stop. That is as safe as it gets for this machine, for me. Spindle stops via hard wire (with soft input to the VFD) and the motion control is aborted from Linux.
To switch on again, I need to pull out the mushroom button and power on the machine again via mouse cklick.

That is a small benchtop mill. I think I can take the risk for this size and speed of machine. On a real heavy industrial machine I would probably do more homework and invest in some more professional hardware.
e.g. on the manual Lathe a bigish contactor is installed by the manufacturer. If someone is barely touching the foot brake, it trips and cuts power to the motor. (all three phases) Before it turns on again, it must be switched off first and then on.

Here I found some other discussion with some aspects.

forum.linuxcnc.org/38-general-linuxcnc-q...-card-7i76e?start=50

Hello everyone,

I am currently setting up my plasma cutter and encountering some initial issues that need resolution. One of these issues is the intermittent loss of my THC encoder signal, which occurs briefly at irregular intervals. Aside from this, the signal quality appears to be satisfactory in terms of noise. When the signal is lost for a few milliseconds, the torch attempts to compensate by raising itself before leveling again. I have attached a photograph (apologies for the quality) that illustrates the signal drop, followed by a voltage increase caused by the raised torch before it levels again.

I am utilizing a Beckhoff EL5101 incremental encoder interface in conjunction with a Mesa THCAD2. I have also tested with a THCAD300 I had available, and the issue persists. Additionally, I am employing hypersensing with a second THCAD2 and another Beckhoff EL5101, exhibiting the same behavior. Given that I previously used the THCAD300 with a 7i76e without issues, I suspect that the Beckhoff modules might be the cause.

Attached are three screenshots: one showing arc voltage at 0V, another displaying encoder frequency initially at 0V and then at 12V for testing purposes, and finally, the problematic screenshot showing encoder frequency during cutting. What options do I have to filter these signal drops effectively?

Thank you in advance for any advice or recommendations.