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.
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.
@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.
Ah. Wish i could try the different order. 
@dc42 said in Toolboard Extruder Motor Stutters (most of the time):
ly tried to fetch and install the firmware, and the LED would flash at intervals. If you turned the power off while it was writing to flash memory, perhaps that corrupted the bootloader (it's not clear from the datasheet whether the bootloader protection provides adequate protection if power is removed while another part of the flash memory is being written).
What I would like you to do now is to disconnect the CAN connector from the tool board, and once again power the board up while both buttons are held down (then release them after powering up). If the
The .bin file was the same one I originally flashed to the Toolboard that was uploaded to /sys
Just tried a reboot with CAN disconnected and buttons pressed. No LEDs on between the buttons, and no bootloader/CAN connection.
@dc42 said in Toolboard Extruder Motor Stutters (most of the time):
an has identified the root cause of the original problem: your M906 command that sets the extruder current was earlier in config.g than the M584 command that defined the extruder driver. So the motor current wasn't being set, which would result in less than 100mA current.
In original post: "Increasing current to 1500 with M906 just makes it louder.", so Ian's theory isn't correct. (wasn't totally obvious that I did that with the console)
Ugggh, so this is weird. I updated the firmware thinking it could have been a firmware issue (long shot, I know).
M997 B20
After waiting many miinutes with no response, I power cycled.
'
Now the Duet3 isn't communicating with my Toolboard - tons of CAN response timeouts. No slow red flash, just the solid blue and solid red leds. The heater and fan turned on (I see the warning about that in the docs), so i removed all connections to the board except CAN and power and stepper.
I tried a double button power on to reset.
M115 B121 (or 10 or 20, the address i previously programmed) also error.
M409 K"boards" yields this:
{"key":"boards","flags":"","result":[{"canAddress":0,"firmwareDate":"2020-03-16b1","firmwareFileName":"Duet3Firmware_MB6HC.bin","firmwareName":"RepRapFirmware for Duet 3 MB6HC","firmwareVersion":"3.01-RC4","iapFileNameSBC":"Duet3_SBCiap_MB6HC.bin","iapFileNameSD":"Duet3_SDiap_MB6HC.bin","mcuTemp":{"current":29.4,"max":29.5,"min":18.3},"name":"Duet 3 MB6HC","shortName":"MB6HC","supports12864":false,"v12":{"current":12.2,"max":12.3,"min":12.2},"vIn":{"current":23.9,"max":24.0,"min":23.9}}]}
Seems the bootloader got corrupted.
Is there a bossa solution to reprogram the bootloader on a Toolboard?