search

pascallanger / DIY-Multiprotocol-TX-Module

Multiprotocol TX Module (or MULTI-Module) is a 2.4GHz transmitter module which controls many different receivers and models.
https://www.rcgroups.com/forums/showthread.php?t=2165676&goto=newpost
GNU General Public License v3.0
1.65k stars 439 forks source link

Flysky x6b receiver behaving weirdly - Part1 #398

Closed LasseLandmand closed 3 years ago

LasseLandmand commented 4 years ago

Okay, so this is kinda a weird problem. I succeeded in binding the RX to the transmitter, and I was also able to read the RSSI value. But when I connected my quad with mamba mk2 stack to my pc, the readings from the receiver tab was weird. For example, if I put the throttle at 10% beta flight would show that value (1100us) but then after a few seconds, the value would jump to 1500us. This would continue to happen on all my channels.

Also, nothing should be wrong with the x6b receiver because it was working perfectly with my previous flysky i6 transmitter and with the same quad setup.

I am using the FLYSKY AFHDS2A protocol with my tx16s internal multiprotocol, and this transmitter is also working perfectly with the same protocol and other flysky receivers.

The transmitter is updated with the lastest version of open tx (2.39) and i am running the latest of Multiprotocol (v1.3.1.36)

Looking forward to any ideas or input :)

pascallanger commented 4 years ago

Have you bound the receiver before upgrading the module? I'm asking because old firmware versions are not using the same hop frequencies and therefore shows exactly the same behavior as what you describe. Can you rebind it and see if you have the same issue? Never heard of an issue with this protocol...

LasseLandmand commented 4 years ago

I have rebound multiple recievers with the transmitter and they all have show the same problem. At this point i am thinking of just going out and buying 3 new frsky recievers. But thanks for the help.

pascallanger commented 4 years ago

Do you have issue only on this receiver? In other words have you tested another RX model? Oups I think you've said you did on your first post... Would you be able to ship me this RX?

pascallanger commented 4 years ago

This issue has been opened for a long time without any new comments for more than a month... Can it be closed?

activa73 commented 4 years ago

I have a same problem with all my X6B reciever and my Radiomaster TX16S with telemtry.

Telemertry is very unstable and lost then all 10 or 15 seconds with the model close or far to me.

I don't understand why? I use last FW for TX16S and use this SW revision for mutiprotocol : multi-stm-opentx-aetr-noinv-v1.3.1.49.bin.

I'm open to test somes solutions.

BR

pascallanger commented 4 years ago

No idea what flyplus is, neither rm16s...

hpoorthuis commented 4 years ago

I have a same problem with all my X6B receiver and my Radiomaster TX16S (latest Software) Do get Messages that Telemetry is Lost. sometimes every 3 Seconds sometime longer. on the Telemetry Tab i see that all Values go to Red for about 1 to 2 Seconds.

