Firmware architecture question trajectory planning
I thought I would ask this question as I could not find a good answer already in the forums. Is there a reason why most(all that I have seen) reprap firmwares don't offload some of the trajectory...
View ArticleRe: Firmware architecture question trajectory planning
Yes you could offload some of the planning to a preprocessor, but this has a number of disadvantages: - It would be another step to run before you print, unless it was integrated into the slicer -...
View ArticleRe: Firmware architecture question trajectory planning
Excellent points. That was why I brought it up in this forum was to get others thoughts. It is always refreshing to see someone else's perspective. Just to add to a couple of your points. 1. I was...
View ArticleRe: Firmware architecture question trajectory planning
The issue with pause/restart is that you need to stop the print cleanly, but after the planning is completed you can get long streams of moves that are merged into each other without the head coming...
View ArticleRe: Firmware architecture question trajectory planning
That makes sense. I can see how that would be impacted then. Thanks
View ArticleRe: Firmware architecture question trajectory planning
Hey, This is not quite what you asked about, but I will mention a possible way to improve the performance of the planning calculation *in the firmware*. Note that I have implemented this in my...
View ArticleRe: Firmware architecture question trajectory planning
Sorry, I just saw your response. I can see what your talking about. Your way does look like it would be more efficient with minimal negative impacts. It does seem smarter than looking each time. Also,...
View ArticleRe: Firmware architecture question trajectory planning
I'm sure it's true that you can reduce the planning time by bunching moves so as to add several at once. However, when debugging my fork of RepRapFirmware, I found that when adding a new move, it...
View ArticleRe: Firmware architecture question trajectory planning
@dc42 I have also wondered about how many moves need to be processed each time. My Apritner firmware does not optimize unnecessary computations, it does a full planning round when it decides to...
View Article