This is meant as totally constructive, but Erv’s documentation is stellar, and he provided the parms to take a look into on your config. You haven’t provided any detail on your config which makes helping a challenge. Here is a section that might help, and a link to the entire doc. I have personally asked for, and received help from Erv, but if if it is possible to find it, I much prefer to leave his free time to innovating!
https://www.plecterlabs.com/Media/D https://www.plecterlabs.com/Media/Doc/Crystal%20Focus%20v10%20rev1.13-GB.pdf oc/Crystal%20Focus%20v10%20rev1.13-GB.pdf
Power Saving - StripOffTM feature
Each pixel uses about 0.9 mA even when the leds are off (as the internal controller remains active). With a blade made of 280 pixels, that's a good 250mA that will empty the battery in a heartbeat if left alone. We're therefore using the 4 onboard drivers of the board to remotely control the strips negative and cut the power totally when reaching deep sleep. If this feature isn't required, the strip(s) negative can return to the main negative of the board.
Since version 10.002 of the firmware, the general configuration uses parameter strippower (bitfield) to control which of the L- driver outputs are used for powering the ledstrip and which are still mirroring the blade color channels.
For instance:
strippower=1110
will configure channels #1, #2 and #3 as strip (negative) power control while channel #4 remains free for mirroring the 4th color channel. This comes quite handy when it’s used to drive a rumbling motor or a spinning crystal chamber.
Keep in mind that usually, at least 2 drivers (3 preferred) are needed to control the strips, based on the power pass-thru. Still, that parameter offers the option to totally bypass the ledstrip power control (removing the blade will do the same) and leave the drivers and their PWM pads free for other use, including: