HK CGS- ApmMega Ublox Mode display problem

HI,

Happy thanks for the GCS!

I have run into a couple of issues (last one nit-picky) and was wondering if anyone someone has any insight.

Using Apm Mega 1.02, UBLOX, 1.2.38 GCS, 72mhz radio.

As mentioned in other posts in this forum the GCS shows Not Locked, even though the amber and red lights are illuminated on the OilPan and the Google Earth view in the right side pane shows the current location.

Shows 0 satellites.

HDOP 0

The mode function is not showing correct data. With everything (APM, OilPan, GPS, 72mhz transmitter and receiver) operating normally the mode display switches between RTL and Loiter at about 1/2hz. This occurs regardless of what mode is selected on the transmitter. The APM is behaving normally, meaning when different modes are selected via the transmitter such as Stabilize or Manual are selected the APM behaves correctly. Tested both with a direct USB connection and 900mhz XBees. Also verified via Modeswitch test in CLI.

Throttle always displays 75%

Not a real big deal but a turn coordinator should not display bank angle but should display change about the yaw axis . The turn coordinator should display the rate of turn or heading change. The type of instrument that is portrayed in the GCS display is used to make coordinated standard rate turns, meaning if the wing tip is touching the right or left index a 360 degree heading change will be accomplished in 120 seconds independent of bank angle.

Joe

// GCS_PROTOCOL OPTIONAL
// GCS_PORT OPTIONAL
//
// The GCS_PROTOCOL option determines which (if any) ground control station
// protocol will be used. Must be one of:
//
// GCS_PROTOCOL_NONE No GCS output
// GCS_PROTOCOL_STANDARD standard APM protocol
// GCS_PROTOCOL_SPECIAL special test protocol (?)
// GCS_PROTOCOL_LEGACY legacy ArduPilot protocol
// GCS_PROTOCOL_XPLANE HIL simulation ground station
// GCS_PROTOCOL_IMU ArdiPilot IMU output
// GCS_PROTOCOL_JASON Jason's special secret GCS protocol
//
// The GCS_PORT option determines which serial port will be used by the
// GCS protocol. The usual values are 0 for the console/USB port,
// or 3 for the telemetry port on the oilpan. Note that some protocols
// will ignore this value and always use the console port.
//
// The default GCS protocol is the standard ArduPilot Mega protocol.
//
// The default serial port is the telemetry port for GCS_PROTOCOL_STANDARD
// and GCS_PROTOCOL_LEGACY. For all other protocols, the default serial
// port is the FTDI/console port. GCS_PORT normally should not be set
// in your configuration.
//
//#define GCS_PROTOCOL GCS_PROTOCOL_STANDARD
//#define GCS_PORT 3

Replies

Paul Mather April 11, 2011 at 10:53pm

Joe, I know this is an old topic, but locked, sats and HDOP should all be fixed using the MAVlink protocol (APM Beta 2.0). Throttle should also be corrected (I think this was a typo I caught some time ago). You're also right about the turn coordinator. I'm missing the gyro value on the ball at the bottom. It's on my To-Do list. I also need to fix the vertical speed indicator. That thing's all over the place and doesn't really show accuracte values other than the plane is going up or the plane is going down.
Joe March 19, 2011 at 4:37pm

3.0v per cell

Phil Cole March 2, 2011 at 7:25pm

Did you change the part of your APM_config file shown below?

If not, then you are probably running the APM binary protocol. The doesn't support a lot of the data that the HKGCS can display, and it won't since APM is changing to Mavlink protocol in the soon to be released Version 2.

The GCS displays the protocol in use in the COM Port Control tab near the bottom left of the window as GPS Type

If you change to using GCS_PROTOCOL_LEGACY you'll get more information on the display.

---------------------------------------------------------------------------------------

Phil Cole March 2, 2011 at 5:07pm

Which protocol are you using?

This reply was deleted.

Discussions

HK CGS- ApmMega Ublox Mode display problem

Replies

Activity