@Exerqtor that looks about right - although you need to test to make sure.

you can just use the spacing setting, rather than the number of points, in you M557 command, since those values come from the spacings reported in the OM.

@T3P3Tony Yeah ofc, sorry I should have done that myself once we discovered it wasn't an isolated thing 🤦‍♂️

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Have you already posted your start.g in this thread? If not, please do so.

Here you go:

; start.g v1.3 ; Called whenever you start a print, run before slicer gcode at start of print echo "start.g start" G21 ; Set units to millimeters G90 ; Use absolute coordinates M83 ; Use relative distances for extrusion M140 S65 ; Set bed temperature to 65°C if exists(global.sb_leds) set global.sb_leds = "heating" ; StealthBurner LED status T0 ; Select Tool 0 M291 P"Print started, preheating." T10 ; Info message G4 S1 ; Wait 1 second M220 S100 ; Reset speed factor M221 S100 ; Reset extrusion factor M290 R0 S0 ; Reset baby stepping M107 ; Turn off the part cooling fan if heat.heaters[0].current < 65 M140 S65 ; Set bed temperature to 65°C M116 H0 ; Wait for the bed to reach its temperature echo "start.g end

@jay_s_uk very clever! thank you!

@dc42 I consulted with the odrive developers, and they said that the step pulse interval was 2 microseconds, and all other values could be zero, So my values now are T0:2:0:0 I tested this witha couple of test prints, and it seems to be working good now.

@t3p3tony I've already tried that, it copies the file, resets and it's back to square one, can't connect to it 😞

I'm a bit confused. Are you using a Pi? If so you would be updating everything with sudo apt update and sudo apt upgrade. If it's failing to update the Duet because it's on a beta firmware you can manually update the Duet over USB to get back in sync.

https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware#Section_Updating_firmware_via_USB