Close

Does this project spark your interest?

Become a member to follow this project and don't miss any updates

explorad

Work in progress: The explorad combines a microcontroller, a display, and star charts in a head-up display for astronomical telescopes.

3.5k 12 58 48

This project was created on 05/04/2014 and last updated 2 months ago.

Description
There are a number of useful things that make an amateur astronomer's life easier. The "Telrad" displays circles of 0.5, 2 and 4 degrees diameter in your field of view. Some astronomical charts also have these circles printed around objects, and together these make it easier to navigate through the night sky and find what you want to look at.

The explorad combines these features in a single device:
- A display and some more optical hardware is used to show telrad circles and some more information, projected into your view at the sky.
- Object information is stored on an SD card. Objects can be marked as a target for easier lookup, but the explorad can also display the position of other objects - there might be something interesting just around the corner!
- The telescope's viewing direction is determined with an electronic compass or with digital setting circles. With an explorad mounted on top, the explorad helps you point your telescope at an object and take a close look.
Details

How the Telrad works:

Here's a little drawing that shows how the Telrad works. It just shows the main parts:

The Telrad contains a screen with three backlit circles. Light emitted from that screen is mirrored to a lens which brings the circles into infinity focus, and then (partially) reflected into the observer's view by a glass plate. The observer's eyes are focused at infinity, looking at a distant object. The resulting image contains the both the object and the red circles.

The size of the circles on the screen and the lens' focal length are chosen to have circles with 0.5°, 2° and 4° diameter. The screen can be moved to hit the right focus point. When you look through a Telrad, you'll see something like this:

(That's a selfmade Telrad clone I made)

How that relates to star charts:

Star charts contain circles with 0.5°, 2° and 4° around interesting objects and around points that are easy to find (bright stars). Here's a sample:

The star chart/Telrad combo can be used to easily navigate through the night sky to find an object for observation.

What the explorad does:

The explorad replaces the Telrad's screen with an OLED display. Why an OLED?

At night, the eyes adapt to the darkness. This adaption is easily disturbed by bright light, especially with wavelengths which the eyes are sensitive to. The eyes are least sensitive to red light, and that's why the Telrad's circles are red. An OLED display has no backlight which could bleed unwanted wavelengths, and we can choose to display only red pixels. That way the eyes are least disturbed.

If only circles are displayed, the explorad does the same thing as the Telrad.

What the explorad also does:

In addition to displaying the Telrad circles, the explorad can determine the telescope's viewing direction and use that information to do two main things:

  • display how the telescope must moved to bring a target into the field of view
  • display nearby objects on the screen which might be interesting to look at.

Determining the telescope's viewing direction is not too hard. A 3D accelerometer is used to measure the altitude (angle between the horizon and the telescope's viewing direction) and roll. I tried using a magnetometer for the azimuth, but that didn't work well - I got distorted readings caused by almost every object around the sensor. That's why I'm attaching an optical encoder to the telescope's base to measure the azimuth.

Demo Video

showing the current hardware, Telrad circles, Target tracking, and nearby objects display:


The display you see in the video will replace the Telrad's fixed 3-circle screen.

Licenses

If the SdFat library is used in the project, the whole project probably has to be published as GPLv3 (I guess).

Components
  • 1 × Teensy 3.1 Cortex-M4 prototyping board
  • 1 × Adafruit 128x128 OLED display
  • 1 × Pololu LSM303D breakout board Electronic Compass
  • 1 × Avago HEDS-5540 H06 optical encoder digital setting circle
  • 1 × input device Look left for the link to the proxy project
  • 1 × Navilock NL-507ETTL GPS breakout board with TTL output
  • 1 × Adafruit CC3000 breakout board For connectivity
  • 1 × A microSD card Mine is a SanDisk 4GB SDHC

Project logs
  • Github repo, System Design Document and licenses

    2 months ago • 0 comments

    I've created a github repo, added a system design document (SDD) and added license information as required by the contest rules.

    The github repo is linked to in the project's link section. It currently only contains the SDD. Code will be added once it is easier to handle (bugs aside). License information was added in the project description, but that's preliminary.

  • I've got a video!

    2 months ago • 0 comments

    After a bit of fighting I can present this video. The annotation looked ok when I watched the video on youtube, but not here.

  • ...and WiFi

    4 months ago • 0 comments

    I've added the CC3000 module quite some time ago, but couldn't use it along with the SD card and my DMA display driver - all use the SPI. SD card and display cooperated, but the CC3000 did something the other drivers didn't like. So I created a small, almost brain-dead library that can save and restore SPI settings and voilá - all three are working.

    The remaining huge problem is that the adafruit library for the CC3000 doesn't seem to support non-blocking operations. I cannot try to update my display 25 times per second, read data from the SD card between frame updates and wait for a ping response that takes 200 ms. A delay function that takes negative arguments would be cool now...

View all 23 project logs

Discussions

Tiago wrote 4 months ago null point

I hear you about the magnetometers, such a pain in the ass. Really sucks that there isn't any better alternatives.

Are you sure? [yes] / [no]

Christoph wrote 4 months ago null point

I threw out the magnetometer, i.e. I'm using the electronic compass only to get altitude and roll values. When I figured out how to properly process the magnetometer values, I might use it again.

Are you sure? [yes] / [no]

pixelk wrote 4 months ago null point

I'm working on a distantly similar project (an aid for polar alignment) and yours is very interesting to me. I try to work with Navspark's module (http://navspark.mybigcommerce.com/) but the truth is, the Arduino environment they ported isn't really ready yet. Too bad as the hardware is a nice addition to the teensy I use for the main board. I'm still trying to interface it with Sparkfun's LSM9DS0 breakout to have an all-in-one navigation reference.

Are you sure? [yes] / [no]

Christoph wrote 4 months ago null point

Which Teensy are you using? If it's an AVR-based one, try the Teensy 3.1 as an upgrade. It looks like it doesn't have as much power as the NavSpark, but I think Paul will soon have the Teensy 3++ (or whatever its name will be) ready.

Are you sure? [yes] / [no]

pixelk wrote 4 months ago null point

Yes, I'm using a teensy 3.1. I pledged for the original Kickstarter for the 3.0 and since then I'm huge fan. Paul Stoffregen delivered as expected and the support is excellent.

Are you sure? [yes] / [no]

Mike Szczys wrote 5 months ago null point

Nice start to this project! Thanks for submitting it to The Hackaday Prize. Have you thought about how this is a "connected" device (see the Basic Judging Criteria here: http://hackaday.io/prize/details)? Part of it could be the input device, which you could package up with a protocol and make it extendable for other uses. But perhaps you want to make a way to save, share, and import information if many people had this rigged up to their telescopes? Just a thought.

I love the logo on the boot screen!

Are you sure? [yes] / [no]

Christoph wrote 5 months ago null point

The input device will have a wired connection to the main device because the input device will (I've almost settled on that now) carry the battery for both. That way, the input device can be detached for charging and the main device can be left on the telescope without destroying its alignment (it must be aligned with the telescope's optical axis).

This device will be "connected" with a WiFi module for downloading the positions of solar system bodies, as they are more dynamic than objects in the milky way or deep-sky objects. I'm also thinking about a link between the explorad and stellarium.

Are you sure? [yes] / [no]

x3n0x wrote 5 months ago null point

Looks really cool! Cant wait to see how it pans out!

Are you sure? [yes] / [no]

Digital Corpus wrote 6 months ago null point

When might you be putting up a parts list, even partial? I'm curious about performance and the like. Is that an OLED display? I commend the choice since you don't have to deal with backlight bleed :)

Are you sure? [yes] / [no]

Christoph wrote 6 months ago null point

What you can see in the pictures is already included in the parts list, and the parts list will grow with the project.
The display is an OLED for exactly the reason you state - no backlight, only red. I can even dim it by adjusting the red value, because the display uses 16-bit rgb.
I will keep updating this project with details as I go along.

Are you sure? [yes] / [no]

Quinn wrote 6 months ago null point

Cool project! Are you going to make the display appear as an overlay to the sky at infinity focus like the Telrad does?

Are you sure? [yes] / [no]

Christoph wrote 6 months ago null point

Yes, it will have the same optics as a telrad and display everything at infinity focus. I'm thinking about adding a secondary display for tasks that don't require seeing the sky in the background.

Are you sure? [yes] / [no]

Similar projects