Advanced Search

Sorry for the poor English, thanks for your help in the future.

Could you share your QtVismach file?

I would measure the voltage between OUT0+ and OUT- when on to diagnose the issue.

it should  be much less than a volt

If OUT5 is used instead (this is suggested for Plasma systems) the voltage may be higher
but no more than 1 volt or so.

 

I tried this ethtool --set-eee eth0 eee off but it did not help at all. No I have tested two independent setups and inserting ethernet switch between Rpi and ETT60n solved the issue. In rpi5 there is no l --set-eee eth0 eee available but same issue when using without switch.

You can use any unassigned GPIO pin  as an input so limit/home switches are supported

Optocoupled step drive wiring:

Sinking:

DRIVE DIR+ --> +5V
CONTROLLER DIR- --> DRIVE DIR-

Sourcing:

Drive DIR- --> GND
CONTROLLER DIR+ DRIVE DIR +

Most step drives have optocouplers built in

BUT the 7I92T is really not intended for direct connection to field wiring.

It will work but a single mistake with grounding can easily damage the 7I92T.
The 7I92T was really designed as a parallel port equivalent device with added features
and is intended to work with parallel port (or Mesa) breakout boards.
 

I have:

Stepper motor drivers DQ542MA

Mesa 7i92TH board (26 pins)

Nema 23 motors

Inductive limit switch NC NPN. BN 10-30V BU0V

C38S6G5-1024Z-G24N DC5-24V encoder

4-channel PC817 optocoupler isolation module

SINO 0.001 mm linear encoder optical scale

24V 10A power supply

Spindel Servo Motor 1000W

Purpose:

4 axes with optical rulers
One rotary axis with rotary encoder
LinuxCNC control

Hi everyone,I’m finishing up my CNC plasma build using a Mesa 7i96s, Spartus ProCut 45PCF, and a THCAD-5 (not yet connected).My issue:
The torch on output (OUT0) from the Mesa won’t trigger the plasma directly.
If I short pin 3 & 4 on the Spartus CNC port manually, the torch fires instantly.
When I run the signal through a relay, it also works fine.
But when I connect the Spartus directly to OUT0+ and OUT0-, (or OUT5) nothing happens — even though the Mesa output LED lights up and I can measure switching.The Arc OK behaves similarly — it only works through a relay. But when i have torch pulse on it stays active. And when cutting a circle is just flashes real quick and torch dies. 
The output LEDs on the Mesa board are about half as bright as the input LEDs.All 0 V lines in my control cabinet go to a common terminal, which is also tied to PE (earth) and the machine frame.
I have 24 V on IN COMMON, and everything else seems correct.Has anyone successfully triggered a Spartus ProCut 45PCF directly from a Mesa 7i96s output (without a relay)?
If so, could you share how you wired OUT0+ / OUT0- relative to the plasma CNC port pins (3–4)?I’ve looked through other wiring diagrams and posts, but haven’t found a clear answer yet.
Any suggestions or example diagrams would be very much appreciated. I will try and make a diagram of mine so you guys can have a look )Thanks!

Does this firmware version also contain pins for ‘End Stop’ for 4 axes?

Does this mean that I have to use optocouplers?
What does ‘a sinking configuration’ mean?

Please tell me, can I use encoders from the Mitutoyo AT111-100F або AT111-200S series?

What version of linuxcnc are you using?

If you really want to upgrade, first thing I would do is boot the latest Linuxcnc image, run latency-histogram --nobase if you get under 100ns latency, rather than upgrade your PC get a mesa 7i92, it will plug into your existing breakout board and start making chips.

The E8400 is a 64 bit CPU.

en.wikipedia.org/wiki/Intel_Core_2

Hello,

I measure every tool after changing, this happens automatically. In principle, only an offset to the previous value is determined; I don't write anything into the tool table. That doesn't make sense to me either since I don't have an automatic tool changer.
Here's another link:
www.patreon.com/posts/29-linuxcnc-der-27282521?l=de
forum.linuxcnc.org/qtvcp/39423-qtdragon-...tool-change?start=30

Many greetings, Frank.

 

Do you want A to rotate around X?
if you load a tool and jog A is this what you see?
Can you test the simulated config?

It appears the core problem is that 2.9 requires a 64 bit processor and my antique is a 686. I guess I will be staying in the past untilll I buy a new desktop.

So, is RTAI over?

I'm already feeling nostalgic.

How difficult will it be to use RTAI from now on (from LinuxCNC 2.9.5 onward)?

The most recent setup I’ve been able to get working is kernel 5.4.258 + LinuxCNC 2.9.4, using the following .deb packages (with isolcpus=3):

linuxcnc.org/dists/bookworm/base/binary-amd64/
linux-image-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
linux-headers-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
rtai-modules-5.4.258_5.3.3-linuxcnc-delta_amd64.deb

linuxcnc.org/dists/bookworm/2.9-rt/binary-amd64/
linuxcnc_2.9.4_amd64.deb

I was not able to get 5.4.290 + 2.9.4 working, nor 5.4.279 + 2.9.2. (I will post the error messages later.)

The 2.9.7 release notes state: "RTAI is still supported, but in the short term, building from source is likely to be the most expedient way to get 2.9.7 on that platform."

I’m wondering whether this is a reasonably straightforward process, or if it requires deeper OS-level debugging knowledge.