Button stopped functioning on Ezra saber after upload

ProffieOS
41

I do not understand what that means ? What is the first session ?

42

this is also incorrect:

{ 0, WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3>>(),
    WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
    WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(blaster),
"01_BlasterSave"},
 
 { NO_BLADE,WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin6> >(),
    WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
    WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(saber),
"00_SaberSave"},

NO_BLADE is the blaster, when you remove the blade, you go from saber to blaster, so it should be:

{ 0, WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3>>(),
    WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
    WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(saber),
"00_SaberSave"},
 
 { NO_BLADE,WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin6> >(),
    WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
    WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(blaster),
"01_BlasterSave"},

The first style of your Preset saber presets is your main blade so you donā€™t want StylePtr<Black>(),

But in Preset blaster presets that is when you can have the first style StylePtr<Black>(),

Also you will need these two directory on your SD card: ā€œ00_SaberSaveā€ & ā€œ01_BlasterSaveā€

43

I meant section. meaning the blade section of the config and blaster section. the first set of identifiers, I guess.

Thanks a lot for looking into it for me. I really appreciate it. looking forward to trying it out when I get some time this evening.

how do I do this? the sd card came with a 01_blastersave folder but not 00_sabersave.

44

you just create a folder, if you are using windows, open sd card in explorer, right click, new, folder, type the name (or copy/paste) make sure it is spelled the same including respecting the capitals.

For your saber/blaster presets, it depends what you want. They donā€™t need to have the same soundfonts if you donā€™t want.

You can have 20 sabers and 2 blasters or 10 and 10 or what ever combination you want as long as you have enough flash memory in the Proffie board. (I have 20+ sabers, 5 blasters)

Edit, I have 41 sabers, 5 blasters, 1 detonator, 2 jetpacks & 1 morsecode presets. Instead of using dual_prop.h, I am using multi_prop.h (multi_prop.h, jetpack_prop.h & morsecode_prop.h are all work in progress)

45

These will be created automatically by the OS based on what name you give them in the blade config.

46

Thanks NoSloppy, I must have miss-understood, I thought they needed to be manually created or POS wouldnā€™t work properly. Sorry about that.

47

No apology needed. Just setting the record straight on how it works.

1 Like
48

okay, friends, so I figured some things out, but I am still just clueless about this thing. itā€™s working pretty well right now. definitely passable. but the config is still all screwy.

I did finally figure out one thing that you guys probably knew all along. I didnā€™t recognize the third ā€œblackā€ blade in each of the profiles. that, I believe, is the blaster light. if it is not black, it stays lit up the whole time the blade is lit.

also, it appears that I have to have the blade profiles written out in both the blaster section and the blade section, or it doesnā€™t work. does that make sense? I now have all blade profiles identically written out in both sections. if I remove them from either section, it doesnā€™t work. I get either all fonts and no lights. or no lights and spoken error code of something not found.

NoSloppy, you helped me switch the two modes from what they were originally. Meaning, the switch used to be up for blaster mode and down for blade mode. now it is vice versa. did we need to do that? not sure if that was part of the solution or a random thing we tried and I just never switched back.

anyways, itā€™s fine as is, so I at least have a working config, imperfect as it may be, I am still hoping to be able to switch it to Fett controls to add edit edit mode and such. Iā€™m going to try to switch the confines that one of you mentioned above.

thank you again for taking the time to look into it for me. Iā€™ll post the config in case either of you are curious and want to take a look. Iā€™m still a newb with all this, but slowly getting better. I got a little cocky after having luck with several ā€œnormalā€ sabers. this blaster config has been a bit of a trip!

thanks again.

49

Great news. Donā€™t know how, but everything is working exactly how I want it to now. I was able to get Fettā€™s prop uploaded with edit mode and Ezraā€™s voice commands, etc. Now my son can edit from the hilt, which is huge. Blaster and saber both working perfectly. I added several of our favorite blade styles and fonts, including some interactive ones. Everything is working great. Iā€™m fairly certain the config doesnā€™t look at all like its supposed to, but it works! thanks again a ton for all your help. couldnā€™t have done it without you, for sure. very happy ending.

I tried to mark the most applicable message you gave me as the ā€œsolutionā€. I hope that was right.

hereā€™s where the config is now if youā€™re curious:

1 Like
50

Yeah, I donā€™t know why you have your saber and blaster reversed.
When you remove the blade, the NO_BLADE blade array should be called, and the CONFIGARRAY(blaster) line would make the Preset blaster[] array active.
Then vice-versa, inserting a blade triggers the other blade array, CONFIGARRAY(saber) is called, activating your Preset saber[] array .

But if youā€™re happy with the way it is working, then great.

1 Like
51

I have no idea. but the way you switch to blaster mode has nothing to do with the blade being inserted or not. there is a switch. if the switch is up, it is in blade mode. if it is down it is in blaster mode. having a blade inserted makes no difference. if it is in blade mode without a blade inserted, it lights up the pixels on the pogoboard.

another weird thing I noticed is that even though the blade profiles apparently need to be indicated in both sections, it doesnā€™t seem to take up any more of the flash memory. they donā€™t appear to take up double memory when I add them to both sections?

Iā€™d like to look into the blaster prop a little more to see if I can add more sounds and customization to the blaster. the only sound I can get it to make is the sound labeled ā€œstunā€ in the blaster file on the provided sd card. I figured out how to change that one sound, but there are a ton of other blaster fonts in there that itā€™d be nice to be able to access.

anyways, yes, itā€™s working how I was hoping now. and I know how to edit it moving forward to add blade styles and everything. thanks again for all your help. this was my favorite part:

that was awesome.

also, very coincidental side note. I pulled up this thunderstorm font that I was going to add to the saber that I found somewhere awhile ago and kind of forgot I had:

Thunderstorn ProffieOS Blade Style/ - NoSloppy

appreciate your contributions to the community :smile:

52

Thatā€™s just because you are using the physical switch instead of the blade to perform the latching. So wherever I said blade in or out, it meant your switch up or down. Same difference.

They absolutely do not. Each preset array contains an individual , isolated set of presets to use while your switch is in that position.

Duplicating presets exactly will take virtually no memory. Only unique code does. Once the compiler has seen a string of code, itā€™s done. Seeing it again it says ā€œI already know how to do thatā€ and doesnā€™t use any additional memory to compile it.

The blaster prop is set to start in stun mode to begin with. You can change that by using #define DEFAULT_BLASTER_MODE MODE_KILL in your config.
The idea is that you can cycle between stun, kill, and autofire mode, but you donā€™t have more than one button, so youā€™re sort of stuck.
Reload, jam, empty, and other sounds all work mostly due to being able to do more things due to more buttons.
The top of the prop file itself has all the instructions for how it works, not sure if youā€™ve read through that yet.

You can edit the prop file to do things like ā€œwhile holding fire, clash the blasterā€ to change modes or incorporate some other gesturesā€¦ or just add another button.