Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Moblite7 + Taranis X9 Lite short range issue
#1
Hi guys,

Finally I've got my Moblite7.
And I am frustrated... I am having major short range issue. It is like 20-25 metres outdoor.
First of all, I have spent about 2 days, trying to bind TX with RX. And all in vain.
I downgraded TX software to 1.1.3 with no success.
I have read all the internet, which told me that I have to get the latest SW for TX, download the latest BetaFlight nightly build, and install latest development build of BF. And then bind in frsky_x_v2 RX mode. And it all settled. But the range is very low. VTX is set to 25 mW. Picture is good. But I have messages "RX critical", "Telemetry lost" all the way and whoop failsaves.

Does anyone have any idea, what to do?
There are some messages on the web addressing the same problem. But I have found no solution.
I can see two options, there are only few people affected and there is no solution. Or the solution is very simple...
And flying time is great. Something between 10 - 12 minutes!

Moblite7 is Crazybee4FR
Taranis X9 Lite is 2.3.12
TX is ISRM 1.1.0/2.1.6 FCC
Code:
#

# diff all

# version
# Betaflight / STM32F411 (S411) 4.3.0 Jun  7 2021 / 22:27:42 (c84170fac) MSP API: 1.44
# config: manufacturer_id: HAMO, board_name: CRAZYBEEF4FR, version: 56f796fb, date: 2019-10-26T09:47:21Z

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name CRAZYBEEF4FR
manufacturer_id HAMO
mcu_id 0029001d3037510637313839
signature

# feature
feature -RX_PARALLEL_PWM

# serial
serial 1 2048 115200 57600 0 115200

# map
map TAER1234

# aux
aux 0 0 0 1450 2100 0 0
aux 1 1 1 900 1300 0 0
aux 2 2 1 1300 1700 0 0
aux 3 27 3 1300 2100 0 0
aux 4 35 2 1300 2100 0 0
aux 5 47 1 1700 2100 0 0

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665    0 5885 5905    0    0
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6     I CUSTOM  5732 5765 5828 5840 5866 5740    0    0
vtxtable powerlevels 3
vtxtable powervalues 0 1 2
vtxtable powerlabels 25 100 200

# master
set acc_calibration = 34,-159,-5,1
set rx_spi_protocol = FRSKY_X_V2
set motor_output_reordering = 3,2,1,0,4,5,6,7
set align_board_yaw = 180
set bat_capacity = 650
set yaw_motors_reversed = ON
set simplified_gyro_filter = ON
set osd_cap_alarm = 650
set osd_vbat_pos = 2370
set osd_rssi_pos = 2105
set osd_throttle_pos = 2168
set osd_vtx_channel_pos = 2451
set osd_ah_pos = 2159
set osd_mah_drawn_pos = 2402
set osd_warnings_pos = 14666
set osd_disarmed_pos = 2411
set osd_nvario_pos = 301
set vtx_band = 3
set vtx_channel = 1
set vtx_power = 1
set vtx_low_power_disarm = UNTIL_FIRST_ARM
set vtx_freq = 5705
set frsky_spi_tx_id = 78,3,14
set frsky_spi_offset = -22
set frsky_spi_bind_hop_data = 1,96,191,51,146,6,101,196,56,151,11,106,201,61,156,16,111,206,66,161,21,116,211,71,166,26,121,216,76,171,31,126,223,81,178,36,131,226,86,181,41,136,231,93,186,48,141,0,0,0
set frsky_x_rx_num = 1
set gyro_1_align_yaw = 900

profile 0

# profile 0
set vbat_sag_compensation = 100
set iterm_relax_type = GYRO
set simplified_dterm_filter = ON

profile 1

profile 2

# restore original profile selection
profile 0

rateprofile 0

rateprofile 1

rateprofile 2

rateprofile 3

rateprofile 4

rateprofile 5

# restore original rateprofile selection
rateprofile 0

# save configuration
save
#
Reply
Login to remove this ad | Register Here
#2
Could be faulty hardware. Or just a lot of background noise where you fly.
Reply
#3
I don't think, it is due to high noise floor, cause tests were outside of the city.
Shall I consider adding external receiver like XM+ or R-XSR? Are they both compatible with ACCESS 2.0 protocol? As mentioned in neighbouring treads, R-XSR has some range issues as well.
Reply
#4
I have a lot of R-XSR and do not have range issue. But worth considering an external receiver.
Reply
#5
Thank you, voodoo614.
Sorry for mistake, I have been thinking about ACCST D16.
I think I will stick to XM+ for it liter weight. And I hope I can flash it with F-port compatible firmware to get RSSI in goggles.
Reply
#6
XM+ do not have F. Port. You can however can flash SBUS firmware with RSSI.
Reply
#7
Ok, I am new here, that is why I am confusing things some time.
Reply
#8
(10-Jun-2021, 08:48 AM)boredwag Wrote: Ok, I am new here, that is why I am confusing things some time.

Do not worry, you are not alone when it comes to this confusion. I still fly a FrSKY radio gave up on FrSKY RX's and their protocols a long time ago.

