I upgraded from Proffie OS 5.something to the latest 7 release, I used a config file that was on the SD card for my saber (Dark Wolf sabers config). Sounds and controls all work fine, and the power pins appear to be correct to how the core is soldered, but just no go on the blade lighting up.
I also have a Xeno3 core and the two blades I have both work fine with it. I figure there is something odd in the config file that is making it not work, but wondering if anyone has any suggestions or a basic t-shooting config I can try to just make sure the blades still work at all and I didn’t somehow toast the board.
Have you flashed this saber before with the same config file?
My suspicion is that the installer sent you a config file that doesn’t quite match the actual installation.
ProffieOS is generally very compatible between version.
Since you checked the power pins, I would try to verify the data pin next.
And post your config file, just in case there is something odd in there.
I have not flashed it before, at all, this is my first time finally tinkering with it. I’m familiar with the basic structures of scripting/coding, but the syntax here has its own flavor for sure.
That…seems to have fixed it, thanks! I have two blades, one with more pixels than the other, is it possible to switch blade length configs on demand, or do you have to re-flash every time?
Now I want to start to dig into making custom blade styles…could get interesting.
edit mode (lets you change the length with a setting.)
Blade ID is automatic, but only works if the hilt can tell the difference between the blades.
Using the setting means you have to change it every time you swap blades.
Hopefully there will be a third way of doing this when OS-8 ships (if my button prop makes the cut) by having two separate blade arrays - one for each blade length. Each blade array would point at the same preset array. It means that all you’d need do is three quick clicks of the button to switch between the two blade lengths.
