Tool for comparing Vbar 5.3.x VBR files? - HeliFreak
Fun, Learning, Friendship and Mutual Respect START  HERE


Unregistered
Go Back   HeliFreak > R/C Electronics Support > Mikado V-BAR


Mikado V-BAR Mikado V-Stabi/V-BAR Flybarless System Software and Hardware Support


Reply
 
LinkBack Thread Tools Display Modes
Old 10-21-2017, 07:55 AM   #1 (permalink)
Registered Users
 

Join Date: Jan 2016
Location: Portsmouth, UK
Default Tool for comparing Vbar 5.3.x VBR files?

I am still using Mini V-bars on many helis. I remember there was a tool available a few years ago for comparing VBR files. But it was for older versions of the firmware. I wonder if there is such a tool available for the latest 5.3.x firmware (not Neo).

Cheers guys.

Last edited by Dr.Rudder; 10-22-2017 at 11:33 AM..
Dr.Rudder is offline        Reply With Quote Quick reply to this message
Sponsored Links
Advertisement
 
Old 10-22-2017, 11:32 AM   #2 (permalink)
Registered Users
Thread Starter Thread Starter
 

Join Date: Jan 2016
Location: Portsmouth, UK
Default

Really? Nobody knows or cares

Well, it does not look too complicated, maybe I can have a look if writing such a tool would be possible
Dr.Rudder is offline        Reply With Quote Quick reply to this message
Old 10-22-2017, 11:43 AM   #3 (permalink)
Registered Users
 
Posts: 2,374
 

Join Date: Mar 2011
Location: Gillette, WY, USA
Default

I think most are on vcontrol these days which is 6.0 and newer firmware and is not backwards compatible with 5.3 firmware including myself.

That being said it would even be nice to do it with vcontrol files. I went to look at Kyle and Stacy’s vcontrol files and couldn’t load one of them into the neo software cause the version I had was newer.


Sent from my iPhone using Tapatalk
tshelby73 is online now        Reply With Quote Quick reply to this message
Old 10-24-2017, 06:58 PM   #4 (permalink)
Registered Users
Thread Starter Thread Starter
 

Join Date: Jan 2016
Location: Portsmouth, UK
Default

I know I am behind the cutting edge, still using mini Vbars and other ancient stuff. Nevertheless, I think such a tool would be useful... so I wrote one!

Go ahead and download it from vbrtool.py

It's a small program written in python. I wrote it on Mac OS Sierra, which comes with Python 2.7.10. I gave it a little test on Linux too. I am afraid Windows users may need to Google how to install Python. Sorry.

Hope somebody finds it useful!

Quote:
VBRTool v1.0.0 - A tool for viewing and manipulating Mikado Vbar .vbr files

Vbrtool is a simple tool written in Python, for working with Mikado .vbr
files from VBar v5.3.x, either Mini or full size.

The tool has three main modes of operation.

1. Print parameters
2. Compare parameters
3. Copy parameters

The set of registers operated on is further selected by command line flags.

Print Parameters

The command line option -P or --print selects print mode. The values of the
selected registers are printed, for each input file.

Compare parameters

The command line option -D or --diff compares the register values in the
input files, considering only the selected registers. The registers that have
the same value in _all_ input files are not printed.

Copy parameters

The command line option -C <vbr-file> or --copy <vbr-file> copies the selected
registers from <vbr-file> to the other input files. Only the selected registers
are copied, all other registers stay unchanged.

Selecting Registers

The tool operates on a (sub)set of Vbar registers, which is selected by one of
the following options:

(none) The default is basic parameters on the settings page

-a, --all All known parameters
-r, --raw All registers from the input files

-m, --main Main rotor expert parameters on the settings page
-t, --tail Tail rotor expert parameters on the settings page
-g, --gov Governor expoert parameters on the settings page
-x, --exp All expert parameters on the settings page

-ms, --main-setup Main/swash setup parameters
-ts, --tail-seutp Tail setup parameters
-gs, --gov-setup Governor setup parameters
-rs, --rx-setup Receiver setup parameters
-s, --setup All setup parameters

Only one of these parameters can be used at a time.

Examples

Print basic settings from all input files:

> vbrtool.py --print bank0.vbr bank1.vbr

Print expert settings from all input files:

> vbrtool.py --print --exp bank0.vbr bank1.vbr

Print all parameters from all input files:

> vbrtool.py --print --all bank0.vbr bank1.vbr


Compare receiver setup between the input files:

> vbrtool.py --diff --rx-setup bank0.vbr bank1.vbr

Compare swash setup between the input files:

> vbrtool.py --diff --main-setup bank0.vbr bank1.vbr

Compare all registers between the input files:

> vbrtool.py --diff --raw bank0.vbr bank1.vbr


Copy governor settings from bank1 to bank2:

> vbrtool.py --copy bank1.vbr --gov bank2.vbr