For your range issues, one additional thing that was always suggested by Betaflight dev's on FrSKY_SPI receivers was to disable Telemetry output via the Betaflight configurator> Configuration page> Other Features as a test.
Reply
#9
I am starting to R/R my rxsr RXs due to some close failsafes.(I’m not alone), and installing crossfire... I. Like to fly over water and faisafe is NOT an option.. and Frsky’s new firmware doesn’t support d8 (poor business decision in my book- I would have EASILY used the new Archer RXs than go crossfire....)
I still have multiple small quads with spin D8 RXs, most have got a antenna mod. Props off fpv is to thank for this .. your exposed element at 32.8mm will give u the best range... I can say first hand I have gotten up to 1,500-1,600 feet before failsafe.. I have also installed the Emax mini d8 rx (fpvcycle-$10).. and will outfly the vtx ..
Reply
#10
kafie1980, disable Telemetry output via the Betaflight configurator is off by default. I have tried to put in on and got crazy telemetry lost - telemetry found merry go round. To fix that I had to reset the whoop to factory defaults.

Rob Axel, Antenna length is not an issue. I have already tried to play with it. And I bought another one for replacement.

If you take whoop and TX few (2...3) metres apart and leave them steady in line of sight, and make a range check in Taranis, RSSI will jump up and down as crazy.

Today I have bought FRSKY Archer M+ from local supplier. I will solder it in tomorrow.
Reply
#11
if you have the onboard receiver on your whoop, try D8, works better than D16, also I don't know if your radio have it , but there is a fine frequency adjustment that you need to do for Max range.(within the limitations of the frysky protocol)
that at least on the J4in1 multi protocol modules
I only know that i know nothing 
Reply
#12
Well,
I have soldered FRSKY Archer M+ ...
Registered it in my Taranis X9 Lite and bound it. Made a quick test just walking with radio in hands around my apartment. Connection seems to be a little bit more reliable, but not much. Probably, as voodoo614  mentioned, my place has too much radio noise.
So, I think this is it for the moment.
As Archer M+ doesn't give me range gain, I will leave my Moblite as is and will find less radio contaminated place and take more outdoor tests.
Archer M+ will go to the next build.

Rob Axel, unfortunately, Taranis X9 Lite doesn't support D8.

Thanks everyone for valuable comments and support.
Reply
#13
I have the same problem. Radiomaster tx16s + Moblite7(frsky D8)

I am thinking of using an off-the-shelf transmitter

banggood.com:
Q:Can external receiver be used? For example TBS Crossfire Nano RX.
A:
Yes. For CRFS receiver, Receiver's TX to FC'S RX1, Receiver's RX to FC's TX1, 5V power for receiver and GND to GND. UART1 set into Serial RX and Proctol choose CRSF
Reply
#14
(02-Jul-2021, 05:54 PM)etelo Wrote: I have the same problem. Radiomaster tx16s + Moblite7(frsky D8)

I am thinking of using an off-the-shelf transmitter

banggood.com:
Q:Can external receiver be used? For example TBS Crossfire Nano RX.
A:
Yes. For CRFS receiver, Receiver's TX to FC'S RX1, Receiver's RX to FC's TX1, 5V power for receiver and GND to GND. UART1 set into Serial RX and Proctol choose CRSF

If you are only flying whoops then a Crossfire system is an overkill.

Get a compatible receiver that your radio can support. Since you have a Radiomaster tx16s then look for an external Frsky receiver.

I like the Emax mini d8 rx option as it is fairly light weight: 0.62 g (with antenna) on a whoop: https://emaxmodel.com/products/emax-tiny...bus-output
Reply
#15
(02-Jul-2021, 05:54 PM)etelo Wrote: I have the same problem. Radiomaster tx16s + Moblite7(frsky D8)

I am thinking of using an off-the-shelf transmitter

banggood.com:
Q:Can external receiver be used? For example TBS Crossfire Nano RX.
A:
Yes. For CRFS receiver, Receiver's TX to FC'S RX1, Receiver's RX to FC's TX1, 5V power for receiver and GND to GND. UART1 set into Serial RX and Proctol choose CRSF
I have the same setup as you but not had any range issues, I've also bound using D8 mode. Do you have any damage to your receiver antenna? I managed to cut a small part of the end of the antenna with the props and the range went down drastically.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Help UZ65 Flysky version binding/arming issue chonfel32 29 2,405 14-Jun-2024, 01:28 PM
Last Post: mstc
  Build Pavo Pico WS Lite mstc 20 2,442 16-May-2024, 12:48 AM
Last Post: mstc
  Help TinyHawk 2 Freestyle Rx issue Diesel79 3 341 27-Mar-2024, 09:15 AM
Last Post: Rob Axel
  Mobula 6 throttle issue with Tattu 300mAh HV batt husafreak 18 2,117 05-Mar-2024, 04:50 PM
Last Post: husafreak
  Build ACK80 Attack Chicken Walksnail with motor issue Cyberess 11 645 13-Feb-2024, 04:55 PM
Last Post: iFly4rotors


Login to remove this ad | Register Here