Our Beautiful Universe - Photos and Videos

Click For Summary
The discussion focuses on sharing the beauty of the Universe through photos, videos, and animations, emphasizing the aesthetic appeal of space alongside scientific information. Participants are encouraged to post clips and images that comply with mainstream scientific guidelines, avoiding fringe theories. Notable contributions include time-lapse videos from the ISS and clips related to NASA missions, such as the Dawn and New Horizons projects. The thread also highlights the emotional impact of experiencing the vastness of space through visual media. Overall, it celebrates the intersection of art and science in showcasing the wonders of the Universe.
  • #1,801
bruha said:
Hi, its beautiful ... can I ask what is this two small bright objects? (second image is left/righ turned isn it..)
Lot of succes :)
The 2nd image of Andromeda (with stars removed) is rotated 180 degrees compared to the 1st. The two bright objects are satellite galaxies orbiting Andromeda. The smaller one is Messier 32, the larger one is Messier 110, and Andromeda itself is Messier 31.
 
Last edited:
  • Like
Likes pinball1970
Astronomy news on Phys.org
  • #1,802
9 minutes to impact…

 
  • Like
Likes pinball1970 and DennisN
  • #1,803
Thanks !
:smile::smile:
 
  • Like
Likes davenn and pinball1970
  • #1,804
The Elephant Trunk Nebula (IC 1396A) captured from my back patio in Sept. 2022. The Elephant Trunk is a smaller part of a larger ionized gas region called IC 1396, in the constellation Cepheus. It's called the Elephant Trunk Nebula presumably because if you squint your eyes and tilt your head to the side, it kind of looks like an elephant with a big, bulbous trunk. Sort of.

ElephantTrunck2022_Final_SmallForPF.jpg


The trunk itself is a dark cloud of gas illuminated and ionized by a bright, massive star, forming a bright rim at the boundary of the dense cloud. The star in question, HD 206267, is not shown in the image because it is outside the frame; it would be located about an additional 1/3 of the image height, above the upper edge of the image. (In the image, "up" is celestial East.)

Equipment:
Meade 10" LX200-ACF fork mounted on an equatorial wedge.
Starlight Instruments FTF2008BCR focuser modified for electronic focusing.
Off-axis guider (OAG) with ZWO ASI174MM-mini guide camera.
Baader 3.5-4 nm Ultra-Narrowband filter set.
ZWO ASI6200MM-Pro main camera.

I was going to go off on a diatribe about pink elephants, but decided not to at the last minute.

Software:
Nighttime Imaging "N" Astronomy (N.I.N.A.)
PHD2 guiding (of course)
PixInsight
Topaz Labs Sharpen AI

It's time we discussed the big elephant in the room. It's the Elephant Trunk Nebula (IC 1396A). It's around 2,400 light-years away from Earth. And it's roughly 30 light-years long, depending on what you consider as part of the nebula.

Integration:
Bortle class 7 (maybe 8) skies
All subframes binned 3×3
SII: 60×10 min = 10 hrs
Hα: 69×10 min = 11.5 hrs
Oiii: 67×10 min = 11.67 hrs
Total integration time: 32.67 hours
 
  • Like
  • Wow
Likes vanhees71, DennisN, Maarten Havinga and 5 others
  • #1,805
collinsmark said:
The Elephant Trunk Nebula (IC 1396A) captured from my back patio in Sept. 2022. The Elephant Trunk is a smaller part of a larger ionized gas region called IC 1396, in the constellation Cepheus. It's called the Elephant Trunk Nebula presumably because if you squint your eyes and tilt your head to the side, it kind of looks like an elephant with a big, bulbous trunk. Sort of.

View attachment 314883

The trunk itself is a dark cloud of gas illuminated and ionized by a bright, massive star, forming a bright rim at the boundary of the dense cloud. The star in question, HD 206267, is not shown in the image because it is outside the frame; it would be located about an additional 1/3 of the image height, above the upper edge of the image. (In the image, "up" is celestial East.)

Equipment:
Meade 10" LX200-ACF fork mounted on an equatorial wedge.
Starlight Instruments FTF2008BCR focuser modified for electronic focusing.
Off-axis guider (OAG) with ZWO ASI174MM-mini guide camera.
Baader 3.5-4 nm Ultra-Narrowband filter set.
ZWO ASI6200MM-Pro main camera.

I was going to go off on a diatribe about pink elephants, but decided not to at the last minute.

Software:
Nighttime Imaging "N" Astronomy (N.I.N.A.)
PHD2 guiding (of course)
PixInsight
Topaz Labs Sharpen AI

It's time we discussed the big elephant in the room. It's the Elephant Trunk Nebula (IC 1396A). It's around 2,400 light-years away from Earth. And it's roughly 30 light-years long, depending on what you consider as part of the nebula.

Integration:
Bortle class 7 (maybe 8) skies
All subframes binned 3×3
SII: 60×10 min = 10 hrs
Hα: 69×10 min = 11.5 hrs
Oiii: 67×10 min = 11.67 hrs
Total integration time: 32.67 hours
Blimey!
Reading your post after looking at your image I was expecting to see, "Hubble" where you listed "Equipment!"
Amazing colour and details.
It took me several squints to get the Elephant but I saw it eventually.
 
  • Like
Likes vanhees71, collinsmark and Ibix
  • #1,806
collinsmark said:
It's time we discussed the big elephant in the room.
I thought you were thinking of your beast of a telescope. :smile:
 
  • Haha
Likes collinsmark
  • #1,807
Recently and unexpectedly between rainy days we got clear sky at night and I succeeded to capture the eastern Veil nebula NGC 6992. Now the couple together with NGC 6960 is completed. I enjoy these bizarrely intertwined reflection- and emission nebulae very much.

Sony A7III - UNC 200 mm f/5 Newton with Reducer - Skywatcher HEQ5 - guiding with StarAid
DeepSkyStacker - Siril - LightZone

NGC 6960 - 28.08.2022 - 25x180s Optolong L-Enhance - ISO 3200
NGC6960 UNC 28.8.22 DSS Hist RAW L-enh 25x180 Siril.TIF_lzn.jpg


NGC 6992 - 30.09.2022 - 23x180s Optolong L-eNhance - 24x45s ISO 3200
NGC6992 30.9.22 DSS RAW Hist 23x180 ISO3200 Lenh 24x45 ISO3200 Siril.TIF_lzn-1 - Kopie.jpg
 
  • Like
  • Love
Likes davenn, pinball1970, Bystander and 3 others
  • #1,808
collinsmark said:
elephanttrunck2022_final_smallforpf-jpg.jpg
I tried imaging this same target back on September 5 but I never posted it because mine came out so poorly... among other reasons I think I only got about 20 minutes of data so the image was extremely noisy. Also I was shooting without any narrowband filters and there was quite a bit of light pollution. We (girlfriend & I) had gone to our first "star party" at whiskeytown lake which turned out to be a park ranger with a laser pointing out different stars and planets and a couple people with visual telescopes set up. I was the only one with an imaging rig. Families with kids kept coming up and asking to see what my telescope was doing and I had to say "oh, the nebula is too dim to see in camera" so they would walk away disappointed. So after 20 minutes I pointed the telescope at saturn so they could see the rings and atmospheric distortion live on the back of the camera (because Saturn is bright enough to see without additional processing), but that meant my original target came out noisy...

2175mm f/14.5 Maksutov-Cassegrain OTA, 90 seconds exposures for 20 minutes, no filters on a Nikon D800, 6400iso:

elephants-trunk-final.jpg


7134786.jpeg


5231674.png


Saturn (live view):
97E89ED9-868C-40A1-B655-1CA8B0524C6A.jpeg
 
Last edited:
  • Like
Likes DennisN, vanhees71, Ibix and 1 other person
  • #1,809
Jupiter, captured from my back patio on the morning of September 23rd, 2022.

2022_09_23_0807_8_Final_SmallCropForPF.jpg

Midpoint timestamp of acquisition: 2022-09-23 08:07.8 Universal Time (UT).

Equipment:
Meade 10" LX200-ACF fork mounted on an equatorial wedge.
Starlight Instruments FTF2008BCR focuser modified for electronic focusing.
Explore Scientific 1.25" 3X Focal Extender.
ZWO Atmospheric Dispersion Corrector (ADC).
ZWO ASI585MC camera.

Software:
FireCapture (for acquisition)
AutoStakkert! (for lucky imaging processing and stacking)
RegiStax (for wavelet sharpening)
PixInsight (for miscellaneous image processing)
WinJUPOS (for derotation and additional stacking of sharpened images)
Gnu Image Manipulation Program, GIMP (to remove some frame/boundary artifacts left over from RegiStax)
Topaz Labs Sharpen AI (for a final sharpening step)

Acquisition:
FireCapture was used for acquisition. This was first light for the new color ASI585MC camera. I ran into some problems with the frame rate, being only around 20 fps, when I was expecting around 90 fps. This is something I'll need to figure out before next time. (Early evidence suggests the USB connection was as if it was USB2.0 instead of the higher speed USB3.1. I need to debug this.)

Integration and processing:
Atmospheric seeing: Meh. Well, mostly meh. There was brief ~6 minute period of pretty good seeing out of several hours of capture, and those six minutes are what I used for the image shown here.
Six, 1-minute contiguous videos were chosen (stored in .SER file format) to be fully processed.
Each video was processed with AutoStakkert! keeping 70% of frames.
Each of these subsequent 6 images were separated into their Red, Green, and Blue components and sharpened separately using RegiStax wavelet sharpening, then recombined back into RGB images.
These 6 sharpened RGB images were then derotated and stacked in WinJUPOS creating a single, derotated RGB image.
That image was then brought into GIMP to fix a weird frame boundary artifact left over from RegiStax.
That image was imported into PixInsight and processed (CurvesTransformation and LocalHistogramEqualization).
Near the end of processing, Topaz Sharpen AI was used for a final sharpening step.
 
Last edited:
  • Like
  • Love
Likes Bystander, DennisN, dlgoff and 4 others
  • #1,810
Awesome! I've been using mono/RGB for planetary forever, but I'm seeing it really isn't necessary and also it's a problem when capturing something that moves pretty fast in realtime like Jupiter and its moons.
 
  • Like
Likes collinsmark
  • #1,811
The Wizard Nebula (NGC 7380, SH2-142), imaged from my back patio in mid-to-late September, 2022. The Wizard Nebula is in the constellation Cepheus.

Wizard2022_Final_SmalForPF.jpg


It's called "The Wizard Nebula" presumably because it remarkably resembles a wizard, either magically levitating some bright orbs (stars) or maybe reaching out to give somebody a big hug.

Equipment:
Meade 10" LX20000-ACF fork mounted on an equatorial wedge.
Starlight Instruments FTF2008BCR focuser modified for electronic focusing.
Off-axis guider (OAG) with ZWO ASI174MM-mini guide camera.
Baader 3.5-4 nm Ultra-Narrowband filter set.
ZWO ASI6200MM-Pro main camera.

There's a chance this might be my last astrophoto posted before the big holiday (Halloween).

Software:
Nighttime Imaging "N" Astronomy (N.I.N.A.)
PHD2 guiding (of course)
PixInsight
GIMP (to fix a couple of saturated stars)
Topaz Labs Sharpen AI (as a small, final sharpening step)

If you wished for a scary photo, think of it as a big scary wizard reaching out for a big loving hug.

Integration:
Bortle class 7 (maybe 8) skies
All subframes binned 3×3
SII: 59×10 min = 9.83 hrs
Hα: 71×10 min = 11.83 hrs
Oiii: 67×10 min = 11.17 hrs
Total integration time: 32.83 hours

[Edit: Slightly reprocessed image.]
 
Last edited:
  • Like
  • Love
  • Wow
Likes pinball1970, DennisN, Bystander and 3 others
  • #1,812
  • Like
Likes pinball1970 and collinsmark
  • #1,813
Had a moon-free clear skies weekend- 3 consecutive (relatively) dark nights when I can stay up past midnight! Mostly I imaged M31 (Andromeda galaxy) and am still processing those. But each night when M31 moved behind a house, I was able to image Neptune and Triton for a few minutes- this was assembled from 3 different image stacks (8s subs), one from each night, 1:1 crop using a lens equivalent to a 100mm refractor:

Neptune 2022.jpg


You can see how Triton is orbiting Neptune and can estimate the orbital period, knowing that the images were taken almost exactly 24 hours apart. You can also probably tell that the image quality is lower than it should be, especially Friday night (top position). I'd like to ask the group some questions about this, I'm still trying to diagnose the problem.

It started when I switched from 400mm to 800mm, meaning I'm much more sensitive to 'user error'.

The main symptom presents as tracking error due to poor polar alignment, but I'm reasonably sure I am aligned within 2 arcmin. I have no real evidence for this, but I rough align using a reticle and then use the GoTo drive to fine align on 2 or 3 bright stars using the camera's live-view, zoomed all the way in and using the illuminated centerpoint as a fiducial. (I don't use an auto guider)

Even so, I am only able to keep < 10% of my subframes, and that metric has proven to be very stubborn: 6s exposures did not appreciably increase the acceptance rate, for example. Re-polar-aligning periodically (every 45 minutes or so) during the night also did not help.

It could be vibration- my 'telescope' oscillates like crazy when mounted, so if it's windy I expect low rates. But Sunday night was calm. I've also tried increasing the amount of time between exposures, to allow the structure time to fully dampen after the shutter moves, to no effect.

It's also not poor seeing conditions- that presents as uniform blurring, which is not what I see.

I don't have any of the bad images, sorry--- I get rid of those fairly early in the stacking process.

It's a little frustrating... any ideas?
 
Last edited:
  • Like
  • Wow
Likes pinball1970, collinsmark, timmdeeg and 3 others
  • #1,814
Andy Resnick said:
... You can see how Triton is orbiting Neptune ...
That's incredible.
 
  • #1,815
Andy Resnick said:
It could be vibration- my 'telescope' oscillates like crazy when mounted, so if it's windy I expect low rates. But Sunday night was calm. I've also tried increasing the amount of time between exposures, to allow the structure time to fully dampen after the shutter moves, to no effect.

It's also not poor seeing conditions- that presents as uniform blurring, which is not what I see.

I don't have any of the bad images, sorry--- I get rid of those fairly early in the stacking process.

It's a little frustrating... any ideas?
Great composite, btw. :smile:

I wouldn't underestimate seeing. Atmospheric seeing can vary quite a bit from night to night and even within that larger fluctuation, can vary quite a bit from minute to minute. [Edit: And technically, from millisecond to millisecond. Seeing is fractal-like in terms of time.]

If you can, try to concentrate/center your acquisition around the time that your target crosses the meridian. This doesn't guarantee good seeing, but since this is the time where the target is highest in the sky for that night, it means less atmosphere to shoot through, thus increases the probability of better seeing.

I can't say for sure that seeing is the only problem though. Astrophotography is like an onion of hurdles, obstacles, and challenges. Peel off one layer, and there's another layer still there, waiting.
 
  • #1,816
collinsmark said:
Astrophotography is like an onion of hurdles, obstacles, and challenges.

To me, astrophotography has felt like when I peel off one layer, I don't find another layer.
I find a couple of other onions. :biggrin:
(or to quote Churchill: "a riddle, wrapped in a mystery, inside an enigma")

Maybe I shouldn't be so frank. I don't want to scare any potential newcomers to the hobby. :smile:
 
  • Haha
  • Love
Likes collinsmark and pinball1970
  • #1,817
dlgoff said:
That's incredible.
Yeah!
 
  • Like
Likes DennisN and dlgoff
  • #1,818
collinsmark said:
Great composite, btw. :smile:

I wouldn't underestimate seeing. Atmospheric seeing can vary quite a bit from night to night and even within that larger fluctuation, can vary quite a bit from minute to minute. [Edit: And technically, from millisecond to millisecond. Seeing is fractal-like in terms of time.]

If you can, try to concentrate/center your acquisition around the time that your target crosses the meridian. This doesn't guarantee good seeing, but since this is the time where the target is highest in the sky for that night, it means less atmosphere to shoot through, thus increases the probability of better seeing.

I can't say for sure that seeing is the only problem though. Astrophotography is like an onion of hurdles, obstacles, and challenges. Peel off one layer, and there's another layer still there, waiting.
I'm fairly certain it's not seeing. Fortunately, I didn't wipe the SD card yet, so I was able to get some raw images to show (these have been converted to jpegs for obvious reasons).

This is a *typical* bad image- not the worst, but very average- scaled 200%. Right ascension is up-down, declination is left-right.
DSC_4076-St-1.jpg


This is what expect to see if the rig is oscillating purely in right ascension- remember, this is an 8s shutter time. However, what can't be seen in a single image, is also a slow drift. This can be seen by 'stacking' successive images- I'm not aligning them, just creating an image stack and keeping the maximum values at each pixel- again, scaled to 200%:

MAX_untitled folder-1.jpg


What you see here is a single vertical sweep to the left and a longer back-and-forth sweep on the right; I stacked a series of 20 consecutive images and a series of 40 consecutive images, separated by about 1 hour. This image shows drift in both RA and declination. This is what I expect to see if my polar alignment is off.

The simple response is "do a better job polar aligning", but given my alignment procedure, I expect (assume!) polar alignment to be within a couple of arcmin.

Any ideas?
 
  • Like
Likes collinsmark
  • #1,819
Are you aiming right at Polaris? If so that may be the issue. Polaris is actually offset by about 3/4 of a degree from the axis of rotation of the Earth.

This is what my polar alignment scope looks like when properly aligned, and the exact aim point varies by time of day/night. I use an app to figure out where the aim point should be exactly.

1192E74E-E7AF-4872-82E3-38ABDD084AE4.jpeg
 
Last edited:
  • #1,820
How are you triggering the camera? If you’re just pushing the button it might be inducing a shake that could take 30 secs to a minute to die down. Using an intervalometer with a delay on the shutter release could help. Or if you shoot a sequence the shaking is usually much less by the 2nd or 3rd image. There’s also an option on your Nikon to release the shutter up to 3 seconds after the mirror flips up to reduce the mirror flip induced vibration.
 
Last edited:
  • Like
Likes russ_watters
  • #1,821
Andy Resnick said:
The simple response is "do a better job polar aligning", but given my alignment procedure, I expect (assume!) polar alignment to be within a couple of arcmin.

Any ideas?

Okay, I see now that there may be bigger issues, possibly in addition to seeing. What mount are you using?

But I don't think we can completely rule out seeing just yet, since seeing alone can cause the apparent position of an object to jump from one place to another as a larger blob of cold atmosphere passes into or leaves the direct line of site of the object. Think of atmospheric layers like ocean waves. Sometimes there are lots of small, turbulent regions, and sometimes, on top of that, there are larger, steady waves that have the effect of shifting things back and forth every few seconds or so.

But let's save this one for later. There may be bigger onions to peel.

------------------

But the present, top-layer of the onion doesn't look to me like polar alignment either. I would instead look to tracking issues with your mount, or vibrational modes of your mount (see below).

The thing about polar alignment is, if you do the mathematics behind it, you'll find that polar alignment errors manifest exclusively as declination drift. In order for polar alignment to significantly affect right ascension, the polar alignment would have to be so far off as to have the mount's pole pointed to the wrong side of the sky.

And both altitude errors and azimuth errors both manifest as declination drift. It's even possible for one to cancel the other out at certain patches of sky, only to have them constructively attack you as huge declination drift at other patches. But never do they have much effect on right ascension.

So if your drift is primarily on the right ascension axis, I'd put polar alignment on the backburner for now. The big problems are probably from somewhere else.

--------------------

Tracking issues. This is a whole bag of onions here, but let's start with the lowest hanging onion. Balance.

Ensure your scope is balanced, complete with everything on your scope as it would be when imaging. Imbalance causes the tracking motor to work harder, and can cause inconsistencies in the tracking accuracy. Think of the starter motor of an old jalopy trying to "turn over" the engine: rather than rotating the engine at a uniform rate, the engine turns in surges and spurts.

[Edit: also, flexure can cause drift in both the declination and right ascension axes. This can happen even if the polar alignment is good. Having a scope that is properly balanced in both right ascension and declination axes can alleviate this somewhat. While precise balance might not eliminate it completely, it helps a lot. By that I mean drift due to mechanical flexure can be pretty bad if the scope is not balanced well.]

As an anecdote, I used to balance my scope meticulously on the night of imaging, before sunset was over. Then I would take off the objective cap and put on the dew shield. And blam: tracking issues that caused multiple images along the right ascension axis (the same as what you show in your first image of your last post). That's because I didn't balance my scope with the dew shield on. Make sure you balance your setup in exactly the same configuration that it will be in when imaging. (E.g., don't adjust your balance with your lens cap on, since you won't have the lens cap on when imaging.)

Periodic error correction (PEC): if your mount supports PEC, consider using it.

Cable management: Don't have a bunch of cables dangling off the very end of the camera, down to the ground. This is where they are most susceptible to negative influence of angular moment on the system, if a breeze or wind is present. Try to tie any cables back such that they come back to the center of the system before running to the ground or elsewhere.

The same can be said for dew heater cables and whatnot. Don't leave them dangling. Try to run all cables to a central location on the system, such that if any cable does get perturbed, it doesn't exert much angular leverage.

----------------------

All systems have some wobble, and that wobble is more pronounced on some axes than others. Do you best to reduce the moment of inertia along all axes. [Edit: while maintaining balance, of course.]

Beyond that, there is the advice given in this forum in the advice to newcomers buying a first telescope (in a sticky post): Don't neglect the importance of the mount. If you have a set amount of money, don't spend most of it on the telescope (optical tube assembly), rather buy a quality mount.
 
Last edited:
  • #1,822
Since you’re using a camera lens you can use a macro focusing rail (like the one I use shown below) to move the camera forward or backward to get it balanced on the declination axis.
26F68101-DE3A-49BE-957D-EB5B44CE1B0F.jpeg


https://www.adorama.com/mcfrss.html
 
  • #1,823
Devin-M said:
How are you triggering the camera?
Devin-M said:
Are you aiming right at Polaris?

Thanks for the ideas!

Camera is triggered automatically, using the built-in intervalometer and 3-second shutter delay.

I polar align using this reticle:

https://www.primalucelab.com/media/...andy_cannocchiale_polare_GM8_G11_reticolo.jpg

Which does account for the slightly off-axis location of Polaris. There is some uncertainty where the 'second star' goes because the markings are per decade (2020 is the main scribed line, 2030 is the one counter-clockwise), but in general I know I have fairly good alignment b/c I can easily check as the night goes on.
 
  • #1,824
Does the reticle account for the time of day?
 
  • #1,825
collinsmark said:
Okay, I see now that there may be bigger issues, possibly in addition to seeing. What mount are you using?

But I don't think we can completely rule out seeing just yet, since seeing alone can cause the apparent position of an object to jump from one place to another as a larger blob of cold atmosphere passes into or leaves the direct line of site of the object. Think of atmospheric layers like ocean waves. Sometimes there are lots of small, turbulent regions, and sometimes, on top of that, there are larger, steady waves that have the effect of shifting things back and forth every few seconds or so.

But let's save this one for later. There may be bigger onions to peel.

------------------

But the present, top-layer of the onion doesn't look to me like polar alignment either. I would instead look to tracking issues with your mount, or vibrational modes of your mount (see below).

The thing about polar alignment is, if you do the mathematics behind it, you'll find that polar alignment errors manifest exclusively as declination drift. In order for polar alignment to significantly affect right ascension, the polar alignment would have to be so far off as to have the mount's pole pointed to the wrong side of the sky.

And both altitude errors and azimuth errors both manifest as declination drift. It's even possible for one to cancel the other out at certain patches of sky, only to have them constructively attack you as huge declination drift at other patches. But never do they have much effect on right ascension.

So if your drift is primarily on the right ascension axis, I'd put polar alignment on the backburner for now. The big problems are probably from somewhere else.

--------------------

Tracking issues. This is a whole bag of onions here, but let's start with the lowest hanging onion. Balance.

Ensure your scope is balanced, complete with everything on your scope as it would be when imaging. Imbalance causes the tracking motor to work harder, and can cause inconsistencies in the tracking accuracy. Think of the starter motor of an old jalopy trying to "turn over" the engine: rather than rotating the engine at a uniform rate, the engine turns in surges and spurts.

[Edit: also, flexure can cause drift in both the declination and right ascension axes. This can happen even if the polar alignment is good. Having a scope that is properly balanced in both right ascension and declination axes can alleviate this somewhat. While precise balance might not eliminate it completely, it helps a lot. By that I mean drift due to mechanical flexure can be pretty bad if the scope is not balanced well.]

As an anecdote, I used to balance my scope meticulously on the night of imaging, before sunset was over. Then I would take off the objective cap and put on the dew shield. And blam: tracking issues that caused multiple images along the right ascension axis (the same as what you show in your first image of your last post). That's because I didn't balance my scope with the dew shield on. Make sure you balance your setup in exactly the same configuration that it will be in when imaging.

Periodic error correction (PEC): if your mount supports PEC, consider using it.

Cable management: Don't have a bunch of cables dangling off the very end of the camera, down to the ground. This is where they are most susceptible to negative influence of angular moment on the system, if a breeze or wind is present. Try to tie any cables back such that they come back to the center of the system before running to the ground or elsewhere.

The same can be said for dew heater cables and whatnot. Don't leave them dangling. Try to run all cables to a central location on the system, such that if any cable does get perturbed, it doesn't exert much angular leverage.

----------------------

All systems have some wobble, and that wobble is more pronounced on some axes than others. Do you best to reduce the moment of inertia along all axes. [Edit: while maintaining balance, of course.]

Beyond that, there is the advice given in this forum in the advice to newcomers buying a first telescope (in a sticky post): Don't neglect the importance of the mount. If you have a set amount of money, don't spend most of it on the telescope (optical tube assembly), rather buy a quality mount.

Wow- thanks! There's a lot here for me to think about. To answer your questions:

1) I am using a Losmandy GM-8 mount, a German equatorial mount.

2) Balancing is pretty easy... Ohh... wait a minute- when I switched to 800mm (adding the 2x teleconverter) I didn't adjust the counterweight, so the mount is currently balanced in DEC but not RA...! Doh!

3) I have no dangling cables or dew shields or anything like that- just the lens and camera, the camera triggered by the internal intervalometer. Easy peasy.

4) PEC. I've tried it, don't really have the skill yet- too jittery with the controls.

Awesome! I have something new to try- many thanks! I'll have some questions about 'meridian flip' soon :)
 
  • #1,826
Devin-M said:
Does the reticle account for the time of day?
Yes, the entire reticle rotates to permit proper alignment.
 
  • #1,827
This is the procedure I use starting at about 5:26…

 
  • #1,828
Another tip: do the precise polar alignment after putting the camera on the mount because if you align before adding the camera, the added weight of the camera can make the mount flex and take it out of alignment. So if you did it the way the guy in the video did without the camera on it won’t work very well.
 
  • #1,829
Andy Resnick said:
Ohh... wait a minute- when I switched to 800mm (adding the 2x teleconverter) I didn't adjust the counterweight, so the mount is currently balanced in DEC but not RA...! Doh!
The teleconverter can take it out of balance in both DEC and RA because it adjusts the weight of the whole camera (affecting the RA) but it also moves the center of gravity away from the lens’s mounting hole (affecting the DEC). Take the camera + lens + teleconverter off the mount and put a pencil on its side on the floor and under the lens’s mounting hole (pencil on its side perpendicular to the lens) and see if its actually in balance at the mounting hole like a see saw. If not you may need the macro focusing rail to move the center of gravity relative to the mounting hole on the bottom of the macro focusing rail.

0A34EF97-869C-4876-A1BC-08B09AE323D2.jpeg
 
Last edited:
  • #1,830
The Earth & Moon in a single photo...
tt1_0718931263_ega1_earth_moon.jpg
"On October 13, 2022, NASA’s Lucy spacecraft captured this image of the Earth and the Moon from a distance of 890,000 miles (1.4 million km). The image was taken as part of an instrument calibration sequence as the spacecraft approached Earth for its first of three Earth gravity assists."

https://www.nasa.gov/image-feature/... -captures-earth-moon-ahead-of-gravity-assist
 
  • Like
  • Love
Likes davenn, Andy Resnick, Maarten Havinga and 3 others

Similar threads

  • · Replies 23 ·
Replies
23
Views
3K
  • · Replies 12 ·
Replies
12
Views
3K
  • · Replies 9 ·
Replies
9
Views
3K
  • · Replies 24 ·
Replies
24
Views
3K
  • · Replies 13 ·
Replies
13
Views
2K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 9 ·
Replies
9
Views
2K
  • · Replies 11 ·
Replies
11
Views
3K
  • · Replies 10 ·
Replies
10
Views
3K
  • · Replies 30 ·
2
Replies
30
Views
4K