- Posts: 7
- Thank you received: 0
LinuxCNC S-Curve Accelerations
Grotius wrote: There is no real scurve math inside. It looks like they hide it somewhere else.
Ok, what about this one, from line #670?
rmu wrote: you can look at this github.com/rmu75/linuxcnc/tree/rs_6otp for an implementation of the 6th order bezier curve. the discrete diff math is not needed in linuxcnc, cpus powerful enough to run linuxcnc are powerful enough to use floating point and "direct evaluation".
I've sucessfully resolve all building/compiling dependencies and will try your approach in a couple of days.
Please Log in to join the conversation.
- TheRoslyak
- Offline
- Elite Member
-
- Posts: 238
- Thank you received: 0
If I build by "make ..." - my ethercat configuration not start. lcec is broken pic1 (
In "hello world" configuration - everything start, but I can't check the robot physically
Please Log in to join the conversation.
Looking at Nico2017's EtherCAT build instructions perhaps the only thing needed is to copy (or link) your system lcec.so into the folder indicated in pic 1?
My system lcec.so is in /usr/lib/linuxcnc/modules/lcec.so.
Please Log in to join the conversation.
- TheRoslyak
- Offline
- Elite Member
-
- Posts: 238
- Thank you received: 0
This means ethercat will only work by "dpkg".
If you have problems with git commits, you can subscribe *.tar.
I'd better build by "dpkg"(without errors) - so I can check on ethercat robot
Please Log in to join the conversation.
Edit: Sorry, I can't help you with the dpkg build, I've never used that myself.
Please Log in to join the conversation.
- TheRoslyak
- Offline
- Elite Member
-
- Posts: 238
- Thank you received: 0
I can't home with your configuration. and get error (pic).
First. I tested on PICO316HGA-N4200 computer and received the same error + latency error.
Then. I test on i9900k and get same error.
I homed robot by linuxcnc-master and start your configuration without homing parameter. I can play my test program but I didn't see the difference in physical.
What parameters I scope to see the difference. (Motion.-vel-cur , "x-pos=>ddt=>ddt=>x-axis-acc" and etc . is not change)
Please Log in to join the conversation.
---
A good parameter to look at would be joint.N.acc-cmd. Without a jerk-limited planner you will see step changes (or just a flat line - so trigging best done on joint.N.vel-cmd) while jogging a joint. With smooth1d you should see a gradual, linear change in acc-cmd.
But again, at the moment I've only replaced the joint jogging planner, so you will not see any difference on axis jogs nor on coordinated motion, i.e. while running a G-code program. Only on un-homed joint jogs.
Please Log in to join the conversation.
- TheRoslyak
- Offline
- Elite Member
-
- Posts: 238
- Thank you received: 0
Wanted to know if progress in work?
What equipment do you have to check it? Mesa, ethercat driver or any else?
Please Log in to join the conversation.
I have EtherCAT servos running with LinuxCNC and also a Mesa 6i25+7i77 combo and analog servos that I can hook up. But I don't have a machine to hook them to. For testing the current issue I need an actual axis including limit switches, which I'm putting together - I have linear rails, ball screws, switches etcetera. But I don't have access to a workshop (I live in an apartment) so it's a bit slow going. Can't make too much noise, weld or do heavy metal working etc.
Please Log in to join the conversation.
I just ran across some new research for Jerk limited trajectory generation.
arxiv.org/abs/2105.04830
The code is MIT licensed and available at:
github.com/pantor/ruckig
Looks like they are solving cubics and quartics in realtime ( and by the looks of it without iterative methods).
-automata
Please Log in to join the conversation.
