@Veti said in Z-Offset to low - BLTouch, Duet Wifi 2:
if you increase the offset to 0.9mm the nozzle now needs to move 0.9 mm closer to the bed when printing. thus squashing into the bed.
Okay make sense thanks. With my coreXY the head doesn't move but the bed goes up or down.
In regards of the odd deploy off the BLtouch pins during print. It just happend during an 8hrs run and it destroyed my print plus the BLtouch itself was crashed ::(
@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.
@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
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
@droftarts said in Checksum errors:
My reply about SD card corruption was in answer to @calibanorg, not you. I've edited my post to make that clear. Ideally people should start a new thread for their problem to avoid confusion, but it did sound similar. But then you weren't the OP, either.
@NAK_3D my apologize that i hijacked your post
@droftarts i will open a new post next time -> Thanks for help anyway.
@droftarts i'm using the Duet SD card socket. I guess i will replace the SD card to make sure this can be ruled out. I checked yesterday the cables and rerouted them so the noise should be less. I started the same print this morning and so far it still printing since then. Another 3h 40min to go so wish me luck i don't have an issue here.
not sure if related i just did a test print and got following error
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
@dc42 @NAK_3D this morning i started a 15hr print and it stopped in the afternoon. When i checked the M122 (see below) it did a reset and cause: power up. Also i had the checksum error (see picture below) on the screen.
It looks like i have the same issue as @NAK_3D?
@dc42 in regards of the power up cause -> is this an issue of not enough power, powerloss? shortage?
M122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet WiFi 1.02 or later Board ID: 08DGM-9T6BU-FG3S4-6JTD8-3S86Q-1BR3F Used output buffers: 3 of 24 (9 max) === RTOS === Static ram: 25680 Dynamic ram: 92748 of which 416 recycled Exception stack ram used: 320 Never used ram: 11908 Tasks: NETWORK(ready,572) HEAT(blocked,1232) MAIN(running,3752) IDLE(ready,200) Owned mutexes: === Platform === Last reset 00:27:54 ago, cause: power up Last software reset at 2019-11-17 08:04, reason: User, spinning module GCodes, available RAM 11736 bytes (slot 1) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 12.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 29.8, current 30.2, max 34.5 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2019-11-19 16:52:39 Cache data hit count 4294967295 Slowest loop: 6.04ms; fastest: 0.06ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 208.25ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address cc:50:e3:4a:dc:00 WiFi Vcc 3.34, reset reason Turned on by main processor WiFi flash size 4194304, free heap 22912 WiFi IP address 10.10.2.21 WiFi signal strength -46dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0
@Veti said in Z-Offset to low - BLTouch, Duet Wifi 2:
@calibanorg said in Z-Offset to low - BLTouch, Duet Wifi 2:
In regards of the odd deploy off the BLtouch pins during print.
i am not a big fan of the bltouch. i build this for myself https://www.thingiverse.com/thing:3303618
I build the sensor you suggested this weekend due i had all material on hand. The sensor is amazingly easy to build and it worked quite right away.
Regarding the config i only changed M558 to P5. But based on the documentation -> https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe "Mode 2" = P2 is might be more suitable?
Again thanks @Veti you saved me 50 Bugs for a new BL Touch
@Veti so i tried to repair my BLtouch and accidentally cut the electromagnetic wires 
so now it is definitely gone. 
so your suggestion comes at the right time. i think i might have all parts somewhere...
@dc42 i did the check as suggested. below the result:```
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.04 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-11-01b1
That is the final release correct?