Advanced Search

A common error is to not have the right vid and pid in the ethercat-conf.xml file.
Double-check that the vendor id and product code from the output ofmatches the vid and pid fields in ethercat-conf.xml.
Check that for all slaves (0,1,2,etc)
If that didn't help please attach the ethercat-conf.xml file, the hal file and the output of "ethercat slaves -v"

The hal and ini files are empty.
Is it the VEICHI SD700 drive www.veichi.com/product/sd700-high-performance-servo-system.html?
 

Hello everyone, I ask for help, I encountered a problem connecting the driver via etcherkat, everything is displayed via the terminal and the driver is visible, but when I launch Linux, the driver does not move. In my case, the driver is connected directly to the PC, and does not go into OP mode. I tried to connect to the delta drivers and everything worked. Unfortunately, there are no instructions for my driver. My assembly (hal, ini and xml files):

I have same issue,
QT5 designer doesnt load custom linuxcnc widgets,

what should I do?

Really situation is these: S1-M20 is a coupler based on Hishler chips as multiprotocol demux. You can set from ethercat modbus and other .... there are not a real connection from DI, DO module. Hishler chips drive the right master in module with correct register used from various protocol type. So if bus is not inizialize on Hishler, no comunication with DI DO, no pdos no sdo .... only comunication established. Need to know right inizialization sdo i think, and producer not know that because not usual with IGH. Really not sure Hishler is supported from IGH. SO for sure need to load original xml file on tiwincat, after check if usable xml is produced .... but probabily need to write a new component based on file that producer share with me. For sure that "driver" as it is write is not possible to build inside ethercat component forlder ... wrong library used and wrong structures. If someone have some suggest on these (whitout writing new component ... that become a sort of copy of one used for EL1xxx or EL2xxx) is welcome.

Real thanks for attention on these.

What does one do if the machine cannot be physically moved to its Home position ?
For example, a large job mounted prior to machine start-up, or a vice.

It is possible to set up 'Immediate Homing' in the INI file:
www.linuxcnc.org/docs/html/config/ini-ho...ml#_immediate_homing

You could then use a probe to jog the machine to the origin of your work piece and issue MDI:

or. if you already know the offset between the machine position on startup and the work piece origin (example x:1 y:2 z:3):
Note though that without properly homing the machine (ie in reference to the physical limits of travel) you will also need to adjust the joint/axes limits.

Good Day,

What is the correct way to update ProbeBasic from a very old version?
sudo apt-get update/sudo apt-get upgrade does nothing.

Best Regards,
Ben

I don't know if it's a Leadshine knockoff, I got it a long time ago.
I knew Leadshine as a cheap but pretty good mfg- I never heard of any "knockoffs" of the Leadshine name.

It was a long time ago, but IIRC I ordered it straight from the mfg or at least a legit distributor.

The only thing that could matter would be if they actually wired the Z channel to DB 8/9. I did look up the manual again, Z is 6/7 and I can't imagine them just skipping it over and using 8/9, but, ok, I'll put that on the list of things to try. since it's easy- move the servo to pin 6/7 and see if it moves independently of Z.

The DB25 is IDCs stamped on a ribbon cable. The 0.1" end plugs into P2 of the 7i92, the first DB25 goes to the 3 axis MX3660 and the cable goes on a few more inches to a DB25 that has a breakout board on it and pins 8/9 are STEP-/DIR- for a servo for the A-axis. The servo has an onboard driver. +5V is STEP+/DIR+ sourced from an RPi power pin.

Well I'm quite sure it has 2 limits on the gantry. I will check tomorrow and I will check if they work tomorrow. sorry for the confusion here I Rod just said read through the configuration manual.

Rod, why?
He did not confirm that the machine has switches on both sides yet, so why send him that way, he will end up with a mangled machine.
Then again, i wonder why is it not possible to answer such a simple question...
Again, do not set -1 to anything if you are not sure the machine has switches on both sides of the gantry and that those switches are properly wired, configured, and working.
EDIT:
You posted while i was answering, there are no home stuff set in that ini file.

I did do what RodW said to do and from that I figured to add "HOME_SEQUENCE = -1" to the two Y motors. would there be anything else I need to add in the INI files?
Also I don't know if you want to take a look but if you do here it is

# Generated by stepconf 1.1 at Fri Apr 25 14:44:59 2025
# If you make changes to this file, they will be
# overwritten when you run stepconf again

[EMC]
MACHINE = 22222222222222
DEBUG = 0
VERSION = 1.1

[DISPLAY]
DISPLAY = gmoccapy
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 0.10
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 1.00
CYCLE_TIME = 0.100
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/probotix/linuxcnc/nc_files
INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in

[KINS]
JOINTS = 4
KINEMATICS = trivkins coordinates=XYYZ kinstype=BOTH

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
PROGRAM_EXTENSION = .nc,.tap G-Code File
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
BASE_PERIOD = 100000
SERVO_PERIOD = 1000000

[HAL]
HALFILE = 22222222222222.hal
HALFILE = custom.hal
POSTGUI_HALFILE = postgui_call_list.hal

[TRAJ]
COORDINATES = X Y Y Z
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 0.10
MAX_LINEAR_VELOCITY = 1.00

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

#*** AXIS_X *******************************
[AXIS_X]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0

[JOINT_0]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
STEPGEN_MAXACCEL = 37.5
SCALE = 8000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0
#******************************************

#*** AXIS_Y *******************************
[AXIS_Y]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0

[JOINT_1]
HOME_SEQUENCE = -1
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
STEPGEN_MAXACCEL = 12.5
SCALE = 4000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0

[JOINT_2]
HOME_SEQUENCE = -1
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.01
MAX_LIMIT = 8.0
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 10.0
STEPGEN_MAXACCEL = 12.5
SCALE = 4000.0
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = 0.0
#******************************************

#*** AXIS_Z *******************************
[AXIS_Z]
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
MIN_LIMIT = -4.0
MAX_LIMIT = 0.01

[JOINT_3]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -4.0
MAX_LIMIT = 0.01
MAX_VELOCITY = 1.0
MAX_ACCELERATION = 30.0
STEPGEN_MAXACCEL = 37.5
SCALE = 8000.0
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.0
#******************************************

Ok so what im getting is that if two joints have a HOME_SEQUENCE = -1 then that tells the two motors to run together right?

No, not yet.
Now is that point where you upload your configuration files here so we can have a look, joint errors are usually miss configuration on stepper systems.
What board are you using?

Please check your ethercat.xml file to see if it contains this pin. Similar to...... <pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>