Skip to content

GPS prearm errors when arming with MavProxy #4138

Description

@khnunn

Bug report

What's the issue you encountered?

Hi, I’m running ArduCopter 4.1 on a black cube through MaxProxy and AirSim. When start AirSim I get the following response in the MavLink console:

pre-arm good
AP: EKF3 IMU0 origin set
AP: EKF3 IMU1 origin set
Got COMMAND_ACK: DO_SET_MODE: ACCEPTED
Mode GUIDED
pre-arm fail
AP: PreArm: GPS 1: not healthy
Got COMMAND_ACK: COMPONENT_ARM_DISARM: FAILED
AP: PreArm: GPS 1: not healthy
AP: EKF3 IMU0 is using GPS
AP: EKF3 IMU1 is using GPS
Flight battery 100 percent
AP: PreArm: GPS 1: not healthy

Mission planner parameters were taken from Tools/autotest/default_params/copter.param.

Settings

{
  "SettingsVersion": 1.2,
  "LogMessagesVisible": true,
  "SimMode": "Multirotor",
  "OriginGeopoint": {
    "Latitude": -35.363261,
    "Longitude": 149.165230,
    "Altitude": 583
  },
  "Vehicles": {
    "Copter": {
      "VehicleType": "ArduCopter",
      "UseSerial": false,
      "LocalHostIp": "127.0.0.1",
      "UdpIp": "127.0.0.1",
      "UdpPort": 9003,
      "ControlPort": 9002
    }
  }
}

How can the issue be reproduced?

  1. Upload ArduCopter 4.1 using Mission Planner 1.3.75 to a PixHawk Black on a Windows 10 machine. Connect to the device under Simulation in Mission Planner.
  2. Run the following commands in CygWin:
cd ArduCopter
../Tools/autotest/sim_vehicle.py -v ArduCopter -f airsim-copter --console --map
  1. Start AirSim.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions