Advanced Search

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.
 

Hello everyone, I got this machine through an auction, it is in good physical condition, but with a controller that, even though I have the parameters, will not perform referencing, simply the switch that supplies power to the drivers will not stick if I hold the z axis, it goes up to the limit switch, turns off the drivers and an error axis error appears. The motors are dc servos with analog input for the drivers and have 500 pulse encoders. my question is whether the Mesa 7i96s+7i77 can satisfy that the motors remain and that the rack ATC will somehow work later. Thanks in advance for your future support.

Thanks for reply. I was testing with a value of 200 instead 400 default.  Then i recognized the mdi commands are qeued, so there is no escape from executing every button press. Now i try something with a normal pushbutton and use the pythonmodul. creating a timestamp on each button press and get the difference, only execute the command if result is >=7. I am still testing

Thanks @Aciera
Finally got it working. Added Home Offset and Home Values to Joint_1 since it was not aligned as in documents and I cant give my arm that postion due to its hardware limits. So Accordingly defined Home and HomeOffset. and Small offset to J2 so that I remain horizontal. And minor offsets to J4. and Assiged Home location of J4 so that it remains vertical.
Thanks a lot.
Yes as @Aciera mentioned DH parameters are good.

125000 bits/sec. All LDCN network comms must start at 19200, then get upgraded.

One sets a servo update rate multiplier (e.g. 20x) so the 51.2 µs becomes only the control loop update time, but the commanded position is updated every 1.024 ms. Yes, correct - at 51 µs, the bandwidth would be insufficient.

If interested, I developed HAL components to initialize the LDCN, enumerate the devices, and expose pins to LinuxCNC. Like any software project, it needs experienced eyes to pick apart the architecture.

github.com/ndemarco/linuxcnc-logosol