VBAR version or Hobbywing V5?

[Timo-72]

I checked now new "VBAR" version of MSRC with Hobbywing V4 120A, Smartport and Frsky X-XSR Receiver

1. I update Hobbywing 120A V4 to latest VBAR Firmware, means I updated to PL-04.1.00-VBar

2. I deleted all sensors in OpenTX and I searched new sensors, but no telemetry available

This means you should rename "VBAR" in the dropdown menue of MSRC:GUI to Hobbywing Platimum V5 (Maybe in addition 150A) If you like, I can ask Hobbywing if all Platimum V5 have same protocol.

Interim wiring to update firmware / to check:

Kind regards and many thanks !!!

[Timo-72]

As you know Vbar is the software of the flybarless system from Mikado (flybarless Vstabi). In the "Spirit" flybarless you have to choose what ESC you use. I think you do the same in the Mikado flybarless called Vstabi.

And than Mikado has programmed the new Hobbywing V5 telemetry. The same like you did. But it is not a universal protocol from my understanding

[dgatf]

I've been looking at the HW V4 spirit page and indeed they say to not use the vbar version for HW V4 to get the telemetry. Also there is a HW V5 telemetry page.

In the HW firmare page, for V4, they say that the vbar version update is related to telemetry. I'm curious what telemetry sends the vbar version for HW V4. Maybe is similar to HW V5.

The advantage of V5 telemetry is that values doesn't need any transformation for voltage, current and temperature depending on model.

Could you enable debug (disconnect bec power to rp2040 or battery when debugging) for the HW 120A to check if something is read by msrc.

[Timo-72]

Hello, I see no benefit to this. I do not know why you hunt now for VBAR. Every VBAR user has a VSTABI Neo or EVO. This system is the "mercedes" and everything is perfectly integretaded bewtween ESC, flybarless and transmitter. But, flybarless 280€ and transmitter 1200€. Everybody who has this system will not need/use msrc. All other people using a V4 ESC can use Hobbywing firmware without Vbar. For Hobbywing V5 new protocol is integrated. So where do you see the benefit?

For sure I can do the debug, but it means to again open 4 screws that are closed with loctide because USB-C is not reachable from RP2040. So, do you see a benefit to Debug Vbar protovol from Hobbywing?

[dgatf]

I know that. But the target is not to give support to vbar users. The target is to use a telemetry protocol that provide data in final units (no need to be transformed). No vbar firmware provide raw sensor data and vbar firmware provide telemetry in final units (V, A, C). Also the transformation is different depending on model, so you need to measure voltage and current to verify that telemetry values are correct. I see much benefit on this.

I've assumed that the v5 protocol uses vbar telemetry protocol. See v5 specs and v4 firmware. v5 and v4-vbar-firmware, both use the same telemetry protocol, vbar. But for some reason the v4 120A with vbar telemetry is not getting through.

[Timo-72]

Hello, I send now again an email to Hobbywing support. Maybe we get the information. Would be easier as debugging. I will tell you when I have feedback.

[Timo-72]

Hello, no feedback so far from Hobbywing. But normally Hobbying support gives answer. It can take view days. This is just for your info.