wornish

Thanks Nigel for sharing your data. Finally had a go but I think your original is better than my effort.

I didn't use the Ha data this is just LRGB processed in PI and then tweaked in PS.

Thanks for the explanation of why star roundness is important.  I never thought of it that way.  Under normal viewing distances its really not noticeable in your data but the goal is a perfect image.

 Will have a go at your data when I get a chance. It has downloaded OK.

Really nice image - well done.

I honestly don't understand this fixation about star elongation I can't see any in your image, which particular star is bothering people?  and more importantly why?

I would really like to have a go at processing the data if you are happy to share.

8 hours ago, kens said:

AFAIK Kstars/Ekos on Windows needs to talk with an INDI server for full functionality. The ASCOM interface uses an INDI wrapper around ASCOM which provides only basic functionality. 

Thats what I found out when I tried it.  You dont get the same functionality or choice of equipment.   Kstars itself seems to be at the same release level as far as I can tell.

11 hours ago, wimvb said:

 

Yep, indi/kstars is wonderful, because everything is "under the same roof". I use it on a raspberry pi clone, so I don't need to take my laptop outside. Support is also excellent, from the indilib forum. The only problem is that once you have it, you want to build a fully automated obsy, to use its full potential.

Yes I am beginning  to realise that.  I will resist ?

I note there is also a Mac and a Windows version.  The Windows version relies on ascom drivers  and other stuff so its not as easy to use as the Linux version which as you say gives you everything under one roof.  Wish I had found out about this earlier.

Kstars software is just amazing.  After finally choosing the correct mount type i.e. EQMOD.  ( and NOT the Skywatchers alt/az ? ) , my mount connected and slewed perfectly.  My ZWO camera also connected and worked straight away.

The whole experience of switching from Windows 10 to Ubuntu linux and using Kstars was way easier than I expected.  Kstars seems very capable and logical to use.

Got to play with it now to do some actual astrophotography.

You certainly don't need to be a computer geek to create a dual boot system the whole process is not that  difficult.  

Take it in easy steps and make sure you have backed up your system first.

3 hours ago, alacant said:

Excellent progress. Do post how you do. 

One thing which hits you with Kstars is its logic. Everything is where you'd expect. The other big plus I found compared to ascom is that it has everything from mount control, imaging, plate solving and guiding all in the same app. There's no more apt, PhD,  eqmod etc to have to install separately and get talking to each other. 

Cheers and good luck.

KStars installed great and started ok. Will try connecting to my mount and camera tomorrow.  Got to say very impressed so far.

Just installed ubuntu 18.04 (the latest release) as dual boot on my HP laptop running Windows 10.  It was relatively easy have to say. I downloaded the ISO from ubuntu and saved to  to a USB  stick using Etcher.

I did do a full back up my C drive first just to be safe.  Installing KStar next.

Sharpcap 3.0 beta is now available to download.

Sharpcap 3.0 beta

1 hour ago, frugal said:

I managed to fiddle with the settings to get SharpCap to recognise about 26 stars last night by tweaking exposure time, digital gain, noise reduction and some others. After a few failed attempts (I know I am trying this at twice the recommended focal length, so I was chancing my arm), I got the image to Plate Solve. Then when instructed, I moved the RA axis 90 degrees and it Plate Solved again. Woot!. Then I clicked Next as told... "Guided Alignment is only available in SharpCap Pro"... [removed word]

This is with the latest beta version. Having a look at the website it says that the beta versions will have all of the licenced features until the end of the beta period. Has this changed?

Does the Polar alignment feature work well in 2.9? Is it worth uninstalling 2.10 beta and installing 2.9?

I had the exact same issue last night, having just updated Sharpcap to the latest Beta.  I was not happy as I didn't realise the new licence was available on their site.

So I decided to take some pictures of the moon and went to bed. 

I have just now downloaded the licence so hoping for clear skies.

I have changed from using a Skywatcher ST80 as my guide scope with a Toupcam to just using the Skywatcher 50 x 9 mm Right Angle Finder with an adapter and the same Toupcam.    Sharpcap Polar alignment works great and it is much lighter.

On 8 September 2016 at 13:54, Xplode said:

The message can not be caused by clouds, it's a problem with the communication to the camera so it sounds like a USB problem, could you tell more about how the guidecam is connected? Cable length? Hub?

Thanks for getting back if you were you referring to my post.  

I seem to have solved the camera message problem,  but last night (first clear night) when I set up again  I couldn't get PHD2 to start tracking because it couldn't connect to the mount this time.

My setup is :

HP Laptop running latest (Aug 2016) Anniversary version of Windows 10.  Also got current ASCOM drivers Version 6.2 

Guide camera is Toupcam GCMOS01200KMB connected by (2 Mtr) USB cable direct from Toupcam into USB port on laptop

plus an ST4 cable (1 Mtr) from Toupcam ST4 port direct to Auto Guide port on AZ-EQ6 GT mount.

Guide software PHD2.6.2  (latest version) 

PHD2 settings were :- 

     Camera :- Ascom Toupcam Driver  (Could see stars although they were very feint because of the bright moon)

     Mount :- Toupcam ST4(ASCOM)

PHD2 said camera connected but kept getting new message saying can't connect to mount because of ASCOM problem, gave up last night and went to bed !!

When I tried it again today in the daylight everything connected OK as long as I start Ascom tools first to get Ascom running in the background.

I plan on trying again next clear night.   This tracking is driving me crazy.   

Am I doing something wrong in my settings or is it just bad luck ?

Just found this thread and it is exactly what I needed after spending 3 frustrating nights trying to get PHD2 guiding to work properly.

Thanks to IanL for providing all the info, read once and will read again to try and get it to stick.

I am using the FLO guiding package  (ST80 + Toupcam)  on my new mount and have only managed once to get guiding to work in 4 attempts.

I seem to get a lot of   "the camera has not responded over 15 seconds"  messages and the whole thing just hangs up.  Tried extending the wait time for response but still get this issue.

I think it most probably was high clouds causing the problem last night, but it seems a strange message when the camera is still actually connected .

I'm running the latest version of PHD2.6.2 running on Windows.  I get a sinking feeling the drivers are buggy under Windows 10.

Anyone using the FLO kit successfully?