Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Yet More FrSky Protocol Confusion
#1
I just saw Pawel's latest video. I thought 1st April was two weeks ago Whistling

Didn't FrSky already shot themselves in both feet? Maybe they have more than two feet that needed to be shot Big Grin

Spoiler: FrSky have just come out with a new protocol.....called FBUS  ROFL ROFL ROFL

[-] The following 2 users Like SnowLeopardFPV's post:
  • hugnosed_bat, Lemonyleprosy
Reply
Login to remove this ad | Register Here
#2
…and I’m sure in 6 months they’ll come out with a “new” version of fbus receivers that run a new firmware version that isn’t backwards compatible with the first version of rx’s that they release that run fbus.

Or those fbus receivers will require some special new non backwards compatible tx to rx protocol.

Or… hell, I can’t even keep my hypothetical straight, much less their actual protocols. Tongue

…does this mean they already gave up on their ELRS fork?
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
[-] The following 1 user Likes Lemonyleprosy's post:
  • hugnosed_bat
Reply
#3
Pawel also mentioned an "F.Port 2" protocol in his video. I didn't even know that was a thing until I heard it today Big Grin

And just when you thought the FrSky mess couldn't get any worse.

I don't think they have given up on their own forked / butchered version of ExpressLRS which is in breach of the GPL licensing because they haven't made the source code for it publicly available anywhere. They are currently offering it on some of their new transmitters as an ELRS "compatible" protocol which has ZERO support from the ExpressLRS developers. The mind boggles.

Someone forgot to send FrSky technicians the memo that when already in a hole that is well above your head, stop digging Whistling
[-] The following 3 users Like SnowLeopardFPV's post:
  • hugnosed_bat, V-22, Lemonyleprosy
Reply
#4
AFAIK

https://github.com/betaflight/betaflight/issues/12398
CRSF looks like diff baud rate for ELRS.. weird
400k baud

IBUS 115.2k baud. 8N2
2 byte header, 28 byte for 14ch frame, 2byte CRC.

SBUS 100k baud 8N1
1 byte header, 16ch 11bit each. etc, byte25 footer
https://github.com/bolderflight/sbus/blo.../README.md

there is also 200k baud fast sbus

FPort 115.2k baud 8N1

I guess FPort2 is 250k baud??
Reply
#5
Another good reason to feel good on leaving Frsky.. I just wish I could replace the internal protocol of my taranis opposed to using an external modules.
Reply
#6
(12-Apr-2023, 11:11 AM)Rob Axel Wrote: I just wish I could replace the internal protocol of my taranis opposed to using an external modules.

I would actually rather have a "dumb" transmitter with NO built-in internal module which ends up being tied to the transmitter. Modular systems are the future where you can just swap, change, and upgrade as you see fit without built-in internal hardware then becoming redundant. Even with Crossfire the Tango 2 had to have a complete new mainboard (twice) when TBS upgraded the transmitting components on it. I've also seen ExpressLRS modules which have been improved with better versions. Having any transmitting hardware as external modules makes it much easier to just "throw away" an out-of-date module and slot in a newer or better one without any fuss.
[-] The following 2 users Like SnowLeopardFPV's post:
  • cali_quad, Lemonyleprosy
Reply
#7
(12-Apr-2023, 10:38 AM)romangpro Wrote: SBUS 100k baud 8N1
1 byte header, 16ch 11bit each. etc, byte25 footer
https://github.com/bolderflight/sbus/blo.../README.md

Even more bizarrely, SBUS is actually 100k baud 8E2, and inverted.
Reply
#8
what is frsky? xD
[-] The following 2 users Like hugnosed_bat's post:
  • Rob Axel, Lemonyleprosy
Reply
#9
IBUS 10bits/byte. 28byte frame. 411 /s

SBUS 11bits/byte. 25byte frame. 363 /s.

What is the frame and serial flow for CRSF.. anybody know?
Reply
#10
(12-Apr-2023, 11:30 PM)hugnosed_bat Wrote: what is frsky? xD

As funny as this is.. when I first got into the hobby I thought Frsky and Flysky were the same thing.. chalked it up to “auto correct”..
Had no idea what a “radio protocol” was..
[-] The following 1 user Likes Rob Axel's post:
  • Lemonyleprosy
Reply
#11
(13-Apr-2023, 10:11 AM)romangpro Wrote: IBUS 10bits/byte. 28byte frame. 411 /s

SBUS 11bits/byte. 25byte frame. 363 /s.

What is the frame and serial flow for CRSF.. anybody know?

https://oscarliang.com/improve-radio-control-latency/
crsfshot locka the frame rate on 150hz to 6.7ms, does this relate in anyway to the values of sbus and ibua above?
i couldnt find better infos so far Undecided
Reply
#12
No. not related.

The radio processes a command and sends a signal. It has specific frequency and amplitude and phase modulation... this is the "air" protocol. Its 150Hz for Crossfire.

The way they encode the data and send it.. this is what the bandwidth allows.

ELRS very cleverly packs the bits for channels and telemetry together.. not wasting "space". Thats why 500hz is possible.

CRSF is the rx protocol between receiver and flight controller. Thats what my post was about.
Reply
#13
Light years ago in another Galaxy far far away I was a Beta Tester for the FrSky X12S. I'd already got a batch 2 Taranis.

Considering FrSky got going by offering greatly cheaper and unapproved Futaba FASST compatible receivers, they pretty soon went poacher turned gamekeeper and the "fun" began on their formats.

Lost the Plot is an understatement on where they are now, but look around the fixed wing forums and you'll find lots of die hard fans who are looking forward to the next greatest protocol change!

Ignoring the non-FrSky Tx's I own (lots) my Taranis has a Futaba FASST module (very rare), and my three X12S are as follows:-

1. OpenTX, iRange Multiprotocol.
2. OpenTX, Namimno ELRS 2.4 v2
3 EdgeTX, Namimno ELRS 2.4 v3
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Spectrum USB programmer to update Frsky rx? baevans11 8 371 23-Apr-2024, 01:24 PM
Last Post: baevans11
  Help Frsky XM+ Firmware versions Steak-9 3 203 26-Mar-2024, 01:28 PM
Last Post: Steak-9
  Help FrSky r xsr receiver not entering bind mode August 1 164 05-Mar-2024, 08:49 PM
Last Post: August
  Help FrSky Archer RS to Speedybee F405V4 through F.Port trecords 0 170 28-Jan-2024, 09:10 PM
Last Post: trecords
  Problem with FRsky R9 900mhz PJKMBAKER 5 489 24-Dec-2023, 02:18 PM
Last Post: PJKMBAKER


Login to remove this ad | Register Here