Newby trying to get first FPV build up and running.
I have a Jumper T-lite that would not bind to FRsky XM+. I figured the place to start was to update firmware on the Jumper t. I flashed opentx version 2.3.14 to the Jumper T and multi-stm-cc2500-aetr-v1.3.2.86.bin to the internal Multi module.
All seemed in order except that in the setup screens under Internal RF I get Status: 'No Telemetry'
This was working before and reported the version #.
ideas?
tnx bcs
Jumper-t lite and int. Multi Status=No telemetry
Re: Jumper-t lite and int. Multi Status=No telemetry
Pretty sure. I had a choice of the CC2500 or 4-in-1 and chose CC2500 to save a few bucks.
Re: Jumper-t lite and int. Multi Status=No telemetry
Hi,
I have exactly the same setup. T-Lite with only cc2500 module.
After flashing to multi-stm-cc2500-aetr-v1.3.2.86.bin I have "No telemetry" for the status of the internaal module and can`t bind.
Also tried older versions and other channel settings (reta, ...) but always the same "No telemetry".
Did you solve your problem and found a working version?
Regards
Dominik
I have exactly the same setup. T-Lite with only cc2500 module.
After flashing to multi-stm-cc2500-aetr-v1.3.2.86.bin I have "No telemetry" for the status of the internaal module and can`t bind.
Also tried older versions and other channel settings (reta, ...) but always the same "No telemetry".
Did you solve your problem and found a working version?
Regards
Dominik
Re: Jumper-t lite and int. Multi Status=No telemetry
hi again,
for your information:
I managed to update the cc2500 module firmware now with the latest release v1.3.30
But there seem to be module versions which use a 64k chip instead of the usual 128k. And the provided firmware supporting all the protocolls and sub-protocolls is to big to fit to the 64k chip.
Now for v1.3.30 they provided a smaller 64k version for the "cc2500 only module". With this version I now was able to flash and the Module status shows the version again.
Binding (FrskyX2 to reciever with v2.1 FCC firmware) also works again.
for your information:
I managed to update the cc2500 module firmware now with the latest release v1.3.30
But there seem to be module versions which use a 64k chip instead of the usual 128k. And the provided firmware supporting all the protocolls and sub-protocolls is to big to fit to the 64k chip.
Now for v1.3.30 they provided a smaller 64k version for the "cc2500 only module". With this version I now was able to flash and the Module status shows the version again.
Binding (FrskyX2 to reciever with v2.1 FCC firmware) also works again.