Advanced Search

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

Try also
www.mesaus.com
Replacements:
7i76E
7i95T
7i92TM + 7i76
7i92TM + 7i85S

I was able to cause it to crash out without going into Linux CNC if i load it up too much with commands like
sudo chrt 99 ping -i .001

It handled running realtime at 1ms delay with averages of .101ms  for 10000, 20000 and 30000 pings, but when I jumped to 50000 pings it crashed out at about 40k pings..

So there is something that someone in the "chain" doesn't like under high network traffic..

and again, unplugging and plugging back in (just the network) fixes it... which is... wierd... (to me)..

Here is my Servo Period:
SERVO_PERIOD = 1000000

and here is my Servo Timeout
setp hm2_7i76e.0.watchdog.timeout_ns 5000000

the whole config can be found here (its where I wrote it a while ago, but my old pc died so working on getting it up and running on this pi)

github.com/Skyfire-community/SVM2-LinuxCNC

jhandel wrote:

Got a strange one with a Pi5...   Network seems fine when I am just pinging my Mesa card (a 7i76e) but when I run Linux CNC, things kick on but then the network crashes and I get a bazillion (technical term) hm2/hm2_7i76e.0: error queuing read iter=xxxx) and everything turns back off.. 

Once it dies I can't even ping the Mesa card (10.10.10.10) until I unplug and plug back in the ethernet cord... Then its happy as a clam pinging.. but once I start up Linux CNC again same crash right as the UI inits. 

(Linux CNC 2.9.3, PI5 8Gb, NVMe Boot)
 

You may want to start reading from here:
forum.linuxcnc.org/27-driver-boards/4223...read?start=20#207308

Unfortunately I don't have any ethernet hardware to test with (only SPI), I have a 7i92 but that's in the mill enclosure and is a PITA to access. From reports the 6.12 kernel on the most recent RPi images have better latency, but I can't say whether that would solve your issue.

Got a strange one with a Pi5...   Network seems fine when I am just pinging my Mesa card (a 7i76e) but when I run Linux CNC, things kick on but then the network crashes and I get a bazillion (technical term) hm2/hm2_7i76e.0: error queuing read iter=xxxx) and everything turns back off.. 

Once it dies I can't even ping the Mesa card (10.10.10.10) until I unplug and plug back in the ethernet cord... Then its happy as a clam pinging.. but once I start up Linux CNC again same crash right as the UI inits. 

(Linux CNC 2.9.3, PI5 8Gb, NVMe Boot)

I've recently updated from 2.8 to 2.9.2  and I'm having issues with the homing of my dual y axis that uses a single limit switch (i'll be adding a second one for auto squaring in the future). Since migrating the Y axis will go to home and them give a switch triggered while in home state 10 error. I've tried adjusting a number of the homing options but none of them resolve the issue. So I'm wondering if there been any changes since 2.8 that would require this setup to be configured differently.

NOTE: I am using a 7i76E and I've attached my config and hal file for reference.   

That looks correct (and indicates a 7I76+7I78 configuration)

all of my test nets stay low whether or not I apply 5v to the pins. 

That is expected as the input must be >60% of the field voltage to be recognized.

Here is 7i76e firmware for a 7I78 on P1 and 7I85 on P2:

 


 

hi, i am studying Linuxcnc and I need to enable coolant on my lathe with an external switch,

my external switch connected to pin as:

an output coolant pin connected as:

how connect  toogle to run flood?
i find this code but understand how it works in linuxcnc


and I find this lesson but don't understand how edit button code to google switch
all my attempts led to errors,

but this code is work good to spindle


and my copy to coolant show error...



And I have a pneumatic spindle chuck and need connect 3 state toggle to open chuck and close chuck,
to open chuсk I receive input but need run 2 step(enable relay(M64 P0) and disable after 3 second(M65 P0))
to close chuсk I receive input and need run 2 step (enable relay(M64 P1) and disable after 3 second(M65 P1))
Maybe this type of chuck is turned on and off differently?
thank you

Readhmid returns: 


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       QCount           0        Quad-IDX        (In)
TB3-10,11              15   IOPort       QCount           0        Quad-B          (In)
TB3-7,8                16   IOPort       QCount           0        Quad-A          (In)

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

 1                      17   IOPort       StepGen         5        Dir/Table2      (Out)
14                     18   IOPort       StepGen         5        Step/Table1     (Out)
 2                      19   IOPort       StepGen         6        Dir/Table2      (Out)
15                     20   IOPort       StepGen         6        Step/Table1     (Out)
 3                      21   IOPort       StepGen         7        Dir/Table2      (Out)
16                     22   IOPort       StepGen         7        Step/Table1     (Out)
 4                      23   IOPort       StepGen         8        Dir/Table2      (Out)
17                     24   IOPort       StepGen         8        Step/Table1     (Out)
 5                      25   IOPort       PWM              0        PWM             (Out)
 6                      26   IOPort       PWM              0        /Enable         (Out)
 7                      27   IOPort       PWM              0        Dir             (Out)
 8                      28   IOPort       SSerial           0        TXData2         (Out)
 9                      29   IOPort       SSerial           0        TXEn2           (Out)
10                     30   IOPort       SSerial           0        RXData2         (In)
11                     31   IOPort       QCount           1        Quad-IDX        (In)
12                     32   IOPort       QCount           1        Quad-B          (In)
13                     33   IOPort       QCount           1        Quad-A          (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


Then for the pullups I get: 
mesaflash --device ethernet --addr 10.10.10.10  --rpo 0x1005
0001FFFF

mesaflash --device ethernet --addr 10.10.10.10  --rpo 0x1004
0001FFFF