Skip to main content

Celestron travelscope 70 + T2 mount + Nikon D3200

The T2 mount is finally here. I was able to use it with my Celestron Travel Scope. The T2 mount took almost 40 to receive it from China. I replaced the eyepiece and removed the mirror prism, and suddenly I had a lens 400mm. Of course, the quality is much worse than the actual lenses, and I will need a lot of post-processing, but the price I paid it was less than 100 euro.
Nikon D3200 attached to the Celestron travelscope 70 using a T2 Mount.
Nikon D3200 attached to the Celestron travel scope 70 using a T2 Mount.

Here is my first impression: I need a good tripod. Even the light wind I had on 4th floor makes the images blurred. The tripod I way too cheap for this work, and the exposure more than 5 seconds does not forgive. Anyway I also did some daylight tests, here are my results:

View from my camera with 55mm.
View using the travel scope.
Here is one plane, note that I had to increase the ISO due to darkness.
My next target was the second most bright object in the sky: the moon. Again the quality was not the best, and I think it is because of the bad tripod. Here is the picture:
Shoot of the moon using the travel scope 70 and the Nikon dSLR.
The shoot of the moon using the travel scope 70 and the Nikon dSLR.

Overall I will say that is a good opportunity to take nice pictures during the day and night. However, you will have to buy a good tripod to be able to have long exposures. Moreover, the quality of the glass is not the best: there is fringe distortion. Again it is an ultra cheap solution that provides acceptable performance. Getting some star photos is my next goal.

Labels:

Popular posts from this blog

Static linking with gcc and g++

In this tutorial, we will explain what the static linking is, how this affect the size of final binary, and why statically linking with g++ sometimes is pain. By definition, a statically compiled binary is a group of programmer ‘s routines, external functions, and variables which are packed into the final binary executable. The compiler or the linker produces the final object and embeds all the functions and variables and the linking phase.  There are two reasons of using dynamic linking and shared libraries: 1) Avoid creating a huge binary, if all the programs use a standard set of libraries why not having the operating system providing to them 2) Compatibility on operating system and machine dependant characteristics: sometimes the libraries must be implemented based on the architecture or the operating system and using dynamic linking is an easy way to avoid this catch. On the other hand, static linking is the ideal way of distributing one software product, pay...
Read more

Processing Milky Way in RawTherapee

This text is an analysis of a video I did some months ago how to process photos of our Milky Way in RawTherapee. You can find the picture here . The photo was taken by wiegemalt. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Editing: Step 1: Fixing lighting The first thing someone notices when opening the picture is the extreme noise due to high ISO used (1600 - check the picture on the right). The first thought is to de-noise the picture, however, if you do that you are going to loose the details of the night sky. The main reason for the high noise is the additional exposure Rawtherapee adds when the 'Auto' button is pressed. In particular, the RT adds +2.4 EV to equalize the picture. This is Wrong! What we want is to keep the noise down and at the same time bring the stars up. That's why we are going to play with the Tone Curve of the RT. To adjust the light properly we increase the cont...
Read more

Auto - Vectorization with little help from GCC!

This tutorial helps the programmers to benefit the progress of the auto-vectorization algorithms that are implemented in modern compilers, such as gcc. Before you start playing with the vectorization of your code i assume that you don't have any bottleneck in you code (like dynamic memory allocation etc) in the critical path. In this tutorial we will use the gcc 4.4.1, but the same steps can be applied to newer or older versions.  First of all there are two issues with auto vectorization:  1) gcc must know the architecture (eg what SIMD instructions are available)  2) The data structures must by properly aligned in memory The first step is to find the architecture of your processor and point it to gcc using the flags -mtune=... / -march=... you specify the architecture.  For example, my laptop is core2Duo so i put -march=core2. You can find more more information  here .  The next problem we must solve is knowledge of memory alignment. ...
Read more