Home › VBar NEO EN › VBar NEO/EVO Information › VBar EVO additional Information

VBar EVO FAQ

Converting from NEO to EVO:

Here is a guideline how to convert a already existing Model from NEO to EVO:

  • NEO stays in the Model
  • Save the Setup with a VBCt/e
  • Upgrade EVO to the same level as NEO
  • Load a new Model setup to EVO, walk through the wizard once
  • Restore the previously saved Setup to the EVO
  • Set Servo / ESC frequencies as Default for Beginning (Swash 144 Hz, ESC 72 Hz)
  • Check new Values in Mainrotor and Tailrotor, zero them if set for first start
  • remove NEO from Model, mount EVO
  • don't forget a pre-flight-check

 

 

Which ESC Framerates should i adjust?

A Framerate of 72Hz is Default - even if unset. It will only make sense to use a higher one in VGov mode -as all others are "Flatline" values.
 
How much we can use depends also on the internal throttle handling of the ESC. Porbably it will get out of sync using too high rates and throttle values. So - in doubt please ask the ESC manufacturer and do some bench tests before maiden a heil with higher framerates. Ensure the ESC is updated to the latest Firmware too!
 
We have proven some examples here:
 
  • YGE 205 HVT, 333 Hz
  • YGE 95 LVT, 333 Hz
  • HW 150 LV V5, 333 Hz
  • Scorpion Tribunus 14-300A, 333 Hz

 

 

Which Swashplate Framerates are useful?

A Framerate of 144Hz is Default - even if unset.
 
How much we can use depends also on the internal handling of the Servo. Probably it will get out of sync using too high rates and throw values. So - in doubt please ask the Servo manufacturer and do some bench tests before maiden a heil with higher framerates (Check force in end positions and also temperature). Please also check RC Power consumption, probably Battery use time. Higher framerates will result in more servo power consumption in most cases!
 
We have proven some examples here:
 
  • Savox 1257 @1500us 333 Hz (LOGO 550 SE)
  • KST X20-2208 @1500us 333 Hz (LOGO 800)
  • Futaba BLS 351 @ 1500us 333 Hz (BO 105 1,80m Elektro, 10 kg)
  • Futaba BLS 177 SV @ 1500us 333 Hz (UH 1-D 2,36m with Turbine, 22 kg)

Please start "from bottom to top" and change step by step! Depending on the model, servos, rotor system etc. sometimes the highest rate is not the best result!

Read this for more detailed infos: <<<< CLICK ME >>>>

 

 

Whih Tail Framerate should be set up?

A Framerate of 333 Hz was the "normal" Max value.

How much we can use depends also on the internal handling of the Servo. Probably it will get out of sync using too high rates and throw values. So - in doubt please ask the Servo manufacturer and do some bench tests before maiden a heil with higher framerates (Check force in end positions and also temperature).

We have proven some examples here:

  • Savox 1257 @1500us 500 Hz
  • Savox 1290 @1500us 500 Hz
  • KST X20-1035 @760us 1000 Hz
  • Futaba BLS 451 @ 1500us 500 Hz
  • Futaba BLS 175 SV @ 1500us 500 Hz

 

 

 How are the USB Modes of a VBar EVO started?

  • for updating with the VBar Control Manager - first connect USB to the PC, then turn on RC power.
  • for use with PC Software - first power up RC and after 1-2 seconds connect USB to PC.

 

 

Which possibilities are there to set up / use a VBar EVO?

  • VBar Control Basic: Usage / Setup w/o new EVO values possible
  • VBar Control Classic: Usage / Setup possible, new values can be acessed through a app with sperate 
  • VBar Control touch: Usage / Setup possible, new values can be acessed through a app which integrates them
  • VBar Control EVO: Usage / Setup possible, new values can be acessed through a app whhich integrates them
  • PC Software: Version 7 contains all new values

 

 

Can a VBar EVO be used with 3rd party radios?

In general - yes, of course. The connection handling is the same as on a NEO VLink. But - the EVO supports only digital protocols at AUX1 (UDI, S.Bus) input. So Spektrum Satellites connected to TELE1 or TELE2 are not supported!

  • If a 3rd party is connected and configured and will have connection at the EVO boot - it is used. The VBC transmission is disabled then.
  • If a 3rd party boots later then EVO power on - a VBC can be bound in addition.

 

 

My VBar EVO does not forward telemetry data on TELE1 to the VBar Control since it was updated

During the VBar EVO update the port TELE1 could get a condition where its usage is not safely set. To solve it - connect the model, go to setup / telemetry / VBar EVO pro options and toggle the check for the usage once forth and back. At least it must be unset of course.