@dc42 Thank you! Glad to know it wasn't just a mistake on my end.

@owend
Thanks for the reply! I forgot to mention that this is a standalone setup. In my case, fan 2 is connected to the mainboard while fan 0 is connected to one of the expansion boards.

I'm attempting to use the {tools[N].fans[M]} object model property selector to retrieve a fan number, but it appears to always evaluate to -1.

4/22/2022, 2:27:45 PM: echo {tools[3].fans[0]}: -1
4/22/2022, 2:27:50 PM: echo {tools[15].fans[0]}: -1

Strangely, I do see the expected fan numbers when running M409 k"tools[N].fans[M]" and when viewing the entry in the Object Model plugin.

4/22/2022, 2:28:00 PM: M409 k"tools[3].fans[0]": {"key":"tools[3].fans[0]","flags":"","result":0}
4/22/2022, 2:28:05 PM: M409 k"tools[15].fans[0]": {"key":"tools[15].fans[0]","flags":"","result":2}

This is on a Duet 3 MB6HC with three EXP3HC boards, all running RRF 3.4.0.

Attempting to replicate the issue with RRF 3.3 also results in the -1 values with the object model property selector and the correct values when viewing the entry in the object model plugin, but when I try M409 I hit the firmware resetting bug that was fixed for RRF 3.4.0.

Has anyone else run into this?