Thanks for the info's.
However, this whole discussion came up relative to the F.Bus protocol. Have you tried it anymore?
I have not.
Entire reason I wanted to use FBus was to have iKon2 & GPS on a single Rx but after deciding to add the R9MX, it's ability to add a second, longer range, telemetry source to my setup that could run the GPS killed the FBus requirement.
I can definitely give it another shot for you guys though.
I just wanted to nail down/make sure the current issue is resolved. Especially since it MIGHT have something to do with the GPS sensor & how it's wired.
Unless your think it may be better to have the GPS running in it's FBus mode on the same line as the Archer RS/iKon2?
As I type this out I don't recall having any RxThrottle spikes on FBus (or at least didn't catch any in the logs), just the uncommanded throttle holds.
I'm still a little apprehensive but I guess I can give it a shot!
Just a reminder that by connecting the GPS to the same bus that is connected to the flight controller, you can also log in the flight logs of the FCU the two parameters Altitude and Vspeed measured by the GPS and added to the loggable parameters as of the fifty-fifth firmware version.Unless your think it may be better to have the GPS running in it's FBus mode on the same line as the Archer RS/iKon2?
Edit: logs to go with this post have been posted in next reply
Hi guys. Here's an update.
1st, with my original Archer RS/R9 MX config:
- I have had a couple instances of the throttle out dropping w/o a corresponding drop in RxThrottle. At least in the logs anyway
- I'll upload the logs when I have access to them. Just thought I'd drop a line first b/c I don't want you releasing what was incorporated in that beta 096 FW for my issue w/o having a look first.
- You guys may have made changes based on your internal testing, but TBH, with the info I have on my end, I'm not entirely convinced any changes were required in the 1st place.
2nd, with only the Archer RS connected with FPort (however, I did keep the r9 MX powered on its own bus in case there were interference issues):
- I'm confident in saying that with the 096 FW there are no issues
- I haven't reverted to the production 094 FW & tested
- I've got a little over an hour of in flight testing w/o any noticable issues with this config other than a few instances of large Fade counts/flights with steady spikes in frame rate
- Nothing enormous, just flights where frame rate doubling was well distributed throughout flight
- How serious are fades? Is there a number or trend that begins to indicate it's not safe to fly a certain config?
- I pushed the Archer RS back further on the boom & seemed to reduce the relatively small number of fades ("relatively small" being based only on my experience & what I've seen elsewhere - hence the question regarding seriousness)
- I'll upload logs when I have access
3rd, with only the r9 MX connected with FPort:
- This is where shit gets weird
- I can't make heads or tails of the logs b/c frame rate just keeps stepping up & up & up & then starts stepping down
- Frame rate flies off the scale
- Fades show a zero line throughout the log, but the max is pegged at 65k & avg is half that
- Events are all messed up & often won't catch a full flight & sometimes no flight
- Events say log deleted but log still exists, etc
- Is there a way to clear all data from the event logs?
- I've reset the unit to default, erased log memory, reloaded FW, reset logging to default using the file menu, etc
- I Don't know what's going on b/c in this config, it flies perfectly (at least as far as my crappy piloting skills can tell)
- Again, I'll upload some logs when I have access to them
(edit: logs posted in next reply)
Regards,
Steve B
Here are the logs and events to go with previous post.
Throttle Out drop with no RxThrottle Drop (original R9 MX sbus out to Archer RS sbus in to iKon2 with FPort):
Archer RS to iKon2 with FPort (events5 covers all 3 flights):
Still only Archer RS to iKon2 with FPort, end of day 2 (just a few fades)
Now R9 MX enhanced to iKon2 with FPort (this is where the weird stuff is):
If these last 2 are accurate I could see redundancy not working correctly. But, again, I didn't notice any weird stuff during flight. Everything seemed fine.
But I'm going to relocate the R9 MX rx out on the boom to see if it does anything with the frame rate.
But not sure why the logs/events seem very buggy just by using the R9 mx directly to the iKon2. Possible FPort bugs? Most recent firmware is pretty old for this Rx.
Regards,
Steve B.
In the answer to question #29 in the FAQ section, you can read that during a normal flight it can be considered normal to have about 150 Fades. The important thing is that the holds remain at zero.
In your log #4, the 186 fades without holds are therefore to be considered "normal."
If by repositioning the receiver antennas away from the shielding carbon parts, you can reduce the fades is obviously better.
I understand that the problems are there when you use the old R9 MX receiver connected alone or in redundant mode with the newer Archer (unlike the older receivers the Archers also work with the new F.Bus protocol).
Since 900MHz/868MHz long-range receivers are only needed when doing long distance FPV flights, not using it is not a big problem with RC Eli since due to their inherent instability compared to drones, they need to be "in sight" at all times in order to constantly control their attitude.
If I remember correctly, you also have an Archer R4. It would be much better to use this receiver together with the Archer RS to do redundancy (unless the Archer RS receivers, which are the only Archer receivers to use a different firmware from all other Archer receivers, has a redundant mode operation problem in its firmware).
Since 900MHz/868MHz long-range receivers are only needed when doing long distance FPV flights, not using it is not a big problem with RC Eli since due to their inherent instability compared to drones, they need to be "in sight" at all times in order to constantly control their attitude.
If I remember correctly, you also have an Archer R4. It would be much better to use this receiver together with the Archer RS to do redundancy (unless the Archer RS receivers, which are the only Archer receivers to use a different firmware from all other Archer receivers, has a redundant mode operation problem in its firmware).
As it stands, everything is pointing to not using the 900Mhz.
I thought my flight area was very polluted on 2.4ghz which is why I'm trying to use the R9 backup Rx, but it looks like better 2.4ghz Rx positioning may be enough. Adding the R4 and/or Archer M+ may just be the way to go.
It's just weird that the R9 MX produces a heli that flies perfectly but produces such issue with the logs & events.
Do you have any comment on that?
From past experience I'm thinking it won't matter, but if you can tell me it's indicative of "old" FPort problems I can at least forward that to FrSky to be ignored. LOL
Anyway, I'm going to move the r9 MX to see if anything changes.
Then move on to testing the R4 & M+.
Hopefully those will test fine on their own, and then I can start hooking up in redundancy mode to see if the RS is in fact not operating the way it should, or if the problem was stemming from the r9 MX the entire time.
Thanks for the FAQ on the fades. Lot of info spread around & I don't always remember where.
Regards,
Steve B.