Posts made by hunterschoonover

@Phaedrux

The error message I get at after the macro finishes is:

M292
Warning: M918: Command is not supported

However, I don't see anywhere in the macro that M292 and M918 are used...?

@Phaedrux said in How do I configure Z-Probe Offset(s) for different nozzles?:

What firmware version are you using? Please send M122 in the gcode console and copy and paste here. You might also find the error message in the console window.

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6J9D4-3SJ6Q-KV8LU
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 97052 of which 44 recycled
Never used RAM 99240, free system stack 134 words
Tasks: NETWORK(ready,67.9%,175) ETHERNET(notifyWait,2.3%,170) HEAT(notifyWait,1.3%,321) Move(notifyWait,34.6%,248) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.6%,333) TMC(notifyWait,55.2%,58) MAIN(running,152.0%,1083) IDLE(ready,0.7%,30), total 314.5%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 43:41:28 ago, cause: power up
Last software reset at 2023-01-08 23:36, reason: User, GCodes spinning, available RAM 100284, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 176
MCU temperature: min 34.1, current 43.9, max 45.0
Supply voltage: min 22.9, current 23.4, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/706/692, gc cycles 2
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, mspos 858, reads 55503, writes 60 timeouts 0
Driver 1: standstill, SG min 0, mspos 392, reads 55507, writes 56 timeouts 0
Driver 2: standstill, SG min 0, mspos 632, reads 55495, writes 68 timeouts 0
Driver 3: standstill, SG min 0, mspos 632, reads 55495, writes 68 timeouts 0
Driver 4: ok, SG min 0, mspos 304, reads 55515, writes 48 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 55553, writes 11 timeouts 0
Date/time: 2023-01-16 19:22:31
Slowest loop: 345.50ms; fastest: 0.04ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.9ms, write time 3.7ms, max retries 0
=== Move ===
DMs created 125, segments created 20, maxWait 62800492ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 711, completed 705, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 36], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.9
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is ready with "M122 " in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X197.007 Y189.339 E4.4092" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 1415591, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 786441/0/0
Tx timeouts 0,0,786440,0,0,629149 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 4829.05ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• Ethernet -
  State: active
  Error counts: 0 0 1 0 0
  Socket states: 5 2 2 2 2 0 0 0

@OwenD

You're the man.

I was able to implement your code with very few changes. Your help is much appreciated!

Currently, there is one command that is not supported on my device, but I haven't narrowed down which one it is yet... the error output to console doesn't specify the command that's failing. I'll post updated code for others that need it after I resolve the issue.

It's currently working and has led to several successful prints. Thanks Owen!

@Phaedrux
that was it. I now have the Reply and Quote button.

Funny that I was able to create a new post, but not reply to my own.

Thanks for your help!

I am attempting to reply to an answer on one of my posts, but cannot find the reply button.

Is it possible that the reply button is not visible to me because I don't have a high enough reputation?

I can't even upvote the answer. It gives the following message:

"You do not have enough privileges for this action."

What am I missing?

How do I configure the Z-Probe offset(s) for different nozzles?

I'm using the BL Touch for z-axis homing, which is a problem because this means that the bed's 0 position along the z-axis is relative to the bed height.

When the leveling nuts or z-axis motors are used to adjust the bed offset to match the new nozzle, this is rendered undone when the z-axis is homed again... the new bed height will be seen as 0.

How does one go about solving this in an efficient and repeatable manner?

Device: Duet 3 6HC