Strange BLTouch issue. Hightmap it off while printing

[Veti]

@RocketPat
your z leadscrews are out of sync. you can correct it manually, but the dual z setup is faster and more accurate.

also unless you converted your cr 10 to 24v you are running your z motors at 6V, which might not be enough.

[RocketPat]

ah okey i am using a 12V PSU but if they run in parallel the voltage should be the same... only the current is dropping

[Veti]

the 2 z connectors on the duet actually run in series rather than in parallel.

from the linked site

Note that the Z driver (drive 2 on Duet2) has a dual socket wired in series for powering two z motors at once.

[RocketPat]

@Veti ohhh okey so that are some bad news i see haha okey. I will give the independent z setup a try.

[Veti]

@RocketPat said in Strange BLTouch issue. Hightmap it off while printing:

M584 X0 Y1 Z2 E3 ; set drive mapping

for now change this to
M584 X0 Y1 Z2:4 E3 ; set drive mapping

connect the second z motor to e1 and place the jumpers on the second z connector.

that way you are using 2 motors for now.

[RocketPat]

@Veti okey i only need to change that or do i have to do more suff i am reading that hole article for the frist time now and i am kinda scared to set up everythig new again. I will do a quick backup and give it a try.

[Veti]

@RocketPat

that changes allows you to use 2 motors for now.
you still need to do the rest later.

my guess for now is that you are losing steps because of the 6v dual z setup.

[RocketPat]

okey i am doing a quick first layer print and see what is happening, looking good so far. Nothing exploded.

[RocketPat]

So now i did quite a bit testing and i got a much better result.

Also the true leveling is working now. But i still have too low presure on the left side. I can get a print startet now and it would be working but maby my current is too low now.

[Veti]

did you measure the real offset of the probe?

[RocketPat]

yep i startet at x100 y100 and moved to x117 y143 what means that the offset should be -17 and -43

[RocketPat]

okey now i got a new problem, after i restarted the board the hightmap is getting generated but is not used. The motors dosen't correct my print anymore.

[Phaedrux]

Can you post your homeall/homez? Where are you probing on the bed to set z0? It looks like you're using a corner rather than the center of the bed.

[RocketPat]

this is my home all

; homeall.g
; called to home all axes
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 22:18:40 
 
GMT+0200 (Mitteleuropäische Sommerzeit)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-245 Y-285 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000       ; go back a few mm
G1 H1 X-245 Y-285 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X118 Y185 F6000      ; 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

and this is home z

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 22:18:40 GMT+0200 (Mitteleuropäische Sommerzeit)
G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 X20 Y55.5 F6000 ; go to first probe point
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

[RocketPat]

@Phaedrux in the home all i am using the middle of my bed

[Veti]

@RocketPat

do you still have the G29 in the start script?

[RocketPat]

yep right after i home all

M107
;M190 S45	  ;set bed temperature and wait for it to be reached
G28          ;Home axis
G29
 
M109 S210 ;
M107         ; Turn layer fan off
G21          ; Set to metric change to G20 if you want Imperial
G90          ; Force coordinates to be absolute relative to the origin
 
G0 X0 Y0 F9000 ; Go to front
G0 Z0.15 ; Drop to bed
G92 E0 ; zero the extruded length
G1 X80 E6 F780.000 ; Extrude filament in a 8cm line
G92 E0 ; zero the extruded length
G1 E-1 F780.000 ; Retract a little
G1 X80 F4000 ; Quickly wipe away from the filament line
G1 Z0.3 ; Raise and begin printing.

[Veti]

@RocketPat

while printing use M122 to check if mesh compensation is active

[RocketPat]

So i think its on, but i am not sure why the offset is 0

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6J1F4-3S06M-193YP
Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94072 of which 44 recycled
Exception stack ram used: 576
Never used ram: 8400
Tasks: NETWORK(ready,716) HEAT(blocked,1224) MAIN(running,1632) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:49 ago, cause: software
Last software reset at 2020-10-25 16:47, reason: User, spinning module GCodes, available RAM 8424 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04417000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 29.0, current 29.8, max 30.3
Supply voltage: min 11.8, current 12.0, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/517
Driver 1: standstill, SG min/max 0/495
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max 0/432
Driver 4: ok, SG min/max not available
Date/time: 2020-10-25 16:50:37
Cache data hit count 279758463
Slowest loop: 154.49ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.4ms, write time 2.2ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 166, MinFreeDm: 157, MaxWait: 15080ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 99, completed moves: 88, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: 3
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== 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 X13.453 Y68.416 E30.30764" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
 

[Veti]

@RocketPat said in Strange BLTouch issue. Hightmap it off while printing:

Bed compensation in use: mesh, comp offset 0.000

that is fine. why do you think its not working?