Thanks for the explanation.
Last thing to try is a forced update of the wifi firmware.
Download this bin file and place it on the SD card in the /sys folder.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/DuetWiFiServer.bin
Then connect to the board via USB terminal and send M997 S1 which should flash the wifi module.
If that doesn't help, then I agree the module is likely faulty. When and where did you purchase the board?
There's a very small volume of plastic in the hotend when loaded so it's not going to have a huge effect. It's not like you're extruding at the time. (Though I suppose you could manually push some through.)
The reason for suggesting you remove it is just to keep it from oozing out or potentially cooking and getting clogged.
It's also suggested to have the cooling fan on at a normal print speed so that the algorithm can take some of that additional cooling into account.
If you follow from here I think you'll get what you need.
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+2:+Configuration/38#s135
If you have a config package from the configurator and prepare the SD card as described in there the Maestro will be set to DHCP and should get an IP address at startup.
The guide then goes through verifying the firmware and updating if needed and connecting to the web interface.
M552 S1 should enable the network. The default is DHCP so it should grab an address. M552 by itself should echo back the received IP.
@tommyb This thread is for people having problems with the Formbot Troodon custom RRF compatible board. Please start a new thread for your issue with the Duet Wifi.
@Meki said in Homing issues on a Delta with Duet 2:
; Endstops M574 X1 Y1 Z1 S1 ; set active low and disabled endstops
This should be M574 X2 Y2 Z2 S1 for high end endstops.
If you're a new user to Duet and this is a new build, it might be a good time to jump to RRF v3.1.1 since you're getting a fresh config from the config tool anyway.
Updating the firmware is easy as uploading two zip files.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
First upload the 3.0 zip file as is without extracting. Then after it updates, do the same for 3.1.1 zip file.
Then you can upload the config file set from the web tool for RRF3.
It would be helpful if you could make a video on your phone or something that showed what the behaviour of each is.
It really makes no sense that the DWC homing buttons and the PanelDue buttons behave differently since they call the same macros.
Well it depends how much you want to check. If you follow that guide it goes through a lot of initial setup checks like connecting over USB etc.
If you connect via USB you can see if it responds to M115 to report it's firmware version.
That looks correct. Now just make sure you have homed the z axis with G28 before creating a heightmap with G29 and the datum error message should go away.
The Duet2 kit would be closest to the maestro. The Duet3 has larger motor connectors.
Post your config.g and homedelta.g
That looks fine, but you must be using G30 in your homeall.g. Also make sure you do NOT have G29 S1 in your config.g
Normally they would be shipped in their own box similar to the Paneldue, but M3D has chosen a different option. Does the board work? Shipping in a bubble bag might be ok, really depends on handling.
So you already have one? If so, here's a guide to installing it on an ender 3 pro. It's a perfect match.
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+1:+Wiring/37
I'm confused, are you relaying someone else's experience there? You've only just got the link an hour ago.
@JohnOCFII said in Inconsistent results with optical encoder wheel filament sensor:
Is there some way to configure M591 to, perhaps, not be so concerned with particulars, but to sense, for example, no movement for 5 seconds, and use that to trigger the sensor?
That seems like a reasonable feature request.
Higher resolution on the slicer end may actually exacerbate the problem because if the moves are sufficiently small they won't get activated because they are smaller than a single microstep.
Using a 0.9 motor on the extruder will get you more natural resolution. Increase the microstepping can get you closer as well, but microsteps are less accurate.
That z datum error message usually means you've loaded a heightmap before you've used G30 to set Z0 first. Or you've used an endstop to set z0 rather than the probe.
Check this calculator out to see if any of your extrusion moves fall below the limit.
https://wilriker.github.io/microstep-calculator/
E0.06994 seems t be the lowest in your posted code, but there may be lower?
You didn't post your other settings and details so I can't really say, but based on 0.4 nozzle, 0.2 layer, you might need to use at least x32 microstepping to get some movement from the smallest sections.
I think prusaslicer also has a resolution setting?
You'll need to provide some more details on the printer, your settings, and gcode sample to get more educated answers.
@MaxGyver said in Pressured air cooling controlled with servo and ball valve:
78% (valve closed) to roughly 90% (valve fully open).
Look at the M106 L and X parameters to set the min and max range to match your usable range. That should scale the S parameter to make S0 to S255 within your usable range.
The filament management function is fairly rudimentary at the moment. I can see it becoming a plugin for DWC which would open it up to others to improve or have different options like the plugins available for Octoprint.
I'll move this to the DWC wishlist forum though because it's a good request.
Your question is a little unclear. Are you using a Duet3 or Duetwifi? are you wanting to use 2 fans on the same tool?
There is also the chance that you might still be able to find a Maestro for sale.
