New RepRapFirmware 1.09x-dc42

I have released version 1.09x-beta3 1.09x-dc42 of my fork of RepRapFirmware at (edited) [github.com]. As usual, follow the link, then press Raw to download it. It's a beta because this release contains major changes, so although it has passed my initial testing, it is more likely than usual to contain bugs. The main changes in this release are:

* New build system to make it easier for developers to set up the build system and to support a different hardware abstraction layer for the next-generation Duet board. The Arduino plugin for Eclipse is no longer required and the Eclipse project is much more portable. A separate hardware support project (CoreDuet) replaces the Arduino core.

* Over-the-web firmware updates are supported. A very big thank-you to chrishamm for implementing this.

* Network changes to improve connection stability. Thanks again to chrishamm.

* Web interface in SD card image updated to DWC 1.10 (thanks chrishamm)

* Print monitor improvements and bug fixes, mostly by chrishamm

* Support for an optional external stepper driver support module, primarily for the next-generation Duet.

* Implemented M143 (set temperature limit)

* Implemented M350 (set microstepping - when supported by the external driver module, because the Duet does not support variable microstepping using the on-board drivers)

* Reduced the number of places where the code assumes there are exactly 3 axes, to make it easier for developers to add additional axes

* Bug fixes:

- When there is a heater fault, display the correct error message
- Extrusion was often prevented if extruders and heaters were shared between multiple tools (e.g. tool 127) unless cold extrusion prevention was disabled
- Following a temperature measurement fault, extrusion could be prevented without a warning message being displayed
- When a corrupted input line with a failed checksum was received, a spurious error message was sometimes generated

Please feed back your experiences (good or bad) with this this release to me.

Edited 2 time(s). Last edit at 03/13/2016 09:21AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

David,

is there something changed in autocal routine in the 1.09x version?

After autocal my head is moving in waves over the bed. Same in chris version.
Back to 1.09k (my reference version) everything is working fine.

Quote
critical_limit
David,

is there something changed in autocal routine in the 1.09x version?

After autocal my head is moving in waves over the bed. Same in chris version.
Back to 1.09k (my reference version) everything is working fine.

I presume you mean auto delta calibration. There have been on intentional changes in that area. It is working OK on my delta. Please try the following:

1. Create a file checkbed.g, the same as bed.g except use S-1 on the last G30 command instead of S6 (or whatever other value you are using).

2. Reset the machine and home it.

3. Run M665 and M666 with no parameters, to print the existing delta parameters.

4. Run checkbed.g.

5. Run G32.

6. Run M665 and M666 again.

7. Check that you still have the problem.

8. Post the output from steps 3-6 displayed in the GCode Console or in Pronterface here.

PS - also please attach your config.g and bed.g files.

Edited 2 time(s). Last edit at 03/12/2016 08:30AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Thanx for your advice,

actually I´m back to 1.09k for taking a look at the Layershift problem (in another Thread).

But what I can say is, that with 1.09k my first Layer is printing like before, but in 1.09x first layer the nozzle is higher than in 1.09k. Filamnet is not sticking anymore at some areas of the bed.
After the actual running 24h print I will report M666 and M665 printouts as well as the bedreport with s-1.

other thing is, that with 1.09k my Layerhight is shown correctly (0,2mm / 0,05mm) but with versions after 1.09k it is shown 1.2mm / 0,05mm every time.

Quote
critical_limit
other thing is, that with 1.09k my Layerhight is shown correctly (0,2mm / 0,05mm) but with versions after 1.09k it is shown 1.2mm / 0,05mm every time.

Can you post your gcode file, or put it on Dropbox or somewhere else where I can get it?

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

PS - how much higher is the nozzle in 1.09x than 1.09k? There was a bug in the auto calibration firmware that caused the homed height to be set slightly incorrectly under some conditions, and I think I fixed this sometime after 1.09k. So if you calibrated your G31 probe height to compensate for this bug, that might explain the difference.

You can see the effect of this bug by running G32 and then the checkbed file. The mean error reported by checkbed should be very close to zero, but in firmware versions with the bug it wasn't so close.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
dc42

