Please tell me what this message means.: No ap_message for mavlink id (271) .Which error needs to be fixed?
Known issue for 1MB-flash boards. Fix is in dev and is marked for backport to 4.6
GCS_Common: fix missing #if for CAMERA_FOV_STATUS by robertlong13 · Pull Request #29339 · ArduPilot/ardupilot
Hi everyone. Have a same problem, use ArduCopter 4.7.0-dev (f328a659) on SpeedybeeF4V3 and to ground station sending No ap_message for mavlink id (271) .
PreArm checking in log, because to screenshot use only 5v connection. With battery the same problem
I was first on Arduplane 4.5.7 and getting the message like this - Sending Unknown Message (44) on Mission Planner with Speedybee F405 v3 Guided Mode
I then upgraded to 4.6.0 beta5 like I found here - GCS_Common: fix missing #if for CAMERA_FOV_STATUS by robertlong13 · Pull Request #29339 · ArduPilot/ardupilot · GitHub but now I’m getting the
No ap_message for mavlink id (271)
as well. I just want to make sure I’m understanding things correctly. I think this is something that’s currently being backported, so the fix right now is patience, right? Thanks to all the work done by the devs - I’m working on a T1 VTOL right now and am excited to try it out.
It’s still the camera FOV message. I saw a post from (I think) Randy the other day saying it’s on the 4.6 issue list that they’re going to stop it from spamming. A lot of us are getting it.
The T1 is a ton of fun! I get mine done, then I decide to change something big (like the flight controller) so I end up having to re-build it. It’s been great! 
1 Like
Oh that’s good to hear, thanks @Allister! I’m hoping things go decently with the T1 for me as well so I can use it in a class scenario. I was working on V2 of that tailsitter from here Learning VTOL Tailsitter but after building a V2 with larger elevons and still having quite a few control issues in the vertical flight phase, I’m thinking a more traditional setup might work better for class, especially since the students will need to fly in the wind/breeze at times, and that tailsitter being so light is just like a kite - all over the place - haha!
I just arrived here because the 271 message started to appear for me also after updating my T1. Last year I wasn’t successful in even getting it to hover (T1 VTOL: Extremely odd behaviour/errors during first takeoff attempts - #19 by UnknownPilot) and gave up. Certainly my most frustrating AP project so far. Maybe better luck this year with 4.7.0-dev, fingers crossed…
There’s a lot of T1s flying around. Yes, there was some issues with early 4.6 betas in fixed wing mode, but the plane still flew well (aside from the motors sounding like they were full of rocks). Beta 5 has that fixed. And quick tune is now available for F405 boards for VTOL mode so that’s helped.
The 271 message is a pain. The devs know about it. I’ve read it’s on the list to be fixed. But it’s just spam, so depending on your GCS/Telemetry set up, it can be ignored.
1 Like
Thanks for the reports. @peterbarker has resolved this issue and the fix will go out with Copter-4.6.0-beta7 within the next week or so. I can’t say exactly when 4.6.0 will become the stable release but hopefully within a month