[RRF 3.2.2] Can't figure out the offset between Z0 and mesh
-
@fcwilt Correct. I am probing exactly one of those spots. I'll try between the 4 tomorrow assuming the printer will even start. Currently, the board refuses to launch (different, known issue with the minis, waiting for a board replacement). If it were only on this printer, I'd think it's the board at fault and leave it at that
But the other printer has the same problem, so yeah. -
@pkos said in [RRF 3.2.2] Can't figure out the offset between Z0 and mesh:
@fcwilt Correct. I am probing exactly one of those spots. I'll try between the 4 tomorrow assuming the printer will even start. Currently, the board refuses to launch (different, known issue with the minis, waiting for a board replacement). If it were only on this printer, I'd think it's the board at fault and leave it at that
But the other printer has the same problem, so yeah.Known issue?
I have 4 Minis - what goes wrong?
Frederick
-
There's apparently a batch that can result in loss of connection to the SD card.
It's described here: https://forum.duet3d.com/topic/21004/duet-3-mini-5-unable-to-connect-via-browser/24?_=1615068562632 -
OK. Now I am even more lost...
3.3b1 solves the problem. Height map is scanned and loaded properly.
Same steps as above exactly. Worked first time.Now to try a print!
-
@pkos said in [RRF 3.2.2] Can't figure out the offset between Z0 and mesh:
OK. Now I am even more lost...
3.3b1 solves the problem. Height map is scanned and loaded properly.
Same steps as above exactly. Worked first time.Glad to hear it is working.
I wonder why.
Was it the update to the new version that did it or was it the update process itself that fixed something?
Curious.
I know I have loaded height maps under 3.2.2 but did I create them under 3.2.2? I don't remember.
I need breakfast.
Frederick
-
It must be the update. I rolled back to 3.2.2 and the issue came back.
Each time, I kinda reset the whole process, so all csv's deleted, etc etc. -
@pkos said in [RRF 3.2.2] Can't figure out the offset between Z0 and mesh:
It must be the update. I rolled back to 3.2.2 and the issue came back.
Each time, I kinda reset the whole process, so all csv's deleted, etc etc.Good to know.
I will have to generate a new height map to see if the problem occurs for me as well.
I hope not as I don't like using beta firmware.
Frederick
-
Happy too fast...
It solves the issue with Switchwire, but does not solve the issue on 2.4.
I am still getting that offset even on 3.3b1. Damn...
-
I went ahead and created a 9 point (to save time) height map under firmware v3.2.2.
No issues.
So I'm still baffled by what is happening on your printers.
Frederick
-
I've been trying to create your problem on my printer and I just cannot.
I tried messing with the probe Z trigger height.
I even edited the CSV file adding 1 to each point.
So far I haven't found out what conditions cause the error.
Frederick
-
Well assuming 3.3 comes out of beta soon, I will close this for now. I have a workaround for 3.2.2 that always works... it's just weird an annoying is all
