← VPlane / VBasic VLink

VLink S.BUS telemetry receiver for micro helicopters: Telemetry loss? translated

VBar › VPlane / VBasic VLink · Started by Thomas6020 on 8 May 2026 18:5908.05.2026 18:59
Thomas6020 8 May 2026 18:5908.05.2026 18:59
Dear Forum Team,

I'm currently flying the new VLink S.BUS telemetry receiver for micro helicopters in my OMPhobby M2V3 Sport. After a successful OFS3 update, I was able to activate telemetry for VBar in the app.

Unfortunately, I now have the following problem: During flight, the receiver loses the battery telemetry 2-3 times. As a result, the flight battery has to be reconfirmed each time.

Does anyone have an idea for a solution?

Best regards from Innsbruck :-)

Thomas

machine-translated from German · Show original
RV 8 May 2026 22:4708.05.2026 22:47
Okay - there are probably two things fighting each other on the OMP side.

We can already imagine what this will be, because both signals in their FBL run through the same I/O on the OFS processor and are alternately switched to it via a multiplexer in the OFS. This might result in "missing times" in our TELE connection – because if the processor is currently listening to S.Bus, nothing arrives at our TELE connection. Perhaps this can be masked:

What update rate is set in Macro Cells => Input/Output Configuration? - I suspect 14ms. Please try 10ms. After changing the setting, please restart the helicopter.

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
Thomas6020 9 May 2026 07:5409.05.2026 07:54
Good morning dear Rainer,

Thank you so much for the quick reply! I set the update rate to 7ms as described in the OMP instructions. I'll try the 10ms you recommended today and let you know how it goes :-)

Best regards
Thomas
machine-translated from German · Show original
Thomas6020 9 May 2026 13:4309.05.2026 13:43
Dear Rainer,

Switching to 10 ms had the desired effect. I flew 10 batteries today and didn't experience a single telemetry loss.

However, I received this message in the log after the flight (see photo), when the VBar Evo+ was lying quite close to the helicopter on the flying table. I suspect this was because the VBar and receiver were too close together – what do you think?

To be on the safe side, I checked all the cables, but couldn't find any irregularities.

Best regards
Thomas

machine-translated from German · Show original
RV 9 May 2026 15:3109.05.2026 15:31
And here we need to differentiate:

The signal does indeed go from us to the OFS - but the controller then receives it processed and passed on by the OFS.

Therefore, the primary focus here is on investigating the connection between the OFS and the controller. We only receive the message via the controller telemetry and display it.

This can ultimately lead to the aforementioned dilemma of using only one UART for both (TELE and S.BUS) with a multiplexer for switching. If this multiplexer switches at a different clock speed than when the processor is supplied with the corresponding signal chains (it's then random whether it's "fully" correct at the time), the OFS could very well "skip" an output here – and the controller will complain.

Therefore - since it probably concerns hardware or the evaluation cycles of the S.Bus and TELE output to us - please contact OMP, we are clean here as we have separate interfaces for TELE and S.Bus.

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.




1 mal bearbeitet. Zuletzt am 09.05.2026 15:32 von RV.
machine-translated from German · Show original
Thomas6020 9 May 2026 15:5409.05.2026 15:54
Dear Rainer,

Thank you so much for the information! I'll keep you updated :-) .

Best regards
Thomas
machine-translated from German · Show original
Max8200 9 May 2026 21:2709.05.2026 21:27
I have the same problem. The OEM OMPHOBBY macrocell presets are set to 7ms. I just tested the M1 and M2 with the new receivers and found the "problem" described by Thomas with both. After switching to 10ms, everything was fine and there were no more problems :-)

Perhaps OMPHOBBY should implement that directly...but someone else is responsible for that ;-)
machine-translated from German · Show original
RV 9 May 2026 21:3809.05.2026 21:38
Well, we're in the process of integrating a current OMP preset; we're in contact about it. Aaron and I are in the final stages ;-)

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
Max8200 9 May 2026 21:4209.05.2026 21:42
Very nice!
It just keeps getting better 8-)
machine-translated from German · Show original
Orpheus 10 May 2026 12:1610.05.2026 12:16
Of course, I have the same problems with telemetry on my M1 and M2 with OFS3 and the new Micro RX Heli Only receiver.
I also had the 144Hz/7ms setting and will now switch to 10ms.

But now my question: wouldn't there have been a better solution for the new receiver than using the now somewhat restricted S-Bus, and then combining it with telemetry on a single UART/port?

And why doesn't this signal problem occur with the predecessors, the RX6 Only receivers, of which I have four in use, and they work perfectly with 144Hz/7ms?



Edited once. Last edited on 10/05/2026 at 12:22 by Orpheus.
machine-translated from German · Show original
thomas1130 10 May 2026 12:2310.05.2026 12:23
RV wrote:
-------------------------------------------------------
> Well - we are currently working on a new OMP preset
> integrate, we're in contact about that. Aaron and I
> are in their final stages ;-)

