Advanced Search

I will try this, but again this will introduce a delay. Currently when the motor disables the brake enables but there is a delay so z axis drops a couple centimeters.

The z axis motor does have a brake but there is s delay between the motor going dead and brake engaging. In that delay time the z axis drops a couple centimeters.

There is a failed power supply somewhere, for sure, so start by checking voltages, usually they are marked on the boards.
And please, please do not do that "on-off-on-off" thing quickly, that is how machines are broken, give it 5 to 10 seconds between tests.
Edit,
upload schematic here so we can have a look.

What PC do you have, and what is the result of:

sudo chart 99 ping -i .001 -q -c 60000 [card_ip_address]

Where [card_ip_address] is the IP address of the 7I96S (Either 192.168.1.121 or 10.10.10.10)

there is a schematic but very weak, I can find out which cables are for encoders and analog inputs for drivers, which is enough to maybe tune the motors, but there are a lot of inputs and outputs of some inductive sensors and the like, so the schematic is a bit useless, I would have to see what activates what. I'm worried because maybe the switch for the drivers is faulty, (see the attached video) plus x, y don't move and I had to remove the driver for z because when I turn on the drivers and hold the z axis it goes up or down quickly.


youtube.com/shorts/p0F6iMwsQ_s?si=DSToSnipQkql-Ad2

I would try for sure to keep the motors and drives.
Does it have schematics?

I am hoping that the increasing interest in Linux (thanks to Windows stupidity) doesn't completely bloat Linux into
a slow pig of a system just to satisfy the new masses that don't want to learn anything more then how to turn the
computer on and watch streaming videos.  

Yes I am somewhat guilty of that myself.

I just updated the code so if a MDI command is running the MDI button will not execute again.

JT

A line was broken in the hal file maybe it is already fixed. Should give an error in the linuxcnc startup windowWhen it goes to safeop it usually tells why in the syslog.
Show us the last 30 lines or so from the command "sudo dmesg"
 

Aye, that it is.

i already follow minimal configuration adjust with my servo drive (SV630N), but still the servo doesn't move following linuxcnc sim, and status on my ethercat slave still SAFEOP for my servo drive. here is my hal and xml conf.

Hola, tengo un plasma CNC con la tarjeta mesa7i96s Estuvo cortando bien hasta ahora y de repente se desconecta pone que ha perdido la señal con la tarjetahm2/hm2-7196s.0: error finishing read! iter=309265 me pone esto 

I assume it is a cia402 drive.
Then the first thing is to try this minimal configuration.
github.com/dbraun1981/hal-cia402/tree/main/example
 

rigth now, the error in my configuration has been resolved, and I can run the LinuxCNC sim using my edited hal/xml. However, my servo drive doesn’t seem to enter OP mode and can’t move the servo motor. I’m confused because there are no errors shown in the terminal, and I’m not sure where to start troubleshooting.

Bring it on, config errors are usually easy to fix.
Error messages, hal file and ethercat-conf.xml are needed.
In general, the ethercat drive pins are created with names from ethercat-conf.xml
Indices are from the id= entry, or if you have names= it takes that first.