Quote
critical_limit
other thing is, that with 1.09k my Layerhight is shown correctly (0,2mm / 0,05mm) but with versions after 1.09k it is shown 1.2mm / 0,05mm every time.

Can you post your gcode file, or put it on Dropbox or somewhere else where I can get it?

No special gcode file. It is on every file. Using S3D as slicer.

Hi David,

here are the results:

with 1.09k:

M665
Diagonal 339.00, delta radius 179.66, homed height 385.16, bed radius 140.0, X 0.15°, Y -0.22°, Z 0.00°

M666
Endstop adjustments X-0.07 Y-0.08 Z0.15

M98 P/macros/Cal Report only
Bed probe heights: -0.039 -0.055 0.030 -0.074 0.064 0.010 0.046 -0.021 -0.021 -0.061 -0.004 -0.011 0.064, mean -0.006, deviation from mean 0.044

G32

M665
Diagonal 339.00, delta radius 179.66, homed height 385.16, bed radius 140.0, X 0.15°, Y -0.22°, Z 0.00°

M666
Endstop adjustments X-0.07 Y-0.08 Z0.15

with 1.09x:

M665
Diagonal 339.00, delta radius 179.52, homed height 384.92, bed radius 140.0, X 0.13°, Y -0.09°, Z 0.00°

M666
Endstop adjustments X-0.18 Y-0.10 Z0.28

M98 P/macros/Cal Report only
Bed probe heights: -0.001 -0.044 0.049 -0.012 0.068 -0.013 0.036 -0.037 -0.014 -0.065 -0.010 -0.026 0.102, mean 0.003, deviation from mean 0.046

G32

M665
Diagonal 339.00, delta radius 179.52, homed height 384.91, bed radius 140.0, X 0.11°, Y -0.10°, Z 0.00°

M666
Endstop adjustments X-0.20 Y-0.10 Z0.31


I see no big difference. seems all normal to me.
With 1.09x I have to lower the nozzle around 0.08-0.12mm,

But with 1.09x the Layershift is back and it seems that nozzle is traveling not in a plane. Filament is not sticking in some areas where other areas are squished.

I will try to use the h-parameter in G30 and look how it goes...

Edited 1 time(s). Last edit at 03/12/2016 03:25PM by critical_limit.

Quote
critical_limit

Quote
dc42

Quote
critical_limit
other thing is, that with 1.09k my Layerhight is shown correctly (0,2mm / 0,05mm) but with versions after 1.09k it is shown 1.2mm / 0,05mm every time.

Can you post your gcode file, or put it on Dropbox or somewhere else where I can get it?

No special gcode file. It is on every file. Using S3D as slicer.

I still need a gcode file that demonstrates this problem. I use S3D too, but the layer heights are reported correctly for me.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
critical_limit
But with 1.09x the Layershift is back and it seems that nozzle is traveling not in a plane.

When you say layer shift, do you mean different layers are not perfectly aligned, and that 1.09x shows this problem worse than 1.09k? Some photos would help.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

see here:

http://forums.reprap.org/read.php?13,631023,638740#msg-638740

picture is in the first post.

We discussed it already. It may be due to Bed is heated via the Duet. My 230V Silicone-Pad and the SSR are on the way....

Good news!

After flashing back and forth between 1.09k and 1.09x I cleaned my nozzle and hit my miniIRboard.

after that "hit" my G31 changed from
G31 X0 Y0 Z0.74 P500
to
G31 X0 Y0 Z1.12 P500

Now the z-parameter is above 1 and everything seems to work.
Layerheight is shown correctly in the webinterface and nozzle is travelling in a plane. Normal ops now.
Is it possible there is something in the code where z-parameter is under 1 it is not doing correct calculations?
Or maybe my mini IR Board was faulty and after the hit it was going back to normal??

hm, strange.

but actually all is working fine again.
Started my 24h print again and will see what happens to the Layer alignment.....