That sounds great - I'm really looking forward to it :-)

My M1 & M2 currently fly perfectly with the OMP macrocell presets at 7ms - and also without problems at 10ms...

But "the better is the enemy of the good" - I'm already curious to see what your new preset has to offer - there's definitely room for improvement 8-)

The "problem" is that the OFS doesn't recognize banks – and therefore, certain parameters (maneuverability, rotational speed) have to be adjusted in both the macrocells and the OFS to achieve the desired "different flight experiences" on the banks.

Best regards,
Thomas
machine-translated from German · Show original
RV 10 May 2026 19:1210.05.2026 19:12
Quote: But now my question: wouldn't there have been another, better solution for the new receiver than using the now somewhat restricted S-Bus, and then also combining it with telemetry on a single UART/port?

The dual assignment of the UART is on the OMP/OFS side – NOT on our end. Our colleagues there implemented it that way due to a lack of I/O hardware (they have I/O on the processor).

S.Bus is simply our interface for this – we have the original Futaba specification and adhere to it. So everything is fine.


Quote: And why doesn't this signal problem occur with the predecessors, the RX6 Only receivers, of which I have four in use, and they work perfectly with 144Hz/7ms?

Are you using the OFS telemetry there? - probably not.

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.




2 mal bearbeitet. Zuletzt am 10.05.2026 19:14 von RV.
machine-translated from German · Show original
steveman 10 May 2026 20:2910.05.2026 20:29
Where exactly do I need to adjust the update rate? Which menu item is it? I'm not very familiar with vBar Control yet. Best regards, Stefan
machine-translated from German · Show original
Orpheus 10 May 2026 21:4910.05.2026 21:49
RV wrote:
-------------------------------------------------------

> Are you including the OFS telemetry there?
> probably not.


Hello Rainer!
Yes, I have a normal SBus connection and telemetry connection from the Tele1 (correct) pin to the CRFS TX pin of the OFS3 on all four NEO micro 6-channel RX Only receivers.
As described in the OMP manual, Revision 5.
And set to 144Hz/7ms.
Here, the entire telemetry and battery management system works flawlessly, and none of the electronic components complain.

The only difference to the new Micro Heli RX Only is that this one only has a 1-pin connection to TX.
With the new one, you have all 4 wires routed to the CRFS, but that doesn't necessarily mean you are using all the pins.

Regards, Dietmar



Edited once. Last edited on 10/05/2026 at 21:52 by Orpheus.
machine-translated from German · Show original
Eddi E. aus G. 11 May 2026 10:1211.05.2026 10:12
Good morning,

We only use one cable on the CRFS (TX); the others stabilize the connector and the (otherwise) poor single cable, which could otherwise easily be torn off.

What I also haven't quite understood is that OMPHOBBY differentiates between S.BUS and S.BUS wide (?), presumably due to different packet 'structure', something proprietary. And for telemetry on the integrated receiver, there even seem to be adjustable ratios between control:telemetry data (always 1:1 with VLink), which could mean that they constantly keep slots free (or have to) to send telemetry data back (but then hardly in real time?). I don't know if and how this also affects external receivers.

However, as I understand it, S.BUS has no influence in the implementation: the S.BUS data stream arrives every 7, 10, 14, ... ms, packet-packet-packet-packet, and the telemetry is received via the other connection, so nothing influences each other in our case.
The VLink receiver handles the transmission to the transmitter in the same way as any other VBar: 5 ms transmit, 5 ms receive, repeat.
The attentive reader will notice that only 5 and 10 have one thing in common: they can run synchronously. With other pairs, there will always be a waiting period (or must be) until the other is able to receive data again or outputs something again (asynchronous).
However, if no data is received from the external system for a certain period of time (the ratio of control to telemetry? If this even has an influence here, which it shouldn't, _or_ the ratio at the I/O, multiplexer, how many cycles are allocated to which), the receiver hasn't passed anything on, and the transmitter 'thinks', 'all good, nothing more to report.' Then, boom, it happens again, battery selection, or worse, if this coincides awkwardly with asynchronous timing, resulting in jerky control.

If S.BUS and telemetry in the external system now run over the same I/O, and this is constantly being switched between listen-speak-listen-speak (like a walkie-talkie, push-to-talk button, but pressed/released for different lengths of time) and not constantly both are being used (like on a telephone), ...

Nobody knows.

OMPHOBBY also points this out, explicitly stating in their documentation that telemetry should only be used when absolutely necessary (?) ... where's the point if they offer telemetry :-) ... if you're not allowed/supposed to use it. Shame on anyone who thinks ill of it...

I don't mean to nitpick, these are just my thoughts. Ultimately, it's not full integration, but rather an external receiver (like an original or reverse-engineered S.BUS or other receivers). I believe original S.BUS receivers would also have a latency of 7/14 ms.

Incidentally, a VBar adjusts itself to the input refresh rate (because it can ^^) when an external receiver is connected.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless