GPS data through FTDI interface?
Greetings all,
Forgive me if this is a common noob question. I have some ancillary equipment on my plane which needs GPS input. I would like to pass the data through the FTDI cable as it would provide a much more convienient method for being able to route the GPS data through my systems than trying to directly attach the GPS to the AP and either recoding to output to my onboard systems or mounting a second GPS source.
The onboard systems are routing the GPS data correctly to the FTDI interface but I am not able to achieve GPS lock on the AP. Tried using UBX and NMEA format data (with appropriate config changes on the AP code). Can anyone provide some input on the right way to pass GPS data to the AP via FTDI cable in order to achieve GPS lock? The goal is to essentially fly the plane with the GPS data streaming in through the FTDI cable vice connecting the GPS to the GPS port on the AP.
I saw a bunch of threads mentioning helper apps to simulate missions via flight sim software and some mention of using the GPS emulator in a similar manner so I am hoping that someone has already beaten this horse to death and can point me in the right direction.
Thanks in advance,
Mike
Replies to This Discussion
-
Permalink Reply by Chris Anderson on
-
Not quite sure I understand the question, but I'll try a few answers:
--First, if you're having trouble getting GPS lock: Which module are you using? If it's a uBlox, did you buy it preprogrammed for ArduPilot?
--Second, about passing through GPS data to other onboard components: That's easy to do. You wouldn't use the FTDI cable (that's just for USB connectivity), but rather the TTL serial lines. Most gear that uses GPS can accept a TTL serial input, which is the native mode of most GPS modules.
-
Permalink Reply by RedQueen on -
Thanks for the reply :)
It's not your understanding, it's my infinitessimal skill level lol. I am very new to this.
1) Well, right now it is the GPS emulator v.1.2.6 outputting UBlox to my onboard systems which are routing the data to the FTDI USB/serial interface at 38400. I've been holding off on buying the GPS unit until I know if this strategy is possible because it effects other purchasing and design decisions.
2) Onboard system's native serial ports are all busy ;) We had plenty of open USB though. FTDI seemed the quickest, easiest way to do it.
I appreciate your taking time to help me, this community is amazingly deep in experience and I am learning volumes just reading and tinkering.
-Mike
Top Content
Groups
-
ArduCopter User Group
478 members
-
ArduPlane User Group
299 members
-
ArduCopter (traditional …
77 members
-
ArduPilot (legacy) User …
77 members
-
Moderators
50 members
-
ROS User Group
31 members
-
Team Prometheus
11 members
© 2012 Created by Chris Anderson.
