First Saber Build – Need Help with Custom Blade Behavior (Tri-Cree+Proffieboard v3)

ProffieOS
21

But you said you have an illuminated switch. That’s your second blade.
Also not sure why you have a Blue Cree defined if you have a WWW Tri-Cree.

SimpleBladePtr<CreeXPE2WhiteTemplate<550>, NoLED, NoLED, NoLED, blade5Pin, -1, -1, -1>()
is incorrect because you are naming a data pad, not LEDpad 5.

Why not try starting simple, get one preset that works, then go from there.
Something like this,

#ifdef CONFIG_TOP
#include "proffieboard_v3_config.h"
#define NUM_BLADES 2
#define NUM_BUTTONS 1
#define VOLUME 500
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 1.0
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {

{ "TeensySF", "tracks/venus.wav",
  StylePtr<Layers<
    White,
    TransitionEffectL<TrConcat<TrInstant,Strobe<Black,White,15,15>,TrFade<300>>,EFFECT_CLASH>,
    TransitionEffectL<TrConcat<TrInstant,Strobe<Black,White,15,15>,TrFade<300>>,EFFECT_BLAST>,
    LockupL<Strobe<Black,White,25,35>,Strobe<Black,White,25,35>,Int<32768>,Int<32768>,Int<32768>>,
    InOutTrL<TrInstant,TrFadeX<WavLen<EFFECT_RETRACTION>>>,
    TransitionEffectL<TrConcat<TrInstant,Rgb<40,40,40>,TrFade<1000>>,EFFECT_IGNITION>>>(),
  StylePtr<Layers<White,InOutTrL<TrInstant,TrFadeX<WavLen<EFFECT_RETRACTION>>>>>(),
"white"},

};

BladeConfig blades[] = {
 { 0,
  SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2WhiteTemplate<550>, CreeXPE2WhiteTemplate<550>, NoLED, bladePowerPin1, bladePowerPin2, bladePowerPin3, -1>(),
  SimpleBladePtr<CreeXPE2WhiteTemplate<550>, NoLED, NoLED, NoLED, bladePowerPin5, -1, -1, -1>(),
  CONFIGARRAY(presets) },
};
#endif

#ifdef CONFIG_BUTTONS
Button PowerButton(BUTTON_POWER, powerButtonPin, "pow");
#endif

“Jumps” to dimmer White, then fades to full brightness.
Clash, Blast, Stab, Lockup, and Drag all so a strobing thing.

22

I forgot I changed that to blue; it runs the same when it’s white white white though. just changed it back thanks for catching it.

I think you’re right, the illuminated button is why the website generated a config with two blades, but I don’t have it wired to bladePowerPin5; I have it wired to the 3.3v pin. so programming it in as another blade won’t work. Even still, it doesn’t make sense why removing the presets for the second blade would mess everything up like it did. Theoretically, it wouldn’t change anything, since the LED in the button isn’t programmed in as a blade anyway.

But like I said, even if I have this “dormant” blade in there, I’m fine with that as long as the saber acts how I want it to.

23

The flickering and all works! I’ll need to play around with some of the intensities, but thank you for that. I really need to learn to use that website haha.