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.
@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?
Today when I turned on my printer the PanelDue5i switched from it's normal colors to a very washed out look. This has persisted even after re-flashing it. Is there anything else I can do to fix it?
Light Theme
Dark Theme 2
edit: Ignore this I misread the first post.
The M563 tool definition line in your config contains "F0" which is linking your part cooling fan to the hot end. Try changing that F1 and see if it corrects the issue .
I recently ran into this same issue and was surprised no one made a easy plug and play solution. I ended making an simple RC circuit since thats what I had on hand at the time. But it would be great to be able to get this as an add-on
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
Progress update:
I enabled the pull up resistor on the "duex.estop6" port and connected the fans alarm wire to "E1_STOP" pin and everything is kind of working as expected. Every now and then during testing it seems to reset the printer, not sure why this only happens intermittently.
edit: It seems that it has something to with PWM control on the fan. If I only use 255 or 0 everything seems to work as expected.
M950 J4 C"^duex.e6stop" ;Assigns e6 Endstop to the fan stuck wire
When sending the M112 command the printer turns off and then starts the hot end fan "fan1" at full speed. I'm hoping to use the new daemon.g file to monitor a rotor stuck alarm wire on the hot end fan and send an M112 if its detected. So the fan continuing to spin after M112 is problematic if it's in a known stuck position.
Printer is running:
Duet2Wifi w/Duex5 running RRF RC3
config.g snippet
; Fans
M950 F0 C"Fan0" ;Define the Parts Blower Fan connected to Fan0
M106 P0 S0 C"Parts Blower" H-1 ;Name the fan, turn off thermistic control and turn the fan off if it was running
M950 F1 C"Fan1" ;Define the Tool Fan connected to Fan1
M106 P1 T40 H1 ;Enable Thermostatic Control to turn fan on 40 degrees
Edit: After some experimentation it appears that any fan with thermostatic control enabled is set to 100% after an M112 command. Is this the intended behavior?
I am trying to connect a hot end fan that has a 3rd wire that signals the rotor is stuck. I would like to wire the signal wire to one of the end stops. I believe the internals of the fan for the signal wire is an NPN Transistor. I found an older post referencing a similar situation and a mention that it only needs to add a diode to the circuit, however it doesn't say where to place it.
The printer runs on 24V and I will be powering this fan off the 12V supply on the Duex5.
Older Post referencing a similar use:
https://forum.duet3d.com/topic/1278/induktive-endstops/3
Snippet from the Fan datasheet
Link to Datasheet:
https://www.mouser.com/datasheet/2/310/OD2510-1623483.pdf
Link to Fan:
https://www.mouser.com/ProductDetail/670-OD2510-12MB02A
@dc42 Is it possible to have the Duet "Emergency Stop" when a Stack overflow occurs?
The console is showing Stack Overflow errors when trying to deploy the BLTouch from a macro that that was started from a Trigger and calls another macro. The probe then fails to deploy.
Process:
A state change occurs on "e1stop" and trigger7.g is run. It calls "UnloadFilament.g" which then runs "CheckifHomed.g". During the homing operation the BL Touch probe fails to deploy and the bed crashes. The console shows 2 Stack Overflow errors when the probe attempts to deploy.
CheckifHomed.g - Runs fine when run on it's own
CheckifHomed.g - Runs fine when called from "UnloadFilament.g" if UnloadFilament was started from the macro menu
CheckifHomed.g - Runs fine when called from startcode.g
CheckifHomed.g - Runs fine when called directly from trigger7.g
If trigger7.g is moved to the Macro Folder and started manually everything works fine.
config.g Info
M950 J3 C"e1stop" ;Load Buton
M581 T7 P3 ;Runs trigger7.g file when pressed - First step of Unload process
Please let me know if you need any more information.
Found a slightly better way to transfer info between macros. Using the same fake fan port you can change the name with an M106 P5 C"NewName" or even an C{Object.Model} as the name. Then recall that information back in another macro or even later in the same gcode.
edit:The below example wont work, the M220 command won't accept {fans[5].name} as an input since its been converted to a string. I'm going to leave it here in case anyone has other ideas
One example I can think of this is storing the current speed factor as a Fan name, setting the speed back to 100, then restoring the speed later in the gcode. I'm sure all this will be much easier once actual variables are implemented but until then this seems like a decent workaround.
;Setting up the fake Fan in config.g
M950 F5 C"duex.fan5"
M106 P5 C"Fake"
;Storing the current print Speed Factor as a fan name
M106 P5 C{move.speedFactor}
;Setting Speed Factor to 100%
M220 S100
;Setting the Speed Factor back to what was stored
M220 S{fans[5].name}
edit edit: I think this might work with a fake heater and storing the integer you wanted as the max temp using an M143