G30Auto-Tilt creates hidden Z-offset-Duet 3-3.0RC2, DSF1.2

Phaedrux

@Luke-sLaboratory said in G30Auto-Tilt creates hidden Z-offset-Duet 3-3.0RC2, DSF1.2:

anything else anyone can think of, let me know. I'm stumped.

I think you're on the right track. Nuke it from orbit and have a fresh run at it.

Luke'sLaboratory

Alright - I nuked the firmware from the heavens and re-flashed it with Bossa - No change in behavior.

I also tried a suggestion from kraegar to delete the m574 line for the z-axis since its probed out anyways in homeall and homez, but this also failed. Similar results.

New clue - on the 3rd probe point after the first set, it gave me an "error - G30 insufficient axes homed for bed probing" on the 7th probe (so while it is supposed to be within the second calibration iteration) from which it completed its probing, but instead of spitting out a deviation, it gave up (i assume errored out of the loop) ran g28, and then sat ready.

Luke'sLaboratory

Alright -

I RTFM, and conditional gcode has nothing to do with this. I'm using a Duet3 w/ a pi, so I guess it just ignores the conditional part until DSF adds support again. My bad.

The original issue still stands - using G30 to probe points and store them adds a nice 2mm offset that appears to be found in the first round of probing, then it "adjusts" for it, then the second round its not found, so it just works.

anyone have any logs I could get that would help them with this bug?

gtj0

Two things you should do...
In /opt/dsf/conf/config.json, add a "LogLevel" line (or modify the existing one) and set it to "debug".

{
  "LogLevel": "debug",
  "SocketPath": "/var/run/duet.sock",
  "Backlog": 4,
  ...

Restart duetcontrolserver.
Then run journalctl -fu duetcontrolserver
That will give you an idea of what the DCS thinks the Duet3 is doing.

Next step...
Connect the Duet3's USB port to the Pi (or any other computer). That will give you access to the Duet3's serial console. You can use Putty, minicom, whatever, to access it.
When you do, issue M111 P3 S1. That turns GCode logging on on the Duet3 and you can see what it's actually doing.

Now run your sequence.

Luke'sLaboratory

Alright -

I'm Back -

Looks like if I take the BL-Touch out of the equation (switched to an inductive sensor now, but once I assemble my jubilee head (soon) this will change to a simple physical switch) - This works exactly as intended without any additional complications with identical gcode.

I greatly appreciate you all taking the time to help me with my issue. I regretfully close this issue out for now on my machine.

It definitely seems to be related to the bltouch implementation.

So thank you all again very much.

Luke

gtj0

No worries! Don't hesitate to yell if you get into trouble again.