@chrishamm Chris, I think it is. Thanks!

@T3P3Tony I will test as soon as I can.

@chrishamm Thanks for the reply.
I was thinking of faster streaming, maybe something along the lines of 100Hz. The added difficulty might be that i'm using CAN Connected boards.

It would be an alternative to making custom boards.

@NineMile thanks, I've included this in 3.6.0-beta.1.

@dc42 The Adafruit documentation is ambiguous because it's internally contradictory by one byte. So I don't know.

@gloomyandy i did look , great 🙂

@moth4017 What you are seeing is the current expected behaviour, there is a feature request to change this, but I do not think it has been implemented yet (or if there is any commitment to implement it).

@dc42 I don't use an accelerometer to tune IS, but the caliper method.
I've now switched from ZVD to EI3 and do some test prints.
IMHO belt teeth cogging would have a much higher resonance, more like VFR-artifacts?

@Dep There is a feature enhancement request for this already, along with various side issues, see:
https://github.com/Duet3D/RepRapFirmware/issues/745
https://github.com/Duet3D/RepRapFirmware/issues/746

Ian

T3P3 created this issue in Duet3D/RepRapFirmware open Feed hold #745 T3P3 created this issue in Duet3D/RepRapFirmware open Controlled deceleration when a homing switch is triggered #746

@DonStauffer I think there's enough drivers and I/O on a Duet 3 Mini 5+ with Duet 3 expansion Mini 2+ (to give 7 motor drivers) to drive your setup.

Ian

@bug2k22 Moved to firmware wishlist.

Ian

@gloomyandy For example, the Protocol 2.0 used by DYNAMIXEL XL330-M288-T, PWM servos cannot be used for torque control and speed control. Two-way communication can be used not only for servos maybe digital sensors or other non-real-time device control.

Bambu Lab may also use a similar algorithm to achieve flow calibration.
https://forum.duet3d.com/topic/33667/auto-pressure-advance-turning-by-hotend-pressure/28?_=1716527681549

@robotsneversleep in the M950 command to declare an LED strip you need to specify whether it is RGB or RGBW because RRF has to drive them differently. Assuming you get that right, if you provide a W parameter but the strip was configured as RGB then that parameter will be ignored.

@GeneRisi some of the RAM is allocated dynamically depending on your configuration; so the linker can't tell you that.

When the machine has run for a while, M122 will tell you how much RAM is unused.

@CanDo415 the reason is that standard CNC GCode uses ( and ) to enclose comments, which is an unfortunate choice. In order to be compatible with this, RRF does the same when in CNC mode unless the ( ) are themselves inside { }.

@dc42 Done. ##986