i have found the problem , the problem was the sentence in the RS274NGC part :
[RS274NGC]
RS274NGC_STARTUP_CODE = G17 G21 G40 G43H0 G54 G64P0.005 G80 G90 G94 G97 M5 M9
# required NativeCAM item : PARAMETER_FILE = linuxcnc.var   <=HERE WAS THE FAULT I HAD WRITTEN THIS BUT THERE SHULD BE THE PLACE WHERE THE DATA SHULD BE => /Usr/linuxcnc/MY_CONFIG/........
SUBROUTINE_PATH = ncam/my-stuff:ncam/lib/mill:ncam/lib/utilities

Ten years ago I mounted a 5i20 on a friend's lathe. I remember we used all four ports because he wanted to use the original switches for feedrate and other things. Now he'd like a spare board in case of failure. What can I use with four ports?

I flashed back the original firmware to my dongle for testing. When commenting out the assert and adding a debug print there instead if r != 0, I get the following output during jogging in auto: I tried more than 10 times in a row, and every time the pendant successfully reconnected. In other words, I cannot reproduce your issue. And unfortunately that also means I cannot be of much help to you.

It is a bit surprising that you get the same issue on two different machines, and I don't. Or are the two machines you tested on fairly similar? Could still be e.g. kernel version difference, I suppose. In case they have fixed some usb bugs related to this. It's a bit of a long shot, but I don't have anything better at the moment.

i have opened the file as an . ngc file but the same error accurs with seeking o word in line 92 what i am making wrong? please help  is there something i could try to find out what the problem is ?
 

Okay, so probably not hardware related then, after all. I'll try to adjust my test setup a little bit and see if I can reproduce the issue.

Hi PCW,

I have wired this up like you said. When I set the P value to 1000 we have continuous motion that doesnt stop and when I set it to 0 it moves a short while and then stops.

Thanks,

jblanscett

the image file that I could not get in the previous message

• Ok, setup the HOME_OFFSET to -0.118 [equivalent inch to the 0.3mm) no luck.
• Tried inverting /- latch and others.Axis has errors so attaching the image
• When attempting MACHINE / HOMING / "any single axis" I get an error message
• Home setup / limits of one [x] axis as exampleExample - output of ini for X-axis[JOINT_0]TYPE = LINEARHOME = 0.0FERROR = 10.0MIN_FERROR = 0.05MAX_VELOCITY = 3.0MAX_ACCELERATION = 2.0

current x-axis example fro ini:


[JOINT_0]
TYPE = LINEAR
HOME = 0.0
FERROR = 10.0
MIN_FERROR = 0.05
MAX_VELOCITY = 3.0
MAX_ACCELERATION = 2.0
# works - can use after home limits estop fixed - MAX_VELOCITY = 5.0
# works - can use after home limits estop fixed - MAX_ACCELERATION = 7.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 6.25
STEPGEN_MAXACCEL = 8.75
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP   = 10000
DIRHOLD    = 10000
STEPLEN    = 5000
STEPSPACE  = 5000
STEP_SCALE = -1016.0030642800001
MIN_LIMIT = 0.0
MAX_LIMIT = 32.0
HOME_OFFSET = -0.118
HOME_SEARCH_VEL = 1.166667
HOME_LATCH_VEL = 1.066667
HOME_FINAL_VEL = 1.100000
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 2
#******************************************

what worked in stepconf and parallel port

[AXIS_X]
MAX_VELOCITY = 3.25
MAX_ACCELERATION = 3.8
MIN_LIMIT = -0.25
MAX_LIMIT = 36.5
[JOINT_0]
TYPE = LINEAR
HOME = 0.0
MIN_LIMIT = -0.25
MAX_LIMIT = 36.5
MAX_VELOCITY = 3.25
MAX_ACCELERATION = 3.8
STEPGEN_MAXACCEL = 6.0
SCALE = 1016.00000104
FERROR = 0.05
MIN_FERROR = 0.01
HOME_OFFSET = -0.750000
HOME_SEARCH_VEL = -1.100000
HOME_LATCH_VEL = -0.40000
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 1
#******************************************

should I purchase an addon card to the 7i92TM to get the home /limits /estop working and wire direct to it?

Have you checked my ini file is this all correct or have i done a mistake 

Thank you, i will check this when i am at home

With loops 100 I easily got a crash.
Unfortunately it dídn't recover. Same old libusb debug message.
This is on the "new" N100 mini pc.

I understand your point about motion being the proper authority for movements.

My current focus is strictly on validating a clean and deterministic CiA402 semantic layer in isolation, before going into deeper motion integration discussions.

As suggested earlier, I think a dedicated thread about motion/motmod integration would be better for that architectural direction.

For now, I will proceed with the next step: extending this modular CiA402 stack toward dual-axis gantry/squaring validation in SIM.

Once the semantic layer is stable and multi-axis behavior is validated, it should be easier to explore tighter motion integration if needed.

It seems that's a missing piece at the end of the file.

Let's try the attached ngc file.
Load in LinuxCNC and see if it works.
It has been generated using your ncam xml project.

Maybe you could compare it with the file which gives you the error.

Regards
Giovanni