Blaster build proffieboard V2

21

When you post you error code, please use the 3 back ticks method, like this:

```
your error code here
```

because it makes it a lot easier to read.

You can also edit your previously posted errors, if you don’t mind.

22

Without the 3 back ticks, I can’t read the errors

23

line 56, also remove the “}”

Edit, no, that is not it, but you have one too many “,” or “}” somewhere or a missing “;”

Edit2, you are missing a “};” after line 45, sorry about the edits
Edit3, you can put the missing “};” on line 46
Edit4, you should have this:

#ifdef CONFIG_PRESETS

Preset presets[] = {

// Default basic blast color with red audio flicker on blast
{ "E-11", "tracks/mars.wav",
StylePtr<Lockup<BlastFadeout<BlastFadeout<Black,AudioFlicker<Black,Red>,250,EFFECT_FIRE>,AudioFlicker<Black,Blue>,1500,EFFECT_STUN>,AudioFlicker<Black,Red>>>(),
StylePtr<Lockup<BlastFadeout<BlastFadeout<Black,AudioFlicker<Black,Red>,250,EFFECT_FIRE>,AudioFlicker<Black,Red>,1500,EFFECT_STUN>,AudioFlicker<Black,Red>>>(),
"E-11"
},

{ "E-11D", "tracks/EzraTheme.wav",
StylePtr<Layers<AudioFlicker<RotateColorsX<Variation,Blue>,RotateColorsX<Variation,Rgb<0,0,128>>>,BlastL<White>, InOutTrL<TrInstant,TrFade<300>,Pulsing<RotateColorsX<Variation,Blue>,RotateColorsX<Variation,Rgb<0,0,10>>,3000>>>>(),
StylePtr<Lockup<BlastFadeout<BlastFadeout<Black,AudioFlicker<Black,Red>,250,EFFECT_FIRE>,AudioFlicker<Black,Red>,1500,EFFECT_STUN>,AudioFlicker<Black,Red>>>(),
"E-11D"
},
};

BladeConfig blades[] = {
{ 0, WS281XBladePtr<144, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),
WS281XBladePtr<20, blade2Pin,Color8::GRB, PowerPINS< bladePowerPin4> >(),
WS281XBladePtr<1, blade3Pin,Color8::GRB, PowerPINS< bladePowerPin5> >(),
CONFIGARRAY(presets) },
};

#endif
24 
Arduino: 1.8.19 (Windows 10), Board: "Proffieboard V2, Serial, SDCARD (SPI), 80 MHz, Smallest Code"











In file included from C:\Users\duart\OneDrive\Desktop\ProffieOS\ProffieOS.ino:621:
C:\Users\duart\OneDrive\Desktop\ProffieOS\config\benoblaster1_config.h:49:13: error: expected primary-expression before 'blades'
   49 | BladeConfig blades[] = {
      |             ^~~~~~
C:\Users\duart\OneDrive\Desktop\ProffieOS\config\benoblaster1_config.h:49:13: error: expected '}' before 'blades'
In file included from C:\Users\duart\OneDrive\Desktop\ProffieOS\ProffieOS.ino:621:
C:\Users\duart\OneDrive\Desktop\ProffieOS\config\benoblaster1_config.h:32:20: note: to match this '{'
   32 | Preset presets[] = {
      |                    ^
In file included from C:\Users\duart\OneDrive\Desktop\ProffieOS\ProffieOS.ino:240:
C:\Users\duart\OneDrive\Desktop\ProffieOS\props\prop_base.h: In member function 'size_t PropBase::FindBestConfig()':
C:\Users\duart\OneDrive\Desktop\ProffieOS\props\prop_base.h:567:25: error: 'blades' was not declared in this scope; did you mean 'bladePin'?
  567 |     static_assert(NELEM(blades) > 0, "blades array cannot be empty");
      |                         ^~~~~~
C:\Users\duart\OneDrive\Desktop\ProffieOS\common\common.h:18:26: note: in definition of macro 'NELEM'
   18 | #define NELEM(X) (sizeof(X)/sizeof((X)[0]))
      |                          ^
In file included from C:\Users\duart\OneDrive\Desktop\ProffieOS\props\blaster.h:34,
                 from C:\Users\duart\OneDrive\Desktop\ProffieOS\config\benoblaster1_config.h:25,
                 from C:\Users\duart\OneDrive\Desktop\ProffieOS\ProffieOS.ino:625:
C:\Users\duart\OneDrive\Desktop\ProffieOS\props\prop_base.h: In member function 'void PropBase::FindBlade()':
C:\Users\duart\OneDrive\Desktop\ProffieOS\props\prop_base.h:622:22: error: 'blades' was not declared in this scope; did you mean 'bladePin'?
  622 |     current_config = blades + best_config;
      |                      ^~~~~~
      |                      bladePin
exit status 1
Error compiling for board Proffieboard V2.


This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
25

Is that any better. I did the 3 back ticks before and after.

1 Like
26

Check my edit 4. That should be good

27

I never have problems with the codeing on sabers. The blaster thing is a new one for me. Sorry.

28

It’s a problem of opening “{” and closing “}” brackets, they need to match, yours didn’t

29

The syntax errors you have had in this thread are not specific to being for a blaster. You would have the same errors if it were a saber config file.

Just make syre your presets look like this

30

Take a look at this page: ProffieOS Documentation: The CONFIG_PRESETS section because that is where your problem was.

31

Ok yes i will. I appreciate you. I been working 12 hour days 6 days a week for over a year i need to get back into it thanks.

32

All good. I started over. With one blade style . One blade .

33