Skip to main content

Celestron 70az: What can you expect to see?

When someone buys a new telescope his first question is what i can see with it. The second is what is the highest zoom i can achieve. Although the maximum zoom can be an attractive measurement when buying a new telescope, the buyer should focus on the aperture size: how much light i can gather? This is the main difference from theoretical to practical highest zoom.

So, what can you expect to see with this telescope?

During the tests i did, the average seeing conditions with medium-low light pollution. These two factors can really improve your experience or.. to destroy it. In my place i would categorize the light pollution in class 5, based on Bortle 's scale. I also tried to improve the lenses by blackening the edges, as i described in earlier post.

A quick note here before discussing my personal views on the topic. Planets and stars have different brightness that we call it apparent magnitude. Lower the number is, brighter the stellar object is. The practical limit of the telescope is around 10 as it is expected by a 70mm telescope. Here is a list of famous stars and planets:

Apparent Magnitude of celestial objects Source: ESA
Apparent Magnitude of celestial objects Source: ESA

To calculate the achieving magnification of the telescope we use this equation: 

magnification = focal length telescope / focal length eyepiece

In our case the telescope has 900mm length, thus we always divide this number by the length of the eyepiece. Here is a table describing the achieved magnification (zoom) in combination with a barlow and some comments from personal experience. 

Tube Length (mm)
Eyepiece
Barlow ( 1X – 2X)
Zoom
Comments
900
32
1
28,13
Wide view, best for star gazing
900
32
2
56,25
Good for star gazing and big planets
900
20
1
45
Wide view, good for star gazing.
900
20
2
90
Lot of light. Stars and planets.
900
15
1
60
Good for star gazing, less light than 20mm
900
15
2
120
Loosing a lot in contrast, but acceptable
900
10
1
90
Less light, but acceptable for stars
900
10
2
180
Telescope limit, bright planets only
900
6
1
150
Telescope limit, bright planets only
900
6
2
300
Unacceptable, even during the day

In short: if you want to use the telescope for star gazing you should use magnification up to 100. For planets, you can go up to 180x, but you are going to loose a lot in terms of brightness. Anything more is unacceptable! In the future, i will make calculations what are you loosing in terms of brightness.

Labels:

Popular posts from this blog

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

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, paying
Read more

TrueNAS core TIPS

And for completion here are some tips in general for NAS:   Use backup. NAS is not a backup. It is a part of backup, never forget this. Always have backup on a different media (or different NAS) and off site if possible! Use hard disks and SSDs from different vendors always. You may be unlucky and receive media from a problematic batch and have multiple failures during the recovery. Use RaidZ2 or RAID6 or better to reduce the risk of completely losing the data. Use high quality PSU. A NAS runs all the time, so selecting PSUs with GOLD certification or better can reduce your power consumption. Use UPS or at least an AVR. It is a very bad idea to stop a NAS system without proper shutdown procedure. Don't overuse the NAS server with multiple VMs/docker instances/Jain instances. Keep it simple! Here are some tips and tricks from my TrueNAS home NAS server. In my previous post I analyzed the reasons for using TrueNAS instead of Linux distributions (ZFS, stability etc). After two months
Read more