Edited 1 time(s). Last edit at 03/12/2016 03:46PM by critical_limit.

If the reported layer height is affected by the Z probe trigger height, then my guess is that your start gcode includes a G32 or G30 command, and Chrishamm's new print monitor code is assuming that the first layer has started when it sees the nozzle at a height below 1mm or so. I'll check if this is the case tomorrow.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

PS - I still need to see the start of your gcode file to properly diagnose this, up to the point at which it starts printing the first layer.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hi David,

thanx for your replies. Everthing is normal in my opinion. Can´t imagine why the layerhight was shown as 1,2mm instead of 0,2mm.
But as writen before, after the z-parameter in G31 was going above 1mm, all going back to normal.

If I have time tomorrow I will crosscheck and maybe bend the diode on the IRBoard that it will triger below 1mm. But have to go back to work again on monday for another 14 days.
So maybe reporting will take some time....

Here is the gcode of an example file:

; G-Code generated by Simplify3D(R) Version 3.0.2
; März 12, 2016 at 1:05:27 PM
; Settings Summary
; processName,Process1
; applyToModels,Testprint
; profileName,ABS (modified)
; profileVersion,2016-02-25 08:59:59
; baseProfile,Default (modified)
; printMaterial,
; printQuality,
; printExtruders,
; extruderName,Primary Extruder
; extruderToolheadNumber,0
; extruderDiameter,0.3
; extruderAutoWidth,0
; extruderWidth,0.33
; extrusionMultiplier,1
; extruderUseRetract,1
; extruderRetractionDistance,4.5
; extruderExtraRestartDistance,0
; extruderRetractionZLift,1
; extruderRetractionSpeed,3300
; extruderUseCoasting,0
; extruderCoastingDistance,0.1
; extruderUseWipe,1
; extruderWipeDistance,3
; primaryExtruder,0
; layerHeight,0.05
; topSolidLayers,8
; bottomSolidLayers,5
; perimeterOutlines,4
; printPerimetersInsideOut,1
; startPointOption,2
; startPointOriginX,0
; startPointOriginY,0
; startPointOriginZ,50
; sequentialIslands,1
; spiralVaseMode,0
; firstLayerHeightPercentage,400
; firstLayerWidthPercentage,100
; firstLayerUnderspeed,0.6
; useRaft,0
; raftExtruder,0
; raftLayers,3
; raftOffset,3
; raftSeparationDistance,0.14
; raftInfill,85
; disableRaftBaseLayers,0
; useSkirt,1
; skirtExtruder,0
; skirtLayers,1
; skirtOutlines,20
; skirtOffset,0
; usePrimePillar,0
; primePillarExtruder,999
; primePillarWidth,12
; primePillarLocation,7
; primePillarSpeedMultiplier,1
; useOozeShield,0
; oozeShieldExtruder,999
; oozeShieldOffset,2
; oozeShieldOutlines,1
; oozeShieldSidewallShape,1
; oozeShieldSidewallAngle,30
; oozeShieldSpeedMultiplier,1
; infillExtruder,0
; internalInfillPattern,Full Honeycomb
; externalInfillPattern,Rectilinear
; infillPercentage,0
; outlineOverlapPercentage,21
; infillExtrusionWidthPercentage,100
; minInfillLength,0.66
; infillLayerInterval,1
; infillAngles,0,120,-120
; overlapInfillAngles,0
; generateSupport,0
; supportExtruder,0
; supportInfillPercentage,30
; supportExtraInflation,0
; denseSupportLayers,0
; denseSupportInfillPercentage,30
; supportLayerInterval,1
; supportHorizontalPartOffset,0.25
; supportUpperSeparationLayers,1
; supportLowerSeparationLayers,1
; supportType,0
; supportGridSpacing,3
; maxOverhangAngle,45
; supportAngles,0
; temperatureName,Primary Extruder,Bed
; temperatureNumber,0,1
; temperatureSetpointCount,1,1
; temperatureSetpointLayers,1,1
; temperatureSetpointTemperatures,245,85
; temperatureStabilizeAtStartup,0,0
; temperatureHeatedBed,0,1
; temperatureRelayBetweenLayers,0,0
; temperatureRelayBetweenLoops,0,0
; fanLayers,1,10
; fanSpeeds,0,25
; blipFanToFullPower,1
; adjustSpeedForCooling,1
; minSpeedLayerTime,15
; minCoolingSpeedSlowdown,75
; increaseFanForCooling,1
; minFanLayerTime,15
; maxCoolingFanSpeed,50
; increaseFanForBridging,1
; bridgingFanSpeed,100
; use5D,1
; relativeEdistances,1
; allowEaxisZeroing,0
; independentExtruderAxes,0
; includeM10123,0
; stickySupport,1
; applyToolheadOffsets,1
; gcodeXoffset,0
; gcodeYoffset,0
; gcodeZoffset,0
; overrideMachineDefinition,1
; machineTypeOverride,1
; strokeXoverride,280
; strokeYoverride,280
; strokeZoverride,380
; originOffsetXoverride,140
; originOffsetYoverride,140
; originOffsetZoverride,0
; homeXdirOverride,0
; homeYdirOverride,0
; homeZdirOverride,1
; flipXoverride,1
; flipYoverride,-1
; flipZoverride,1
; toolheadOffsets,0,0|0,0|0,0|0,0|0,0|0,0
; overrideFirmwareConfiguration,0
; firmwareTypeOverride,RepRap (Marlin/Repetier/Sprinter)
; GPXconfigOverride,r2
; baudRateOverride,250000
; overridePrinterModels,0
; printerModelsOverride
; startingGcode,G21 ; set units to millimeters,M83 ; use relative distances for extrusion
; layerChangeGcode,
; retractionGcode,
; toolChangeGcode,
; endingGcode,G28,M18 ; disable motors,M104 S0 T0 ; turn off extruder T0,M140 S0
; createX3G,0
; celebration,0
; celebrationSong,Random Song
; createMB5G,0
; postProcessing,
; defaultSpeed,1200
; outlineUnderspeed,1
; solidInfillUnderspeed,1
; supportUnderspeed,1
; rapidXYspeed,18000
; rapidZspeed,18000
; minBridgingArea,5
; bridgingExtraInflation,1
; bridgingExtrusionMultiplier,1.5
; bridgingSpeedMultiplier,1.25
; filamentDiameter,1.75
; filamentPricePerKg,39
; filamentDensity,1.2
; useMinPrintHeight,0
; minPrintHeight,0
; useMaxPrintHeight,0
; maxPrintHeight,65
; useDiaphragm,0
; diaphragmLayerInterval,20
; robustSlicing,1
; mergeAllIntoSolid,0
; onlyRetractWhenCrossingOutline,0
; retractBetweenLayers,0
; useRetractionMinTravel,1
; retractionMinTravel,1.5
; retractWhileWiping,0
; onlyWipeOutlines,1
; avoidCrossingOutline,0
; maxMovementDetourFactor,3
; toolChangeRetractionDistance,15
; toolChangeExtraRestartDistance,-0.5
; toolChangeRetractionSpeed,2400
; allowThinWallGapFill,0
; thinWallAllowedOverlapPercentage,22
; horizontalSizeCompensation,0
G90
M83
M106 S0
M140 S85
M104 S245 T0
G21 ; set units to millimeters
M83 ; use relative distances for extrusion
G1 E-4.5000 F3300
G1 Z1.200 F18000
; layer 1, Z = 0.2
T0
; tool H0.200 W0.330
; skirt
G1 X-7.804 Y-0.001 F18000
G1 Z0.200 F18000
G1 E4.5000 F990
G1 X-8.107 Y-0.962 E0.0277 F900
G1 X-8.146 Y-1.095 E0.0038
G1 X-8.486 Y-2.361 E0.0360
G1 X-8.592 Y-3.031 E0.0186
G1 X-8.666 Y-4.451 E0.0390
G1 X-8.666 Y-4.781 E0.0091
G1 X-8.595 Y-6.171 E0.0382
G1 X-8.826 Y-6.352 E0.0080
G1 X-9.769 Y-7.199 E0.0348
G1 X-9.933 Y-7.357 E0.0063
G1 X-10.643 Y-8.092 E0.0281
G1 X-10.888 Y-8.377 E0.0103
G1 X-11.659 Y-9.389 E0.0349
G1 X-12.033 Y-10.014 E0.0200
G1 X-12.518 Y-11.085 E0.0323
G1 X-12.667 Y-11.481 E0.0116
G1 X-12.946 Y-12.402 E0.0264
G1 X-13.003 Y-12.708 E0.0085
G1 X-13.020 Y-12.715 E0.0005
G1 X-13.899 Y-13.098 E0.0263
G1 X-14.073 Y-13.180 E0.0053
G1 X-14.895 Y-13.599 E0.0253
G1 X-15.056 Y-13.687 E0.0050
G1 X-16.151 Y-14.326 E0.0348
G1 X-17.412 Y-14.981 E0.0390
G1 X-17.752 Y-15.185 E0.0109
G1 X-18.586 Y-15.759 E0.0278
G1 X-18.997 Y-16.094 E0.0146
G1 X-19.896 Y-16.961 E0.0342
G1 X-20.232 Y-17.340 E0.0139
G1 X-20.898 Y-18.224 E0.0304
G1 X-21.261 Y-18.834 E0.0195
G1 X-21.728 Y-19.866 E0.0311
G1 X-21.951 Y-20.556 E0.0199
G1 X-22.150 Y-21.534 E0.0274

