Alpha Testing - New ProffieOS Config Helper Tool

ProffieOS Fett263 Corner
31

Hi Fett! I’ve tried your tool and can’t find how to generate two things:

  1. The defintion of shared power lines for NeoPixels. When doing Blade ID you need to specify all the MOSFET that feed those lines.
#define ENABLE_POWER_FOR_ID PowerPINS<bladePowerPin2, bladePowerPin3>
  1. I put an SMD resistor between Data 1 and 3.3V so I can poll the “true” resistor value in Blade ID.
#define BLADE_ID_CLASS ExternalPullupBladeID<bladeIdentifyPin, 22770>

Another issue is that I have more presets than presetneopxl and presetnoblade. I use one stricly for charging modules, another for illuminated bladeplugs and fifth one for Shtok’s NPXL-TriCree adapter. All those need different style definitions than normal blades and no blades. That info is actually in the Blades definition, but even being able to manually add more blades preset, would help me enormously.

32

I haven’t used and never ran across those in documentation when researching the defines so they’re not there. Not sure how easy or hard they’ll be to add or when I’ll have a chance to look but I’ll see about them at some point.

33

Additionally, you’re setup is not a typical beginner use case, which is whom the tool is geared toward assisting.
You’re at like DEFCON 3 on the build complexity level meter.
(DEFCON scale goes from 5 (normal) to 1 (nuclear war))

1 Like
34

Fett has just explained in this thread, that if you use this tool, you get a printout of all the saber commands for the user. I do installs for friends and have not touched Battle Mode (in fact, have never configured anything but the saber.h prop), because I don’t want to deal with explaining it to them. But if this tool allowed to make a nice printout of all the commands, I would more than gladly enable all the bells and whistles since I can send them to RTFM. :rofl:

35

Ah. I usually just direct people to read the instructions already included right in the prop file itself, but I see now it tailors the output to be " based on the defines selected in the tools.
That’s cool.

36

Yeah, it’s intended to help “as many users or installers as possible” so I’ll certainly look at the missing defines.

For your purposes, those defines don’t actually affect controls so you could still use the tool to generate the config and print outs for Controls, Styles, Sound, etc. but then just add them in before you upload. Those do appear to be more obscure defines but I’ll try to get them in when I have a chance.

1 Like
37

I can add the obscure defines with no problem. I don’t know about the multiple presets in general. But I can add those presets myself, too. So it’s quite useful as it is.

38

Working well so far.

I wanted to add a basic save so I can start up where I left off in my presets.

Can you add a check box for #define SAVE_STATE as an alternative to the well documented #define KEEP_SAVE_FILES_WHEN_PROGRAMMING please?

1 Like
39

SAVE_PRESET got lumped in with ENABLE_ALL_EDIT_OPTIONS, I have moved it out separately. Just refresh to see it.

SAVE_STATE is actually just a combination of the ENABLE_ALL_EDIT_OPTIONS defines
with SAVE_PRESET added, so it’s not actually used in the tool to avoid confusion.

If you want to select/delect the other save/dynamic options simply uncheck ENABLE_ALL_EDIT_OPTIONS and they will appear individually and you can pick and choose which ones you want, but checking ENABLE_ALL_EDIT_OPTIONS automatically selects them all anyway (except for SAVE_PRESET) :wink:

1 Like
40

So I was really looking for SAVE_PRESET to just bookmark where I am when I power down.

Unchecking ENABLE_ALL_EDIT_OPTIONS in the Congfig Helper works great. SAVE_STATE is something I see I don’t really need.

Thanks!

41

Oops, just had to push a fix to the script so the define actually gets into the CONFIG_TOP. Just refresh again and it should work now.

1 Like
42

@Fett263 We tried ConfigHelper out again today. See the attachments since I also included a copy of my working config. :smiley:

OS6_Config.h (45.3 KB)

43

Here’s the working edit. Please let me know if there’s anything I missed.
confighelperedit.h (38.0 KB)

44

You didn’t read the instructions for BladeConfig section. There is a large box telling you EXACTLY what to do :wink:

1 Like
45

@Fett263 You are absolutely correct. I read that but we (Padawan and I) did miss the pixel count. There was something that got input out of confusion since she’s learning on line count 40-46 but I fixed it.

Screenshot 2023-02-10 at 4.32.21 PM
Screenshot 2023-02-10 at 4.32.21 PM1920×1070 157 KB

46

I have no idea what you’re asking or referring to. This tool just generates a config in the correct syntax based on the options selected, I have no idea what line count or board reading you’re asking about. It just creates a config.h file that’s all.

47

spaces and line returns are irrelevant

So this        is  just as             valid
as
if 
you        had it 
      all smooshed        
together         in a normal
    sentence
48

@Fett263 I should clarify. By “line count” I meant at which line(s) of the config when looking at it in Sublime the error or other thing is listed. As-in item-x is on line count (or line #s) 13 thru whatever.

49

Not sure how that would ever matter so the answer is no. The error you got was from not reading the instructions provided in the tool. The tool just outputs the config in the correct syntax based on selections made and presets you built. BUT if you paste the wrong things in the wrong text fields the tool has no way of knowing, hence all the time I put into writing the instructions that appear on the page. If you read the instructions AND follow them it will output a config without errors.

50

New and Improved version is now up and running for use and testing, I started a new thread since it’s essentially all-new.