I read about this comet yesterday on Seiichi Yoshida's website: http://www.aerith.net/comet/catalog/2016A8/2016A8.html
Although it's rather faint (12th magnitude), it is at least well-placed in the sky, in Andromeda.
So I decided to have a look for it using the iTelescope T16 in Spain, and set up a job to run on this overnight (around 3am our time).

But then the sky here in Bolton cleared as night fell, so I decided to have a go with my own kit too, and did indeed manage to detect it, before the clouds came over again just before 11pm:
Given that there was a bright Moon (low in the South) and I was only using 90-sec exposures (the best I can manage unguided), I was quite pleased with this, my 60th comet.

Then this morning I had a look at my data from the iTelescope in Spain:This showed the comet better (including a hint of the tail), but the tracking wasn't quite right: the mount should have been following the comet's trajectory. And they suffer from aircraft lights too!

I got a clearer picture of the comet last night, despite the moonlight being even brighter than on Sunday. This time I was using an old Starlight Xpress MX716 camera (which I picked up a few months ago for under £100: http://www.boltonastro.co.uk/forums/vie ... ?f=9&t=862) fitted with a Meade f/3.3 reducer, on the back of my Celestron C8 SCT. I'd not tried this combination before, but it worked very well.

And as an experiment, I was running without any Light-Pollution Reduction filter, so I could only manage exposures of 60-sec without the background becoming too saturated. And this bright background did show up the vignetting of this optical system all too clearly:Of course a proper flat-field would have compensated for this effect, but I found the Local Estimation Gradient Removal in IRIS was a good quick-fix.

So here is my final image, which does show a hint of the comet's tail:
The small gaps in the trails of the background stars are due to me omitting a few of the 1-min exposures which were too badly trailed by my unguided mount, but the large gap was due to an unexpected phenomenon: a major power-cut. It was good news that all the streetlamps went out, but although I was running my mount from a 12V battery and the laptop had its internal battery, I was still using a mains power-unit for the SX camera, so it didn't record any data.
And then when the power was restored a couple of minutes later, my neighbour's security light came on, so I had to wait for that to re-set before continuing my captures.

This comet has certainly faded since I last caught it 3 weeks ago.

Last night I'd set up my Starwave 80ED refractor, mainly to try out my PiGuider autoguiding system (which I'd not used since May), and as the comet was high in the sky (in Vulpecula, near the M27 nebula) it made a good target.

The guiding system worked perfectly, but even after I'd stacked a load of 2-min images I still couldn't see the comet, which is in the ringed area:
As I couldn't see the comet on any of the individual images, stacking was quite a challenge! I needed to accurately calibrate my image-scale (3.3 x 3.5 arc-sec/pixel) and then calculate the rate of the comet's track across the sky in odrer to determine the parameters for the TRACK2 command in IRIS . This did reveal the comet (at the second attempt):