RRF2 to RRF3 - Error: G10: Attempt to set/report offsets...

[calibanorg]

Hi There,

I upgraded recently from RRF2 to RRF3 and after conversion and some adjustments i get following error when after the pre-heating phase the printer attempt to start the the print:

Error: G10: Attempt to set/report offsets and temperatures for non-existent tool: 1
Error: G10: Attempt to set/report offsets and temperatures for non-existent tool: 2

What i'm not clear if this triggered by a wrong start.gcode or some error in the configuration.

My config.g below (btw: is it correct that the config.json (rerap config) will update the config.g file?)

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Mar 07 2021 12:30:03 GMT+0100 (Central European Standard Time)
 
; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"Caliban3d"                              ; set printer name
M669 K1                                        ; select CoreXY mode
 
; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet
 
; Drives
M569 P0 S1                                     ; physical drive 0 goes forwards
M569 P1 S0                                     ; physical drive 1 goes forwards
M569 P2 S0                                     ; physical drive 2 goes forwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M569 P4 S0
M584 X0 Y1 Z2:4 							   ;U4 E3 P3 ; Driver 0 For X, 1 for Y, Z=2:4 U=4, Extruder 3 	; Motor remapping for dual Z
;M671 X10:180:180:10 Y170:170:10:10 P0.5       ; point1 (10,290), point2 (290,290), point3 (290,10), point4 (10,10)
M671 X-25.8:245.8 Y112:112 S6                ; Define positions of Z leadscrews
M667 S1
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z400.00 E420.00            ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X1360 Y1360 Z1200 E600 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout
 
; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X190 Y180 Z160 S0                         ; set axis maxima
 
; Endstops
M574 X1 S1 P"xstop"                            ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                            ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop+e1stop"                                   ; configure Z-probe endstop for low end on Z
 
; Z-Probe
M950 S0 C"exp.heater7"                         ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X21 Y0 Z2.068                           ; set Z probe trigger value, offset and trigger height
M557 X28:195 Y0:185 S20                       ; define mesh grid
 
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                          ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.262 C406.9 D1.12 S1.00 V23.0        ; Auto Tuned 08.03.2021
M140 H0                                        ; map heated bed to heater 0
M143 H0 S120                                   ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 R2.248 C230.1 D4.97 S1.00 V23.8                             ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                   ; set temperature limit for heater 1 to 280C
 
; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.3 H-1                               ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
 
; Tools
M563 P0 D0 H1                               ; define tool 0
G10 P0 X0 Y0 Z0                           ; set tool 0 axis offsets
G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C
 
; Custom settings are not defined
 M575 P1 S1 B57600

[engikeneer]

@calibanorg The error message says that the issue is in setting the temperatures for Tool 1 and Tool 2, but your config only has a tool definition for Tool 0 (M563 P0 D0 H1 ; define tool 0).

Looking at your drive mapping, I think you only have one tool, so the error is likely in your start gcode. Maybe post that and we can help you.

RE the config.json file, this is an output from the config generator that allows you to go back to the same state to edit things and generate a new set of config/homing/bed etc files. After creating the new files (including a new config.json file), you would need to upload them to the Duet.
A quick word of warning - if you make manual edits to your config/homing/bed etc files, then these changes won't be reflected in the config.json file. In general I find using the config.json method very useful when first setting up a printer and getting your head around things, but as you start playing with more advanced things and get happier with the gcodes etc, you may have to switch to manual edits

[calibanorg]

@engikeneer thanks for the fast reply i actually did some more testing and figured that this only happens when i print -> https://www.thingiverse.com/thing:34558/files for my bed leveling issue. if do the cube -> https://www.thingiverse.com/thing:1278865 it works like a charm (besides the 1st layer issue)

(thanks for the config.json explanation!)

my start.gcode i'm using with CURA 4.8.0

; Startup Gcode
G91                      ; Relative Positioning
G1 Z-1                   ; Move Z down 1mm
G90                      ; Absolute Positioning
G28 XY                   ; Home XY
M561                     ; Clear any bed transform
G1 X79 Y100              ; Move Probe to middle of bed
G32                      ; Start 2-point probe sequence
G29 S1					 ; Load heightmap
G1 Z20.0 F6000           ; Move Z to 20
G1 X5 Y5                 ; Move Head to front left
G92 E0                   ; Zero Extruder
G1 F200 E20              ; Prime the extruder
G92 E0                   ; Zero Extruder

[engikeneer]

@calibanorg That seems odd... are you generating both gcode files from the same slicer with the same profile? Maybe open both of the sliced gcode files in notepad and see what the first 50 lines or so are (particularly looking for something with G10 P1 ... and G10 P2 ...)

[calibanorg]

@engikeneer same slicer same profile indeed. i tried another bed leveling example (https://www.thingiverse.com/thing:13053/files) and it worked. Something with the *.stl with the other one is wrong, when i sliced it with Cura it didn't show anything in the preview - which isn't normal.

I will try to fix my current bed leveling aka adhesion issue with the new test file.

Thanks for the help.