Thanks for that. I see that you don't have a G32 or G30 command in there. What was the last thing you did before printing the file, when you have the problem - was it by any chance a G30?

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

I have now released 1.09x-dc42 (i.e. it is no longer a beta). This contains two bug fixes since beta3. One caused the Z probe and temperature readings to be inaccurate on Duet 0.8.5 boards, the other is to fix a network reliability issue.

If you are using 1.09x-beta3, please upgrade. You can do this on the Settings tab of the web interface by first uploading file iap.bin (if you haven't uploaded it before), then uploading RepRapFirmware-1.09x-dc42.bin. If the web interface doesn't prompt you to install the new firmware, send M997 to do that.

Edited 1 time(s). Last edit at 03/13/2016 09:22AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Which version of the web control should we use with this update?

Quote
dc42
I have now released 1.09x-dc42 (i.e. it is no longer a beta). This contains two bug fixes since beta3. One caused the Z probe and temperature readings to be inaccurate on Duet 0.8.5 boards, the other is to fix a network reliability issue.

If you are using 1.09x-beta3, please upgrade. You can do this on the Settings tab of the web interface by first uploading file iap.bin (if you haven't uploaded it before), then uploading RepRapFirmware-1.09x-dc42.bin. If the web interface doesn't prompt you to install the new firmware, send M997 to do that.

David, not found the Duet IAP on your Github, I assume this is what is issued by Chrishamm here ?:
[github.com]

Quote
dc42
Thanks for that. I see that you don't have a G32 or G30 command in there. What was the last thing you did before printing the file, when you have the problem - was it by any chance a G30?

Yes, before every print I make a auto cal with s6.
This is my makro for that:

M561 ; clear any bed transform, otherwise homing may be at the wrong height
G31 X0 Y0 ; don't want any probe offset for this
G28 ; home the printer


G1 F3000
; Probe the bed and do 6- or 7-factor auto calibration
G30 P0 X0.00 Y120.00 Z-99999 H0
G30 P1 X121.24 Y50.00 Z-99999 H0
G30 P2 X112.41 Y-83.45 Z-99999 H0
G30 P3 X0.00 Y-140.00 Z-99999 H0
G30 P4 X-112.41 Y-83.45 Z-99999 H0
G30 P5 X-121.24 Y50.00 Z-99999 H0
G30 P6 X0.00 Y50.00 Z-99999 H0
G30 P7 X60.62 Y15.00 Z-99999 H0
G30 P8 X51.84 Y-47.04 Z-99999 H0
G30 P9 X0.00 Y-70.00 Z-99999 H0
G30 P10 X-51.84 Y-47.04 Z-99999 H0
G30 P11 X-60.62 Y15.00 Z-99999 H0
G30 P12 X0 Y0 Z-99999 S6

G1 X0 Y-140 Z350 F3000

Sometimes I comment the last G1 out, sometimes I make a G28 after that. But in any cases there are no changes in the behavior.

Now I´m 18h in my 24h h print. Layeralignment is still bad. I printed same Testfile now for 4 times. Anytime the layers are shifting at different places. But not to right or left, not to back and forth. Seems some layers are smaller or bigger in complete diameter. And it´s not only one or to, I´m talking about 50 layers.
Or 80 Layers. Can´t find any pattern.

Big hope it is the psu. Waiting for my SSR and 230V silicone heater will show if it is a matter of voltagedrops/peaks. I don´t think so, but we will see....

Quote
WZ9V
Which version of the web control should we use with this update?

I recommend version 1.10, or the forthcoming 1.11.

Quote
PRZ
David, not found the Duet IAP on your Github, I assume this is what is issued by Chrishamm here ?:
[github.com]

Yes. I have put copies of it in all SD-Image/sys- folders in my repo.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

I updated the wiki page 'Duet Firmware update' to take into account the in application update :
[reprap.org]

Is there a way to set the name that appears in mdns? I'd like to be able to remove the MAC address from the name that appears via bonjour if possible.

Edited 1 time(s). Last edit at 03/14/2016 03:32PM by jmg123.

The mdns module creates the name from the printer name and the MAC address. I guess the MAC address is included to guarantee that if you have more than one printer on the network, they have unique names. You could rebuild the firmware to avoid appending the MAC address, in file mdns_responder.c.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Working well here, both the beta and then the update via web interface (so awesome, thanks to all who worked to get that feature in there). So far my issues with 1.09r with file uploads have been solved. I should say that I've only uploaded a few files to print thus far, but one was a 47 meg, which would likely have caused issue before. Uploading the firmware update was painless as well.

Quote
dc42
The mdns module creates the name from the printer name and the MAC address. I guess the MAC address is included to guarantee that if you have more than one printer on the network, they have unique names. You could rebuild the firmware to avoid appending the MAC address, in file mdns_responder.c.

Thanks, I'll give it a go

Quote
jmg123
Is there a way to set the name that appears in mdns? I'd like to be able to remove the MAC address from the name that appears via bonjour if possible.

At the moment the mDNS responder announces three hostnames. I tried to remove two of them (the ones that contain parts of the MAC address), but I found this had some bad side effects so I reverted to the original code.

Thanks for the mDNS support.

Hey David,
I have been reading elsewhere you were talking about implementing a jammed filament sensor support in Duet FW. I could figure out the sensor myself, but we all would need a FW support to pause the print if the signal comes in...
I guess now I can just e-reset the printer to stop it from printing, but it would be a really nice thing be to able to pause the print until the 'filament problem' is solved.
Also, perhaps it has been addressed already - but I had issues with apparently a bad SD card, so the Duet reported the error in GCode file, stopped the print, but left the nozzle at place and and still heated to 230deg... Until I found it like this next morning. Would be nice to disable the heaters in case like this.

Anyhow, thanks for your work!

Firmware support for filament sensor would be great, we are working on an integrated, firmware independent sensor working just as an endstop.
It's based on optical encoder, when a wheel stops to turn it triggers a timer, after timer passes a given amount of seconds it sets HIGH (5V) on output pin.
If a wheel should start turning again before the time set passes, the timer zeroes and printing goes on.

If only it would be possible to connect it to duet and set a copy of pause.g macro to run when it's triggered.

At the moment we have a working prototype, waiting for tests.
I wish to use it with duet and marlin for starters.

We run a small printfarm and this kind of sensor is practically a must have.
Even if the printers are perfect once in a while there comes a blob on the filament