LinuxCNC S-Curve Accelerations

ANd also try installing this 6.12 kernel another user built
drive.google.com/drive/folders/16Xlry00L...SlwznPLv?usp=sharing

Thanks,

Will give it a try tomorrow.

Hi,

Before starting to change kernels etc. I thought maybe first do the latency-histogram test.
I did this on 2 different pc's.

From what i read here : max us > 100 = is bad.
Is this value both the same for base- & servo-thread?
Or maybe i am reading the histogram not correct.

 
 
 

Always use --show at the end of latency histogram, it will show the number of excursions that are not inside the visible area of the histogram, but they can be seen as multicolored columns on both sides of the histogram.
Also, use --nobase if there is no need for the base period, it adds more timing strains to CPU that will mess with the servo period latency results.
For both periods For servo period only

SSH and samba are security risks, hence usually not included in major distros.
They should be installed only by whoever actually needs them, and some security info should be digested before venturing into it.

wrote:

Though "included" ≠ "enabled"

They are enabled when installed and fully functioning.

Grotius wrote:

@Rodw,

Thank you for your effort, all your input so far.

I have tried to create a .iso for day's, using the lb build system and also by using a chroot environment.
However it failed at some point when the .iso installation was ~60% complete.
Also the linuxcnc live build failed at some point, it had something todo with filmware, but that's no problem.

Then creating .deb packages is also a lot off work. As you have at least 2 types. The normal packages and the -dev packages
wich includes .headers etc.
I think we have to use 3 types, like the normal, the -dev and the -source.

For now i use a Qemu vm. Install debian and the software we need. Then the Qemu .img file can be compressed and
downloaded by others to test in their vm.
For running on real machines, i have to do a extra conversion step from .img to other .img type,
then write the .img to usb, and it will run.

I’m just watching the sidelines from a car driving by the football game … but it seems to me like you’re doing an awful lot of work to avoid making a new git sign in and creating a pull request, etc.

It just seems like it further fractures and obfuscates an already fractured project that is kind of on life support as it is.

Just my $0.02 for what it’s worth. ¯\_(ツ)_/¯

@SnowGoer540,

At the moment we have 2 testers who failed to run scurve on their machines. One off the testers
is running the cia402 with ethercat. Somehow linuxcnc has following errors using the tpmod_scurve.
At the moment we are unable to find the reason. Maybe kernel is too slow, mabye it's something else.

The other tester is anonymous and problably has multiple machines running. He pointed out the latency is very bad for
the latest debian 13 rt kernel. So i made a debian 10 and a 4.19 rt kernel wich he is familair with. But this also runs dramatic
on my laptop.

Then on my laptop i got also poor results using ethercat steppers at the moment.
In the past everything worked flawless, but this was on a normal desktop pc running ethercat and steppers.
Therefore maybe the problem is just the laptop, performing poor on the rt kernel.

Then there is the cmake build system wich i use to compile the scurve planner. The linuxcnc makefile is unable to
compile c++ code along with it. And i think the cmake build system for the scurve planner will not be merged to the linuxcnc
github source, because it doesn't align with the current makefile system.

Then there is that extra licence note, that will not be approved, but still has our attention.

So even when the scurve run's nice in a linuxcnc simulator config. There are still other problems that has to be resolved at the moment.
Therefore i think it's too early to do a git push request.

Personally i don't see linuxcnc as a fractured project. Best is too stay positive

Fair enough. Perhaps when it’s ready for prime time, we can work through the other issues to come up with a cohesive solution and find a way to push the project as a whole forward.

I prefer to be positively realistic

Keep up the nice work!

Hi,

Using the linuxcnc iso & ethercat my jog speed is max 5000 mm/min. and apptime 50000.
This is tested on a laptop. Very bad performance.

I used to have apptime 15000 and jog speed around 19000 mm/min using a desktop pc.