Hi to everyone who is beta testing this sensor. I built upon the geometry for the housing, and modified it so that the PTFE tube can't be pulled out , and also it is split-able so that you can remove the remnant filament after the tail end has been fed past the hob gear.

Video explaining it here: https://youtu.be/RmZ7aJYvWLc?t=7m40s

.stl file here: https://www.myminifactory.com/object/3d-print-splitable-duet-laser-filament-bracket-for-bowden-tube-printers-73781

@veti @dc42 @deckingman

Thank you all for your input and help! Here is my conclusion for anyone else finding this thread and needing an answer:

The following settings using veti's method work:
M305 P0 T97700 B4619 C9.743561e-8 R2200
M305 P1 T97700 B4619 C9.743561e-8 R2200

The following settings using dc42's numbers also work:
M305 P0 T98801 B4185 R2200
M305 P1 T98801 B4185 R2200

I'm guessing that anyone using run of the mill thermistors from China (purchased on ebay or aliexpress, etc) with a Duet Maestro board will find these settings to be functional. I notice little difference between the settings from dc42 and the ones from veti. They vary from each other by only about 2°C at the high end (ABS printing temperature), and they completely agreee/match at room temperature. I'm going to go with dc42's numbers as he explained he was correcting for a rounding error, so potentially more accuracy there. All of this is assuming that the original numbers from the Marlin table were accurate.

Disclaimer: I'm measuring the bed temperature using an IR thermometer which gives varying readings +/- 1.5°C. The accuracy of the Thermometer is also questionable (+/- 2.5°C?). I have no way of accurately measuring the temperature of the hotend. To gauge this I'm manually forcing ABS Filament through the nozzle. While I haven't gotten my fingers calibrated recently, I am comparing the feel of this to the same filament going through my other printer which is properly calibrated for temperatures, and has the same size nozzle. Given these constraints, my conclusions are more of an art than a science.

Your start code seems overly complicated. Most worrisome to me is why are you setting your Z offset at the beginning of every print? This should be set with G31 "trigger value" in config.g.

I showed how to do it in the video here: https://youtu.be/BgkJVgFnPaE?t=21m47s

Once that is set correctly, you should be able to use a very simple start script. Mine is this:
G28 ;Home All
G29 S1 ; Load old Bed Map -- remove the S1 to build a new bed height map
G0 X0 Y0 Z5 ; Move print head to front left corner 5mm off the print surface in preparation for printing
G92 E0 ; Set the extruder to zero
G1 E8 ; prime the nozzle
G92 E0 ; Set the extruder to zero

You may find that you need a file called iap4e.bin in order to update/upgrade the firmware on your Duet2 control board. I know of at least two people who have had this problem. This file can be somewhat hard to find at the moment because it doesn't seem to be included in the newer versions of the Duet firmware. Here is a github link to an older version of the firmware which does include this file. Simply put it in your duet file system and proceed with the update:

https://github.com/dc42/RepRapFirmware/releases/tag/v1.19.2

I hope this helps.

I've succeeded in accomplishing Octolapse-Like Timelapse videos without using a raspberry pi: https://youtu.be/CwHVQ81GfXw

Total project cost was under $10

It would still be nice to be able to trigger photos based on a time interval.

@bot Actually, it's a bit of G-code that I have implemented into my slicer (simplify 3D) By inserting it at every layer change.

I will try the changes you have suggested. These appear to be very good information. Thank you.

@bot That worked thanks. Turns out that it was retracting for each layer change already so I didn't need the M83, but that was a good tip. Thanks. Here is what I ended up with:

G60 S1 ; store current locating information
G1 X267.5 F6000 ; move off the edge of the bed for print wiping
G1 R1 ; recall location information from the G60
M400 ; wait until movement is finised before proceeding

Thanks Phaedrux M400 seems to be working, but I didn't do rigorous before and after testing so I can't say if it is needed or not. At any rate the above script achieves the desired outcome.

@bearer Thank you!

As I understand it:
The PS_ON header has three wires. 5V, GND and Signal (PS_ON). The GND pin is connected to the GND rail of the Duet board. The 5V pin is an INPUT meant to accept 5v-20v from an external source. The PS_ON pin is controlled via M80 and M81 commands. When activated by an M80 command this pin will be connected to the 5V input pin next to it.

Is this correct?

Please forgive me for asking a question which should be easily testable and not require a forum post. I suspect I might have burned up this circuit, so I am trying to verify how it is supposed to work.

@Phaedrux Well, apparently the problem is not fixed in version 3.01-RC12. Bummer. Now I need to downgrade to the previous 2.05.1 version of the firmware. Bummer.

@Phaedrux The Chamber heater problem was on an older version of the firmware. 2.01 maybe. I need to get back to that project.

@Phaedrux Thanks! Helpful as always you.

maybe you'd prefer an old version of marlin?

Ha Ha. No thanks. I like the thermal runaway protection, I just don't like not being able to control what rise in temperature is determined unsafe. That's why I felt I was being Nannied. The issue as you explain it is more nuanced and I guess if it worked correctly (as it apparently does in 3.01) I wouldn't feel like I was being over protected.

-Ender 3 Pro printer with newly installed Duet2 WiFi running Reprap firmware version 3.0
-This printer was working perfectly running with a Maestro board and an older firmware version. No issues with bed heating
-When I try to heat up the bed I get the error: Heating fault on heater 0, temperature rising much more slowly than the expected 1.6°C/sec
-The bed is wired correctly with crimped ferrules going into the screw blocks, and the solder joints at the bed are flawless.
-I can get the bed up to temperature by babysitting it and manually increasing the temperature by 1° increments until the desired temp is achieved.
-The wires connecting the bed to the Duet are cool to the touch. Even when the bed is holding a temperature of 100°C

I believe that my only issue is the firmware setting that decided my bed heats too slowly. How can I change this setting, or disable it entirely. I don't like being Nannied here. I know my hardware works. The manufacturer knows it works. Why is the Duet board telling me that it is unsafe?

@bot That worked thanks. Turns out that it was retracting for each layer change already so I didn't need the M83, but that was a good tip. Thanks. Here is what I ended up with:

G60 S1 ; store current locating information
G1 X267.5 F6000 ; move off the edge of the bed for print wiping
G1 R1 ; recall location information from the G60
M400 ; wait until movement is finised before proceeding

Thanks Phaedrux M400 seems to be working, but I didn't do rigorous before and after testing so I can't say if it is needed or not. At any rate the above script achieves the desired outcome.

@bot Actually, it's a bit of G-code that I have implemented into my slicer (simplify 3D) By inserting it at every layer change.

I will try the changes you have suggested. These appear to be very good information. Thank you.

During Layer changes I want to move the print head to the far extreme of X movement. To this end, I am using a G60 S1, to save the last print location, then a G1 R1 to recall that location and move the print head back to the location. This is functioning perfectly. I'm having a problem with retraction. Specifically the re-priming of the nozzle to resume printing. As you can see in the code of my macro, the priming command is issued AFTER the "G1 R1" This should mean that the printer moves to the last print location before priming the nozzle. The machine is instead priming the nozzle before the print head has finished moving back to the saved print location. Is there a way to ensure that the Duet board will pause on a line of the G-code and not do anything else until the previous command has completed it's action?

G60 S1 ; store current locating information
G91 ; relative coordinates
G0 F2000 ; feedrate of 2000mm per min
G0 E-4 ; retract 4mm of filament
G90 ; absolute coordinates
G0 F5000 ; feedrate of 500 mm per min
G0 X267.5 ; move off the edge of the bed for print wiping
G1 R1 ; recall location information from the G60
G91 ; relative coordinates
G0 F2000 ; feedrate of 2000mm per min
G0 E4 ; prime nozzle for restarting print
G90 ; absolute coordinates

I updated from:
Firmware Version 2.03
WiFi Server Version 1.23
Web Interface Version 1.22.6

Board: Duet WiFi 1.02 or later (duetwifi102)

Following your instructions is the same as simply reuploading the new firmware .bin file. It updates the firmware without incident. After that update it still will not update configuration files such as config.g when pressing the "upload system files" button. Also, it does not restart the board for changes to take effect

I think the problem is with uploading a config.zip and having the duet unzip that file. When I unzip the files on my PC, and upload them individually it works just fine.