I would be interested in seeing a configurable heater timeout. The idea would be to have heaters turn off after a set amount of time when a print is not in progress. This would be a good safety feature. It would also help reduce the scenario where the material is loaded and the hotend and is left on for a long period of time before a print is started etc. This can cause carbon build up in the nozzle if the material is sitting in a hot hotend without being extruded.

Maybe this already exists, but could not find any documentation on it.

Text strings that are longer than the width of the 12864 display currently get cut off. I would like to request that functionality be added so that text strings that exceed the width of the display scroll horizontally.

This is particularly relevant for:

• listing gcode jobs on the SD card
• Popup message generated by the system and M291

Please let me know if I need to add more info.

@dc42

Okay I got it to work. I was powering off the Duet after erasing and resetting the panel, which gives the white screen state. In this state, it does not seem to work.

What did work.

• With the Duet powered on and plugged into the panel
• hold the erase button on the panel for a few seconds
• press the reset button on the panel
• DO NOT power cycle the Duet
• The panel will remain on, displaying as usual
• Bossa will now recognize the panel via it's serial port
• Upload the new panel firmware as usual via Bossa
• When complete, unplug the usb from the panel and power cycle the printer.

Very embarrassing, but it appears I had a typo in my IP address and even though I thought I had double-checked, I somehow missed it. Everything is working just fine. Can access DWC from my computer while it's using 5ghz even though the duet is using 2.4ghz.

Feeling pretty stupid lol

Right now, as far as I am aware, there is no option to run a custom script when a stall is detected on a particular diver. I would like to use StallGaurd to detect filament jams and the run a custom script afterward. Perhaps we could introduce R4 which would pause the print and execute a custom script. It would be great if we could have custom scripts for stalls detected on each driver.

For example, if a stall is detected on driver 0,1,2... and stalled detection for that drive is configured with R4 it would pause the print and execute /sys/stall0.g, /sys/stall1.g, /sys/stall2.g etc.

@dc42

Okay, thank you for the info. Would it be possible to add the ability to do this to the wishlist?

I use macros to enable a lot of core functionality on the printer I'm developing and it would really make things a lot simpler if we could push one zip that contained macros, sys, and firmware files.

Our beta testers currently have to upload macros separately and there doesn't seem to be a way to include the file system we have set up for the macros. This means our users have to upload the macros and then recreate the file system if they want to have an organized way of viewing the macros.

@jckray I figured it out. micro usb port on the paneldue had been bumped and the solder joint had been broken

This is a firmware feature request for additional functionality for 12864 displays.

I would like to request additional values to be added to the alter/value list. I would like to be able to call all these values with the value function, but some may not be suitable for the alter function. They are listed in order of my personal priority.

1. Tool material status (name of loaded material i.e. PLA, ABS, None, etc.) - value
2. Mac Address - value
3. Current Job name - value
4. Printer Status (printing, busy, idle, etc) - value
5. Tool offsets (X,Y,Z) ideally after altering an M500 would be triggered to save the new offset to config-override - value/alter
6. Heater status (i.e. active, standby, off) - value/alter
7. Slicer time estimate - value

Please let me know if anything is unclear. Thanks!

Nevermind, found them!

Here's a DigiKey link in case anyone else needs this info.

https://www.digikey.com/product-detail/en/QPC02SXGN-RC/S9337-ND/2618262/?itemSeq=278874495

@hauschka I have also been thinking about this. Please update if you get anything working!

Very embarrassing, but it appears I had a typo in my IP address and even though I thought I had double-checked, I somehow missed it. Everything is working just fine. Can access DWC from my computer while it's using 5ghz even though the duet is using 2.4ghz.

Feeling pretty stupid lol

@mintytrebor Thanks for the suggestion. I gave this a go and I was able to get my computer connected to the 2.4ghz band, however, I was still unable to access DWC, so it must be something else causing the issue.

I can't access DWC on any of my devices by typing in the Duet's IP address. I'm using a Google Nest WiFi to provide the WiFi network. I think the issue is that all my devices automatically connect to the 5ghz band while the Duet can only use the 2.4ghz band. On the router I was using previously I was able to access DWC from a device connected to the 5ghz band, but on Google Nest WiFi communication between devices on different bands doesn't seem to be working, or at least I can't get it to work. Band assignment is handled automatically on Google Nest WiFi, and I don't think I'm able to manually switch my computer to the 2.4ghz band.

Hoping someone might be able to help me out.

Is there any documentation on a good process for creating custom .img files for the 12864 Display? I can't seem to find much of anything and I haven't been able to successfully create an .img file the displays correctly. Most of the time not is displayed or I get a solid white rectangle. Any help would be much appreciated.

@phaedrux I forgot about start.g, thanks for reminding me! I will give that a go.

@phaedrux I had that thought, but that can interfere with the print jobs if mesh leveling is done at the beginning of each print. At least in Cura, it outputs the tool command for the first tool used during a job before it inserts the start gcode. This means if the job is supposed to start using T1 and there is a T0 command anywhere in the start gecode then the job will start using T0 rather than T1. Thus, I have been trying to avoid any use of tool commands in the start gcode. This is pretty annoying though, so I might have to look into changing how Cura outputs gcode in the back end instead.

My idex machine has the z probe attached to T0. If T1 is the active tool it tries to home z and probe the bed using T1, which does not have a probe attached. I realize the simple solution is to make sure T0 is active when running G28 or G29, but is there any way to ensure that if this is accidentally done with T1 active it will still probe with T0? If you're not paying attention and trying to home z or run mesh leveling with T1 active it crashes the tool into the bed.

@phaedrux Will do, thanks!

I think I have a bad SD reader on my Mini 5+. The board randomly reports no sd card found in the middle of prints, or and startup. Has been happening with increasing regularity. It's gotten to the point where it won't detect the card 4 out of 5 times on startup and can barely make it a few minutes before if it is able to detect it on startup.

I'm wondering if there is anything else that might be causing this or if I should get the board replaced.

I have already tried using a different sd card, but this resulted in the same problem. I have also tried both SD cards on a different Duet 3 Mini and they work fine there.

@Phaedrux Yeah super strange!