Tool Offset for Z axis not working properly in 3.4.0beta2?

Phaedrux

Ok, so this is a multi tool delta printer?

Can you also please post the results of M122 and M98 P"config.g"?

What do you have in bed.g?

When you send T1 would changing the z by -35 mean the head would be below the current bed reference location or something?

code7

@phaedrux

Yes this is a multi-tool delta printer.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta3 (2021-08-24 13:56:10) running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6JTD0-3SN6K-TTHQR
Used output buffers: 3 of 24 (17 max)
=== RTOS ===
Static ram: 23940
Dynamic ram: 75304 of which 124 recycled
Never used RAM 12712, free system stack 184 words
Tasks: NETWORK(ready,10.3%,227) HEAT(notifyWait,0.0%,326) Move(notifyWait,0.0%,340) MAIN(running,84.3%,441) IDLE(ready,5.4%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:17 ago, cause: software
Last software reset at 2021-09-01 14:59, reason: User, GCodes spinning, available RAM 12664, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 42.4, current 43.1, max 43.4
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 39673, standstill, SG min/max not available
Driver 1: position 39673, standstill, SG min/max not available
Driver 2: position 39673, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-09-02 14:05:13
Cache data hit count 671485677
Slowest loop: 8.05ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 159.75ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address dc:4f:22:6e:e2:a0
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27168
WiFi IP address 192.168.1.3
WiFi signal strength -45dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Yes this is correct - when sending T1 changing the z by -35 means the head would be below the current bed reference location.

I also tried reverting back to FW 3.3 and it still acts the same way.

Phaedrux

@code7 said in Tool Offset for Z axis not working properly in 3.4.0beta2?:

Yes this is correct - when sending T1 changing the z by -35 means the head would be below the current bed reference location.

And are you able to position it such that it wouldn't be below the bed and see if it would work then?

code7

@phaedrux

I'm not exactly sure what you mean. If T0 is set, I read X0 Y0 Z5 on the display.

After sending T1, the display reads X2.0 Y-2.5 Z5.

Phaedrux

Does it change to an expected value if you do a small Z movement?

What do you have in your toolchange files?

code7

@phaedrux said in Tool Offset for Z axis not working properly in 3.4.0beta2?:

Does it change to an expected value if you do a small Z movement?

If I move down 1mm the display will indicate Z4.

For the toolchange files: tfree0.g, tpre0.g, tpost0.g are all empty and there are no other such files for the other tools.

I wasn't having this tool change problem previously and I haven't yet figured out what may have changed.

Phaedrux

Can you step backwards in firmware versions to find the last time it worked?

3.3? 3.2.2? 3.1.1?

code7

@phaedrux
I went back and checked my notes and it was actually working fine in 3.4.0 beta2. The only thing that I believe I've changed between now and then was the homedelta file as we've discussed in another post. I reverted those changes as well but it is still not offsetting the Z value of T1 properly. Are you able to replicate this on your side?

Phaedrux

You mean from here?

https://forum.duet3d.com/post/248771

The homedelta you posted above looks correct, so I don't think that is the difference.

So it was working in 3.4 beta 2 and now it's changed in beta 3? That's more helpful.

code7

@phaedrux
It somehow stopped working a week or two into me using 3.4 beta2 then you had me update to 3.4 beta3 and it still isn't working. Maybe it has nothing to do with the FW after all. I'm just not sure what else could cause this behavior. Do you have any other ideas?

Phaedrux

@code7 said in Tool Offset for Z axis not working properly in 3.4.0beta2?:

Do you have any other ideas?

Unfortunately not. If you can identify a firmware version where it works as you expect then we have an idea of where to look in the changes between firmware that may be the cause.

code7

@phaedrux

I removed the G10 offsets for T1 from the config.g and added it to the T1 post file and it's working now.