Issue: My UW Ben Solo’s Power and Aux buttons no longer light up after flashing the proffie.
I suspect this is because the stock configuration is missing a blade code in the bladeconfig.
To remedy the situation, they have provided me with the configuration to their Kylo Ren Crossguard lightsaber.
I was thinking that all I would have to do is identify the codes for the side vent blades and then remove it, but in reality I have no idea.
Any help would be appreciated! (Configs are below)
Ben Solo Stock - BenSolo_Stock.h - Pastebin.com
Kylo Crossguard Stock - Pachstore/UW Crossguard_Stock.h - Pastebin.com
So, it’s hard to say what the problem is without actually knowing how they are wired. I do see that the BenSolo says it has accents on LED5 and 6, while the crossguard says it has accents on LED1 and 5. Not sure if that’s the change you need to make though.
1 Like
Unfortunately a picture of what is going on with the wiring situation will likely not be helpful, because of the confounding way they completed the prost production.
Guess it’s down to trial and error then.
1 Like
I really have no idea where to start. This is the one section of code that I am most in the dark about.
Any ideas for where to start regarding trials and combinations?
Wait. Why did they send you a crossguard config? Why didn’t the send the config that’s sent with the saber? That would be written for the way it’s wired, and you wouldn’t have any issues editing it.
1 Like
Originally they did provide the Ben Solo configuration file, however it seems to be missing the bladeconfig code that controls these LEDs. I think that they were thinking that by use of process of elimination I would be able to compare the two configuration files and extract what was missing in the Ben Solo from the crossguard. Thus, in my original post I post pastebin links for both configurations.
So they shipped you a non working saber?
You said “not working anymore” which would indicate that they DID work at one point.
From the BenSolo config:
BladeConfig blades[] = {
{ 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin1, bladePowerPin2, bladePowerPin3> >(),
WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
SimpleBladePtr<CH1LED, CH2LED, NoLED, NoLED,bladePowerPin5, bladePowerPin6, -1, -1>(),
CONFIGARRAY(presets) },
};
This shows 2 non-pixel LEDs wired to LED 5 and LED 6 that are lumped together into using a single blade style (so they blink together basically).
If you did this instead:
BladeConfig blades[] = {
{ 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin1, bladePowerPin2, bladePowerPin3> >(),
WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
SimpleBladePtr<CH1LED, NoLED, NoLED, NoLED,bladePowerPin5, -1, -1, -1>(),
SimpleBladePtr<CH2LED, NoLED, NoLED, NoLED, bladePowerPin6, -1, -1, -1>(),
CONFIGARRAY(presets) },
};
then you would use 4 blade styles per preset, and control the LED’s separately.
Right?
1 Like
So they shipped you a non working saber?
You said “not working anymore” which would indicate that they DID work at one point.
Upon arrival and under the factory installed configuration the power and auxiliary buttons did light up. See Pic: (Left Pic)
I have 3 proffie sabers (soon to be more) and I like them all to have certain presets. Some are unique to each hilt, additionally all 3 share some presets that I consider as standard. Because I don’t know how to make a config from scratch I asked PachStore customer service for the default config. I copied their BladeConfig section into my config. After flashing this I lost the button lights. I have tried to have a conversation with their customer service regarding this issue, but they do not seem to understand the issue. I took this photo after flashing the stock Ben Solo configuration, just to prove a point, the button lights do not work (likely because some code is missing or incorrect?): (Middle pic, the button color seen here is referred from the blade connector board LEDs)
@NoSloppy - Thanks for your assistance. I like that the LEDs react as a single unit. So, I don’t think that I want to separate them.
The only LED I can seem to see to notice is the one that lights up near the bottom of the hilt: (Right Pic)
That is unless the blade connector board LEDs count as and LED…
This leads me to think that maybe the issue lies in this line?:
WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
Well, what has 8 LEDs?
The emitter PCB?
The thing in the pommel?
Did you open it and check things out?
I would just make solid color styles for a minute to suss out what is what.
Just do like
StylePtr<Red>>(),
StylePtr<Green>>(),
StylePtr<Blue>>(),
And see what shows up where.
If the buttons don’t light, see which color is missing etc…
1 Like
For whatever reason your code would not compile, so here is what I did instead (copied lines from the Stock Ben Config):
{ "Font;common", "Track.wav",
StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(),
StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(),
"Preset Title"
},
The blade and PCB (assuming that is the blade connector board LEDs?) came out blue.
The pommel LED came out green.
And I got no Magenta…
Sorry, I had an extra closing bracket on each. Should have been:
StylePtr<Red>(),
StylePtr<Green>(),
StylePtr<Blue>(),
Anyway, CH1LED and CH2LED specify to use Red and Green respectively.
What color are the actual LEDs in the buttons?
They are single color simple LEDs, yes?
Magenta isn’t going to light up a green one.
1 Like
So that you get a better idea of what it used to do, there was a demo video:
If you watch it from this point, you’ll notice at the LEDs are very reactive much like it to LEDs in the blade. When the user changes the preset, the buttons also change color to reflect the color of the preset. This is sort of what leads me to believe that it might have something to do with that “WS281XBladePtr<8” line…
Well I’m really confused. This isn’t supposed to be this difficult.
Are you hesitant to disassemble stuff because of some warranty coverage maybe?
I would’ve had that thing apart probably before even turning it on to see exactly what is wired to where.
In the video, the 2 buttons look to be controlled separately.
However, it could also look like they are clear buttons and the blade lighting is spilling down and seen through the top button.
When the blade is off for example, the bottom button is green while the other is off.
That’s not possible with one style over 2 LEDs.
They also change color, indicating they are either RGB LEDs or addressable pixels. If pixels, they don’t get the SimpleBladePtr and could be either individual LEDs or something like a mini strip, (possibly the mystery “8”), and have a blade style when off that only lights the bottom part.
Again though, none of that is evident in either of the configs you posted.
I would email Aaron and get a straight answer to how it’s wired, and get the appropriate BladeConfig from him.
Otherwise, just disassemble the thing and look for yourself. 
1 Like
I don’t know what you mean by disassemble. Everything seems to be glued down, or otherwise not made to be disassembled. Personally, I don’t disassemble anything because I don’t have tools and/or knowledge to reassemble it. I’m glad there experts like you around to help plebs like me.
The way I noticed the buttons to work under the factory configuration was more like that they were a blade. The two buttons I believe to have a strip of LEDs underneath them that act as a blade. When the saber would ignite the strip would light up from the bottom to the top. And upon retraction they would power down from the top to the bottom. I did not notice any point in which one was on and the other was off.
Aaron who? Can you DM me some information?
I will not be disassembling this.
ok, what BladeConfig did you use with this preset to get the results you stated?
1 Like
The Ben Solo stock BladeConfig.
ok so if you have this then:
{ "Font;common", "Track.wav",
StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(),
StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(),
"Preset Title"
},
.....................
BladeConfig blades[] = {
{ 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin1, bladePowerPin2, bladePowerPin3> >(),
WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
SimpleBladePtr<CH1LED, CH2LED, NoLED, NoLED,bladePowerPin5, bladePowerPin6, -1, -1>(),
CONFIGARRAY(presets) },
};
And your buttons aren’t lighting, and you suspect a pixel strip in there, then you could try putting a pixel blade definition with all the power pads, and start at bladePin3 and work your way up.
If you get the buttons to light, next you can use LengthFinder<> to see how many pixels it is.
Then you can narrow down which LED pad. It might be shared, who knows.
1 Like
Any you can give an example of what that might look like and where I would put it in the code?
Sorry for being such a noob here, I know how to adjust numbers in increments of one and reflash, but that is about it…