-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRSF input for Trainer mode #1607
Comments
@wimalopaan would you be interested in adding this to your trainer protos? |
Luckily the channel data in CRSF is encoded 1-to-1 as with S.BUS. Here as a helper, a short CRSF parsing code by kobata, where he connected a HappyModel EP2 receiver via MCU to USB to act as a joystick: https://qiita.com/kobatan/items/40728fbb625057d9f42b |
Yes, I'll have look at it |
Does anyone have a full protocol spec at hand? For this the control-part (no sensor reply) would be sufficient. What would be the best test-setup for someone not owning CRSF hardware? Are the PC-based generators e.g. to use with some USB/serial converter? |
Crossfire is a bidi protocol as oppsed to SBUS oder IBUS-Controlpart. At a first glance it looks like the Crossfire-RX does not expect anything from the FC (the radio in this case) to be returned for packets of type |
Correct, you could just wire up the EP2 (CRSF) receiver TX line and leave the RX unconnected. Here a capture from the EP2 TX line (snippet):
What you get are CRSF_FRAMETYPE_RC_CHANNELS_PACKED (third byte 0x16) and CRSF_FRAMETYPE_LINK_STATISTICS (third byte 0x14) packets. |
Cool, thanks for the data: will use that as replay ... |
If I would like to get real HW, what would you suggest as RF-Module and RX? Available, simple and cheap... |
Here some more change in data for your experiments:
Have a look at HappyModel ES24TX and EP1 or EP2 |
The other protocols like SBUS, IBUS oder SumD/V3 use a fixed known baudrate. As I read CRSF can use different baudrates. But in the hardware-tab there is no more a baudrate selector. What would be your suggestion how to implement that (at first):
|
400k is ok for a start, I think. Autobaud might be doable but it normally requires some bit patterns to be efficient and precise. |
There is also the “brute force method” that just switches between known baud rates and tries to decode some traffic. |
... that's what I meant above under 3) |
Isn't the receiver side always 420k 8N1 irrespective of the update rate? |
In #1462 now we have
This is available on AUX serial ports (AUX1 or AUX2). |
For SUMDV3 I intend to do the following:
So, if one wants to use the binary switches that come in via SUMDV3 trainer, she has to setup the wanted LS as above before. |
I'll grab another ELRS RX out later to try the CRSF support... |
I do not guarantee for anything ;-) |
It seems to be working fine... only checked with the first four channels so far though :) |
Sounds good, thanks for testing. |
Thank you for working on this. Do you know if this enhancement is targeted for a release? |
Should be in 2.8. |
Is CRSF input for Trainer mode still planned for 2.8? If so, can I test this with 2.8.0-rc3? |
It is not going to be in 2.8.when you check PR #1462, you will see, that it needs to be rebased I clouding a bunch of manual work for translations. |
Maybe you want to checkout my |
Yes, it does. |
Kind of a "pot pourri", we'll need to sort that out and extract features one by one. |
Yes, it is. Actually I don't have time to sort that out by myself ... sorry. |
Lol... have no fear, the skeleton will be picked clean, and credit given where credit is due ;) |
Currently, Trainer mode only allows PPM or SBUS input. I am requesting CRSF input for Trainer mode.
Here is why.
I place a receiver in the JR module bay and connect the receiver to the Batt, Ground, and HeartBeat terminals. I then bind the receiver to the student transmitter. If the receiver will output PPM or SBUS, then this allows wireless trainer mode.
The problem is ELRS receivers do not output PPM or SBUS. Therefore, to use student transmitters with internal ELRS, there is a need for trainer mode to support CRSF protocol.
The text was updated successfully, but these errors were encountered: