### Help Support HomeBuiltAirplanes.com:

#### Aerowerx

##### Well-Known Member
I have done a bit of reading on Arduino GPS shields and related software libraries.

There is not much you would have to do other than hook everything together. With some of the GPS units you give them the coordinates of your waypoint or destination and it spits back your course, heading, ground speed, and estimated time remaining. So all you would have to do would be display the data in the desired format.

I also see that the best choice for the display would be a transflective LCD. This will work in bright sunlight and most of them have a backlight that can be turned on in dim light. There are even some transflective graphics displays, if you want to get extravagant.

#### cluttonfred

HBA Supporter
I think the monochrome OLED displays are also bright enough for direct sunlight and oddly the OLED graphic (pixel matrix) displays are actually cheaper than the character displays. For example, this 1" diagonal, 128x32 pixel display costs just $17.50, includes an onboard voltage regulator and uses only 3 pins to communicate with the board via I2C. https://www.adafruit.com/product/931 #### Aerowerx ##### Well-Known Member The transflective displays are backed up with a reflector so they reflect back the incident light. They also have a LED back light for dimmer environments Not sure if the OLED displays are transflective. #### cluttonfred ##### Well-Known Member HBA Supporter The transflective displays are backed up with a reflector so they reflect back the incident light. They also have a LED back light for dimmer environments Not sure if the OLED displays are transflective. They are not as far as I know, but since they are tiny LEDs (not backlit LCDs) I think with an anti-glare cover you should be OK, but that's just speculation on my part. #### Pilotgil ##### Well-Known Member OLEDs in general are not good in sunlight but some are getting quite good. They are emitters of light so limited. I use transflective LCDs. It's not as easy as just hooking it up but as long as you can write C code it's not terrible. The RPM/EGT system I built was about 40 pages of code if printed. #### Aerowerx ##### Well-Known Member ....It's not as easy as just hooking it up but as long as you can write C code it's not terrible. My comment in post #21 refered to deriving the course, heading, etc. from the GPS data. It is done for you if you pick the right GPS module. The only C code you would have to write would be to capture the data and send it to the display. #### Aerowerx ##### Well-Known Member Here's a 4" diagonal, transflective LCD panel, 240 x 64 pixels and controlled via I2C for$40.
I saw their web site, but it didn't tell me much. Haven't looked at Mouser or Digikey yet.

Nixie tubes

#### Aerowerx

##### Well-Known Member
Nixie tubes
I think they would get washed out in bright sunlight.

(And how many on here know what they are?)

#### Hephaestus

##### Well-Known Member
Probably but it would look cool and behind a opaque bit of acrylic they almost resemble 7 segment LEDs. Which might be the best option come to think of it.

And the steampunk folks would go nuts lol

#### Aerowerx

##### Well-Known Member
Probably but it would look cool and behind a opaque bit of acrylic they almost resemble 7 segment LEDs. Which might be the best option come to think of it.

And the steampunk folks would go nuts lol
Huh? The Nixies I am familiar with have a separate element for each digit, stacked one behind the other. 11 pins on the base. A type of vacuum fluorescent display. Just apply voltage (around 100-150vdc, IIRC) to the digit you want.

I do have a bunch of 7 segment incandescent displays around here---in a homebrew* frequency counter.

-------
*homebrew: What DIY used to be called, among amateur radio enthusiasts.

#### Hephaestus

##### Well-Known Member
Yup those are the ones, I was thinking like a 7 segment in overall look/glow. Other than the curves instead of hard edges - similar visibility.

Didn't the USSR use them in aircraft displays? I know they were mostly instrumentation in North America.

I'm no nixie pro - but I do want a nixie steampunk watch

#### Hephaestus

##### Well-Known Member

See I want like this... But it's vfd and not that cool...

But these would do...

#### Pilotgil

##### Well-Known Member
My comment in post #21 refered to deriving the course, heading, etc. from the GPS data. It is done for you if you pick the right GPS module.

The only C code you would have to write would be to capture the data and send it to the display.
With the exception of very primitive data such as COG and GS and PPOS, most modules that I have used do not have databases or any complex user controlled intelligence. Normallly, they output location, course over ground, ground speed, gps altitude, gps time, checksums, etc. Generally, the host CPU provides the UI, database, and display and most importantly, the process for navigating. For me, the SNS needs an aviation database (so you can enter an airport ID rather than Lat/long) , UI, display, system management (checksums, GPS status, error handling, etc.). The prototype that I working on is very simple, enter a airport ID, the system pulls the lat/long from the database, calculates a DTO, and then provides a process for staying on course and the principal navigation data. I normally use Garmin OEM GPS Sensors but just finished my first using a very inexpensive GPS Sensor and have been very impressed. There are no shareware libraries for the graphics modules I use (they fit perfectly in a 2 1/4 inch instrument) so there's a bunch of code to make it work.

#### Aerowerx

##### Well-Known Member
.... For me, the SNS needs an aviation database...
Then it wouldn't be a Simple Navigation System, would it?

#### gtae07

##### Well-Known Member
Then it wouldn't be a Simple Navigation System, would it?
Depends how you define "simple".

I like to look at operational simplicity and ease of use. By that measure, a moving-map handheld GPS or Android/iOS app simply blows away a text-only system that requires lat/long coordinates. I've used a text-only aviation GPS before, and for all its "simplicity" it's a lot easier to goof up and miss a small-ish but eventually significant mistake than it is on a moving map.

BJC

#### Aerowerx

##### Well-Known Member
Depends how you define "simple".
By simple, I mean not having to program the database with a list of ICAO designations and corresponding lat and long, and database search routine. And displaying the essential information, namely bearing to destination (and heading, speed, and time to arrival would not be too difficult).

Take a look at these, taken from this web site:
$GPBOD - Bearing, origin to destination$GPBWC - Bearing and distance to waypoint, great circle

$GPGGA - Global Positioning System Fix Data$GPGLL - Geographic position, latitude / longitude
$GPGSA - GPS DOP and active satellites$GPGSV - GPS Satellites in view
$GPHDT - Heading, True$GPR00 - List of waypoints in currently active route
$GPRMA - Recommended minimum specific Loran-C data$GPRMB - Recommended minimum navigation info
$GPRMC - Recommended minimum specific GPS/Transit data$GPRTE - Routes
$GPTRF - Transit Fix Data$GPSTN - Multiple Data ID
$GPVBW - Dual Ground / Water Speed$GPVTG - Track made good and ground speed
$GPWPL - Waypoint location$GPXTE - Cross-track error, Measured
\$GPZDA - Date & Time
(My emphasis)