@gnydick Nice idea 👍
It could easily be adapted to

Just wondering, if it could also debounce the pushbutton for the first usecase

@mikeabuilder it's probably better to check if it is > 0 (or eventually not = "null")
then, a single reading should be enough

Thanks @chrishamm. Reading your response made me realize that I not only mistyped "SBC" but also that I was backwards about it. My system is NOT running in SBC mode, it's stand-alone. So thanks for answering that version of the question.

I'm restating your "never supported NPT" comment to see if I understand the implications for a machine running in stand-alone mode:

The stand-along RRF will not "know" the time until a client connects. This means all log entries will have a timestamp based on the machine's uptime (time since boot).

If/When a client connects, if that client is DWC, then DWC will set RRF's date-time.

If a client other than DWC connects, and it connects using rr_connect with the time option, then RRF will update with the time from the client.

This explains a lot of unexplained macro errors I've observed over the past three years. And I can see now that I'll need to rewrite all the macros to not use state.time for measuring duration. I'll convert them all over to using state.upTime rather than state.time.

I think I'll also look into making an Rpi pico that powers up with my system and that does the rr_conenct function.

@p8blr said in Duet not consistently running code:

@dc42 Interesting. Any idea on an estimated completion date on the feature request? Or maybe a workaround I could do instead?

See https://github.com/Duet3D/RepRapFirmware/issues/959

Scheduled for “after 3.6.0”.

Ian

@Notepad @droftarts ,

My goal is to test a shitload of probes, and see how much it starts to deviate after thousands. Your script might actually work, let me test

@droftarts said in Possible object model error:

I'm sorry, but you'll have to ask @chrishamm why it works! I think it changes the data type to a string.

ok 😂

@Proschi3D yeah I understand. Best way would be to break up the parts and call them as separate macros guarded by conditionals, but if you do that, you can use the built-in tool prep macros.