So the question is: @lil_hubby, what ProffieOS version are you using ?
Yes I am using the correct config. I have been making sure the one I’m editing is the one being uploaded to the board.
I believe I am using 7.14. How could I double check?
Using version in the serial monitor should tell you.
Sorta a side topic but relevant here.
Clarify please as that term “cargo cult” refers to old-hat inclusion in programming while what I suggest refers to honestly just keeping up with basic housekeeping. I was taught, and this was later reiterated that if you’re going in and doing a reprogram it’s best either way to remove old stuff (tmp and ini files) that shouldn’t be in there for any reason other than for the use while running the current program, not what you’re replacing it with. Why? Because regardless of the define being in or not in there it gives the user a clean slate to test with.
That said, I do get what you mean about clarifying my question.
@lil_hubby Idea of the Day: A few of us take our freshly downloaded versions and edit the intro line in Arduino as that is the best spot to “see” what version you’re on quickly and easily. 
Example
/*
ProffieOS Control software for lightsabers and other props.
http://fredrik.hubbe.net/lightsaber/teensy_saber.html
Copyright (c) 2016-2019 Fredrik Hubinette…
*/
Becomes
/*
ProffieOS_7.14 01_05_2024: Control software for lightsabers and other props.
http://fredrik.hubbe.net/lightsaber/teensy_saber.html
Copyright (c) 2016-2019 Fredrik Hubinette…
*/
Changing the little bit of info in that line does nothing other than give you a heads up. 
Good idea.
We already sort of do this to the version string, which can be found further down, but it would be hepful to put it at the top too.
In this case, cargo cult refers to mimicking behavior with little or no understand of why it works (or doesn’t work) Generally speaking, deleting the INI/TMP files is not necessary. For most people it’s extra work, does nothing and could potentially cause SD card corruption. There are cases when it might help, but for those cases, we should explain to people why it might be needed and that it generally only needs to be done once.
Some people delete their INI/TMP files every time. Some people run zadig every time. Some people press BOOT+RESET every time. Some people re-install all their fonts every time. Some people probably knock on wood every time they hit upload… Without understanding, all of this is “cargo cult”.
@profezzorn I shouldn’t be laughing because THAT I also get. 
You all, well those above my station, deal with it a ton more than some of us and I appreciate (on so many frustrating levels) that nobody else, let alone cheap hot-shot drop-ship sellers really follow any sort of standardized set of protocols or steps. Yeah, it would be great to have that happen. In the meantime obviously we all do get stuck hunting snipes.
That said there’s merit to what I was taught and honestly what @NoSloppy later reiterated to me. It works for Mac stuff, but that’s likely pertinent only to the Mac and how and what I/We may be doing at a specific level and totally may or may not apply to the masses. Right?
Have a Great Evening Professor, I appreciate ya!
EndSideTopic
Begin tl;dr
@lil_hubby let’s try a different approach, something simpler. The way we’re gonna track if things work is by using only the first blade preset and changing your upper chamber to green and lower chamber to blue and track what happens after the flash. Try this edited config by copying and pasting it onto your specific config, and be sure to hit SAVE using Sublime Text in C++ Mode to replace what your current config is. DON’T WORRY, I left it reversible. Now flash it over using Arduino.
As far as your SD Card goes, for the purposes here, YES please DELETE the ini and tmp files and EMPTY THE TRASH before you disconnect the saber or SD Card so we’re sure they clear.
Got it? I’ve commented out the original setup colors on the first preset and you can always go back to it if you wish. If the changes take and it’s no longer white we’ve made progress. If not then we can look deeper.
Sorry for the late response been working. But I am on 7.15 of Proffie OS
I’ll definitely do that for future versions thank you!
I did everything as you said to the letter and unfortunately it’s still white.
Can you post your latest config. Something doesn’t add up.
Did you do the:
And did you get a compile error, after deleting the “S” ?
Here is the paste from @A_Rogue_Child , but I still copy and pasted it to a new document. I deleted the “S” and I got an error.
Paste: copy pasted - Pastebin.com
Ok, that’s good, now you can put the “S” back.
Would you be willing to try the most basic preset config possible ? Only one preset, fixed single colors (different for each blade) that will be ON all the time (while powered):
#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 3
#define NUM_BUTTONS 2
#define VOLUME 2500
#define BOOT_VOLUME 100
const unsigned int maxLedsPerStrip = 155;
#define CLASH_THRESHOLD_G 3.5
#define ORIENTATION ORIENTATION_NORMAL
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#define SAVE_VOLUME
#define DISABLE_DIAGNOSTIC_COMMANDS
#define NO_REPEAT_RANDOM
#define FETT263_TWIST_OFF
#define FETT263_THRUST_ON
#define FETT263_THRUST_ON_NO_BM
#define MOTION_TIMEOUT 60 * 10 * 1000
#define IDLE_OFF_TIME 60 * 10 * 1000
#define FETT263_MULTI_PHASE
#define FETT263_EDIT_MODE_MENU
#define ENABLE_ALL_EDIT_OPTIONS
#define DISABLE_BASIC_PARSER_STYLES
#define FETT263_SAY_BATTERY_PERCENT
#define FETT263_SAY_COLOR_LIST
#define FETT263_SAY_COLOR_LIST_CC
#define FETT263_DISABLE_COPY_PRESET
#define FETT263_HOLD_BUTTON_LOCKUP
#endif
#ifdef CONFIG_PROP
#include "../props/saber_fett263_buttons.h"
#endif
#ifdef CONFIG_PRESETS
//Blade Styles Start
Preset presets[] = {
{ "STARFALL;common", "/tracks/March.wav",
//Main Blade
StylePtr<Blue>(),
//Upper Chamber
StylePtr<Red>(),
//Lower Chamber
StylePtr<Green>(),
"starfall"},
};
//Blade Styles End
//Blade definitions Start
BladeConfig blades[] = {
{ 0,
//Main Blade - Data Line 1, power 2 & 3
WS281XBladePtr<122,bladePin,Color8::GRB,PowerPINS<bladePowerPin2,bladePowerPin3>>(),
//Chamber Upper
WS281XBladePtr<1,blade2Pin,Color8::GRB,PowerPINS<bladePowerPin4>>(),
//Chamber Lower
WS281XBladePtr<1,blade3Pin,Color8::GRB,PowerPINS<bladePowerPin5>>(),
CONFIGARRAY(presets)
},
//Blade definitons End
};
#endif
#ifdef CONFIG_BUTTONS
Button PowerButton(BUTTON_POWER, auxPin, "pow");
Button AuxButton(BUTTON_AUX, powerButtonPin, "aux");
#endif
If this still gives white in your crystal chamber, then it’s a baffling hardware problem.
1 Like
I just noticed, why is this 155 ? It should be 144!
I saw that in OP’s original paste and left it alone for now focusing on just editing the color ways on the three blades of the preset. I’m down to it being a hardware issue at this point although I’ve never seen a LED burnout or a short occur that makes it go white rather than a primary color.
Maybe also try dimming things down and see if it still is at the same output or not versus just open the hilt up and look closer…
I tried your config and changed to 144. Unfortunately, still white. I’ll have to send this to someone who can fix it.
And your main blade was what color after flashing the new config ?
As @A_Rogue_Child said:
If you want to test dimming, you can use this:
//Blade definitions Start
BladeConfig blades[] = {
{ 0,
//Main Blade - Data Line 1, power 2 & 3
WS281XBladePtr<122,bladePin,Color8::GRB,PowerPINS<bladePowerPin2,bladePowerPin3>>(),
//Chamber Upper
DimBlade(50.0, WS281XBladePtr<1,blade2Pin,Color8::GRB,PowerPINS<bladePowerPin4>>()),
//Chamber Lower
DimBlade(50.0, WS281XBladePtr<1,blade3Pin,Color8::GRB,PowerPINS<bladePowerPin5>>()),
CONFIGARRAY(presets)
},
//Blade definitons End
Do you see a difference in brightness ?