Couple of weird behaviours.



  • Okay so one thing odd that happened during delta autocalibration with the IR probe. It probed 5 points then on the 6th it didn't trigger and the nozzle just carried on descending until I cut the power. I'm using printbite and normally it reads extremely well.

    The other, occasionally it will heat the bed, autocalibrate then not wait for the hot end to heat up but start printing straight away. I can't see why as my start gcode uses M109.

    I'm running 1.15e FW.



  • @DjDemonD:

    The other, occasionally it will heat the bed, autocalibrate then not wait for the hot end to heat up but start printing straight away. I can't see why as my start gcode uses M109.

    I'm running 1.15e FW.

    Was there a heater fault? This is how the firmware "handles" heater faults: switch off the heater and then proceed. Newer firmware, I think, cancels the print; I'd like to see an emergency stop on heater fault. Heater faults can happen spuriously if your tuning isn't quite ideal.



  • @DjDemonD:

    It probed 5 points then on the 6th it didn't trigger and the nozzle just carried on descending until I cut the power.

    The same issue for me. But this happens very rarely. Maybe 4-5 times a year.


  • administrators

    If you execute M109 with no tool selected, then the firmware doesn't know which tool you want to heat, so it generates an error message and carries on. You should always select a tool before running M109 - or preferably, set the tool temperatures using G10 and then select a tool. Sadly, many slicers still tend to assume that there is only one tool and don't bother sending a tool selection command. You can normally work around this by putting the temperature setting and tool selection commands in the slicer start b gcode.



  • Thanks David will try that.



  • So if I used
    M109 S[first_layer_temperature] T0
    that would do it?


  • administrators

    Preferably use:

    G10 P0 S[first_layer_temperature]
    T0
    M116

    Or you can do the T0 first, it doesn't matter.



  • Okay so the tool selection fix above worked, thank you for that one DC.

    The other issue, the sensor not triggering and crashing the nozzle I have identified was the IR sensor getting too hot. Mine is quite close to the heater block, and despite being cocooned in kapton, and shielded by the E3d silicone cover, my fan assembly had rotated slightly meaning the IR sensor was a little too warm to function reliably. Straightened it and I'm back to normal running.



  • Little update to this, it turns out that the sensor getting hot might have contributed, but it also made a big difference in that I had the threshold set slightly too high at 536 or something similar, the sensor was not triggering properly with this setting. Now I have set it lower to 480, it always triggers perfectly every time.


  • administrators

    As stated in the fitting instructions, the G31 threshold should always be set to 500 when using the IR sensor.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.