Advanced Search

now i have no idea what is going on.

with the 5i25_7i76x2_2pd loaded my hal does load the pwm without alarm (i have not checked actual output though) but my A(3) axis does not work. If i revert to 5i25_7i76x2 A axis is good but obviously no pwm

???

thanks

Are the "enable" inputs on the drives wired to something?
Do the motors lock when powering on the machine and stay locked after running LinuxCNC?

If those are step/dir drives, you should be looking here:
forum.linuxcnc.org/10-advanced-configura...glass-scale-feedback
Also
dirsetup and dirhold to 20000
and stepspace and steplen to 5000
Untill you get things working properly, then you can lower the steplen and stepspace while testing to make sure there are no missed steps.
As you have them, chances are some steps are being missed by the drive so LinuxCNC keep upping the number of steps till it catches up.
-
Yes, i am aware the drive manual might say 200ns, but that is almost always not correct, except on very good quality drives.

I would set these ini values and re-try:

DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 5000
STEPSPACE = 5000

Are these step/dir servos with encoder feedback to LinuxCNC?

If so it seems there is significant delay from command to motion.
This may well be a drive tuning/setup issue. Maybe drive acceleration
set lower than LinuxCNCs setting or some other filtering or constraints
in the drive.

I would need a bit of hint on my tuning of AC servos + 7i95t, as I cannot decrease those spikes on acceleration and deceleration, doesn't matter if I go higher or lower with FF2. On linear move there is f-error 0.001mm or less. Should I start adjusting parameters on diver?
Also if I "go crazy" with short presses on arrow keys for jog, especially with changing direction, f-error is all the way up to 1mm or more.

Captures below are taken during running some test g-code:
 


 

 

I removed GladeVCP from ini and it boots. The spindle works, but xyz joints are not working. Will not jog. Homing does not fix anything, the values move in LCNC, but no physical machine movement. I get an error for:
cannot jog joint 1 because home_sequence is synchronized (-3)

Joint 0 is X
Joints 1 and 2 are my Y axis that are synced.
Joint 3 is Z

For example on TB2, if you set num_stepgens to 4, the TB2 step04/dir04 pins become
available as GPIO, but they only work as outputs because they have a buffer with its inputs
from the FPGA and outputs on TB2.

Well, that was easy! Thank you sirl
I think I'll make some chips!

External e-stop (fault) on EC500 input. 

Hello,

It's solved.
Git is updated.

@Evgen can replace or overwrite the tp_scurve.c from codeberg.
Then do a recompile for cmake : ./buid_cmake

The problem:
    In control.c Line 1867 it looks for 2 types :
    EMC_MOTION_TYPE_FEED
    EMC_MOTION_TYPE_ARC

Clothoid motion was giving no type.
Then the clothoid motion is now set to type EMC_MOTION_TYPE_FEED in the planner.

Now the motion.feed-value flippering is not there anymore.

What is using the hal pin : motion.feed-mm-per-second for example?
 

 
 

from:
linuxcnc.org/docs/devel/html/man/man9/motion.9.html

Set the servo period in the ini file to 2000000 (2 million) and set the P value for each joint/axis to 500.

So... 

What if LinuxCNC complains while starting...?

When running the latency test Tommy suggested, I saw a similar graph.

I migrated my working configuration to the PI4.. Then, I was visited by the dreaded latency complaint. 

Everything appears to work. I am running a Mesa ethernet card. What are the steps to debug and rectify the situation on a PI? 

Frank.hal attached. Do you need to see any more files?


 

Can you post the gcode?

Gcode is attached here:
forum.linuxcnc.org/38-general-linuxcnc-q...ner?start=210#324830