@tekkydave yep that's all done in slic3r at slice time , nothing in the firmware

@dc42 double sided double density 1.2M

@dc42 https://www.dropbox.com/s/eh33zxsda53bvhv/2020-02-21 13.56.06.jpg?dl=0 look familiar?

https://www.dropbox.com/s/oamu8uhdz134qj6/2020-02-21 13.55.32.jpg?dl=0 from our antique computing pile at work

@Garfield the maxwell linkages allow for the spacing between the mounts to vary as the joints move. so using a ball socket joint will not work well

probably a good to post your config.g file

for reference adafruit DotStar LEDs are APA102(or SK98225) LEDs so any APA102 4 wire LEDS will work

g92 just sets the current position to the specified value

so G92 X100 sets the current location to X100 it will never move a motor

@chrishamm same here too from rc1 to rc2

@chrishamm Tested here - looks good - thanks

the BLV interface doesn't use i2c, it uses the existing paneldue serial/JSON interface. you might look at the M150 command which controls addressable LEDS from Gcode

@dc42 @chrishamm did you see the compare i did - doing a M111 P3 S1 and logging the duet3 usb port while running TEST.gcode ( see above) I see random lines of gcode being swapped in order. the 2 runs in the compare were done by just restarting the running job

i'm somewhat suprised others are not seeing the same issue.