I currently have 2 and in the near future will have 3 Duet based printers. I really wanted an easy way to monitor and control them all without needing to pull up a web browser or use my phone I've also had 2 Panel Dues fail on me and dont want to spend anymore money on them.

The box is using an ESP32 wit a 4x20 display and a i2C backpack along with some cheap switches. Total cost is around $30 from Amazon and possible cheaper if you source from overseas.

The code is very basic, mainly because I'm working from examples on google. So far it sends a Type 3 status request to both printers and then reads in the resulting JSON blobs. The display uses the JSON data to show estimated print time remaining (based on filament)

The top row of buttons let me select which printer I want to control (Red, Blue or Green) and an Escape button which isn't implemented yet.

The rest of the buttons send an http rr_gcode request to which ever printer has been selected for control. So far I only a few basic commands implemented but I plan on adding more like baby step and print speed.

If there is interest in a very basic controller like this I'll try to clean the source code up and post it.

Is there currently a way to set a global variable from one macro and check it from another? My current work around is to setup a fake FAN port and set it with an "M106 P5 S255" from one macro and then check "fans[5].actualValue" from the other macro. I'm doing this because after I run my "Filament Unload Macro" I would like my "Filament Load" macro to check if the Unload macro has already been run. My current method seems hackish at best

Currently the firmware is limited to trigger0-trigger9 with only 2-9 being user defined. Is there a chance that could be expanded ? I recently wrote some macros to use physical buttons to load and unload filament and used up Triggers 2-7. Then I made another button to turn my LED lights on and off and used Triggers 8-9. It would be nice if we could use up to Trigger 100 or even if there was way to tell it what macro to call instead of a trigger number. Thanks

Load/Unload/Purge/Resume done with 2 buttons
https://www.thingiverse.com/thing:3584561

@fcwilt It's an extremely popular browser plugin that's been around for over a decade.

https://en.wikipedia.org/wiki/Tampermonkey

Got this all working. The new features in RRF3 are awesome.

daemon.g

if sensors.inputs[4].value == true && fans[1].actualValue == 1.0 		;Checks if the Fan is showing a stuck rotor alarm and also checks if the fan should be spinning
	G4 S1									;Buffer in case the fan took a second to spin up
	if sensors.inputs[4].value == true && fans[1].actualValue == 1.0	;Second check to see the fan is still in alarm
		echo "OH CRAP WE STUCK"			;Console message that can be checked on the PanelDue to see what happened
		M106 P1 S0 H-1 				;Turns off Thermostatic control on the fan so it doesnt try and turn back on 
		M112					;Emergency Shutdown

Turn on "Interface Layer" under support settings in Cura

If you have multiple Duet printers and are looking for an easy way to tell them apart in DWC then you should check out this Tamper Monkey script. It lets you easily/automatically change the color of the title bars in DWC based on your printer IP address. It also works with both light and dark themes

https://github.com/joshenders/userscript-duetwebcontrol-colors

@fcwilt Thanks, I've fixed the link

So glad I found this post after struggling with this sensor.

I ended up sistering a 1.5k resistor across the existing 4.5k SMD resistor for a combined resistance of 1.1k. The sensor now works correctly with all LED indicators also still functioning.

This is the Gcode command I used for RepRap 3.2
M591 P2 C"e0stop" S1 D0 ;Filament is out when switch is Low, Extruder 0

Turn on "Interface Layer" under support settings in Cura

I currently have 2 and in the near future will have 3 Duet based printers. I really wanted an easy way to monitor and control them all without needing to pull up a web browser or use my phone I've also had 2 Panel Dues fail on me and dont want to spend anymore money on them.

The box is using an ESP32 wit a 4x20 display and a i2C backpack along with some cheap switches. Total cost is around $30 from Amazon and possible cheaper if you source from overseas.

The code is very basic, mainly because I'm working from examples on google. So far it sends a Type 3 status request to both printers and then reads in the resulting JSON blobs. The display uses the JSON data to show estimated print time remaining (based on filament)

The top row of buttons let me select which printer I want to control (Red, Blue or Green) and an Escape button which isn't implemented yet.

The rest of the buttons send an http rr_gcode request to which ever printer has been selected for control. So far I only a few basic commands implemented but I plan on adding more like baby step and print speed.

If there is interest in a very basic controller like this I'll try to clean the source code up and post it.

Check your router setting to see if you can assign the IP or mac address a hostname. Then you can add a ".lan" or ".printer" extension to them

This is how the settings look in routers running dd-wrt firmware. But you should be able to google similar directions for your router

@fcwilt It's an extremely popular browser plugin that's been around for over a decade.

https://en.wikipedia.org/wiki/Tampermonkey

@fcwilt Thanks, I've fixed the link

If you have multiple Duet printers and are looking for an easy way to tell them apart in DWC then you should check out this Tamper Monkey script. It lets you easily/automatically change the color of the title bars in DWC based on your printer IP address. It also works with both light and dark themes

https://github.com/joshenders/userscript-duetwebcontrol-colors

I have flashed it multiple times with the firmware and the problem persist. The original panel was purchased from Printedsolid.com on 1/11/2019 and had to be warranty replaced on 2/28/2019 after it stopped working.

Here is a picture of the back of the panel.

Any ideas? Should I consider it dead? Any possibility this could be covered by warranty?

I thought that at first but the Setup screen still seems to show the correct colors on the color bar.
Maybe the contrast control went out?