GoldTop57

Not bad for a cheap mount that was never designed for AP 🙂

Sorry - it was powerlord who was having problems with DEC runaway.

At least your DEC looks fairly stable now.  A bit of a saw tooth going on with RA so may be you want to dial back the aggression a touch. What is your exposure time for guiding?

Siril and GIMP (with PYAstro PlugIn) for me on the Mac - both free.

Its official - ASIAIR Plus on the ZWO site now: https://astronomy-imaging-camera.com/product/asiair-plus

That calibration graph on the right looks iffy - its as if you have the left arm version of the FW installed.

Haha - the clue is in the title 😀

Very nice - did you shoot that from the Smoke? Did you use any filters?

Yes - sorry missed that in your post. They did a trade in deal going from ASIAIR to ASIAIR Pro last time. Will see what features they are offering in the Plus before deciding.

👍 for ASIAIR Pro - though due to be superseded by the ASIAIR Plus which I understand will come with an antenna and emmc storage.

I wonder if you could modify the Siril script, find the preprocess command and subtract the bias from the dark (having put your dark flats in the bias directory) then it would calibrate in the right sequence.

Hi - this from the DeepSkyStacker site - I assume dark flats in the bias folder isn't going to work - you could always give it a try though:

Also is there a 1.25" extender included that you can screw into the front of the camera so it can sit further out of the scope?

FLO sell different EQDIR cables for HEQ5 and AZGTi so presumably they are not compatible?

Yes I wonder if the 50/50ms setting for max DEC/RA duration is too short for the corrective pulses being generated by PHD2 to keep the mount on track, could try going for the max 10,000ms and then tune later by dialling down the DA/RA aggressiveness.   

Thats a shame @powerlord, I was getting DEC run away and RA wasn't looking too clever either prior to the latest firmware version but 3.32 has made a massive difference. I'm using ASIAIR Pro too - I've got the Guiding rate set to x0.9 under Telescope/Mount Settings and under Guide Settings I have Max DEC and Max RA Duration both set to the maximum value of 10,000. Also DEC and RA aggression are set to 80 and 70 respectively. Mount is fairly well balanced but is overloaded with about 4.5kgs of kit.

Theres a huge thread on the mount here: https://www.cloudynights.com/topic/586532-new-skywatcher-az-gti-goto-wifi-mount/page-120

Managed to try the new firmware 3.32 last night and was guiding with median total RMS between 1.5" and 2.0" for a good portion of the session - very pleased with these figures for this little mount. 

Not had a chance to test 3.32 but positive feedback over on Cloudy Nights:

Posted Today, 04:27 AM

Good news - so my tests of v3.32 last night were positive and no Dec runaway! I imaged quite high above the horizon (the Veil Nebula) for close to three hours. The guiding error had an occasional blip towards 5 arcsecs, but also long periods of between 1 and 2 arcsecs. The results look fine with my 275mm focal length scope and ASI2600MC Pro camera (3.76 um pixel spacing) undersampled of course at 2.89 arcsecs/pixel. I’d like to pin down and remove the causes of the ‘occasional blips’ but at least this firmware appears to allow the software to recover the situation. I’m using KStars/Ekos/Indi (Astroberry) and the Internal guider with all default settings so I need to study how to adjust the guiding parameters (aggressiveness, hysteresis etc). 

Tried 3.31 last night - run away on both axes now! I've nothing to lose going to 3.32.

Will be interested to see what features/fixes the new version brings.

What's the consensus on 2nd hand cooled cameras? I've noticed a few where the cooling systems have failed and have been repaired, I understand the warranties are not transferable.