M500 not saving correctly in SBC mode. 3.2.2 Duet3

dc42

@th0mpy said in Weird error on my Delta:

@dc42 Ok, I tried it, it does save it but there seems to be a formatting issue on the A and B params:
; Delta parameters
M665 L291.060:291.060:291.060 R137.239 H281.544 B120.0 X-0.138 Y0.266 Z0.000
M666 X-1.000 Y-1.000 Z-1.000 A0.10 B0.10
; Heater model parameters
M307 H0 R0.630 C141.300:141.300 D4.00 S0.75 V14.0 B0
M307 H1 R2.227 C104.400:104.400 D6.00 S0.75 V14.0 B0
Am I going crazy here?

Odd, I did the same and it worked correctly. Are you definitely running firmware 3.2.2 ? Send M115 to check.

droftarts

@th0mpy Are you using an Single Board Computer with your Duet 3? Your M115 doesn't report this. I just tested the following, which seems to be stored and retrieved correctly:

The resultant M501 looks like this (in part):

; Delta parameters
M665 L161.612:161.612:161.612 R81.896 H173.484 B75.0 X-0.843 Y-0.003 Z0.000
M666 X-1.000 Y-1.000 Z-1.000 A10.00 B10.00
; Heater model parameters
M307 H1 R2.429 C140.000:140.000 D5.50 S1.00 V0.0 B0 I0

Though this is on a Duet 2 Maestro running 3.3beta2 (2021-03-10).

Ian

Th0mpy

Here's the result of M115:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-02-11

I am running in SBC mode.

Phaedrux

It would appear that DSF in SBC mode isn't saving the config-override.g correctly. One for @chrishamm ?

chrishamm

@phaedrux Yes, that's right, the tilt factors must be multiplied by 100 before they're written to config-override.g. I'll fix that in the next version.

Th0mpy

@chrishamm Will that fix it from not saving at all with M500 after calibration?

Th0mpy

@chrishamm do you know when you might have a version to test? I'd be happy to give it a whirl.

Th0mpy

@chrishamm and @dc42 Hey guys, just checking in. Did these updates make it into 3.3.0-b3? I just saw that was released but didn't see anything in the release notes. Can you let me know when I can give it a test?

chrishamm

@th0mpy Those changes are part of the 3.3-b3 pre-release. Feel free to test it again.

Th0mpy

@chrishamm @dc42 that solved it! Thanks guys!