Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
-
Hi,
There is already support to visualize the cpu temp on the "Temperature chart" under the "Extra" tab.
Maybe add the driver temperatures here too? Since the overheat protection is being done / is done, at least part of the coding is done for that. -
The driver's don't actually report their temperatures, just overheat warning and overheat error flags.
-
1,2,7,17,18
-
Hi,
There is already support to visualize the cpu temp on the "Temperature chart" under the "Extra" tab.
Maybe add the driver temperatures here too? Since the overheat protection is being done / is done, at least part of the coding is done for that.As David said, the driver chip itself does not supply the actual temperature, just alarms. However, there is a way to do it by sticking a bead thermistor to the top of the driver chip. Not only can you display the temperature but you can also use it to control a fan. I did a bit of write up on my blog explaining how to do it https://somei3deas.wordpress.com/2017/04/18/stepper-motor-and-electronics-cooling/. At the time, I had to create "dummy tools" but things have since moved on and I now use the "virtual heaters" feature which is in later firmware versions. This also allows meaningful names such as "X Driver chip" to be used.
HTH
-
Hi,
There is already support to visualize the cpu temp on the "Temperature chart" under the "Extra" tab.
Maybe add the driver temperatures here too? Since the overheat protection is being done / is done, at least part of the coding is done for that.As David said, the driver chip itself does not supply the actual temperature, just alarms. However, there is a way to do it by sticking a bead thermistor to the top of the driver chip. Not only can you display the temperature but you can also use it to control a fan. I did a bit of write up on my blog explaining how to do it https://somei3deas.wordpress.com/2017/04/18/stepper-motor-and-electronics-cooling/. At the time, I had to create "dummy tools" but things have since moved on and I now use the "virtual heaters" feature which is in later firmware versions. This also allows meaningful names such as "X Driver chip" to be used.
HTH
Thanks, it is not that crucial, I just tought that the driver ics reported the temp and the overheat warning was a software feature.
If this was the case, and we both had the ic temps and the infrastructure to report the cpu temp as well, it would have been a fun feature and one that was easily implemented. -
A nice feature for aligning hotends on IDEX printers would be a G31 hole probe routine. Where you could G31 probe X and Y in positive & negative directions (with multi touch) and then position in the center. Not sure how close the DuetWifi is to running out of resources for adding features but this would be a nice one.
One could then use a ring type gauge mounted on a piezo disk to pick up the touches. It can be done manually right now but an automatic routine would make life easier.
Any thoughts on that David?
-
A nice feature for aligning hotends on IDEX printers would be a G31 hole probe routine. Where you could G31 probe X and Y in positive & negative directions (with multi touch) and then position in the center. Not sure how close the DuetWifi is to running out of resources for adding features but this would be a nice one.
One could then use a ring type gauge mounted on a piezo disk to pick up the touches. It can be done manually right now but an automatic routine would make life easier.
Any thoughts on that David?
I'm sorry, I don't understand what you mean by a "hole probe routine".
-
I mean having a steel cylinder with a precision hole bored through it mounted on a Piezo disk. The hole is larger than the hotend nozzle.
The way the routine would work is you would jog the nozzle roughly over the center of the hole. Then drop enough of the nozzle tip in below the top of the cylinder. Enough so the cone shape would make contact with the inside edge of the cylinder if it were moved in any direction in X or Y.
Then call up a G31 S-3 (or whatever parameter you choose). The printer would then move in X+ till it reads a contact (just like a Z probe move). When stopped record position, Then move back to start point. Probe in X- until another contact is read. record position position, subtract first stop point from second stop point (X+ pos. - X- pos.) then move to the resulting position. Basically moving the the center of the 2 stops in X.
Then do the same probes in Y+ & Y-. Do the calculation for y and move to that new center point.
Repeat X probes to ensure the true center of X again.
Now if you run the same routine on the second hotend then the difference in positions between the two hotends is what would get entered in G10 X Y for the second tool.
Does that make sense?
-
18
5
6 -
Would it be possible to make the Paneldue play a tune when the print finishes? This just makes the whole experience a bit more friendly, especially when we show off the printers at maker faires etc.
-
19
17
1
2
18Thanks
-
@mitchd said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
Would it be possible to make the Paneldue play a tune when the print finishes? This just makes the whole experience a bit more friendly, especially when we show off the printers at maker faires etc.
I think it should already be possible, using a combination of M300 and G4.
-
@dc42 Implement G29 T1 tag to list the height table, this makes it possible to communicate with Bed Level Visualizer
see https://plugins.octoprint.org/plugins/bedlevelvisualizer/ for info.All Octoprint users will love this I guess.
Low priority since this exists in the DUET GUI as a workaround.
-
13
Didn't I read somewhere that it is already implemented or was it a wishlist too? (firmware not Deckingmans script) -
@dc42 This is already possible, I have the following in my end gcode -
;Play beep beep beep to show print ended.
M300 P500 S5000
G4 P400
M300 P500 S5000
G4 P400
M300 P500 S5000
G4 P400
M300 P500 S5000 -
@mitchd If you're looking for a little jingle when a print is finished and not just a beep, try this one:
; Play a triumphant tune to celebrate a successful print. M400 ; Clear queue before jingle G4 S1 M300 P250 S750 G4 P251 M300 P200 S1250 G4 P201 M300 P250 S750 G4 P251 M300 P200 S1250 G4 P201 M300 P250 S2500 G4 P251 M300 P150 S2000 G4 P151 M300 P150 S2500 G4 P151 M300 P350 S3700 G4 P351 M400
-
That is too cool
@phaedrux said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
; Play a triumphant tune to celebrate a successful print.
M400 ; Clear queue before jingle
G4 S1
M300 P250 S750
G4 P251
M300 P200 S1250
G4 P201
M300 P250 S750
G4 P251
M300 P200 S1250
G4 P201
M300 P250 S2500
G4 P251
M300 P150 S2000
G4 P151
M300 P150 S2500
G4 P151
M300 P350 S3700
G4 P351
M400 -
@jnolan72 If you like that one I have another one for printer start up and another for right before the print starts.
I've tried to program more complex tunes but the more commands you send the more likely the system is to miss a tone or stutter. The buffer can only handle so much I guess. Hence having to issue an M400 before and after. This is more noticeable at printer startup than it is say before or after a print.
; ; Startup Tune. Placed at the end of config.g ; M400 G4 S2 M300 P200 S2000 G4 P201 M300 P200 S2250 G4 P201 M300 P200 S2000 G4 P201 M300 P200 S2855 G4 P201 M300 P200 S2500 G4 P201 M300 P200 S2200 G4 P201 M300 P200 S2500 G4 P201 M300 P200 S2900 G4 P201 M300 P300 S3500 G4 S1 M400
; ; Lucky tune to start print off on the right foot. Placed in slicer start g-code. ; M300 P200 S1000 G4 P201 M300 P200 S1250 G4 P201 M300 P200 S1100 G4 P201 M300 P200 S2000 G4 P201 M300 P200 S1500 G4 P201 M300 P200 S1000 G4 P201 M300 P200 S1300 G4 P201 M300 P200 S1000 G4 P201 M300 P300 S1500 G4 S1 M400
-
1,4,5,16,17
-
Thanks guys for the beeps and tunes! My old Creatbot beeps and I was missing that on this new build.