Intel® Aero Platform For UAVs
Peer-to-peer support only
Announcements
This is a peer-to-peer only forum. This forum is not monitored by Intel.

Accessing GPS data

APope1
Beginner
1,790 Views

Hi there,

I was wondering if there was a way to programmatically access (such as through an API) the GPS data on board the Intel Aero RTF UAV?

Andrew

0 Kudos
1 Solution
idata
Community Manager
135 Views

Hello Andrew,

 

 

Thank you for your patience.

 

 

The GPS module is connected directly to the flight controller. To access the GPS data, you would need to use an API like dronekit or mavlink to get GPS information. We have basic documentation here regarding Python programming: https://github.com/intel-aero/meta-intel-aero/wiki/04-Autonomous-drone-programming-in-Python https://github.com/intel-aero/meta-intel-aero/wiki/04-Autonomous-drone-programming-in-Python

 

You can start there then look at the mavlink or dronekit manual for additional commands/arguments.

 

 

Hope this helps.

 

 

Regards,

 

Octavian

View solution in original post

3 Replies
idata
Community Manager
135 Views

Hello Andrew,

 

 

Thank you for your interest in our Intel products.

 

Your request has been received and is currently being investigated.

 

We will get back to you as soon as possible.

 

 

Regards,

 

Octavian

 

idata
Community Manager
136 Views

Hello Andrew,

 

 

Thank you for your patience.

 

 

The GPS module is connected directly to the flight controller. To access the GPS data, you would need to use an API like dronekit or mavlink to get GPS information. We have basic documentation here regarding Python programming: https://github.com/intel-aero/meta-intel-aero/wiki/04-Autonomous-drone-programming-in-Python https://github.com/intel-aero/meta-intel-aero/wiki/04-Autonomous-drone-programming-in-Python

 

You can start there then look at the mavlink or dronekit manual for additional commands/arguments.

 

 

Hope this helps.

 

 

Regards,

 

Octavian
APope1
Beginner
135 Views

Thanks for the info.

Kind regards,

 

Andrew
Reply