M150 execution time.
-
Hello all, I am working with a Neopixel LED strip on a Duet 3 Mainboard 6HC, RRF v3.4. Using the M150 (not the config statement) command in a macro loop it seems the execution time for this command is around 200-250ms. If I run a series of M150 commands or a loop the result it the same. I can't find anything in the documentation regarding execution time so I'm not sure if this is expected behavior or something else I need to look into. I would like to make more rapid updates if possible.
TIA - John -
@Johnnyg at the very least make sure you are upgraded to RRF 3.4.6. -- previous releases waited for motion to complete before setting some kinds of LEDs. There may have been further improvements in the 3.5 release train. Try 3.5rc3 which is mostly stable and improved over 3.4.6 (there are some post rc3 builds floating on the forum which also work reasonably well).
<>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>
-
@Johnnyg How many LEDs do you have in the string?
-
@oliof Thank you, I will look into upgrading to see if that helps. I haven't done a firmware upgrade yet.
-
@gloomyandy I have only been testing up to 30 LEDs on the strip so far,
-
@Johnnyg I'd say 250mS sounds a little much for updating 30 LEDS. How are you measuring the time it takes? Having said that it's probably not a good idea to be updating neopixels frequently especially during a print job. What is it you are trying to do?
-
@Johnnyg note that updating LEDs connected to the dedicated LED output (Duet 3 only) does not suspend motion. If you are using Duet 2 or another pin on Duet 3, motion will be suspended while the LEDs update. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/IO_Neopixel_DotStar#connections
Are you updating all LEDs with one command, or each LED separately with 30 M150 commands?
Ian
