- Posts: 79
- Thank you received: 0
Low Speed for 3d Printing application
But if we blend points in a XYU space, when the u movement isn't actually happening, wouldn't this create artifacts or other issues in the printed part?
Please Log in to join the conversation.
You could try running the G-code in a simulator, then doing a global search-and-replace of U for Z (well, I would use U -> & , Z -> U, & ->Z ) and run the code again, see if it gets faster.
Please Log in to join the conversation.
Today i printed a model with a very low polygon count (a low poly pikachu), and it took about 5 - 6 hours, while cura considered that a 4.30 hour print. That's much closer than usual, so it's a matter of segments number.
Please Log in to join the conversation.
- tommylight
-
- Away
- Administrator
-
- Posts: 22010
- Thank you received: 3
For plasma cutting i give it 20 to 100% more time depending on how complicated the end result is. That is also due to probing time as that increases a lot the overall time it takes to finish a job.
Please Log in to join the conversation.
For optimal operation, this probably requires delaying the motion in hal
before its feed to the joints so the extruder response over time can be
modelled and compensated
I believe that Machine kit has implemented a delay component that could
be used for delaying motion. If simple lookahead is not good enough, a
FIR filter could be used to process the velocity signal. All of this is pretty
slow so a servo thread loop time resolution should be fine.
Please Log in to join the conversation.
PCW wrote: One way to avoid the entire TP issue is to use velocity based extrusion.
For optimal operation, this probably requires delaying the motion in hal
before its feed to the joints so the extruder response over time can be
modelled and compensated
I believe that Machine kit has implemented a delay component that could
be used for delaying motion. If simple lookahead is not good enough, a
FIR filter could be used to process the velocity signal. All of this is pretty
slow so a servo thread loop time resolution should be fine.
How would this work? Do you need to make changes in the gcode to have velocity data or it can be done with the information already present in a normal slicer gcode?
Do you have any advice on where to start?
Please Log in to join the conversation.
Please Log in to join the conversation.
github.com/dabit20/rpi_cnc
and guess what? he runs the machine with swapped A - Z axes.
I'll try to ask him if he did that to fix this exact problem
Please Log in to join the conversation.
Muz94 wrote:
PCW wrote: One way to avoid the entire TP issue is to use velocity based extrusion.
For optimal operation, this probably requires delaying the motion in hal
before its feed to the joints so the extruder response over time can be
modelled and compensated
I believe that Machine kit has implemented a delay component that could
be used for delaying motion. If simple lookahead is not good enough, a
FIR filter could be used to process the velocity signal. All of this is pretty
slow so a servo thread loop time resolution should be fine.
How would this work? Do you need to make changes in the gcode to have velocity data or it can be done with the information already present in a normal slicer gcode?
Do you have any advice on where to start?
In the very simplest case you would take motion.current-vel, scale it and feed it to the extruder stepgen velocity
Next would be to delay all motion joints with a delay component and feed the non-delayed velocity to the stepgen
Fancier would be to feed the non-delayed velocity to a filter that compensates for the time domain response
of the extruder
Please Log in to join the conversation.
“The good news is, I have a branch that supersedes it, and does a slightly more complex blend (using two tangential arcs), and can also blend in ABC as well.”
Please Log in to join the conversation.
