← Cafe

A collection of ideas & wishes, part 2 translated

Public Talk › Cafe · Started by MikeBravo on 26 November 2025 12:5726.11.2025 12:57
MikeBravo 26 November 2025 12:5726.11.2025 12:57
Hello everyone,

Here are a few more ideas/wishes from me for what I think would be a great feature/app for the VBar:

1. Local Updates:

Since I'm a lazybones and usually don't feel like getting the helicopter off the shelf, finding a LiPo battery, and turning everything on just to do an update, I often postpone it until I get to the flying field. But then you still have to set up a hotspot with your phone just to install updates. :-)
My idea is this: at home via Wi-Fi, you could simply download all available updates to the VBar Control beforehand. The 4 GB of internal memory should be more than enough for that. Then, the next time you switch on the helicopter, you could perform the update directly, without needing a hotspot or internet connection at the airfield.
Since the VBar Control doesn't know which software version is currently installed on the VBar without a connection, in my opinion you could simply save all available software versions locally on the VBar Control (there aren't that many).

2. Automatic Update Notices:

Since you release minor updates and bug fixes quite regularly, it would be great if the Mikado News app would notify users, for example, "Bugfix XYZ is available." This would encourage users to regularly update their VBar Control and keep the software up to date. (And it's good advertising too, as it lets users know that the software is constantly being improved and maintained.)
Even better, however, would be a solution like those used on Android or Apple phones. Small updates run automatically in the background, while larger updates are displayed (ideally with a changelog) and can then be manually approved.

3. Auto Rotation Rescue:

Since I finally want to practice autorotations next season, here's another idea that could make the whole thing more relaxed:

If you set the motor switch to autorotation and then trigger the rescue function, the stabilizer not only tries to save the helicopter, but also starts the motor at the same time.
In comparison to a normal rescue, it might also be useful here for the rescue to remain active for a little longer, so that the helicopter is definitely back at a safe altitude and position.
It would be necessary to consider that the engine switch would still be in the autorotation position. The pilot would then have to switch the engine back to the "engine on" position before another autorotation rescue is possible. A corresponding announcement or warning message would probably be the best solution here.

4. Inverted Rescue / Rescue 2.0:

Why would I want an inverted rescue system? Either I've lost my bearings a bit and I want to realign the helicopter, or things have gone seriously wrong and the helicopter is about to crash into the ground (which I obviously want to prevent at all costs).
Currently, in its inverted state, the VBar performs a flip and then climbs away. This works perfectly as long as the helicopter is relatively stationary. However, if you're approaching the ground at a significant speed, you might miss those crucial milliseconds that would otherwise prevent a crash.

Other systems (OMP (OSF3), Rotorflight, Spirit) have, in my opinion, solved this more elegantly. Here, the helicopter first aligns itself horizontally (normal or inverted), actively climbs away, and only then, if necessary, is it rotated back into the normal horizontal orientation (see image 1).
Additionally, I think it would be great if the rescue system could be personalized a bit more. Personally, I'd like a rescue system that levels the helicopter as quickly and forcefully as possible and then only lets it climb a few meters.
Currently, you can essentially only adjust the rescue pitch, nothing more. However, if you increase it too much, the rescue will work better, but then the helicopter tends to transform into a Saturn V rocket and try to launch towards the moon, which isn't exactly the desired outcome.
Since these are functions that beginners don't necessarily need to deal with, it would make sense, in my opinion, to place such things in an expert menu.

5. Waking from standby in both directions:

It's really quite basic; currently, the VBar Control can only be woken from standby with a swipe from right to left. I think it would be nice if it also worked the other way around, from left to right :-)

6. VBar Evo USB Sim Mode:

I am currently using an old VBar Neo connected to a Betaflight flight controller (in USB HID_CDC mode) to use VBar Control for sim flying, as I am absolutely not a fan of a wired solution and the UDP/WLAN solution only works with Heli-X and then only if you are on the same WLAN and the router is configured correctly (as soon as you are not on the home network, it tends to cause problems).
My proposed solution would be dedicated simulator software (like VPlane) installed directly on the VBar Evo. The VSim adapter and VSim app were also available at one time. Then you would only need to connect the Evo to the PC via USB and could use the VBar Control wirelessly with virtually all simulators.

7. VPlane further development:

The last major update for the VPlane software was a few years ago now. I would really like to see another update. The hardware around VPlane, such as the VBasic receiver, satellite receiver, extender, and so on, is, in my opinion, very mature by now; it's just the software that's somewhat outdated.

Yes, in principle you can program pretty much anything you want with the VPlane software and macrocells, but unfortunately, it's not really simple or intuitive. The user interface and programming with macrocells are not very inviting for beginners. You first have to watch several videos about macrocells and also know, for example, that there's a separate vector control app that you also have to unlock.

I currently fly fixed-wing models with a Spektrum transmitter. Its user interface is so simple that in most cases I don't even need the manual to program wing mixers or similar functions. Although I'd really prefer to only take one transmitter to the flying field when I'm flying both helicopters and fixed-wing aircraft.
But there's no need to reinvent the wheel. My main goal is a simpler and clearer user interface, so that most settings and area mixers can be configured without macro cells, which would significantly simplify the overall programming.
However, since every user naturally has different ideas and requirements, it would also be useful in this context if other users could comment on what an ideal solution would look like for them.

8. Display event log events in the flight graph:

I currently find it somewhat cumbersome that one always has to switch back and forth between FlightGraph Beta and the event log (in the web browser) if one wants to find out whether relevant events occurred during the flight.
I think it would be better if the flight graph offered the option to display status messages, notes, or warnings directly in the graph at the relevant times. This would be similar to the current ability to show or hide individual values like current or voltage.
In this context, clearer naming would also be helpful. I suspect that many people aren't aware that the regular Flightgraph is sorted by flight time, while Graph Beta displays the data by time of day.

9. Advanced parameter linking:

Personally, I would like to see more customization options for the individual flight banks. Currently, you can only use three banks with different RPMs. However, I also like to fly with different agility at the same RPM. While this is possible, it uses up two banks just to have different agility at the same RPM.
Therefore, I think a more advanced parameter linking system would be useful. Currently, you can only assign a single parameter to a switch. It would be practical if you could assign multiple parameters per bank, such as maneuverability, control response, stop assist, etc., to a single switch. Essentially, three sub-banks per bank. This way, you could adjust the helicopter's behavior from smooth and relaxed to hardcore 3D at the same head speed.

10. Search on VStabi.Info:

Quite simply, the search function on VStabi.Info is currently broken and only returns an error message (see image 2):

warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /var/www/vhosts/vstabi.info/httpdocs/modules/search/search.module on line 334.

The search query must contain at least one valid keyword with at least 3 characters.


No matter what you search for, even simple terms like VBar, VSim, or update, you get the error message. This issue is browser-independent and occurs in Edge, Chrome, and Firefox alike.
And the search function is only available when you're logged in. I think it would be better if you could use the search function without an account. Then interested or new users could quickly find things on the site.



And if you ever need a guinea pig for new software or beta software, I'd be happy to volunteer :-)

Regards, Kilian



[Part 1: https://www.vstabi.info/forum/read.php?42,204062,204079 ]



Edited 3 time(s). Last edit at 11/26/2025 01:04PM by MikeBravo.

machine-translated from German · Show original
Eddi E. aus G. 26 November 2025 14:0926.11.2025 14:09
Hi,

6. This already works. Program the EVO Pro (or VBasic, or RX-Only) with macrocells as the sum signal output PPM8 or 12 / Rev., and connect ground and signal from AUX1 to the stimulator adapter.
Then, feed cells E1ff. with sticks and switches as required by the simulator.

10. The entire site is to be revised, but that will be a mammoth task, and will probably only include current content, not the collected works of the last almost 20 years, which will probably still be available in read-only mode.

Semi-pro tip: Google (site:vstabi.info #search term) ... that works quite well.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
MikeBravo 26 November 2025 16:1226.11.2025 16:12
Eddi E. from G. wrote:
-------------------------------------------------------
Hi,
>
> 6. already works. EVO Pro (or VBasic, or
> RX-Only) with macrocells as sum signal output
> Program PPM8 or 12 / Rev., and mass and
Send a signal from AUX1 to the stimulator adapter.
> Add cells E1ff. and so on, using sticks and switches.
> Feed it as the simulator requires.


Yep, that's exactly how I've currently set it up with a VBar Neo. I'm using a Betaflight flight controller as the simulator adapter. It works in principle, but the Neo constantly complains that it's only receiving an input voltage below 4.5V, since it's powered exclusively via USB. The log is then always filled with thousands of lines: Warning; Voltage drop below 4.5V :-)

I think it would be great if you could simply connect an Evo directly to the PC via USB and use it as a simulator adapter without any additional adapter or other hardware.



> 10. The entire site should be revised so that
However, this presents a mammoth task, and will likely be...
> Only copy current data, not the collected data
> Works from the last almost 20 years, which will then
> read-only version will probably still be available.


If you ever completely redesign the site, I think it would be good if all the information were accessible in a Wikipedia-like structure, for example based on MediaWiki.



> Semi-Pro Tip: Google (site:vstabi.info
> #searchterm) ... that works quite well.

That's exactly what I'm doing right now too :-)



Edited 6 time(s). Last edit at 11/26/2025 05:12PM by MikeBravo.
machine-translated from German · Show original
Eddi E. aus G. 27 November 2025 09:1527.11.2025 09:15
Good morning,

Hmm, but doesn't USB supply 5V?

Just for fun, I reinstalled it with my old Chinese adapter, a five-minute job, AUX1 -> PPM 8 rev. 20 ms; assign E1ff transmitters, while checking in HELI-X that something is happening for all inputs, then move the sticks as instructed, move the switches as instructed, motor bank control – it works.

I have no idea if the USB port of a virtual stabilization unit could be configured as HID, and what kind of effort that would entail... it's an idea, though: an app, tick a box, done. On the other hand, WiFi is available and works; an app, tick a box, done, I don't even need a stabilization unit for that.

Grüßle

Eddi

Born to fly ...
forced to work.



Edited 2 time(s). Last edit at 11/27/2025 09:18AM by Eddi E. aus G..

machine-translated from German · Show original
MikeBravo 27 November 2025 10:2127.11.2025 10:21
Hi,

In theory, yes, USB should supply 5V. However, the USB specification already allows deviations of ±5%, and even up to 4.45V at USB hubs. My flight controller likely also "swallows" a few millivolts, so that the stabilizer ultimately receives an input voltage of about 4.3–4.4V.

But I also want to give you guys a shout-out: The stabilizer and VBar Control handled the low-voltage warnings without any problems, cleanly logged everything, and continued to run stably. After about 30 minutes of sim flying, you can easily accumulate over 10,000 log lines, or around 600,000 characters, without any issues whatsoever. 8-)

Regards, Kilian



Edited 2 time(s). Last edit at 11/27/2025 10:32AM by MikeBravo.

machine-translated from German · Show original
Eddi E. aus G. 27 November 2025 11:0127.11.2025 11:01
Hi,

Even though this is drifting into off-topic :-) ... the 'thing' I have doesn't actually have a power supply for anything, only for itself.
Normally, there would only be a jack plug cable with ground and signal, and whatever is connected to it would need its own power supply, such as a transmitter with a student socket.

Instead, I simply tapped directly into +5 VCC and GND with a patch cable to power the stabilizer itself, which only needs a few mA, and connected the signal cable where the signal should arrive.
Just don't try to run a servo on it, otherwise you'll fry the USB hub, the computer port, or worse ;-)

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
Chriss 31 December 2025 08:2631.12.2025 08:26
Hello Mike Bravo,

Those are great ideas.

What about point 7?
"7. VPlane Further Development"

Is there an internal roadmap for this? Or does it look like the V-Plane is slowly but surely being phased out?

Thank you very much

Kind regards
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless