The voice can be helpful with testing HAL stuff. Qtvcp has a test_led component that can speak on hal pin state changes.

Maybe the problem is a race condition that doesn't effect me. I'll get looking.
I wonder if adding a m5 to the abort script would help?

If no one else is having this problem, then it's clearly just me. There's no point in pursuing this further.

That's strange, though, because I downloaded the entire program from Git, compiled it, and the same problem persists. Older master builds don't have this problem.
With a freshly compiled program, I open one of the default qtdragon configurations, open some gcode, run it, press stop, and the program stops, but the spindle doesn't turn off. I have to press stop again to turn the spindle off.

After running a few tests, it appears that, in my case, the problem was caused by a missing software package. Installing gir1.2-rsvg-2.0 fixed the issue for me.

It is also worth mentioning that I installed Glade and configured it to use GTK 3.16 and WebKit2GTK 2.28.

For reference, I am running LinuxCNC 2.9.8 RMD on a Raspberry Pi 5.

Hopefully, this helps anyone experiencing a similar issue.

If you use 7i97t_7i74d.bin firmware,  sserial channel 0 is on the 7I97T and
sserial channels 1..7 are on the 7I74.  (Physical channel 0 is skipped on the 7I74)

email me: sscnet at yurtaev dot com
which drives have you got?

There is a bug in the MPG encoder mode parameters (marked read only) ,
so we will have a firmware update coming.

It seems all there from my quick review.
Voltage output is raw 1:1 (probably reduced to non lethal amperage)
Includes torch on  and arc OK.

Usually, the arcOK is a dry contact relay. Miimium current is usually 100 mA.You need to respect this otherwise oxidisation can result in intermittent operation. There are a couple of ways to do this discussed in the qtplasmac docs.

So tried lcec.activate, but that results in an error that activate isn't a valid command.

I have however juggled things to match the first lines in scottlaird's example HAL files in the linuxcnc-ethercat github ( linuxcnc-ethercat/tests/scottlaird-lcectest1/cia402-all.hal at 31e3f343ccc2438d7ae0f843b1819f3926b44bc3 · linuxcnc-ethercat/linuxcnc-ethercat · GitHub ), and LinuxCNC now starts, but I can't seem to get any response from the drives. They do go online, as I can see on them that they've been allocated slave numbers, although strangely they're in the reverse order (first in the chin is 03, with the last being 01).

I've attached my files to see if anybody can spot anything obvious.

Thanks, i use new relays to keep that separation and use the old ones to the tool changer (not automatic, but to grip the tool holder i dont know how its his name in english) and another auxiliary, but i want to keep the 7i74 and 7i73 to the future in the end, I will use the 7i84u connected by the port in 7i97t.
Looking at the pins in it using the standar bin it will recognize the 7i84, now i have the bin of the 7i97t & 7i74 i will be a problem or its better to upload the standar?
And the configuration to connect the board its ussing this no?
 
Again, thanks for all the help.

 I'm integrating a HITBOX HBC65 plasma cutter with LinuxCNC/QtPlasmaC via its CNC interface (AEC ready signal). Looking for documentation or first-hand experience on:

• Pinout of the CNC interface connectors
• Signal type/level of the AEC-ready (Arc-OK) output — is it a dry relay contact, open-collector, or a voltage-level signal? What voltage/current rating?
• Whether the arc-voltage-divider output is already isolated/scaled, and what the scale factor is (V per V, e.g. 1:50)
• Torch-start/pilot-arc control input requirements (voltage, active-high/low)

Manufacturer documentation seems sparse — has anyone reverse-engineered or received datasheets for this specific interface? Happy to share results back once I get it running.

hi, I'm very interisting at the sscnet control board,i want to try your product,how can I get it?

looking good. In the commercial software I used, they defined a list of upper and lower tools and material.
So then when you defined a job, you included tools and material so you could save for later. Over time I tweaked my regular jobs so they were perfect. Mainly tweaking that back gauge position.

Some screenshots of my first shot at this. In the bend editor, clicking the bend angle setting will open a whole new page with dies and steel selection. Which will auto-fill most of the remaining values below it.

Now I think I should indicate on the main screen what dies and plates are selected.