VBar Settings Viewer

[RichardV]

I've created a utility to view NEO settings while disconnected from the model. It allows selecting multiple files for side-by-side viewing.

https://vbarutilities.azurewebsites.net/

It's mostly complete, just a few more values to figure out, but you can get almost all of them. Submit a few files and you'll get something like this.

[bigpops]

Good work.

You'll be please to know it works with files saved via the Vstabi Neo app (connected via USB) as well. So you can get your setups from the Neo that way, which is possibly quicker than over the radio link. I know restoring over the link is painfully slow, but over USB is virtually instatnt.

[RichardV]

Ah, that's good that they've kept the format the same. Hopefully the Touch will be similar.

A few of the settings are linked and making it difficult to unravel, like the governor limits and outputs but I'll have them soon enough.

The plan is to add descriptions and links to documentation on what each setting means, as well as suggestions for optimizing some of the values.

[nkma]

Great Utility!
I got my VBC three days ago, wednesday, and tried this utiity the next day, thursday.
I'm still at an early point in the VBC learning curve and will use two radios, but I expect to use this to document my setups.
Quite frequently I make observations flying and like to compare with setup later, without having to power up VBC and heli in the living room...

Then this utility will come in handy.

Save Result
I saved the result as a PDF-file on my computer.
This is how it came out.
191101_0200_VBar Utilities_Logo700.pdf

Close to perfect! If I would have a wish, that would be a little more left margin...

Out of curiosity
Just ignore, if you don't want to share, but how did you implement this?
I sense jQuery and Bootstrap on a MS cloud server, but am a little curious about how you read the "Mikado binary" and turn it into HTML.

/Bo

[RichardV]

Great, that's exactly why I made it. I used to put all the settings into a spreadsheet, but stopped due to the effort it took. I sent Mikado a message a while ago saying they should do something like this, along with an analyser for flight and battery logs that makes suggestions or shows warnings.

The Mikado file in is hex and there are 600 values. Each value is mapped to a setting by it's position, so position 101 is Mainrotor Style Bank 1.
I've mapped about 200 so far by changing a value in the vbar, saving and comparing. Some of it is made easier by blocks being repeated for current values, bank 1, bank 2, etc.

If there's any interest, I could put the parser on github.

BTW, I added a few more settings this morning, so you should be able to see the tail servo selection and a few more screens.

[nkma]

Just checked the new version and got some more and better tail info! Thank You!

I wish I could help figuring out the file content, but I haven't even learned to do screen dumps on the VBC yet, so I use the phone camera...

Slightly off-topic:
I don't know how well known it is, but I find this VBC utility also useful.

VBar Control flight analyzer:
VBar Control flight analyzer – Automatic logging and performance analyzer

Sample output:



/Bo

[RichardV]

No problem, I'm glad you're getting good use out of it. I'll sort the layout out once all the settings are done. The Swash mixer is a pain with all the linked values though.

I wish I could extend what Linus has done with the VBar Analyzer. Although I have a basic understanding of Javascript and Electron, he's using unfamiliar libraries and I can't get his code to compile. It's a pity, as it runs on Mac and Windows, and would have been perfect to add deeper analytics and the settings parser.

[andypaddlerking]

hey rich

hope your well.

been having a play with this and its been working great for me! thanks for the hard work you put in to making it.

Andy

[Mike Sanders]

All greek to me.