Copy tail setup from bank0 to bank1 and bank2:

> vbrtool.py --copy bank0.vbr --tail-setup bank1.vbr bank2.vbr
Dr.Rudder is offline        Reply With Quote Quick reply to this message
Old 10-27-2017, 09:23 PM   #5 (permalink)
Registered Users
 
Posts: 1,108
 

Join Date: Apr 2009
Location: Sheffield, UK
Default

Nice. One question python related question though:

If it's python 2, how come you're using the print function from python3 - print('string') - instead of the keyword print<space>'string'?
__________________
Current fleet: Raptor E700, Trex 700L, Logo 600, Gaui X5, Trex 500 ESP, HiSKY HCP100S - Vbar Control - 5" and 3" FPV racing quads and a Taranis
Next heli(s): Logo 550, Logo 700 or a Goblin 700
Bigpops is online now        Reply With Quote Quick reply to this message
Old 10-28-2017, 08:56 AM   #6 (permalink)
Registered Users
Thread Starter Thread Starter
 

Join Date: Jan 2016
Location: Portsmouth, UK
Default

Good question. I am mostly using Python 3 at work, but did not want to install it on my mac. I was not paying attention on that detail when I wrote it.

In Python 2.7 'print' is a keyword rather than a function. So 'print(foo)' actually means print the array (foo), which reduces to 'print foo'. So it is the same thing in this case. With multiple arguments, like 'print(foo,bar)' it would not work correctly.

I can see I only used it with one argument, so it is working ok, though the syntax is not exactly correct.

I'll fix it next time I make changes.

Cheers!
Dr.Rudder is offline        Reply With Quote Quick reply to this message
Old 10-30-2017, 04:52 PM   #7 (permalink)
Registered Users
 
Posts: 1,108
 

Join Date: Apr 2009
Location: Sheffield, UK
Default

I understand. It's being interpreted as print being passed a tuple as an argument and not actually a function call, so it works itself out as you've written it.
__________________
Current fleet: Raptor E700, Trex 700L, Logo 600, Gaui X5, Trex 500 ESP, HiSKY HCP100S - Vbar Control - 5" and 3" FPV racing quads and a Taranis
Next heli(s): Logo 550, Logo 700 or a Goblin 700
Bigpops is online now        Reply With Quote Quick reply to this message
Old 11-27-2017, 02:20 PM   #8 (permalink)
Registered Users
 
Posts: 426
 

Join Date: Feb 2006
Location: Leicester, UK
Default

Do files saved by the VBar Control use the same format?

I'm trying to find something that parses the new format files as it's a pain to maintain a spreadsheet of the figures manually. For example Smacktalk have provided Bert and Kyle's files, but I can't see the values without loading them into a NEO.
__________________
MKMHC, LARCS, LMAC ~ T-Rex 700e ~ VBar Control ~ my flight log
richardv is offline        Reply With Quote Quick reply to this message
Old 11-27-2017, 03:36 PM   #9 (permalink)
Registered Users
 

Join Date: Jan 2007
Location: London
Default

Nope, the format is top secret
__________________
Oxy 2+ | Oxy3+ | Logo 480XX | 600SX | 650SX | 690SX | 700 | 700XX | VControl
mahbouni is offline        Reply With Quote Quick reply to this message
Old 11-27-2017, 04:32 PM   #10 (permalink)
Registered Users
 
Posts: 426
 

Join Date: Feb 2006
Location: Leicester, UK
Default

It looks to be a similar format to the breakdown used in the Python file above, just with different positions.
I changed a single value through the NEO app and viewed the change in hex, and you can see it's the new value. It's just figuring out what each position means.
I wonder how Dr.Rudder got all the registers for his script.
__________________
MKMHC, LARCS, LMAC ~ T-Rex 700e ~ VBar Control ~ my flight log
richardv is offline        Reply With Quote Quick reply to this message
Reply




Quick Reply
Message:
Options

Register Now

In order to be able to post messages on the HeliFreak forums, you must first register.
Please enter your desired user name, your REAL and WORKING email address and other required details in the form below.
User Name:
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself. Use a real email address or you will not be granted access to the site. Thank you.
Email Address:
Location
Where do you live? ie: Country, State, City or General Geographic Location please.
Name and Lastname
Enter name and last name here. (This information is not shown to the general public. Optional)
Helicopter #1
Enter Helicopter #1 type and equipment.
Insurance
Please select your insurance company (Optional)
Helicopter #2
Enter Helicopter #2 type and equipment.
Helicopter #3
Enter Helicopter #3 type and equipment.
Helicopter #4
Enter Helicopter #4 type and equipment.

Log-in

Human Verification

In order to verify that you are a human and not a spam bot, please enter the answer into the following box below based on the instructions contained in the graphic.



Thread Tools
Display Modes

Posting Rules
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




Copyright © VerticalScope Inc. All rights reserved.
 

SEO by vBSEO 3.6.1