ArduPilot / ArduPilot/MissionPlanner
geottaging failed when use AMSL alt is checked
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
Hi !
I use Missionplanner 1.3.32
I can't geotag when "use AMSL alt" box is checked.
Missionplanner says :
Using AMSL Altitude True
Reading log for GPS Messages in order to get AMSL Altitude
Log file problem. Aborting....
When i uncheked the box, it works fine but I can just geottag with RelAlt.
I checked in the log file and in each CAM message, there is the Relalt and the alt, so the information is inside the log.
In the log file, the parameters at the beginning are : (extracts)
FMT, 130,45,GPS,BIHBcLLeeEefI,Status,TimeMS,Week,NSats,HDop,Lat,Lng,RelAlt,Alt,Spd,GCrs,VZ,T
...
FMT, 148, 31, CAM, IHLLeeccC, GPSTime,GPSWeek,Lat,Lng,Alt,RelAlt,Roll,Pitch,Yaw
And an example of a CAM message in the log :
CAM, 199703600, 1866, 46.5888149, 3.877452, 360.49, 59.68, 5.64, -9.19, 338.91
360.49 is the absolute Alt and 59.68 is the relAtl.
Thanks for your help !!
Best regards from France.
Arnaud.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce geotagging in Mission Planner 1.3.32 with “use AMSL alt” enabled, using a log containing the shown FMT and CAM messages. Start by tracing the geotagging log reader’s handling of CAM Alt and RelAlt fields. Done means AMSL geotagging completes successfully and uses the absolute Alt value while RelAlt mode continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100