The Web programmer page. Might be good for brand nubians

Yes, it should.
I suppose I could update it to actually show the error messages, but I don’t actually have enough processing power on my server for lots of people sitting around using trial-and-error to make it work. Not showing the error message discourages using it that way.

The V3 configuration generator has a lot of improvements, making it better at generate configurations, and it may also make the web programmer more useful.

I think if it would just work smoothly, you could sell it as a simple, quick way to upload, and leave the errors for Arduino. If someone could load it themself from the browser, all they would need is help cleaning up their configs, which is easily done online without screen sharing or anything (as opposed to walking someone through Arduino/Zadig). Then they could move on to troubleshooting configs when they gained confidence. I know it would have made it far simpler for me when I was learning.

Can the V3 configurator be used for a V2 board

Nope.
You could use it as an example, but that’s about it.

FWIW I just successfully pasted in a custom test config file and it worked fine.

#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 4
#define NUM_BUTTONS 1
#define VOLUME 1000
const unsigned int maxLedsPerStrip = 144; 
#define EXTRA_COLOR_BUFFER_SPACE 30
#define CLASH_THRESHOLD_G 3.5
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#define ENABLE_SERIAL
#define SHARED_POWER_PINS
#define SAVE_STATE
#define ENABLE_DEVELOPER_COMMANDS
#define IDLE_OFF_TIME 60 * 1 * 1000
#define MOTION_TIMEOUT 60 * 1 * 1000
#define FEMALE_TALKIE_VOICE
#define VOLUME_MENU_CYCLE
#define NO_REPEAT_RANDOM
#define ENABLE_SSD1306
#define OLED_SYNCED_EFFECTS
#define BC_STAB_ON
#define BC_THRUST_ON
#define BC_TWIST_ON
#define BC_TWIST_OFF
#define BC_FORCE_PUSH
#define BC_FORCE_PUSH_LENGTH 5
#define ENABLE_AUTO_SWING_BLAST
#define ENABLE_SPINS
#define BC_LOCKUP_DELAY 200
#define DISABLE_BASIC_PARSER_STYLES
#endif

#ifdef CONFIG_PROP
#include "../props/saber_BC_buttons.h"
#endif

#ifdef CONFIG_PRESETS

Preset saber [] = {

{ "TeensySF;common", "",
StylePtr<Stripes<16000,100,Red,Black,Green,Black,Blue,Black,White,Black,Rainbow,Black,Yellow,Black,Rgb<60,0,255>,Black>>(),
StylePtr<Pulsing<Black,Red,800>>(),
StylePtr<Pulsing<Black,Blue,800>>(),
StylePtr<Pulsing<Black,Green,800>>(),
  "1-TeensySF"},

{ "RgueCmdr;common", "testfont2a/tracks/track2.wav",
StylePtr<Red>(),
StylePtr<Pulsing<Black,Red,800>>(),
StylePtr<Pulsing<Black,Blue,800>>(),
StylePtr<Pulsing<Black,Green,800>>(),
  "2-RgueCmdr"},

{ "SmthFuzz;common", "testfont2a/tracks/track2.wav",
StylePtr<Green>(),
StylePtr<Pulsing<Black,Red,800>>(),
StylePtr<Pulsing<Black,Blue,800>>(),
StylePtr<Pulsing<Black,Green,800>>(),
  "3-SmthFuzz"},

{ "SmthJedi;common", "",
StylePtr<Blue>(),
StylePtr<Pulsing<Black,Red,800>>(),
StylePtr<Pulsing<Black,Blue,800>>(),
StylePtr<Pulsing<Black,Green,800>>(),
  "4-SmthJedi"},

};

BladeConfig blades[] = {
{ 0,  
  WS281XBladePtr<13, bladePin, Color8::GRB, PowerPINS<bladePowerPin1, bladePowerPin2> >(),
  WS281XBladePtr<14, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin3, bladePowerPin4> >(),
  WS281XBladePtr<14, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
  WS281XBladePtr<14, blade4Pin, Color8::GRB, PowerPINS<bladePowerPin6> >(),
CONFIGARRAY(saber),
"00_SaberSave"}, 

};
#endif

#ifdef CONFIG_BUTTONS

Button PowerButton(BUTTON_POWER, powerButtonPin, "pow");
Button AuxButton(BUTTON_AUX, auxPin, "aux");

#endif

Cool. Did you have to boot/reset?

nope.
First connect pairing was with Proffieboard.
Second connect when prompted again, this time STM32BOOTLOADER.
Compiled and uploaded.

Nice. I’ll give it a go when I get home. Stupid work schedule…

1 Like