← VBar Control Touch / EVO

RX SBus only - Model setup transferred translated

VBar Control › VBar Control Touch / EVO · Started by thomas1130 on 6 May 2026 15:0306.05.2026 15:03
thomas1130 6 May 2026 15:0306.05.2026 15:03
Hi :-)

Now that I've managed to get my hands on two of the new RX (1) only SBus receivers, I'd like to replace the existing (stripped) RX-7 only in my M2V3 with the new small RX...

Quick question for clarification:

If I back up the old model setup and transfer it to the new receiver, should that work?

Does that mean all macrocells are transferred along with their settings?

Or does it work differently than with Neo / Evo?

Thanks!

Best regards,
Thomas
machine-translated from German · Show original
Eddi E. aus G. 6 May 2026 15:4106.05.2026 15:41
Good morning,

No, everything works the same way every time; the bus receiver is a VBasic like RX-Only or just VBasic.

. As is typical with VBar, perhaps create a new setup first so that everything is properly configured (remember, on a brand new NEO or EVO, the servo output is also locked until you...)
Then load the saved MC, and load the saved setup, and 'watch out', turn off the reeds/prop first in case something starts up.

Or from the very beginning,

. infect
bind
off-on
New setup, OMP or OFS3 depending on the helicopter
Pre-flight check
. go flying

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
thomas1130 6 May 2026 15:5506.05.2026 15:55
Thanks Eddi,

I wasn't entirely clear on the "basic insemination" thing - I thought that only applied to EVO / NEO - and not just RX-only...

I just have to wait until the storm here in Vienna subsides, otherwise the dwarfs won't happen ;-)

THX!!

Best regards,
Thomas



Edited once. Last edited on 06/05/2026 at 15:55 by thomas1130.
machine-translated from German · Show original
Eddi E. aus G. 7 May 2026 08:5607.05.2026 08:56
Good morning,

I'd have to test it again myself, I don't have a virgin one here right now.

But that's what the average person does anyway, a new setup.

Only the specialists want to take shortcuts :-) (and sometimes even make it worse by carrying over a setup that has been dragged along for years from the version before the one before the one before, or by loading a foreign setup instead of creating a new one, even improving something in the process, and being amazed...).
It's not that complicated for us either: keep an eye on the versions, scripts, conduct test flights, research the results, readjust, set up telemetry, ... :-)

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
thomas1130 7 May 2026 12:5707.05.2026 12:57
Hmm - I've tried it now - but I'm not entirely sure...

I know how it works with "normal helicopters" and EVO or NEO - no problem, I (almost) always do a new setup anyway.

But here - with SBus only plus macrocells I'm unsure:

When you back up/load the setup, are the macro cells also backed up or loaded?

Is/must the macrocell be backed up or reloaded "separately"?

Background - the "flight characteristics" and rotational speeds are hidden in (painstakingly determined) values in the macro cells - therefore, a "new setup" simply doesn't help me - I would then be back to square one..


Please clarify - THANK YOU!

Best regards,
Thomas

EDIT:

Additional "problem":

The radio went directly into setup after connecting the RXmini - no registration prompt.

Therefore, the recipient does not appear under "my devices" in the cloud!?

How can I restart this?



Edited once. Last edited on 07/05/2026 at 13:01 by thomas1130.
machine-translated from German · Show original
Dirtygeri 7 May 2026 13:0707.05.2026 13:07
Hi Thomas!
You can't see the forest for the trees, can you?
Connect/turn on the RX7 - Save the setup under name XY, then save the macro cell setup under name XZ and turn it off.
Then connect the RX S-Bus to power/switch it on - bind it to the transmitter - create a new setup... switch it off when finished.
Then connect/switch on the RX S-Bus - load the RX7 setup (names XY, macrocells) - load the RX7 setup (names XZ)... switch off when finished
Then install/connect the RX S-Bus to the new model, connect it to power (it's best to do this without blades to avoid any accidents) - switch it on and check all functions; if everything is OK, attach the blades and fly...

Just like always... 8-)

Best regards, Geri
machine-translated from German · Show original
Eddi E. aus G. 7 May 2026 13:2007.05.2026 13:20
Hi,

Quote: me
Then load the saved MC and load the saved setup.

This implies that you have to save and load both :-)

The issue of 'laboriously acquired through flying' is another one of those: OMPHOBBY wants further settings to be made only in the helicopter.
Many roads lead to Rome, though.

Quote: thomas1130
The radio went directly into setup after connecting the RXmini - no registration prompt.

This always happens when a new device/one without a suitable setup is detected.
Normally, you would simply do it and finish, or finish and update via the VBar NEO/EVO Updater app and the QR code there.
However, it doesn't come up with the 'short' ones; either something else will come, or one cannot (and must not...) register them.
But this does not affect the functionality.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
thomas1130 7 May 2026 13:2107.05.2026 13:21
Thanks Geri - that's exactly how I did it "intuitively" - first setup - then macro... - and it worked as expected... :-)

Eddi didn't explicitly "mention" it - or rather, I "overlooked" it - so I asked again here 8-)

The problem with registration remains:

I have the flights in the cloud - but the recipient does NOT appear under "my devices".

LG
Thomas

PS: He is "cute"... :-)

P.S.: This overlapped with Eddie's answer.



Edited 4 times. Last edited on 07/05/2026 at 13:36 by thomas1130.

machine-translated from German · Show original
thomas1130 7 May 2026 13:4007.05.2026 13:40
Quote: Eddi
However, it doesn't come up with the 'short' ones; either something else will come, or one cannot (and must not...) register them.
But this does not affect the functionality.

Just checked - the old RX7 only doesn't appear in my device list either - I hadn't even noticed that before - seems to be "normal".

I do wonder why – and how one would create a service request in such a case – but as you rightly say – it doesn't affect the functionality :-)

Best regards,
Thomas
machine-translated from German · Show original
Dirtygeri 7 May 2026 13:4707.05.2026 13:47
I do have the flights in the cloud - but the
The receiver does NOT appear under "my devices".
> on..

I don't have an RX SBus receiver (yet), but normally on the VBAR Updater (where you do the update on the Vbar Neos / Evos 8-) ) - QR code appears and then, as always, scan, etc., right?

Geri
machine-translated from German · Show original
Eddi E. aus G. 7 May 2026 13:5007.05.2026 13:50
Hi,

I just connected a NEO mini (based on RX-Only 7), and the updater appeared; I could register it.
It has a normal NEO serial number (200...).

Regarding the service case, I would first note down the serial number somewhere (totally 90s, yes :-) ), and then you can also create a ticket without a serial number under vstabi.info/rma with 'Other parts', or for NEO/EVO, if the system 'eats' the serial number.

These are just backend issues, but we'll take a look at them sometime.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
thomas1130 7 May 2026 16:4907.05.2026 16:49
The updater isn't showing up for me – which I'm wondering about, how am I supposed to update the firmware if there ever is an update!?

But it flies perfectly fine - so that's not the problem.

And to everyone who is silently reading along here:

Definitely remove the rotor blades – the rotors will start spinning during setup anyway...

Best regards,
Thomas



Edited once. Last edited on 07/05/2026 at 16:49 by thomas1130.
machine-translated from German · Show original
RV 7 May 2026 22:0307.05.2026 22:03
- The devices cannot be registered by the customer.
- If necessary, we will provide an app for a possible update.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless