← Cafe

XD Fly controller translated

Public Talk › Cafe · Started by HP on 2 December 2025 18:5602.12.2025 18:56
HP 2 December 2025 18:5602.12.2025 18:56
Hello folks!

Has anyone here had any experience with XD Fly controllers?
There are a few things in the controller settings that I simply don't understand, such as the P and I values or SR on/off.
Or do these parameters not apply at all when using the VBar Gov.?
machine-translated from German · Show original
Eddi E. aus G. 3 December 2025 09:0003.12.2025 09:00
Good morning,

Those would be questions for XDFly support.

But if you program the controller via the VBar Control/VBar (one-click), all parameters are set, you don't have to adjust anything :-)
And in VBar-Governor mode, the controller's internal control parameters I(integral) or P(proportional) actually have no influence, as the controller works like a throttle servo.

—Eddi

Born to fly ...
forced to work.



Edited 1 time(s). Last edit at 12/03/2025 09:00AM by Eddi E. from G..
machine-translated from German · Show original
HP 9 December 2025 19:0409.12.2025 19:04
Hello Eddi!

A brief review:

The speed controller has arrived, been installed, and test-flown. It works perfectly, just as you said.
If you set VBar Gov., the parameters mentioned above are not available for selection anyway.
What I noticed immediately during the first test flight:
The RPM remains rock-solid, really good I must say. Better than the YGE 90LV I had before. That one's getting on in years now. As a result, the tail also holds its position better when making pitch adjustments with the Savöx 1290.
What's not quite ideal is that when switching between banks, the engine speed increases or decreases rather abruptly, causing the rear end to always swing out slightly. This was smoother with the YGE engine.
The battery capacity is also not quite right; the battery runs out too quickly when the capacity is set to 70%.
You have to be a bit careful during the first few flights. I think you can still manage it with the controller's internal correction.
Otherwise, adjust the starting capacity or the remaining capacity. I don't know which would be the better approach here.
machine-translated from German · Show original
RV 9 December 2025 22:3609.12.2025 22:36
Correct the error where it originates. So if the controller is measuring incorrectly – correct it within the controller itself.






Please compare the percentage of charge remaining with a LiPo checker after the flight, and compare the discharged capacity according to the ESC telemetry with the subsequently charged capacity according to the charger. Subtract approximately 30 mAh from the charger's capacity to account for balancing losses.






Example for a 5000 set to 70%:

Controller - 3532 mAh
Charger - 3545 mAh
Lipochecker - 10% remainder

So the controller is working – and the battery itself no longer has 5000mAh, but rather less. I would then subtract 20% of 5000mAh and thus enter 4000mAh as the starting capacity, and set the aging to medium. Then check again.






Would the values look like this:

Controller - 3932 mAh
Charger - 4425 mAh
Lipochecker - 10% remainder

You would need to turn the controller up by approximately +12%. Then test again.






It could also be both - incorrect starting capacity due to aging effects and misalignment in the controller!

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.




Edited 3 time(s). Last edit at 12/09/2025 10:48PM by RV.
machine-translated from German · Show original
HP 10 December 2025 19:2510.12.2025 19:25
Hello Rainer!

Thanks for your answer!
Next time I'll check if the removed capacity matches the reloaded capacity. That was the crucial point; I hadn't paid attention to it.

I have another question: is there a way to make the RPM change during bank switching smoother so the tail doesn't spin out anymore? The controller also has start-up power and acceleration parameters in VBar Gov mode.
Are these parameters still relevant once the VBar government has taken over?

Kind regards

HP
machine-translated from German · Show original
RV 10 December 2025 20:3110.12.2025 20:31
You'd have to ask XDFly about that. I would rather reduce the acceleration in Vstabi Gov from 3 to 2 and decrease the integral slightly.

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
TBIndustries 23 December 2025 08:2323.12.2025 08:23
Hello with O........
Are XDFly controllers as easy to use as YGE controllers?
So, gas paths are automatically transmitted from the touchscreen and fully adjustable via the app?
Thanks in advance.



Edited 1 time(s). Last edit at 12/23/2025 08:23AM by TBIndustries.
machine-translated from German · Show original
Eddi E. aus G. 23 December 2025 08:5423.12.2025 08:54
Good morning,

Basically yes, and with the parameters provided by XDFly.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
johnahamelv 21 January 2026 08:4221.01.2026 08:42
I want to follow up on this last point. I am used to paring YGE ESCs with my VBC EVO radio and EVO flight controllers. After installing the YGE app on the VBC EVO radio, I like how the radio recognizes the YGE ESC and automatically calibrates the throttle channel, so I do NOT have to calibrate the throttle channel using the high stick and low stick calibration steps.

I plan to use the XDFly HPro 195 ESC. I installed the XDFly app in the Mikado VBar Control radio.

Does the Mikado VBar Control EVO radio recognize and automatically calibrate the throttle channel with the XDFly ESC (like with YGE), or do I still need to conduct the high stick and low stick throttle channel calibration steps?
Eddi E. aus G. 21 January 2026 08:5621.01.2026 08:56
Hi,

it works basically the same, with XDFly ESCs.

Best,

Eddi

Born to fly ...
forced to work.
johnahamelv 21 January 2026 09:0421.01.2026 09:04
Hello Eddi,

