@dr_ju_ju said in How should the firmware respond to a heater fault?:

My take on it, would be that any heater fault detected, should imediately re-set the printer thereby disabling all sources of heat generation i.e. bed & heater cartriges and motors.

If a mosfet fails open (e.g. heater on) then a controller reset will not prevent heating - what you ideally want is a digital IO to a kill switch, cutting the mains power.

Thanks for the information. I'll try this at home later this week.

Yes, you can use the Windows formatting tool.

Does https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M585_Probe_Tool do what you want?

I would also probably use this if it was available. Another thing to add to this is a secondary beep or alarm as a reminder that the heat is still on after a user set time or something.

@deckingman

Yes, I'm actually reading it all the time. I get confused often, since the letters mean different things on different commands.

Ah, had not found the one linked off that page which interpolates the 25C result. Thanks!

@t3p3tony said in Steppers with Brakes:

releasing all the breaks at once

Yes releasing all the breaks at once will be good.

But I'm afraid for example, when idle, steepers may off by timeout. Or, you might not notice that the steppers' shutdown command will be added by the slicer.

Therefore it will be fine if this option will be in the firmware!

ok thank you for the confirmation

cheers

true, but wouldn't that also require a separate M584 call everytime I want to jog a different axis?

right now I'm using a workflow like

M584 ... (set up all four pairs with overlapping drive assignments) G0 FRONT_PAIR G0 RIGHT_PAIR G0 REAR_PAIR M584 ... (restore drive mapping for normal operation) <normal operation>

If I understand correctly, your suggestion would require to change this to:

M584 ... (set up mapping for FRONT_PAIR movement) G0 FRONT_PAIR M584 ... (set up mapping for RIGHT_PAIR movement) G0 RIGHT_PAIR M584 ... (set up mapping for REAR_PAIR movement) G0 REAR_PAIR M584 ... (restore drive mapping for normal operation) <normal operation>

Added to the firmware wishlist.

@T3P3Tony:

Hi Ian, thanks for the suggestion. I guess this should buffer the files to the local SD card storage.

Hi Tony,

I'll leave the practical implementation (if there is one) up to you experts. I stream HD videos and stuff from a single server, concurrently to a variety of devices but what happens inside all these various boxes is largely a mystery to me 🙂

@dc42:

RepRapFirmware was written originally for 3D printing applications, so we are still learning about how CNC controllers are expected to behave. Are you saying that the F parameter should only apply to G1 moves, and G0 moves should always execute at the machine limits set in M203?

Yes typically G0 commands run at the CNC machine max feed rates. There is usually a switch that lets you choose to run at 100% (max) 50%, 25%, and the linear feed rate which is then controlled by the feed overide switch to drop the feed rate even slower.

I can see the issue when using the Duet for a CNC mill because almost all cam systems use G0 (rapid moves) when not actually machining to shorten run times. For example when drilling holes, you jump from say one hole to another you want the move as fast as possible.

Slicer software uses G1's set to yourt "travel" feed rate so the moves between printed parts is fast.

You just have to manually change the G0's to G1's.

yes! Thank you!

+1 for this I've brought this up before.

@Agniusm:

Would it be possible to have last print time next to a file in G-Gode files section. It would be good for tuning speed and for people printing same parts over and over. Also stored somewhere on SD rather than eeprom

One thing I have been considering is that when a file is printed of simulated, a comment giving the print time could be appended to that file. RRF and DWC would be able to extract that information. I'd probably make this optional, because some users might not want the Duet to modify their GCode files.

Try touching the buttons with your fingernail instead of with the pad of your finger.