Should issues found during beta be reported just here, or also filed as an issue on GitHub for good measure?
There’s still this data “afterimage” thing on LEDs once IDLE_OFF_TIME expires. Confirmed on different sabers.
Current test shows it on my 4 accent LED strip labeled with comment here:
{ NO_BLADE,
WS281XBladePtr<144, bladePin, Color8::GRB, PowerPINS<bladePowerPin3> >(), // D1 dead?
WS281XBladePtr<144, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin3> >(), // D2 test leads
WS281XBladePtr<4, blade5Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(), // Onboard 4 LEDs
CONFIGARRAY(noblade),
"00_NO_BLADEsave", },
Can anyone else confirm something similar?
Original post from Alpha test thread:
Ok I have a thing now.
After IDLE_TIME_OFF expires, I get a lingering “afterimage” on the Hilt side blade PCB LEDs.
However only with StylePtr<>() styles.
With a default style such as StyleNormalPtr<CYAN, WHITE, 300, 800>() the LEDs are fully off after IDLE_TIME_OFF expires.
The color shown is whatever was last showing, so it’s behaving like the data stream was lost (expected), but there’s still some leaking power.
The PCB’s blade is:
WS281XBladePtr<5, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()
No blade in hilt, but it’s wired sharing FETs for LED pads 2&3 (typical)
When adding #define SHARED_POWER_PINS
a single Green LED (not one of the original 3) is lit, regardless of style color, including testing with Rainbow.
This all started today, I believe after I synced the SVF related updates, (possibly styles/color_select.h or around there somewhere?)