Maslow 4 - z-probe settings set in the settings menu, but not changed in Probe panel

Troubleshooting
1

Edited to correct terminology:

Aloha,

I am not currently able to set up my machine for operation—space is the perennial issue—but I do plan to set up the z-probe per the thread Instructions - How To Make And Set Up A Z-Probe On The M4, and so among the first settings I change after a full firmware/index.html.gz/maslow.yaml upgrade is to turn on the probe panel and set the plate thickness to 0 (zero) in the drop-down Settings menu per the instructions linked above.

For the last several upgrades, I have noticed that even after setting the plate thickness to 0 in the settings menu, when I navigate to the probe panel after, the plate thickness is set to 0.5mm. It’s like the setting change doesn’t propagate to the probe panel.

Just FYI; not really a big deal at the moment.

BTW, @Andith, do you know if/how the setup process might have changed with the transition to 1.x firmware/index.html.gz/maslow.yaml?

Mahalo,

2

David Negaard wrote:

For the last several upgrades, I have noticed that even after setting the
z-offset to 0 in the settings menu, when I navigate to the probe panel after,
the z-offset is set to 0.5mm. It’s like the setting change doesn’t propagate
to the probe panel.

the zoffset values for each anchor are not related to the z probe, they are the
difference between where the belt is at the anchor and at the frame (in the z
direction, with the router all the way down)

David Lang

1 Like
3

Edit:

My apologies; I don’t think I clearly communicated what I’m seeing.

I can set the plate thickness to 0 (zero) in the Preferences menu, but when I go to the probe panel, the value for plate thickness does not align with what I entered.

1 Like
4

@md8n could this be related to the settings not persisting issue that we were seeing?

5

@bar, I suppose it could be, but it’s distinct; in the preferences menu, at least, the settings do persist now.

1 Like
6

Not sure if this is related, but after upgrading to FW 1.05, I started experiencing a lot of persistence issues—values wouldn’t stick in the software, and the new X/Y scaling factors kept disappearing from my YAML file. I tried reuploading FW 1.05, but the update kept failing due to “not enough space.” Eventually, I flashed the firmware over USB, and everything started working again. I suspect some kind of memory corruption, maybe caused by a weak Wi-Fi signal during the update. Just a guess, though…

1 Like
7

@bar the cause of the actual non-persistence issue has been fixed.

However, that code has other problems, like some of those values were never persisted anyway from certain screens, or only in certain specific circumstances.

2 Likes
8

This thing was an utter omnishambles - I figured out I had an introduced a bug … didn’t matter .. there were plenty others all interwoven in this bit of nascent nastiness.

If you wanna try it out for yourselves, here it is:
index.html.gz - v1.05.01 (117.4 KB)

2 Likes