- Posts: 30
Frsky compatibility
- shadow
- Offline
I cleared the fixed id and still nothing. I wondering if I have a bad tx module.
Please Log in or Create an account to join the conversation.
- phantom8
- Offline
- Posts: 109
Please Log in or Create an account to join the conversation.
- shadow
- Offline
- Posts: 30
I am using a Devo 8s
I bought 2 modules I will try the other one
Just a pita to solder
oh and tx power is stuck on default
thanks
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.
- phantom8
- Offline
- Posts: 109
Please Log in or Create an account to join the conversation.
- Chispas
- Offline
- Posts: 7
Worth buying a cc2500 module and setting it up for my devo 7e to link with FrSky Receiver D4R-II
Please Log in or Create an account to join the conversation.
- sbstnp
- Offline
- Posts: 649
phantom8 wrote: I was trying to range test earlier today. With distance of 300m, I set my Devo 7e tx power to 150mW. As expected, I got a solid connection. I turned down the tx power to lowest 100uW. To my surprise, I still have a connection at 300m. I understand Frsky receivers are known for good range, but I didn't expect 100uW power to cover 300m range. Next time, I'll try to range test at a much farther distance.
Which version did you use?
Devo 10 + 4in1
FrSky Taranis + TBS Crossfire
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
Please Log in or Create an account to join the conversation.
- phantom8
- Offline
- Posts: 109
sbstnp wrote:
phantom8 wrote: I was trying to range test earlier today. With distance of 300m, I set my Devo 7e tx power to 150mW. As expected, I got a solid connection. I turned down the tx power to lowest 100uW. To my surprise, I still have a connection at 300m. I understand Frsky receivers are known for good range, but I didn't expect 100uW power to cover 300m range. Next time, I'll try to range test at a much farther distance.
Which version did you use?
I'm using D4R-II receiver.
Please Log in or Create an account to join the conversation.
- shadow
- Offline
- Posts: 30
humm
Did you connect the reset pin to the TCK pin?
Please Log in or Create an account to join the conversation.
- phantom8
- Offline
- Posts: 109
shadow wrote: Ok changed out the module and still nothing. I am getting power to module but it doesn't initialize.
humm
Did you connect the reset pin to the TCK pin?
If you're talking about the Multi-Module connection, then yes. I've connected the MM's Reset pin to TCK pin on the Devo. For the MM, I've connected all pins except the 5V (pin 1) one.
[EDIT]
I'm using Devo 7e and have no problem with CC2500. However, I read that btoschi also has problem with CC2500 with Devo8s. Maybe it's a bug specific to that combination.
www.deviationtx.com/forum/7-development/...dule?start=440#24711
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
I managed to bind perfectly my devo 10 w/ MM with the FrSky V8R7-II receiver. I am uploading a video as tutorial. It can help someone in the future.
EDIT : with the video
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
I am uploading another video showing both procédures
EDIT :
Please Log in or Create an account to join the conversation.
- Tomcor
- Offline
- Posts: 12
parkrcmodels.com/product_info.php?produc...tvkv46ofn4qe14slqoi3
Does anyone have a wiring diagram for connecting the module to the Devo 10?
Is the telemetry working with this module?
Thanks for any help.
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
I just reeived my D4R-II module. It's binding perfectly in D mode but the I got only 2 voltages in the telemetry channel. Is it normal ? No RRSI information for example ?
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Topic Author
- Offline
- Posts: 4402
On the Devo8, Frsky uses the Devo display rather than the DSM one.
I only implemented:
Temp1,2
Volt1,2,3
RPM1
GPS
I'm not sure if I have the info on RSSI to be able to decode it. I'll take a look.
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
PhracturedBlue wrote: It looks like I messed up the telemetry parser on the Devo10.
On the Devo8, Frsky uses the Devo display rather than the DSM one.
I only implemented:
Temp1,2
Volt1,2,3
RPM1
GPS
I'm not sure if I have the info on RSSI to be able to decode it. I'll take a look.
I don't know if it's related, but a Hobbyking user of the D4R-II wrote
"Great little receiver.
4 channel output, and if the jumper is used on CH3&CH4 it does output a 8 channel PPM stream plus a RSSI voltage signal on channel 2. RSSI voltage goes from 3,16V (full signal) to 0,18V (no signal).
Perfect for multi copters and for FPV copters.
This telemetry receiver uses A1 for internal receiver voltage and has an external A2 input for your own voltage sensor. "
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
There is a new nice FrSky receiver "L9R" working in the "LR12" mode of the taranis ? Do you think it's possible to also implement it ?
Maybe you don't have such RX ?
Any news for the RSSI in the telemetry information ? (for my devo 10 at least)
Please Log in or Create an account to join the conversation.
- ryane67
- Offline
- Posts: 2
I've connected my CC2500 through a multimodule as well as a direct connect (made a little adapter so I can switch back and forth just in case) but for whatever reason I cannot get the thing to bind to a brand new D4R-II.
Im getting no errors, the cc2500 is properly recognized, it just won't talk to the rx. Sadly I dont have a second frsky rx to test it on... or any other rc toy that uses the cc2500..
I've removed the fixed ID, tried both v8 and normal... my rx just never seems to receive a signal from the tx.. just stays in that constant both LEDs on mode that it starts in when you hold the button down.
Im on 4.0.1-92e1705
Please Log in or Create an account to join the conversation.
- SeByDocKy
- Offline
- Posts: 1016
//byte1 == data len (+ 2 for CRC)
//byte 2,3 = fixed=id
//byte 4 = A1 : 52mV per count; 4.5V = 0x56
//byte 5 = A2 : 13.4mV per count; 3.0V = 0xE3 on D6FR
//byte6 = RSSI?
//verify pkt
//printf("%02x<>%02x %02x<>%02x %d<>%d\n", pkt[1], fixed_id & 0xff, pkt[2], (fixed_id >> 8) & 0xff, len, pkt[0]+3);
if(pkt[1] != (fixed_id & 0xff) || pkt[2] != ((fixed_id >> 8) & 0xff) || len != pkt[0] + 3)
return;
len -= 2;
//Get voltage A1 (52mv/count)
Telemetry.p.frsky.volt[0] = (u32)pkt[3] * 52 / 100; //In 1/10 of Volts
TELEMETRY_SetUpdated(TELEM_FRSKY_VOLT1);
//Get voltage A2 (~13.2mv/count) (Docs say 1/4 of A1)
Telemetry.p.frsky.volt[1] = (u32)pkt[4] * 132 / 1000; //In 1/10 of Volts
TELEMETRY_SetUpdated(TELEM_FRSKY_VOLT2);
And finally RSSI informartion is not retrived ((u32)pkt[5] ?) It's not completly sure that the sixth byte is the RSSI ?
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- Frsky compatibility