I wanted to use the meta-commands to adjust my babystepping for prints, however, my if statements never trigger even if they are true. So instead of testing the commands inside of a gcode over and over, I made a quick macro and get the same results. And for the life of me, I cannot figure out what I am doing wrong. Below is what I have tried.

echo move.axes[2].babystep
if move.axes[2].babystep = 0.050
echo "it worked"
echo "it didn't work"

DWC echos the value from my Z axes babystep, and then echoes that the if statement was not true.

set global.offset = move.axes[2].babystep
echo global.offset
if offset = 0.050
echo "it worked"
echo "it didn't work"

Again DWC echos the value in the global offset variable, which is axes 2 babystep value, but the if statement does not see the expression as true.

The only time I've gotten the above meta to work is by setting it to NOT equals, in which case the if statement evaluates as true.

7/28/2021, 11:39:54 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)

@ChrisP I was hoping for similar, but rather I just wanted the numeric value displayed by the board voltages.

Wow......I feel ridiculous. I've used that page so many times as a reference, yet I forgot to look at it to see about additional I/O options ><.

@dc42 If I configure it as a linear analog sensor, where does the data get displayed?

I'd like to add a current sensor to monitor how much of my power supply I'm using. What are my options to get the reading into the CPU and then displayed on the DWC?

Persist over power cycle isn't was I was going for sync any time I do a power cycle, an M999 command, E-stop/reset DWC button, etc I have config.g pull up a macro to do the bed leveling etc after I acknowledge it's safe to do.

The persistent counter I want to do stems from this covid-19 ordeal where my printer is on 24/7 and once a print is done I pop it off then tell DWC to reprint. I want the software to count how many times I start a print. Then between print N and print N+1 I want to perform a bed level check then start print N+1 and reset the counter.

This way if the controller resets or power is removed the printer will do a bed level check anyways. Hopefully, that makes more sense now.

I feel the need to add cooling I just haven't figured how I want to do it though. I also have not printed it yet.

If this helps you or anyone else this is how I have my 2 Noctua 4pin fans:
NF-A6x25
NF-A4x10

; Fans
M950 F0 C"!out4" Q25000                         ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Extruder" S0.2 L0.2:1.0 X1.0 H1 T60:180                  ; set fan 0 name and value. Thermostatic control is turned On, low low speed at 60c max speed at 180c+
M950 F1 C"!out5" Q25000                         ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Part" S0.2 L0.2:1.0 X1.0 H2 T25:80                      ; set fan 1 name and value. Thermostatic control is turned on low speed at 25c and max speed at 80c

Specifically, I'd like to perform a G29 or G32 at startup every time and also every # number of prints. While I have figured out how to do an auto-execute on power-up (reset, etc), I still have not been able to figure out how to execute a macro basically every x number of prints.

The reason for this question is that at first, I thought I'd just do a G29 or G32 and be all set. But, then I realized that after each print I usually removed the glass build surface. Which got me thinking that I then needed to do the G32 or G29 for every print and thusly added it to my simplify 3D script.

Well, now I have a wham-bam build surface so I should have to worry about my mesh changing much. But, I'd still like to make sure I have a good mesh at power-up and a validation run every nth print.

Does anyone know how to do that or have any suggestions?

Oh yeah, I understand the concern as well for having the machine do motions automatically hence I plan on placing an M291 S3 command at the start of both scripts to reduce the risk of issues. Which brings me to an issue while testing my auto gcode when my:

M291 S3 R" Reset detected" P" Press ok to begin power-up routine, cancel if this was just a reset."

When the above g-code is executed I do get a pop-up, however, there is no text and only the OK button when using the DWC.

I don't consider sensorless homing as a gimmick. The way I've had to test it while testing trinamic drivers it was not very accurate due to the function in the library not actually sending the correct command nor receiving the correct info to set it properly. So I had to poll the motor load register and compare it to a set min that related to a stop, then send the stop position command. All of which added several us of delay. But, otherwise gave very usable homing positions and measuring, at least until a step was skipped of course. I really like this function because the Z -end stop on my Maker Gear M2 is a pain in the but to install, set, and it always moved. Since the sensor had to be clamped on a smooth rod.

I had a feeling they didn't add traces for the encoder IO, would have been really nice though. Guess I'll have to do encoders with an Arduino or other micro to send position data to the duet. The only concern is data bandwidth, timing, reaction time, and program timing. Whereas if the encoder IO was accessible the driver could handle skipped steps and stop/send interrupts.

The other issue with stall guard / trinamics skipped step detection is that they use the amperage and back emf from the motor, but the back emf I dependant on motor specs and velocity, along with the sense resistor value.