- Posts: 588
Frsky compatibility
- Hexperience
- Offline
Cheers!
There are 10 types of people in this world. Those that understand binary and those that don't.
Please Log in or Create an account to join the conversation.
- Hexperience
- Offline
- Posts: 588
I now have weird lines running across the screen, or some kind of color shift. Some thing is wrong with it.
Also, when I select PPM protocol for simulators my voltage displays at a steady 4.2v, when I select devo or dsmx protocol, it shows steady 4.17. However, if I select SLT or Frsky the voltage display flickers between 4.13-4.17
I must have wired something wrong?
There are 10 types of people in this world. Those that understand binary and those that don't.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
So now I've ordered 2 new receivers (one 'D' supporting the hub, and an 'X' using S.Port). I also ordered an S.Port telemetry sensor. So hopefully with all that, i can actually get full Telemetry support functioning.
Please Log in or Create an account to join the conversation.
- robca
- Offline
- Posts: 174
I'm planning to replace a Lemon Rx PPM (which is only 6 channels) with a DR4-ii (which can output 8 channels as PPM) in one of my quads, but I wonder if it's safe enough to use at this point (I love Deviation Tx with the Lemon Rx, of which I have a few)
And, yes, I understand I need to add the right module, it has been sitting in a drawer for some time
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
That said, it has only seen very limited testing by others than myself. The DSM2/X protocol was exceptionally difficult to get working robustly on everyone's hardware. I don't expect the same issues with Frsky, but I cannot be 100% confident in that.
Please Log in or Create an account to join the conversation.
- IMback!
- Offline
- Posts: 84
PhracturedBlue wrote: Skyartec protocol has good range.
It dose but the mw numbers dont corolate at all with the range in any reasonable way (see the skyartec range bugreport) maybe the power nummbers should be renamed to 1, 2, 3, 4 etc or made different for diffrent modules?
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
PhracturedBlue wrote: Frsky seems to work well for Tx in the nightly builds. There is no telemetry yet though. I have not range tested it either, though I don't expect that to be an issue since the Skyartec protocol has good range.
That said, it has only seen very limited testing by others than myself. The DSM2/X protocol was exceptionally difficult to get working robustly on everyone's hardware. I don't expect the same issues with Frsky, but I cannot be 100% confident in that.
Good news ... coz I would prefer to have FrSky RX than DSMX. FrySky RX are know to have very good range ...
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- IMback!
- Offline
- Posts: 84
Please Log in or Create an account to join the conversation.
- robca
- Offline
- Posts: 174
PhracturedBlue wrote: Frsky seems to work well for Tx in the nightly builds. There is no telemetry yet though. I have not range tested it either, though I don't expect that to be an issue since the Skyartec protocol has good range.
That said, it has only seen very limited testing by others than myself. The DSM2/X protocol was exceptionally difficult to get working robustly on everyone's hardware. I don't expect the same issues with Frsky, but I cannot be 100% confident in that.
Good enough for me I'll solder the CC2500 and give it a try
thanks!
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
I haven't figured out what the variometer data looks like yet, so I'm not sure if it is part of the 2-way data or if the s.port transmission is something else. I see a bunch of other data in the stream on the X6R, but it is all '0x0f'. LikelyS.Port doesn't work properly yet.
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
code.google.com/p/telemetry-convert/wiki/FrSkySPortProtocol
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
I need to wire up to the Taranis SPI and take a look at the D16 protocol.
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
The X8R must be bound in D16 mode for any S.PORT sensors to work in S.PORT mode.
D8 mode on a X8R will only give you RSSI telemetry, no other sensors will work.
My new X6R receiver states in the instructions that SPort Telemetry is only available in D16 mode.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
On my X6R, I didn't see any note about S.Port only being available for D16. Maybe I should read the manual more carefully
Please Log in or Create an account to join the conversation.
- mazi
- Offline
- Posts: 28
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- Frsky compatibility