error zoffset for bl touch and duet3 firmware 3.4 beta 7+1

massimilianoconti · 13 Jan 2022, 21:28

duet 3 v1.01

firmware 3.4 beta 7+1

24 volt

Hi I'm noticing the following inconsistency problem on BLTouch : when I start the new print the z offset does not remain costyante as per the setting done to the machine, I notice that sometimes the nozzle gets too close and triggers the extruder motor. when I reset the machine then resumes the right z offset, in short, from one print to the next z offset changes a little it seems that the firmware loads the modified values ...

Phaedrux · 13 Jan 2022, 21:35

Can you give us more info on your setup? Configs?

Have you tried the latest beta updates?

https://forum.duet3d.com/topic/26787/unofficial-rrf-3-4-0beta7-4-files/

massimilianoconti · 13 Jan 2022, 21:37

firmware 3.4 beta 7+1

; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Dec 31 2021 12:22:58 GMT+0100 (Ora standard dell’Europa centrale)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 300X Dual" ; set printer name
M955 P0 C"spi.cs3+spi.cs2"
M669 K1 ; select CoreXY mode

; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3:0.4 ; set drive mapping
M350 X128 Y128 Z128 E128:128 I1 ; configure microstepping with interpolation
M92 X640.00 Y640.00 Z5120.00 E3367.10:3367.70.31 ; set steps per mm
M566 X800.00 Y800.00 Z60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z500.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X2300.00 Y2300.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X900 Y900 Z1000 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M593 P"zvd" F70

; Axis Limits
M208 X-18 Y-5 Z0 S1 ; set axis minima
M208 X305 Y305 Z260 S0 ; set axis maxima

M671 X10:300:300:10 Y290:290:5:5 P0.5
M591 D0 P5 C"e0_stop" R40:120 E3.0 S0

; Endstops
M574 X1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io2.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" P9 H5 F500:100 T6000 A5 R0.1 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X12.5 Y-20 Z1.55 ; set Z probe trigger value, offset and trigger height
M557 X20:290 Y15:300 S25:20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
M950 H0 Q10 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"pt1000" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S400 ; set temperature limit for heater 1 to 400C
M308 S2 P"temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C

; Fans
M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H1:2 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
M563 P1 D1 H2 F1 ; define tool 0
G10 P1 X25 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

; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool
M150 X0 ; set LED type to NeoPixel and set SPI frequency to 3MHz
M150 B255 P128 S65 F0
M501

Phaedrux · 13 Jan 2022, 21:43

@massimilianoconti said in error zoffset for bl touch and duet3 firmware 3.4 beta 7+1:

M558 P9 C"^io7.in" P9

Not sure if it will make a difference but you have P9 listed twice.

Can you post your homeall and homez?

Are you using mesh compensation or auto leveling?

@massimilianoconti said in error zoffset for bl touch and duet3 firmware 3.4 beta 7+1:

the nozzle gets too close and triggers the extruder motor.

What exactly does that mean?

massimilianoconti · 13 Jan 2022, 21:49

Yes

use mesh compensation or automatic leveling

maybe it's not good P 9 repeated I don't know how it happened

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 01 2022 15:36:30 GMT+0100 (Ora standard dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-310 Y-310 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-310 ; home X axis
G1 H1 Y-310 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-310 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-310 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X15 Y35 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Phaedrux · 13 Jan 2022, 21:53

When do you run G32 or load a mesh?
Post your bed.g and the slicer start gcode as well please.
Also test with the new 3.4 beta 7+4 updates.

massimilianoconti · 13 Jan 2022, 21:54

Ok thank you. meanwhile I removed the P 9. could you give me the link to download the firmware 3.4 beta 7+4?

Thank you

start script

G28 F4000;

M150 X0 ; set LED type to NeoPixel and set SPI frequency to 3MHz
M150 R255 U255 B255 P128 S65 F0

M561 ; Clear any bed transform
G29 S1;

G1 Z0.470 F7800.000
G1 X10 Y8 Z10 F3000
G1 Z0 F500

T0
G92 E0

G1 Z0.25 F400
G1 X80 Y8 E60 F100

T1
G92 E0

G1 X140 Y8 E60 F100

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.2 on Sun Sep 26 2021 01:04:15 GMT+0200 (Ora legale dell’Europa centrale)
M561 ; clear any bed transform
G29 S2; Clear bed height map
; Probe 4-point
M401 ; Deploy probe - deployprobe.g
G30 P0 X10 Y290 Z-9999 ; Front Right
G30 P1 X300 Y290 Z-9999 ; Front Left
G30 P2 X300 Y5 Z-9999 ; Center Rear
G30 P3 X10 Y5 Z-9999 S4 ; Center Rear
M402 ; Retract Probe - retractprobe.g
M300 S715 P1500
G4 P1500
G29 S1

Phaedrux · 13 Jan 2022, 22:10

@massimilianoconti said in error zoffset for bl touch and duet3 firmware 3.4 beta 7+1:

could you give me the link to download the firmware 3.4 beta 7+4?

I did. https://forum.duet3d.com/topic/26787/unofficial-rrf-3-4-0beta7-4-files

When do you call G32 to do the leveling and loading of the mesh?

@massimilianoconti said in error zoffset for bl touch and duet3 firmware 3.4 beta 7+1:

M401 ; Deploy probe - deployprobe.g
M402 ; Retract Probe - retractprobe.g

This is not needed with the BLtouch

massimilianoconti · 13 Jan 2022, 22:13

Thank you. I think it will be uploaded. Printing is fine.anyway how do you see exactly if the mesh is loaded?

Phaedrux · 13 Jan 2022, 22:14

If you send M122 it will have a line for compensation in use. If it says mesh, it is active. If it says none, it is not.

massimilianoconti · 13 Jan 2022, 22:17

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7+1 (2021-12-22 16:03:36) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6J9DD-3S46N-TVFH8
Used output buffers: 1 of 40 (23 max)
=== RTOS ===
Static ram: 150664
Dynamic ram: 95148 of which 164 recycled
Never used RAM 100928, free system stack 130 words
Tasks: NETWORK(ready,24.0%,219) ETHERNET(notifyWait,0.1%,169) HEAT(notifyWait,0.0%,324) Move(notifyWait,1.5%,248) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,362) CanClock(delaying,0.0%,333) TMC(notifyWait,8.9%,58) MAIN(running,65.4%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:24:15 ago, cause: software
Last software reset at 2022-01-13 22:50, reason: User, GCodes spinning, available RAM 104696, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 153
MCU temperature: min 43.9, current 46.7, max 46.9
Supply voltage: min 23.6, current 23.8, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 206422, ok, SG min 0, mspos 967, reads 52485, writes 17 timeouts 0
Driver 1: pos 7789, ok, SG min 0, mspos 571, reads 52485, writes 17 timeouts 0
Driver 2: pos 33670, ok, SG min 0, mspos 641, reads 52485, writes 17 timeouts 0
Driver 3: pos 0, ok, SG min 0, mspos 620, reads 52485, writes 17 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 1, reads 52486, writes 17 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 52492, writes 11 timeouts 0
Date/time: 2022-01-13 23:15:16
Slowest loop: 32.87ms; fastest: 0.05ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.7ms, write time 5.2ms, max retries 0
=== Move ===

list itemDMs created 125, segments created 38, maxWait 211955ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 16146, completed 16101, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X167.119 Y158.677 E0.0301" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 13102, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 7276/0/0
Tx timeouts 0,6,7275,0,0,5818 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 39.85ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

Phaedrux · 13 Jan 2022, 22:52

@massimilianoconti said in error zoffset for bl touch and duet3 firmware 3.4 beta 7+1:

bed compensation in use: mesh

Yes it is active

massimilianoconti · 13 Jan 2022, 23:45

perfect. I tried to install version 3.4 beta 7+6 but in the end from an error drive 0

perfect. I tried to install I think it's the firmware that has something in the wrong installation. I put back the 3.4 beta 7 + 1 and it went immediately fine. version 3.4 beta 7+4 is not present among the downloaded files but only the 3.4 beta 7+6

dc42 · 14 Jan 2022, 09:08

@massimilianoconti the spurious error from driver 0 is fixed in the 3.4beta7+7 files now at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0.

massimilianoconti · 14 Jan 2022, 11:21

perfect thank you very much. now the version works in the installation. I do some tests and let you know

massimilianoconti · 16 Jan 2022, 00:26

This post is deleted!

massimilianoconti · 16 Jan 2022, 00:26

Firmware 3.4 beta 7+7 solved the heater problem when starting a new print. the heater is fine part good also the bl touch seems to be fine. I do further tests and communicate news