Hi Arciera,
the ./installer script seems to fail every time.
But ./build_lcnc && ./start_lcnc works fine. Maybe the problem is in ./deps_lcnc.
The custom
trajectory planner
component "tpmod.so" has already some logic inside now.
It is succesfully linked to multiple libraries.
link.
It can load the gcode file using "tpAddline" & "tpAddCircle". "tpAddRigidTab" is also used, but later on we have
to talk about implementation properties like synchronised motion for tapping, wich are unknown for me now what to do.
This all then is stored into the
vector library.
During loading it add's also empty fillet segments to the
vector library and creates the fillets using the
filletizer library based
on the given G64 values.
In the same flow the
motionizer library calculates optimal trajectory velocity's using curvature extrema's, vm's, lenght's.
This optimalisation is done every gcode load cycle, as i don't know how to do it else. It's a fast algo, so i think it
Then step by step we make progress to the code.
We can decide if we use a max buffer size for our vector library. For example buffer 500 segment's max.
This is more or less how lcnc it does at the moment. We can also decide to make a ringbuffer. A buffer with
250 segments in the past and 250 segments in the future.