With an other Receiver TGY-IA10 (FlySky FS-IA10B) i do not have this Problems. it looks a little bit that the Receiver is loosing Telemetry packets i did Take some Photos the FlySky FS-IA10B have 6 Telemetry Parameter the X6B has 7 Parameter and the Stars are Flashing 2 x Black then one Round Missing ( with Telemetry Lost Message) [https://drive.google.com/file/d/1GhYWUb7L3o2GzWMsgqn9m1BDPqaKWgqj/view?usp=sharing](FlySky FS-IA10B ) [https://drive.google.com/file/d/1355ku9QlPAFDwFht-ixSHjcecyN3xQtN/view?usp=sharing](FlySky X6B) [https://drive.google.com/file/d/1ub6bvYsldRYyTJ2KlZKAlcbzUc3fqWwN/view?usp=sharing](FlySky X6B)

Firmware of the X6B: [https://drive.google.com/file/d/1tPQ7izlu5-XkqrHpp2eWYaMZsGx4x5cu/view?usp=sharing](14 Channel Firmware) [https://drive.google.com/file/d/1dtQkyaLYALKZzGwZNCq3S8EdJbXqW6k3/view?usp=sharing](8 Channel Firmware)

pascallanger commented 4 years ago

I might have a fix for the x6b issue but I need to do some research in the coming days. I hope you will be able to test quickly any new code I'll publish on master.

pascallanger commented 4 years ago

@hpoorthuis @activa73 @LasseLandmand Can you test v1.3.1.67 and see if it fixes your issue? (need to compile from Master)

hpoorthuis commented 4 years ago

@pascallanger , i did compile and install your latest (multi-stm-1.3.1.67.bin). i would say, this goes in the wrong direction. the number of lost Telemetry Messages are heavy (more frequently) yesterday i was out flying with 1.3.1.65 , and i was surprised that the number of Messages reduce if the quadcopter is no longer near. i'm open for new source. Thanks for helping so fast.

pascallanger commented 4 years ago

@hpoorthuis Are you sure that you were testing 1.3.1.67/65 in the same conditions (same distance, orientation...). I would think that the change can either improve or do nothing but not degrade. Can you make sure to retest in the exact same conditions?

hpoorthuis commented 4 years ago

No did test the 1.3.1.67 short distance at Home , and the 1.3.1.65 on the Field (Flying) Will see what can Find out, but need a few Days

pascallanger commented 4 years ago

I've pushed 69 but frankly I don't think it will change anything...

hpoorthuis commented 4 years ago

Today i detected that after I remove the TBS Module the Problems are gone. so it seems to go in an other direction. any Idee? I just updated the TBS Module to the latest Firmware , move the TBS antenna al little away from the Main antenna. All Problems are gone! maybe others have same conditions/ issues. i would say this is not longer a BUG.

pascallanger commented 4 years ago

May be the TBS module was always transmitting and therefore preventing your module to receive correctly the telemetry signal.

activa73 commented 4 years ago

Hello, very strange because, I have exactly the same issue without external module. I don't think the issue is due to external module. Weather is very bad and I can't test new release. I keep you in touch.

Le dim. 27 sept. 2020 à 12:00, pascallanger notifications@github.com a écrit :

May be the TBS module was always transmitting and therefore preventing your module to receive correctly the telemetry signal.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398#issuecomment-699613776, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWSYXNTQKTOSTCGSDLSHWDSH4ELNANCNFSM4PE35OCQ .

sinoseque commented 4 years ago

any update on this? i have same problem with 3 x6b receivers and v1.3.1.69

pascallanger commented 4 years ago

any update on this? i have same problem with 3 x6b receivers and v1.3.1.69

Is the issue still opened?

sinoseque commented 4 years ago

any update on this? i have same problem with 3 x6b receivers and v1.3.1.69

Is the issue still opened?

it is, but part 2 not, anyway is there something i could help with? i mean, could help some debug traces or something like that?

activa73 commented 3 years ago

Hello Pascal, have you try my reciever and show the issue? Thank you.

pascallanger commented 3 years ago

Hello Pascal, have you try my reciever and show the issue? Thank you.

Sorry it's on my desk untouched. I've got some personnal issues getting in my way to get anything completed lately...

activa73 commented 3 years ago

Pas de problème.

Bonne continuation

Le mer. 2 déc. 2020 à 14:44, pascallanger notifications@github.com a écrit :

Hello Pascal, have you try my reciever and show the issue? Thank you.

Sorry it's on my desk untouched. I've got some personnal issues getting in my way to get anything completed lately...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398#issuecomment-737238541, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWSYXJP3QRDSFVMTCFV5NTSSZAELANCNFSM4PE35OCQ .

emolina82 commented 3 years ago

I had both problems, first the receiver in betaflight worked weird. It was fix by himself ... Trying different protocols sbus ibus and didn't happen anymore. But I still having the problem with telemetry (lost and recover)

If you find a solution .. let us know, I'm running the last version of multi module and opentx under Radiomaster TX16s Multi hall gimbals

Best regards

pascallanger commented 3 years ago

Try v1.3.2.45 from here: https://downloads.multi-module.org/latest-test/ The X6B generates loads of FEC errors making the telemetry really sparse. I've disabled the FEC check and only care if the CRC is correct. I hope it won't have bad impacts on telemetry values since only the CRC16 is protecting the payload...

emolina82 commented 3 years ago

hi @pascallanger, I've tried this change and looks like it works like a charm.

I haven't flight yet with this firmware (I suppose it is safe ¿?) but I could do if there is not risk

I've restored to the version v1.3.2.30 and the problem still happens

If you need more test on my side, please let me know and I'll try to help

Thank you so much!!!

pascallanger commented 3 years ago

You should be able to fly safely with this test version as I'm near a release. Please report how it behaves during a flight test.

emolina82 commented 3 years ago

Ok, I will try as soon as possible (but maybe it'll take some time due to covid lockdowns ... )

Is it only affect to FlySky X6B receptor or to all FlySky receptor?

BR

activa73 commented 3 years ago

Hello All, I'm, happy that you have find a solution for this issue. BR

Le lun. 15 févr. 2021 à 20:19, pascallanger notifications@github.com a écrit :

You should be able to fly safely with this test version as I'm near a release.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398#issuecomment-779408443, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWSYXPL6THYNNOGHRH4RGDS7FXTNANCNFSM4PE35OCQ .

pascallanger commented 3 years ago

@emolina82 As said earlier the change affects all RXs.

pascallanger commented 3 years ago

@activa73 As soon as I have good reports i can send you the RX back.

activa73 commented 3 years ago

Thank you Pascal, take your time.

Le lun. 15 févr. 2021 à 20:31, pascallanger notifications@github.com a écrit :

@activa73 https://github.com/activa73 As soon as I have good reports i can send you the RX back.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398#issuecomment-779412691, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWSYXKNR656R3JKJRXUO2DS7FY7VANCNFSM4PE35OCQ .

pascallanger commented 3 years ago

@LasseLandmand @hpoorthuis @emolina82 @Tygrys-1 Has anyone tested the change? I still have @activa73 RX that I've used to troubleshoot and I would like to send it back...

Tygrys-1 commented 3 years ago

Change tested on version 1.3.2.51. Looks like all 5 receivers I tested now are working ok. Telemetry is stable and values looks correct. Good work and thank you for this. :-) I needed to rebind some of my receivers, but AFAIR this was announced some version ago, so no problem.

Whatever this FEC is, if it adds more safety for the protocol than it might be valuable to have for other receiver type. Can you make an option or a sub protocol for the X6B-s, and enable FEC on other AFHDS2A receivers?

I want to share my observations from the tests. With 4 of my receivers everything was smooth, but the last one did act different. 1) I powered the receiver and transmitter and it was bound, but no telemetry. I deleted the sensors and tried to discover - none was found. 2) I rebinded the receiver and tried to discover sensors again. At first it has not found anything. After some time (1 min?) sensors have been discovered, but stayed in red, occasionally blinking black, with low TRSS values ie. 12 and with low RSSI. After some time (20s) sensors stayed black, but still changing and with low values on TRSS. 3) I tried to move the transmitter and reoriented it's antenna, and after a few seconds "normal" TRSS of 248 started to show, sometimes dropping to 100 or so, and after that (next 20s or so) it stabilized itself at constant "good" values, and now it is stable. 4) I tried to switch off/on receiver, transmitter and everything is rock solid and ok.

As I remember, this receiver stopped to send the telemetry during my earlier tests and was not doing that even with the original i6X Flysky radio. Now it returned "back to live", but it was not an instant improvement, but rather a process. Have you any idea, what happened? Does the receiver uses some "autotune" or maybe other error correcting algorithm, which made it "out of sync" with telemetry on my previous tests with the earlier multiprotocol software, and now it returned back to the telemetry working state?

pascallanger commented 3 years ago

Thanks for testing. No idea what your 4th RX is doing... Let's close this issue then. @activa73 can you PM me to make sure I have the correct return address?

activa73 commented 3 years ago

Hello Pascal, what is your PM address please?

Le mar. 2 mars 2021 à 20:30, pascallanger notifications@github.com a écrit :

Closed #398 https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/398#event-4397715918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWSYXIWIDTJTRUZUA6TMCTTBU4G3ANCNFSM4PE35OCQ .

pascallanger commented 3 years ago

hpnuts on RCGROUPS

emolina82 commented 3 years ago

hi @pascallanger

I tested the last weekend and everything looks fine. I only had two telemetries lost alerts, I suppose this is normal in some scenarios.

Thanks!!!!