Brilliant, thank you.

We’ve not built this particular firmware before but we can certainly look at this.

Thanks again.

Cheers,

James

@DC42 might resurrecting M135 be a possibility?

Our final goal was to integrate the Duet into a commercial product. In the meantime we can go back to v2 firmware but this isn’t really a longer term option.

Cheers,

James

Thanks for the replies.

Unfortunately it’s the PID interval I need to change, M950 Q sets the the PWM base frequency.

I should have said that we reduce it using M135 from 250ms to 100ms (so increasing the sample rate from 4Hz to 10Hz).

We have been using several Duet controllers with stock firmware to run some prototypes incorporating a thermal system with a relatively short tau (fast response).

The default PID interval is too slow for robust control so we have been reducing this using M135 to give us ~10Hz update rate.

Wanting to use some of the newer features we proceeded to update to RRF v3 only to subsequently realise we are no longer able to use M135.

Has M135 gone for good, or are there options for reimplementation?

Could we change a hardcoded interval as an alternative?

Cheers,

James