geeklee

I really enjoy imaging clusters. Coming from the observation side, it's fascinating seeing the deep, rich star field view of imaging.

Thanks Olly, I've definitely come across Selective Colour in Affinity Photo (and I'm sure APP has a similar function). I'll pull out the old stacked data and try this out ... and also keep it for future sessions too.

Yep, that weather sounds about right - especially recently. Tag me if you end up hitting the same targets with the 183 - be interesting with the smaller pixels and wider FoV. Should turn out lovely. Agreed on the jump from a DSLR (admittedly not modded). One of my frustrations was the lack of computer control as it was an old, entry level Nikon. Lee

I haven't used a duo-band filter yet, but it's on the wish list. Very nice image here from Ivo with the 533 and ZWO duo-band:

Hi Andy - I'm not sure if there's any useful info in this thread: This was purely with the native driver though. With the ASCOM driver, I only tried Apt and no problems - capture and cooling were fine. It may be that SG Pro and NINA haven't updated their ZWO SDK yet so the native driver support isn't there for the 533. Both SharpCap and Apt have both updated now and I've not seen any issues yet although I think I had already just started using the ASCOM driver. Did you browse through the settings in SharpCap to change the default formats: https://docs.sharpcap.co.uk/3.2/#Preferred Video Format (mentions .fits)

All of those are images look great, but those first two are my favourites - excellent 👍

19 minutes?! Tough to pick between them, but second one just shades it for me for the additional contrast and (perceived) sharpness. Nice one 🙂

Thanks everyone for your kind comments. In hindsight it was perhaps best this post sat in the Getting Started in Imaging. I've had (and continue to have) plenty of frustrating and comedic moments - in equal measures - but that feeling when you finally capture data, integrate and do first stretch... The imaging (previously I'd been solely observing) started with the Back Garden Astronomy week in S@N magazine. I did some sloppy wide field stuff with a DSLR and a tripod and was hooked...

First light on 17th Dec and my first dedicated astro camera with the ASI 533 MC Pro. The moon was starting to rise when IC 410 was capturing and my inexperience with Apt has got poor framing 😕, but some faint data is coming through for a low integration time. Equipment - Sky-Watcher 80ED DS Pro, 0.85x FF/FR, ASI533 MC Pro. Software - PHD2, Captured in Apt, integrated and lightly processed in APP and Affinity Photo I started imaging Deep Sky in October with an old DSLR although have some experience with Lunar - all comments and advice very welcome. I'm conscious of the low integration times - the constant clouds and desire to get *something* captured made me plough on🙂 M35 60 x 30s, 110 x 60s (with Flats, Darks, Dark Flats, BPM), -10degC, defaults in camera - Gain 100 (unity) & Offset 70, Bortle 5/6 NOTE: I noticed that something had gone very wrong with the stacking of the previous. While comparing it to one with more data I saw it seemed to have duplicated parts of the image elsewhere. This one should be more accurate. IC 410 24 x 300s (with Flats, Darks, Dark Flats, BPM), -10degC, defaults in camera - Gain 100 (unity) & Offset 70, Bortle 5/6

Let us know how you get on. They definitely sound different, but it's the official Skywatcher firmware so must be OK... right? 😄

That'll be quite something - good luck! Lee

The cropped version is great, but when you scroll down to the full version it has so much more impact (for me). The colour differences, the layers of structure, the contrast... 👍

😁 Awesome, I'm glad that's all it was!

Just to cancel out something else... I'll apologise in advance as I'm sure this isn't the case but I've got mixed up on my DEC before and loosened it then thought I was tightening it and loosened it to the max thinking it was locked (as the clutch was "locked") but DEC moved easily as I'd obviously gone in the wrong direction. This isn't what's happened here is it, but with RA? I just see in the picture the bolt looks all the way over the right, but IIRC the locking direction is to the left then moving the bolt along the right and going left again.

Hi Ivor. I have the same mount but I don't think I've even really loosened up the RA clutch a lot. Do you mean you've kept loosening, then undoing the bolt, moving it back to the bottom left of that picture, screwing it into new hole, then loosening again - and kept doing that? Sorry, just trying to get a feel for what might have happened. I know when I first got mine, after I loosened the RA clutch by moving towards to the top right of that picture, the tightening wasn't enough going back the way, so I unscrewed the bolt and moved it round to the right and tightened it a little bit more (towards bottom left)

I've had mine for a week or so - still waiting for some decent clear skies! 🤔 I've started to build up a Dark library but from what I'm reading (and seeing around) it might not always be necessary (as I have BPM too). Also using Apt to determine the right exposure for Flats 👍 Did you add on the duo band filter? It sounded like orders direct from ZWO in the US were getting this included? 😮

Must be a good feeling when you find that sharp frame amongst the others 🙂 😁 Previously I would use a manual mount to capture the video sequences but had to use careful framing as I would always lose X% to it moving across view during capture (with a smaller sensor camera) - so appreciate the extra effort going into focusing and capturing here.

Amazing clarity for a single frame - great focus and seeing? My lunar images that look sharp(ish) always need lots of frames and deconvolution! The detail on the full disc shot from terminator in about 1/5 is lovely - some great stuff to spend time on from top to bottom.

Thanks for the report Ivo and really enjoyed the image as well! I'm still waiting for some clear skies to test my 533 out (a step from DSLR for myself). I don't yet have a duo-band filter, but (excuse my lack of knowledge on this) is the image coloured like that coming off the camera? What a difference before and after moon had set; as a beginner it was great to see those initial frames on Astrobin too. (Thanks also for adding the updated driver and SDK so quickly to Apt for the 533)

Just echoing the comments above, but that's a great image. The overall colours of the image + detail and contrast within all the structure is excellent!

I just wanted to add some closure to this thread for any prospective ASI533 users out there. After some back and forth with ZWO support, I replaced the ASI camera DLL file in SharpCap and Apt with the latest version from ZWO SDK (for developers). This did appear to "fix" the issues described but felt like a bit of a hack! Knowing the above outcome at least showed that the application developers just need some time to catch up with the latest native drivers and SDK in their apps. Coincidentally, Apt released 3.82 yesterday with specific support for the ASI 533 mentioned. After installing this version, I could see the latest DLL file was present in the Apt folder and the native driver transferred the images from the camera fine. I'm sure SharpCap will follow suit soon enough.

I have the AZ-EQ6 GT Pro mount (so not the same) but it made this noise as well. While doing some routine checks of firmware, software etc, I noticed Skywatcher had a selection of updated versions for these two mounts with the built in USB port. After updating to the latest (3.07) it no longer makes this noise, but alas the motors now sound a little different so that has me thinking on the flip side of "if it ain't broke...". I wondered if the noise was the motors not slowing in a measured way and the gears catching quickly at the end, but pure speculation with no knowledge 😁 The latest firmware is here - http://skywatcher.com/download/software/motor-control-firmware/ There's the firmware loader and the firmware itself - being careful to select the correct one for your mount (and whether it has the built in USB port). I didn't find the loader particularly clear for two reaons (1) The PDF instructions are geared to Serial connection. When using the USB, it's not obvious but unchecking the box about using the hand controllers PC direct mode resulted in a very fast transfer & update over USB - assuming you're using USB 🙂. and (2) the version numbers are odd matched. First, click "MC Version" to confirm the program can talk to your controller and you'll see what I mean - you can then match them up to the release notes. Mine came with "3.03" but querying the controller showed something like X.Y.3 (I think) i believe you're able to load older firmware if you don't like the new one for any reason.

Thanks @Allinthehead for the prompt reply. As part of the troubleshooting, I tried all the elements you mentioned - early on, just removing the guidecam. The strange thing is usually you might find the occasional dropped frame or inconsistent behaviour but this is just a flat 100% drop of every frame using the native ZWO driver in SharpCap and Apt. Using the ASCOM driver, everything appears OK - had the guidecam in SharpCap and ASI533 in Apt and vice versa no problem doing testing. For now, I'll continue to assume hardware is OK and utilise the ASCOM driver, with some proper testing... if the cloud ever gives way 🤨

Hi all - I've just received the new ASI533MC Pro and was getting acquainted with it yesterday evening while the cloud was in. This included the usual driver install (native and ASCOM), connectivity, USB2 hub to guide camera, cooler and functionality. I have an issue where the native driver is causing problems in SharpCap and Apt, but appears to be working fine in ASICAP (assuming it uses the native drivers). SharpCap and Apt just drop all frames - SharpCap telling me along the bottom, Apt just never completing an exposure and showing "busy". Using the ASCOM driver in SharpCap and Apt appear to be working fine - basic test dark exposures happen and save in a few moments to disk. I've run through almost all the troubleshooting options I would normally associate with dropped frames - esp around USB, but as the ASCOM driver is OK and ASICAP (again, assuming it uses the native driver) can push max frames per second on USB3 when testing millisecond type exposures (seen along bottom in app) it's making me think it's likely a application / native driver compatibility. I'm guessing the way SharpCap and Apt interact with the native ZWO driver is maybe the issue with this new camera as the Apt forum does have a mention of a new minor version (3.82) coming very soon around ZWO drivers. I just wanted to put the feelers out for anyone out there that has also received the camera and whether they're all good in these applications with the native ZWO driver or seeing similar issues? I'm also making sure I don't have a camera hardware problem (it doesn't sound like it from evidence above though). Thanks in advance.

Having taken the journey mentioned above a couple of years ago, I definitely wouldn't go back and change it. Looking back at that initial FLO order, the key items were - Skyliner 200P Dob, Turn Left at Orion and a Cheshire collimating eyepiece. These items were based on existing advice throughout SGL that intimated at this being a great first step. It was more than that - the things I saw through the 200P in my first year (and beyond) were amazing and it really got be me into the star hopping and associated pattern matching to find targets. I now have a good number of sky atlas as well, but compliment these with something like Sky Safari too. The cherry on top was a RACI finder (and Rigel quick finder) which just made everything that bit more comfortable too. While I've added additional equipment since (including just recently a GOTO mount) I can't see a reason why I would ever sell the 200P. Each person is different and learning the sky can also come with a GOTO depending on your approach.