Advanced Search

At least some honesty.

I was responding to  MWalz  13 Jan 2025 21:26  #318886  on this thread. 

Hi, 
beim Gewindeschneiden mit 33.1 wird eine Fehlermeldung ;missing k-word" ausgegeben, obwohl es vorhanden ist. 
Wenn man die Meldung ignoriert, wird er ausgeführt, allerdings bleibt der Programmlauf daraufhin stehen.

Im MDI funktioniert der Befehl allerdings problemlos.

Funktioniert der Befehl bei euch?

Gruß

PCW you are impressive! I checked the original wiring of the Mach3 board the mill came with, and it used single ended wiring using only the negative wires for STEP and DIR, so I tried to change that.
No change when using the UI, it still shows following error. But then I tried the servo tuning test in pncconf, and the steppers are now moving

Now I just need to figure out the following error, but at least now I know that the hardware is working.

Thank you very much, your help is much appreciated!

 

I think the max value is to high.
Maybe the cpu needs to tweak?

I installed version 2.9.4 and 2.9.7 and they work worse, replacing this error with another one - Queue is not empty after probing.
In this regard, I ask you to publish a complete road map on what is quoted here forum.linuxcnc.org/38-general-linuxcnc-q...obing?start=0#333528"
a solution to this topic.
It says about "Great HAL": www.forum.linuxcnc.org/38-general-linuxc...dlock?start=0#332412

Now I have such entries in hal -
By analogy with "Great HAL" I assume this -

However, how can this be related to the M64 P0 + M65 P0 call?
It is not clear why the Greet HAL example contains addf flipflop.1 (in addition to addf flipflop.0) if flipflop.1 is not used in any way according to the example?

Thanks for you help.

I found the problem, I guess I am getting too old. (72)
It was a new install and I copied the wrong hal configuration.
I do regular backups and name folders by date (2025-11-11)
I must have read the folder wrong.
Culprit was
setp pid.x.maxerror 0.0005

Every thing is back to normal

If you get a following error, no further movement will be possible so a configuration
issue the causes a following error is s show-stopper.

Other possible reasons for no motion are wrong scaling, too short step lengths
high drive requirement (try single  ended wiring rather than differential)

Single ended wiring:

DRIVE STEP+  --> 7I76EU STEP+
DRIVE STEP-  --> 7I76EU GND

etc
 

yeah, think that is all machines, but could be wrong

I think you are spot on with the "enable" output comment, the motors where not locked. I disconnected "EN+ -> TB2 pin 6 +5VP" and bingo, the motors where locked. So far so good, thank you I have measured Dir+/- and the voltage here change when I jog the axis.

But alas, the motors will still not move. How ever, now I get the "Joint 0 following error" immediately when I try to move the X axis, so I suspect this is why nothing is moving. I have tried to read up on the error, and it seems to point at a misconfiguration in the PID/Acelleration/etc part of the config. But I can't really see it being SO wrong, that the motor won't start at all?

Found it out myself: it was: Is it a known problem that in "linuxcnc probe basic sim" jogging is not working after a program was run.

Workaround: clicking the “Manual” button after stop.

great glad you got it sorted out! what thread for the other issue, i do not see it in the qtpyvcp section?

The watchdog error is a sign of network latency issues.

I would try:

sudo chrt 99 ping -i .001 -q-c 60000 10.10.10.10

which should run for 1 minute and then print timing statistics
to see if this is the issue.

 

could be lost steps causing some errors. i would set the drive settings to fault for ANY lost steps and tune the system until it is not faulting. this would eliminate that. you don't want to run the system in a state where it is losing steps because of motor sizing and machine mass problems.

also i would make sure that your acceleration calculations for both axes come out to be the same.and ideally give both axis the same reduction. just takes several things out of the equation.

Also consider installing from the official LinuxCNC ISO, if you can tolerate XFCE.