GLOBAL_POSITION_INT vs GPS_RAW_INT

[pgiacalo]

Hi guys,

Question. It appears that mavelous is using mavlink message type GPS_RAW_INT rather than GLOBAL_POSITION_INT for data updates. If so, is there a particular reason for this choice?

The mavlink web site has this to saw about GPS_RAW_INT...

"The global position, as returned by the Global Positioning System (GPS). This is NOT the global position estimate of the sytem, but rather a RAW sensor value. See message GLOBAL_POSITION for the global position estimate..."

Thanks,
Phil

[pchickey]

Hi Philip,

We're probably doing that wrong. I implemented it originally and never
found any good reason to change it, but I agree we should if it will help
us work with more vehicles than just ArduCopter, which sends the same info
in both messages.

If you could please file this as a bug to investigate on github, that will
help me remember once I have some time to work on Mavelous again (next two
weeks are not so good...).

Best
Pat

On Wed, Jan 30, 2013 at 5:57 PM, Philip Giacalone
[email protected]:

Hi guys,

Question. It appears that mavelous is using mavlink message type
GPS_RAW_INT rather than GLOBAL_POSITION_INT for data updates. If so, is
there a particular reason for this choice?

The mavlink web site has this to saw about GPS_RAW_INT...

"The global position, as returned by the Global Positioning System (GPS).
This is NOT the global position estimate of the sytem, but rather a RAW
sensor value. See message GLOBAL_POSITION for the global position
estimate..."

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47.

[pgiacalo]

Ok, thanks. I'll file the bug. Sorry about that...

---

From: Pat Hickey [email protected]
To: wiseman/mavelous [email protected]
Cc: Philip Giacalone [email protected]
Sent: Wednesday, January 30, 2013 8:35 PM
Subject: Re: [mavelous] GLOBAL_POSITION_INT vs GPS_RAW_INT (#47)

Hi Philip,

We're probably doing that wrong. I implemented it originally and never
found any good reason to change it, but I agree we should if it will help
us work with more vehicles than just ArduCopter, which sends the same info
in both messages.

If you could please file this as a bug to investigate on github, that will
help me remember once I have some time to work on Mavelous again (next two
weeks are not so good...).

Best
Pat

On Wed, Jan 30, 2013 at 5:57 PM, Philip Giacalone
[email protected]:

Hi guys,

Question. It appears that mavelous is using mavlink message type
GPS_RAW_INT rather than GLOBAL_POSITION_INT for data updates. If so, is
there a particular reason for this choice?

The mavlink web site has this to saw about GPS_RAW_INT...

"The global position, as returned by the Global Positioning System (GPS).
This is NOT the global position estimate of the sytem, but rather a RAW
sensor value. See message GLOBAL_POSITION for the global position
estimate..."

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47.

—
Reply to this email directly or view it on GitHub.

[pchickey]

Oh, crap, I just realized I responded to an actual github issue - for some
reason I though this was a mailing list post. I'm sorry for not having any
idea what was going on!

On Wed, Jan 30, 2013 at 10:40 PM, Philip Giacalone <[email protected]

wrote:

Ok, thanks. I'll file the bug. Sorry about that...

---

From: Pat Hickey [email protected]
To: wiseman/mavelous [email protected]
Cc: Philip Giacalone [email protected]
Sent: Wednesday, January 30, 2013 8:35 PM
Subject: Re: [mavelous] GLOBAL_POSITION_INT vs GPS_RAW_INT (#47)

Hi Philip,

We're probably doing that wrong. I implemented it originally and never
found any good reason to change it, but I agree we should if it will help
us work with more vehicles than just ArduCopter, which sends the same info
in both messages.

If you could please file this as a bug to investigate on github, that will
help me remember once I have some time to work on Mavelous again (next two
weeks are not so good...).

Best
Pat

On Wed, Jan 30, 2013 at 5:57 PM, Philip Giacalone
[email protected]:

Hi guys,

Question. It appears that mavelous is using mavlink message type
GPS_RAW_INT rather than GLOBAL_POSITION_INT for data updates. If so, is
there a particular reason for this choice?

The mavlink web site has this to saw about GPS_RAW_INT...

"The global position, as returned by the Global Positioning System
(GPS).
This is NOT the global position estimate of the sytem, but rather a RAW
sensor value. See message GLOBAL_POSITION for the global position
estimate..."

Thanks,
Phil

—
Reply to this email directly or view it on GitHub<
https://github.com/wiseman/mavelous/issues/47>.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-12929833.