Atreta

Hi, what exposure length are you using? 

18 hours ago, Adam1234 said:

I heard that any calibration files in the main group get applied to all groups? 

Nice, didn't know that.

Edit: I just read the information at dss site and you are right, thanks for pointing it out.

1 hour ago, alacant said:

Really? Are you sure you had between 75 and 80mm cc to sensor? 

I'll give a try with a larger spacer that i have, i remember to have tried with 75 and abou 77mm.

Yes each group will be processed in separate , but there will be only one final stacked image. 

Since you have calibration files for each session, in DSS you can place the images in different groups, for instance you load the first night's images it will be in the main group tab(right in the bottom of the screen) and it will create a group 1 tab, you put the second session there along with its proper calibration files, thenit will create a group 2 and so on. 

But if you use only one set of calibration files you can load them all together in the same group. 

1 hour ago, dyfiastro said:

very nice

I can recommend the Baader MPCC if you are looking for a replacement. I have had very little issue getting it to work with both my 130PDS and my 200p

Thank you.

I'm considering saving up for the MPCC as it is well recommended in here.  One thing that i liked about the gso cc is that it increases the focal length and  so we have to rack the focuser outwards and this removes the Pacman effect on  bright stars. 

Haven't been imaging for some time due to lack of clear skies, but got two good days in a row.

This is my latest image of the good old carina nebula  with about 5 hours of data processed with startools. I have a few more hours of previous data, but i'm getting some overlapping problems.

Forgive me for the huge coma around the corners, I gave up trying to use the gso coma corrector because the stars were looking better without it.

Well this is just a guess,.

t's been a long time i don't try to sync within stellarium. But if it behaves the same way when issuing a sync command from aot, then it will not sync if you don't press the tracking button in eqmod(apt also has a button for that). And by looking at your screenshots tracking is disabled, so you could try that and see if it works. 

8 hours ago, bencevokoszt said:

. I have RS323 usb converer. I use it with it but stops at 24

When i upgraded mine, i had that same problem with my usb adapter. I had to connect the cable to an older pc with a serial port and the update worked fine. 

14 hours ago, GrampyG said:

Hi

 

I'm probably doing something stupid but DSS won't stack on my Desktop computer - I get the message that Folders are read only. This happens with all folders. It does, however, work perfectly on my laptop.

Any ideas

Thank you

Hi, can you give more details? does DSS stack the images, but give an error when it is about to save  the image, or give that error right away?

on my windows 10 machine it won't allow to save anything  to the root of the disk, the c:\ "folder". Maybe that's your case,

Also can you tell an example of a folder you have tried to use?

with more details we may be able to help you.

1 hour ago, Marvin Jenkins said:

120 x 30 sec subs at ISO 800 and ten darks. I went through the subs before stacking and discarded four due to satellite trails. My first stack in DSS with the help of YouTube of course went perfectly.

That's a great m42 image.  You can keep those images with satellite trails, if you stack with sigma or kappa signa methods(forgive me  I can't remember the exact name, I'm not on my pc right now) dss will remove them in the final image. 

Nice, glad it worked. I'm thinking about Kev M problem, i never seen it before. 

Edit: i was reviewing my last sessions and it looks like it's mirroring after each image. First one is OK, second one mirrored, third one ok, and so on. 

And looks like this is happening only in apt image browser, under windows explorer everything is normal. 

It looks like a bug within apt. 

6 minutes ago, almcl said:

I have a similar issue in APT, (win 10 and a Canon 700).  An upgrade or so ago the displayed image started showing up randomly flipped. 

At the same time some of the lights are now displayed portrait rather than landscape style in File Explorer.  

Not sure if this s a camera issue, a Windows one or and APT problem or some combination of all three.

Be interested to know if you find anything out?

Can you check if in your camera is set to auto rotate vertical images? 

https://support.usa.canon.com/kb/index?page=content&id=ART136901&actp=LIST

6 hours ago, Jkulin said:

I tried yesterday with CC 2019 and CC2020 and the plug-ins will not install

Hi, was it a 64 bit version of cc? Mine was photoshop cc 2014.  Fits liberator only installed a plugin for the 32 bit version. It won't install for the 64 bit. 

Maybe it also stopped working on newer  photoshop versions, i gave up on it after i started to use startools to process. 

17 hours ago, Longinthetooth said:

I can't find detailed instructions on how to install the Fits Liberator PS plugin. The webpage below leaves a lot to the imagination! Would you outline what you did to get the plug in "plugged in" please?

https://www.spacetelescope.org/projects/fits_liberator/download_v301/

this is the file i used to install: https://www.spacetelescope.org/projects/fits_liberator/download_v23/

sorry i didn't mention it before because i didn't remember if used the v3 or the v23 install, but i looked  inside my old notebook hdd and found it.

the install routine will ask for the photoshop executable, plugins, scripts and actions folder, if the install path is correct it should populate the fields automatically. 

4 hours ago, Brushman said:

I was using Sky Safari to try and solve this myself and it said that PANSTARRS was much higher in Cassiopeia - is Sky Safari not as accurate with comets or something? 

I'm sorry, It looks correct, i misplaced it "near" the wrong star. It was nearer Segin (  ε cas). 

I uploaded your cropped image to nova astrometry and it solved this: 

http://nova.astrometry.net/user_images/3379473#annotated

Using stellarium i looked for V Cas and zoomed in and it showed that c/2017 T2 PANSTARRS  seems to be around that area.

On 29/01/2020 at 12:30, wornish said:

Even the "updated" Version 3.01 of fits liberator was released in 2010!

The website refers to PS version CS4 and CS5. and Windows XP !!

Is there a version that will work on Windows 10 running as a Photoshop CC plug in?

 

IIRC it should work fine. I used to use it under windows 7 and photoshop cc. Fits liberator will install the plugin automatically. 

I never used it, but as far as I know it is used to control the mount using a gamepad in place of a synscan controller. You can remove it If you won't use a gamepad for that. 

Very nice,  and a good opportunity for your friend to also learn how to remove gradients/light pollution. 

What program did you use to process it? 

9 hours ago, han59 said:

later, proposed. See https://www.ap-i.net/mantis/view.php?id=2264

Very nice, thank you for proposing it. It will be a great helper if this can be implemented. 

That's interesting, just out of curiosity, would this work with a manual focuser and tell when the best focus is reached? 

I think i made some progress tonight, I switched the 12mm spacer for a 20mm one and the total backfocus for the gso coma corrector+ camera became about 76mm.

Then i also reviewed the collimation and took some time doing it with a star test and when i thought it was ok, i went for the test shots.

the corners look a lot better, yet not perfect, one other thing i noticed is that it was a bit harder to get the best focus ( maybe i'm getting old, lol) 

anyway, here is a picture to showing the result of tonight`s efforts.

ps: a noob question: is a coma corrector also a field flattener?

I'll try again tonight if it's clear and report back. 

I can make a tad smaller ring so the corrector + camera can be inserted deeper into the focuser tube and have it  focus more inward without protruding into the light path. 

4 hours ago, alacant said:

Hi

Where's the focus position? Is the focuser tube protruding into the light path or is it a long way from the tube?

Anyway, assuming you nailed the collimation, it looks like the camera is tilted; too close at the bottom of the frame, OK centre, astigmatic/too far at the top.  It's a common problem with the sw focuser. Quite often, loosening the screws and re-seating the camera in the focuser is all that is required, albeit hit and miss. You can drill and tap m4 at 120º for a third screw to hold the camera more positively in the focuser. More definitively, the gso gives enough back focus to be able to use one of these, but then you're on your way to a proper replacement focuser. From bitter experience, these are best avoided;)

Also, unlike other ccs, the gso has a 10mm working range so maybe try a further 2 to 3mm away from the sensor too.

HTH and clear skies

Hi Alacant, 

The focuser is almost all the way out. I made a 30mm length ring to make some space between the camera and the top of the focuser to avoid it being inserted too far and having to pull by hand and misalign.

I'll print a longer m48 extension today to see if it gets better being more distant from the sensor.  

The baader click is interesting for a future upgrade,  I'll have it in mind. 

Thanks a lot for the help.