This is a discussion moved from this issue https://github.com/ArduPilot/ardupilot/issues/17332
hardware: Kakute F7 with R9 MX OTA Receiver
video: https://youtu.be/kiTocs65BFE
This is a discussion moved from this issue https://github.com/ArduPilot/ardupilot/issues/17332
hardware: Kakute F7 with R9 MX OTA Receiver
video: https://youtu.be/kiTocs65BFE
Hello,
I tried again with a full reset of parameters and still got the same results.
Enclosed a log file, but I check it and I didn’t show anything and I got no informations/errors/warning in Mission planner
Link to the log file (@khancyr)
https://drive.google.com/file/d/1v0JpnE5wI15o7BFyB47_NT-ZzBxQDVWy/view?usp=sharing
It’s taken me some time to get back to this but in any case, I’ve sent a request for perms to the log. txs!
Hi @Dronotique,
I doubt it has helped any but could you see if -beta4 works any better? I suspect it won’t but I’d like to be sure.
@yaapu, do you think you could help me look into this?
Hi @rmackay9,
I tested with V4.1.0-beta4 (37070bfe).
I don’t get the error anymore, thanks!
But my setup changed a little bit. Now I have a R9M Lite RF module instead of the Pro one.
And I didn’t keep the old beta version of Arducopter firmware (arround 5th may) to make a comparison
OK, well, good news in any case.
If you’d like to re-test with beta1 I’ve put a Kakutef7 binary for Copter-4.1.0-beta1 here.
I forgot to mention that my FC is a Kakute F7 “Mini”
@rmackay9 Sorry, i’ve just seen your message… I don’t found still the time to continue on this issue, I’m sorry for the delay
Hi, if you could re-test with the latest beta that would be a great help. I’m reviewing all our outstanding issues to ensure they have all been resolved.
At the moment -beta7 is the best beta to use but we are planning another beta release in the next few days.
Hello,
I tried to reproduce the error but I didn’t get it anymore with beta 7… I think it’s OK now.
Do you have any informations about the problem?
Thanks a lot!
Great, thanks for the feedback. I’m not aware of any specific changes to FPort but perhaps @andyp1per has some ideas as to what change might have fixed this.
No idea, sorry Glad its fixed though.