Topics created by Jacotheron

I swapped the PT100 channels and now it is reading slightly higher than the thermistor for ambient, but that is fine. I was able to perform a PID tune and it is quick like it should be.

Hi @dc42 I have no M80/M81 in my slicer, as usually the printer should remain on after a print is done - I slice multiples to schedule them one after another and usually don't know it is the last one unless until it already started to print (which is why I had it in the sleep.g file, but removed it when I started experiencing shutdowns).

I don't have thermostatic heaters, and thus don't defer shutdown with it.

The only 2 places where the M81 is active is inside my Shutdown macro (which asks the user if it should shut down), or inside my Emergency stop trigger (trigger2.g). This macro homes in X and Y (which is what happened on the first failure, but not on the second failure).

I am going to try running it without the emergency stop enabled (maybe there is a loose contact which may only sometimes disconnect).

@jacotheron I am not up to speed with it either. I will look into it once i get a version working.

@jacotheron said in IR Z Probe not very repeatable, nozzle crashed again:

An unrelated thing that was bugging me (not very important) is due to my starting G-code, the first 10 layers are seen as the first layer in the interfaces (and then layers 2-10 is completed in 0 seconds). Any way to tell the firmware where the first layer is starting, so that it does not estimate so high Time Left?
The part in my starting G-code that cause this is a line where I extrude a bunch of filament while moving slowly in the Y direction, and being 1.5mm above the bed. This is to prime my nozzle, and in stead of putting it all down at the origin (like some printers/slicers do with factory settings), this leaves a simple fat line, which also clears the outside of the nozzle.
Since I use Simplify3D, the first layer is marked with "; layer 1, Z = 0.150" -> I think if it finds anything like this, it should be the a good hook to start layer counting?

Please monitor this thread https://forum.duet3d.com/topic/5288/empty-layers-causing-incorrect-layer-count/8 as your issue sounds similar and that one is already flagged for investigation.

I found it: while looking through the code to paste, I checked the homey.g file, and noticed that for some reason, when moving in the Y direction, it is not negative the maximum. So it was like Kezat said, it homed backwards and was inverted.

Undoing the invert fixed the issue.

Thank you for the help.
When starting this thread I knew it was something small and simple that just did not want to work, but it is getting late here.

At 1.36A you are unlikely to need any cooling, unless your bed heater draws close to the 18A maximum for the Duet or the Duet is mounted in a very confined space with no natural convection. If you do need cooling, best is a fan that blows air over both sides of the board, especially the back and in the vicinity of the stepper drivers. Stick-on heatsinks are not very effective because the plastic tops of the driver chips do not conduct heat well. Modern SMD chips are designed to be cooled through the PCB instead.

It's normal for the WiFi module to run a little warm.

Hi, thank you for the answers, they are exactly what I needed to know.

I only found them now, since I did not subscribe to the thread. Now set my settings to auto subscribe when I start one.

Hi

Have a look at this wiki page
https://duet3d.com/wiki/Setting_up_to_resume_a_print_after_a_power_failure_or_planned_power_down

The Duet has the capacity to pause a print when the VIN drops below a set level, save the state and then that state can be used to resume.

Cheers

Tony