New FrSkyX protocol

petsmith wrote:

sfersystem wrote: on my Devo10, is it now possible to have the battery voltage with the XSR ?

Yes, extended telemetry is supported on Devo 10. That is, you can see your model's battery on your Devo 10, provided your FC can supply the battery info to XSR via s.port.

Must i buy something else to make it works, or just setup in the devo ?
I have a X-Racer F303 V3.1 FC.

Thank you

petsmith wrote: okay, I took the time to move the FrskyX Extended Telemetry code from RAM to ROM and created a special version for Devo7e.

Thanks so much for the hard work! That was really above and beyond my man. I will try and flash this tonight and report back.

sfersystem wrote: Must i buy something else to make it works, or just setup in the devo ?
I have a X-Racer F303 V3.1 FC.

Thank you

It looks like your FC has VBAT which is what you would need. You would wire your battery's direct voltage (not filtered or stepped down) directly to that port (observing polarity and checking it more than twice) and set up battery voltage monitoring through cleanflight. No additional hardware needed other than 2 pieces of wire to connect your PDB to your FC.

LumpyLouis wrote:

sfersystem wrote: Must i buy something else to make it works, or just setup in the devo ?
I have a X-Racer F303 V3.1 FC.

Thank you

It looks like your FC has VBAT which is what you would need. You would wire your battery's direct voltage (not filtered or stepped down) directly to that port (observing polarity and checking it more than twice) and set up battery voltage monitoring through cleanflight. No additional hardware needed other than 2 pieces of wire to connect your PDB to your FC.

Oh yes, i got it, i'll connect direct the lipo power 3s and / or 4s on these pin i setup on the Devo, thank you very much

I looked at what comprise a protocol module and found that RF chip code goes there to save space for the main body. Maybe we can remove CYRF6936 code from the module and move it to main body, freeing some space which can be used for telemetry. CYRF6936 maybe used directly from the main code and is there anyways.

@petsmith thank you so much for the work you did. You didn't have to and you still went out of your way to do it.
Thank you so much again !
And sorry for my lack of understanding regarding this. I should read the source code a bit

@petesmith: I flashed your custom firmware and received the following message when i power on:

Protocol Mismatch:
0801dd6c
6c6e4f3b

I hit "OK" and went to my model to rebind but received the same message as above. Any suggestions?

LumpyLouis wrote: @petesmith: I flashed your custom firmware and received the following message when i power on:

Protocol Mismatch:
0801dd6c
6c6e4f3b

I hit "OK" and went to my model to rebind but received the same message as above. Any suggestions?

Did you copy the protocol directory from the zip to your 7e? Besides flashing the firmware, you also need to update the protocol modules.

I must have missed something, I reflashed and recopied and no more error now! On the main page config the battery voltage is displayed when I choose "TelemVAmp" but I cannot seem to select TelemVAmp as an option under Telemetry config page. Im trying to set the low battery alarm.

LumpyLouis wrote: I must have missed something, I reflashed and recopied and no more error now! On the main page config the battery voltage is displayed when I choose "TelemVAmp" but I cannot seem to select TelemVAmp as an option under Telemetry config page. Im trying to set the low battery alarm.

It's called VoltA under Telemetry config.

I am an idiot and you are the man. Thanks so much!

LumpyLouis wrote: I am an idiot and you are the man. Thanks so much!

I'm glad that it works.

victzh wrote: I looked at what comprise a protocol module and found that RF chip code goes there to save space for the main body. Maybe we can remove CYRF6936 code from the module and move it to main body, freeing some space which can be used for telemetry. CYRF6936 maybe used directly from the main code and is there anyways.

The CYRF6936 code isn't used by FrskyX, it wouldn't help in this case. It may help if there is a need to support DSM2 extended telemetry on 7e. For FrskyX, the RF CC2500 code is used, but it's quite small and I doubt it will help after moving to ROM space.

petsmith wrote:

victzh wrote: I looked at what comprise a protocol module and found that RF chip code goes there to save space for the main body. Maybe we can remove CYRF6936 code from the module and move it to main body, freeing some space which can be used for telemetry. CYRF6936 maybe used directly from the main code and is there anyways.

The CYRF6936 code isn't used by FrskyX, it wouldn't help in this case. It may help if there is a need to support DSM2 extended telemetry on 7e. For FrskyX, the RF CC2500 code is used, but it's quite small and I doubt it will help after moving to ROM space.

You're right, and even for DSM it will not add much.

petsmith wrote:

LumpyLouis wrote: I must have missed something, I reflashed and recopied and no more error now! On the main page config the battery voltage is displayed when I choose "TelemVAmp" but I cannot seem to select TelemVAmp as an option under Telemetry config page. Im trying to set the low battery alarm.

It's called VoltA under Telemetry config.

That's right i get now a voltage on the DEVO, but the value is not correct.
I have a 3s lipo with 3.8v at each cell, and in Telem V1 i have 4.8V and in Telem V2 i have 2.67V
Is it possible to have the sum of the 3 cell ?

I found the AD2GAIN to adjust voltage ''factor'' but if i change to a 4s lipo it doesn't show the good voltage.

Is there something special to setup in betaflight too ?

Thank you for help.

If you use the vbat input to the FC, you'll need to also make a connection from the xsr s.port pin to a uart on the FC and set up betaflight to output s.port on that uart. Then you'll get extended telemetry (not available on 7e) for the total voltage.

Alternatively you can use this information to use the AD2 input on the xsr. A voltage divider is needed to limit AD2 to about 3V. The AD2GAIN is then used to calibrate the reported value.

hexfet wrote: If you use the vbat input to the FC, you'll need to also make a connection from the xsr s.port pin to a uart on the FC and set up betaflight to output s.port on that uart. Then you'll get extended telemetry (not available on 7e) for the total voltage.

I think that is the best way, i'll do that.
The s.port pin (3rd) on uart 2 for example.

But on uart i have :
Tx
Rx
5V
Ground

Must i connect 4 wire to make it work or just the s.port on RX ?

Thank you hexfet, i'm almost ok

The s.port pin on the receiver both transmits and receives. Don't know how that connection is made with your FC and betaflight. I haven't done it myself, but google says for the naze FC and cleanflight the uart TX and RX are tied together and connected to the s.port pin.

Ok, thank you for the time spend, i'll try tonight and will give some news.

Edit : You're rigth, will try it tomorow
Explanation here !!

I bridged the rx and tx pin from my F303 V3.1 and connected to smartport of the xsr, on the telemetry menu from my DEVO10 i saw 4.8v (maybe the voltage of the FC) and always the 2.6v. I've done the modification in betaflight (activated the softserial, the telemetry and the vbat) and selected smartport in port menu for the softserial line.

i miss something ?

I have the right voltage in Betaflight