Can VBC-t Cloud Setup Files Be Shared?

I want to share a macrocell setup with another VTouch user. I can download the file and send it to the other person but how can it be imported into his VBC-t Cloud for his use?

Thank you,
Bob

Store the file via USB to his VBCT.

Stephan

Hi,

mind that if there is no macrocell folder yet, on the target radio, you must create it, or pretend saving macrocells one time (save macrocells on one model, even if yet unchanged), so the radio creates the folder.

As a safety precaution: please also mind that this way, you are having a USB removable drive connected to your computer, so eject the drive/volume VControl on the computer prior to disconnecting, to avoid file system errors.

Kind regards

Eddi

Born to fly ...
forced to work.

Thank you. We will give it a try.

We got it to work. Thanks again.

We continue to be amazed and impressed with the VBar system. Like Windows vs DOS when compared to all the others, i.e., Futaba, Spektrum, JR, etc.

Question: Even though the model programming is stored in the Neo, it appears that the VTouch also retains all settings/model setups/etc. similar to the VBC-t Cloud. Is this correct?

The VBC has the setup files for the Flight Contols (Vbar, Vplane, VBasic, VCopter) and Macrocells (Seperately) only if stored there as user action when a model is connected.

If you store them - tey are also available in the cloud.

The VBC does not store by itself as it isn't needed for flying.

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.

Hi,

in our universe, the VBar (legacy or NEO) is the model memory. This allows model sharing / bind and fly.
Plus, all calculations are done in that VBar, on the model, so we can use a very narrow signal rate.

VBar Control is basically 'only' a sophisticated game controller with a display

Means, if you save a setup on the radio, it's basically only a copy / backup, which will also diffuse into the Cloud.
You can load a saved setup back onto a VBar, from the radio.

This is also why you can't make changes to a model setup, without the model connected. Simply makes no sense, you'd always be working on a copy, with all the risks.

I'm sure, in the future it will also be possible to upload setups to the Cloud, to push them out to the radio via WiFi, so you don't need to connect the radio to the computer for that any more, too.
Or to share setups already saved in the cloud, with someone, with a different MikadoID.
Maybe even to share existing batteries wit ID Tags, if you own more than one Touch radio, or with buddies.
So many ideas

Kind regards

Eddi

Born to fly ...
forced to work.



Edited 1 time(s). Last edit at 02/05/2020 09:18AM by Eddi E. aus G..

Excellent explanations/clarifications. Thanks again.

Eddi E. aus G. Wrote:
-------------------------------------------------------
> Hi,
>
> in our universe, the VBar (legacy or NEO) is the
> model memory. This allows model sharing / bind and
> fly.
> Plus, all calculations are done in that VBar, on
> the model, so we can use a very narrow signal
> rate.
>
> VBar Control is basically 'only' a sophisticated
> game controller with a display
>
> Means, if you save a setup on the radio, it's
> basically only a copy / backup, which will also
> diffuse into the Cloud.
> You can load a saved setup back onto a VBar, from
> the radio.
>
> This is also why you can't make changes to a model
> setup, without the model connected. Simply makes
> no sense, you'd always be working on a copy, with
> all the risks.
>


Very good explanation, you need to have this mindset on the vbar control to understand the basics.

Regards (EN) / Gruss (DE)

Anders Norlin