I have a Pixracer R15 from mRobotics
In order to flash arduplane 4.0.3 do I need to do something special or is it Ok if I I do it from mission planner ?
Alcala
Ps : i posted same request in another post but I believe it is more appropriate to do it here
I finally had the chance to test-fly 4.0.3 stable yesterday, and I had a very successful flight. Upon analysis of the logs, I’m not sure I undertand what is driving a roll demand oscillation in the middle of an automatic mission. See the screenshot (red line indication) and attached log below.
it is navigation indecision. The plane was flying south and the next waypoint was to north. It flipped between turning right and left a couple of times. We do have code to prevent this type of indecision but it isn’t perfect, and sometimes we get temporary indecision depending on the yaw rate of the aircraft at the time.
I am trying to have camera triggering happen on the ground before flying, and now I’m having no luck. It was working a few days ago, and I don’t recall having issues with previous firmwares but now something is different. I believe the logs indicate that the trigger message is not getting through as I can’t find any TRIG events. RC6_Option = 9, and that has worked in the past. Trigger camera now from mission planner is also not working. Log at the following link. https://1drv.ms/u/s!AunBK4rE1ZDCged5m_r3Z2tkNfI0GQ?e=JlXe8S
just a reminder that I’d love to see logs from the 4.0.4beta release. I can’t do the release till I have sufficient logs to be confident everything is OK
We had the same experience while we only had the R-XSR in really, so not even connected to the AP. Ergo Firmware could easily be eliminated.
After tracking down the issue to R-XSR. We replaced them with good old X8R and the problem went away. This was in multiple builds, not just one. So quite confident that the RX is the culprit.
Also we were using X10 (Horus) RC, not X9D as you were.
So it FrSky (R-XSR) internal issue. Maybe can be fixed with firmware, maybe not). The issue only happens if the s-port is enable with any telemetry pass-though. I guess that is why it has laid dormant for so long. Not many people used that s-port. They have been dropping the ball a lot since early last year. Hope they don’t end up like Nokia soon.
EDIT: Sorry, was not clear, we had the issue even before 4.0.4beta was out, so I don’t think it is related to the Firmware IOMCU.
Test your system with X8R or X4R-SB and see if you get the same issue.
the only issue i came across is getting analogue rssi to work on on sbus pin ( 103 )
the rx is outputting voltage as it should i was getting frsky rssi on my tx
and in auto-tune i could get it turn after a pass Turing it took about 300 meters to turn back lol with full aileron turn the only way i get to come back was put in manual mode so with all all that done will test auto takeoff mode next a session