Thank you for responding. Just to be clear, if I understand you correctly, I do NOT have to conduct the high stick and low stick throttle calibration steps when pairing an XDFly ESC with the VBC EVO radio and EVO flight controller assuming I have the XDFly app installed in the radio?
Eddi E. aus G. 21 January 2026 11:1621.01.2026 11:16
Hi,

I must leave a back door open ;-)

Compatible XDFly ESCs will be programmed directly via bi-directional telemetry, like all others.
No need to stick-beep-program, like in the '90s :-)

But since ESC manufacturers do their own thing, it is possible that existing or future ESCs will not behave as expected, if their firmware is somehow not communicating as expected, or if they were developed later than specs or device IDs were negotiated, means, if our latest version of the App does not know them yet.
All telemetry items report in with name and rank at power on so they can be addressed properly, with their individual features.
If there's the figurative new guy on the block, we may not know until either the ESC manufacturer tells us, or until we learn from customers and go ask a manufacturer.

Best,

Eddi

Born to fly ...
forced to work.
johnahamelv 22 January 2026 03:3422.01.2026 03:34
Hello Eddi,

There are threads (yes, more than one thread) in the XDFly Facebook page discussing whether or not one has to conduct high stick and low stick throttle calibration when paring an XDFly ESC with a VBar Control Touch/EVO radio using a Neo/EVO unit. Some folks say yes, you have to conduct the high stick and low stick throttle calibration. Then some folks say no, you do not have to conduct high stick and low stick throttle calibration. Both of these folks cannot be correct.

In my case where I plan to pair an XDFly HPro 195 ESC with my VBar Control EVO+ radio using an EVO Pro/Rescue unit, do I have to conduct the high stick and low stick throttle calibration with this ESC?
Eddi E. aus G. 22 January 2026 09:2822.01.2026 09:28
Hi,

I'm afraid people out there on socials often think ... kinda backwards?
Or simply don't have it connected properly, don't have the Apps loaded on their transmitters, or have made weird adjustments (because they can :-) ), somehow inhibiting the automatic.
And their discussions raise more questions than they provide answers.
Facebook, Reddit, RC forums, even AI (which often can't really tell good answers from bad answers in AI training ... with ambiguous results), you name it.
If they all were right, I would need to look for a new job ^^

I have no first hand experience with XDFly ESCs, but since their Web site says: Telemetry: Mikado VBCT/E/RF2/Futaba SBUS2/Jeti/MSH Brain/iKon, I suppose it's compatible.
And then you wouldn't have to do anything but select the Governor type you desire, VBar Governor or XDFly Governor, dial in the gear ratio and motor pole count, and you're good to go.
Provided it's connected properly to TELE1 or TELE2 on the VBar, ESC wire to ESC, RPM signal output to RMP, like with all other compatible ESCs.
If VBar EVO and TELE1, also make sure that port is not set to Temp sensor permanently, in the Model Setup/Telemetry menus.

Cheers

Eddi

Born to fly ...
forced to work.
johnahamelv 22 January 2026 09:4922.01.2026 09:49
Hello Eddi,

I believe XDFly "telemetry" compatibility with VBar is already pretty well established.

I am focusing specifically on "automatic throttle calibration".

I am looking for a straight black or white (not grey) yes or no answer; Is there a need to conduct a high stick and low stick throttle calibration when pairing a VBar radio/unit with an XDFly ESC?
RV 22 January 2026 10:2422.01.2026 10:24
Never needed on any ESC with our bidirectional telemetry

Stone Age relics... ;-)

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.




Edited 1 time(s). Last edit at 01/22/2026 10:24AM by RV.
machine-translated from German · Show original
Eddi E. aus G. 22 January 2026 10:3722.01.2026 10:37
Hi John,

another attempt at re-phrasing:

_if_ <ESC> is connected properly;<REQUIRED APPS> are installed;<ESC> is detected properly by telemetry
_and if_ exactly three adjustments have been made [SelectGovType;EnterGearRatio;SelectMotorPoleCount]
_then_ no further adjustments necessary—also no stick calibration

The _ifs_ remain because since I have no first hand experience with this ESC, and since there are other prerequisites (_and ifs_), is why I can not give a black or white answer.

On the scale of 50 shades of grey, it's almost 0 (white, vanilla, good, will work, no stick calibration),
with a small chance that changes made to the ESC manually (like, selecting a different telemetry protocol)
or with the off chance that a particular type of ESC or firmware version is not directly compatible,
flip the switch to 50 (black) where you can't program the ESC directly via telemetry (including automatic setting of stick end points).

In these cases, you might have to change settings in the ESC manually, or if nothing helps, we (XDFly and us) would have to talk.

For our own products, we can easily tell yes or no.
For interoperability with foreign products, we can tell yes _if_ the previously negotiated terms are (still) met.
For both, there are still some prerequisites to be met.

A real-world example from yesterday: a customer called, in, he updated his HW ESC, and now he's cut off telemetry (and one-click setup).
My white answer for HW is usually, V4 and up work.
Now a change by the customer and/or HW negated that assumption, but I still can not start telling customers now 'HW doesn't work', black answer.

Best,

Eddi

Born to fly ...
forced to work.
VStabi VStabi Pioneer of Flybarless