Hi Everyone

After using the Ender 3 (Cartesian) and upgrading to use full E3D hot end/ BL Touch/ Bond-tech extruder in marlin, I decided it was time to join the 32 bit movement and purchased myself a Duet WiFi and PT100 This will be my last upgrade till the E3D tool-changer build becomes available (will use this motion system and tool changers in future)

As part of the Duet WiFi wiring process I extended my cables to reach inside a IKEA lack case I've built. Wiring went smoothly and also initialising network on the Duet was a smooth and simple procedure.

Now I've come to the difficult bit, setting up the RepRap Firmware on the Duet, after reading through the marlin setup I had I filled in the config tool and ended up with this final config. https://pastebin.com/6TycU2B4

Unfortunately I'm having a few issues which I feel has to be down to Firmware / Slicer settings.

Issues:

• I can home all which works including the BL Touch probing, However as soon as i print an object the head crashes into the bed before starting the print. RESOLVED

• The first layer prints but then the following layers are all quite separated its like the z axes moves to much for each layer RESOLVED

• Cooling Fan not working RESOLVED

Ender 3 Cura Slicer Start G-code
M104 S{material_print_temperature_layer_0} ; Set Extruder temperature
M140 S{material_bed_temperature_layer_0} ; Set Heat Bed temperature
M190 S{material_bed_temperature_layer_0} ; Wait for Heat Bed temperature
M109 S{material_print_temperature_layer_0} ; Wait for Extruder temperature
G28 ; Home all axes
G92 E0 ; Reset Extruder
G1 Z5.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed

Any suggestions on what could cause these symptoms?

Thanks for the update, is there an updated wish list somewhere?

I did look here before posting here: https://forum.duet3d.com/topic/938/firmware-wishlist-and-priorities-for-duet-wifi-and-duet-ethernet/101 but the thread seams to end in December 2018.

I did notice that number 3. Logging of various events, including print start/pause/resume/cancel/end, and error messages. Done in 1.20 which I believe is this https://duet3d.dozuki.com/Wiki/Logging text based solution could you confirm? Ill have to take a look at this but it would be nice to have a GUI for this in DWC.

Hi All

I recently purchased the filament monitor and I'm about to do the wiring, the connections being ground, 3.3v and Output.

Normally black for ground and red for 3.3v but is there a colour standard for output?

Thanks

As a recent convert from marlin, there are a few plugins/features that I have used previously that I think would be a great addition to the duet ecosystem.

• Exclude Region
  print multiple objects say 3 for this example, if one lifts from the bed during print you simply select that object and exclude, the print continues but skips the g code for the excluded object allowing the other 2 objects to still be printed.

• Automatic Shutdown:
  Enable automatic system shutdown after finishing a print job, duet turns off but power remains on.

• Printer Statistics
  Statistics of your 3D Printer, Number of success / fails / cancels / errors

Been a while since Feb and they appear to be out of stock, any idea on restock or if any re-seller still sell (most dont seam to now) or an alternative solution? or is this no longer available as if I'm not mistaken there is a new one in development?
https://www.duet3d.com/laserfilamentmonitor

@dc42 I had the heat-sink cooling fan always on and the extruder fan wasn't working due to bad wiring (negative had come loose from connector)

I've replaced the wiring and connected the extruder fan to fan 0, working great now.

Thanks for the tip, Ill move the heat sink fan over to fan 1

also feel free to move this thread if possible I seam to have posted it in the wrong section, meant to post in "Firmware installation"

You got me thinking so checked back at the setup, first noob mistake made i posted config.json not config.g will correct above and indeed the z value was incorrect. testing now and will update.

Update: Yes the Z layers are now looking much improved will allow the print to finish and look to diagnose from there. I've also set the motor currents again and the combination seams to have resolved both issues.

One issue I can see now I'm going further into the print is the extruder cooling fan isn't working at the moment.

Oops sorry I believe I set the paste bin private by accident

Hi Everyone

After using the Ender 3 (Cartesian) and upgrading to use full E3D hot end/ BL Touch/ Bond-tech extruder in marlin, I decided it was time to join the 32 bit movement and purchased myself a Duet WiFi and PT100 This will be my last upgrade till the E3D tool-changer build becomes available (will use this motion system and tool changers in future)

As part of the Duet WiFi wiring process I extended my cables to reach inside a IKEA lack case I've built. Wiring went smoothly and also initialising network on the Duet was a smooth and simple procedure.

Now I've come to the difficult bit, setting up the RepRap Firmware on the Duet, after reading through the marlin setup I had I filled in the config tool and ended up with this final config. https://pastebin.com/6TycU2B4

Unfortunately I'm having a few issues which I feel has to be down to Firmware / Slicer settings.

Issues:

• I can home all which works including the BL Touch probing, However as soon as i print an object the head crashes into the bed before starting the print. RESOLVED

• The first layer prints but then the following layers are all quite separated its like the z axes moves to much for each layer RESOLVED

• Cooling Fan not working RESOLVED

Ender 3 Cura Slicer Start G-code
M104 S{material_print_temperature_layer_0} ; Set Extruder temperature
M140 S{material_bed_temperature_layer_0} ; Set Heat Bed temperature
M190 S{material_bed_temperature_layer_0} ; Wait for Heat Bed temperature
M109 S{material_print_temperature_layer_0} ; Wait for Extruder temperature
G28 ; Home all axes
G92 E0 ; Reset Extruder
G1 Z5.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed

Any suggestions on what could cause these symptoms?

I've managed to resolve the issue, Incase anyone else comes across this thread in future.

When selecting "Sensor Channel" in the reprap firmware, I mistakenly put PT100 on E0 input, Changing to MAX31856 on CS1 resolved my issue.

Hi All

I've recently purchased the Duet WiFi with the 2 pin PT 100 sensor and daughter-board.

After configuring my software through the reprap configurator. I've been able to home the axis and test the heated bed. However the pt100 just reads a constant 2000C.

I've found this post which seams to be the same issue.
https://forum.duet3d.com/topic/1292/pt-100-temperature-constantly-at-2000-degrees-after-failure/19

Following what was posted there I can see that my PT 100 does indeed have a 100+ ohm resistance when disconnected or connected.

M305 P1 X0 followed by M305 P1 X200, works fine so it can communicate with the chip on the daughter board,

Same when run for 201, I've also verified the error reporting is working by trying a channel I don't have such as 202 or 203. and sure enough I get the error.

Any idea's on next steps?