Ocho Camino on the discords.
My #1 feature request is an option to sort the gcode filenames by date. 99% of the time I want to print the file I just uploaded.
Scrolling thru all the files, while trying to remember what I just uploaded is pretty annoying. I end up with a lot of gcode files that look like aaaaaaSomeobject.gcode with the aaaaaaa to get it to sort at least to the first page. Obviously this isn’t a very good workaround.
The current RRF documentation for M593 indicates that there's a single frequency selectable for the input shapers. Will this be changed to support independent frequencies and shapers per axis? Machines are far from iso-resonant, so choosing one frequency and shaper for both axis will yield a sub optimal result.
Bedflingers in particular have radically different resonant frequencies.
On my crossed gantry 500x330 printer, one axis is best served by a 46hz ZV and the other by 68hz MZV shaper (according to klipper recommendations).
I got significantly better layer stacking with my Delta with LDO steppers when i upgraded from OMC (same as ones linked above).
LDO datasheeet: https://cdn.shopify.com/s/files/1/0239/9287/files/LDO-42STH47-1684MAC_RevA_9f61050a-7275-4b98-a6c5-9f28bd0cb2b7.pdf?172
Filastruder carries them.
@arhi said in PanelDue Improvement Tips:
TBH it is easier to make slicer name file with YYMMDDHHmm prefix
Unfortunately PanelDue sorts A-Z so the most recent files are at the bottom, requiring scrolling.
Would be really nice if PanelDue allowed you to set the sort order.
@dc42 if ram is a constraint, then that's an acceptable reason for duet2. But, i'd prefer if some other features were limited (like the LPC port does) to free up ram to support it.
If there isn't 2 axis input shaping in rrf3, I will await the klipper port to duet3. Duet3 mini port has been completed.
Input shaping is THE killer feature. And 2 axis is essential for it to work well.
@dc42 if ram is a constraint, then that's an acceptable reason for duet2. But, i'd prefer if some other features were limited (like the LPC port does) to free up ram to support it.
If there isn't 2 axis input shaping in rrf3, I will await the klipper port to duet3. Duet3 mini port has been completed.
Input shaping is THE killer feature. And 2 axis is essential for it to work well.
I should try the same shaper and freq for both axis to see how that impacts print results. Away from printer until monday...
Some before and after pix (ignore the schmoo near the bottom. i have a fan connection that is wonky). 2K to 14K accel at top. 200mm/s
The current RRF documentation for M593 indicates that there's a single frequency selectable for the input shapers. Will this be changed to support independent frequencies and shapers per axis? Machines are far from iso-resonant, so choosing one frequency and shaper for both axis will yield a sub optimal result.
Bedflingers in particular have radically different resonant frequencies.
On my crossed gantry 500x330 printer, one axis is best served by a 46hz ZV and the other by 68hz MZV shaper (according to klipper recommendations).
@arhi said in PanelDue Improvement Tips:
TBH it is easier to make slicer name file with YYMMDDHHmm prefix
Unfortunately PanelDue sorts A-Z so the most recent files are at the bottom, requiring scrolling.
Would be really nice if PanelDue allowed you to set the sort order.
@dc42 said in Duet 3 Mini 5+ : Initial announcement:
We have reduced the stepper driver support from 5+3 to 5+2. T
Deal killer for me. Oh well. I was excited for this board. It was going to be the recommended board for CroXY.
I'm using a hemera on my d300 (with linear rails). it works fine and gets great prints.
https://www.thingiverse.com/thing:4027625
I'm using tricklaser arms which don't pop off like magball arms do. I'd be very hesitant to use magballs and a direct drive extruder.
Check the railcore discord. A used rc with first class components ya was posted about 10 days ago.
My #1 feature request is an option to sort the gcode filenames by date. 99% of the time I want to print the file I just uploaded.
Scrolling thru all the files, while trying to remember what I just uploaded is pretty annoying. I end up with a lot of gcode files that look like aaaaaaSomeobject.gcode with the aaaaaaa to get it to sort at least to the first page. Obviously this isn’t a very good workaround.
@wingtip I'm fighting the same issues with dual X and dual Y motors. Can you post your final config.g and homeall.g (or homex.g)? Might be able to figure out my problem without needing to make a new post.
Thanks.