don4l

This isn't much help, but my images are exactly the same. I think that vlaiv is correct. It is probably a mix of LP with other stuff. I did some imaging from a very dark site once, and they didn't have this problem at all.

Hello Han, I've been playing with this. It's excellent! At first, the labels were far too large, and overlapped each other. However, if I zoom in before annotating, it uses a smaller font. I mention this in case other people have the same issue.

Why do people think that the above image would benefit from darks?

POTH is definitely not needed. In CdC click "Telescope -> Connect Telescope" and then "Select". There should be 2 EQMOD options. The "Simulator" can be useful for testing. Make sure that anything else that uses the mount also uses the same EQMOD driver. If the mount is fixed in an observatory, then you can use PHD2 to do a remarkably good polar align. Sharpcap also has an align procedure, but I've never used this.

I don't worry about GMT/BST. It is important to make sure that the PC time is correct. Why do you use the POTH hub? I just specify EQMOD in everything that I want to connect.

This happens to me as well. However, I discovered that the error was exactly the same every night. Recently, I did an accurate polar align with PHD2, and I had a few nights where it put my first star bang on the centre of the camera. So I think that it can be very accurate, given the right circumstances.

Two copies???? You should not have more than one copy visible. The two applications should both communicate with the same copy. Are you using EQMOD to control more than one mount? If you are controlling more than one mount, then you really need to watch the Youtubes that I mentioned earlier. There are various configurable options that control what happens when you do a sync. One of the options means that points are just added to the "model" and are used the next time that the mount is connected. Of course, if it is a different mount, then some confusion is likely. The good news is that you can have more than one sync file, but you will have to manually load it every time that you set up.

When you do a "sync" from Cardes du Ciel, the information is stored in EQMOD. Depending on what options you have selected, EQMOD can end up with a lot of points, some of which may be in conflict if they are from different days. Chris Shillito has put up some youtube videos which are well worth watching. I usually clear out any old sync data before adding a sync point near to my target. This way, I only ever have one sync point. I leave this saved in EQMOD, and this usually gets me very close at the next session.

Are you using EQMOD?

I don't know much about the ASIAir or Stellarmate. I did some tests with the Pi, and the results were surprising. Download speeds from the camera varied from 40 seconds, up to 1m33s for a single 12Mb image. I did various tests, some with Wireless Ethernet, and some cabled up. Cabled up performed better than wireless. Even when using cables, there was a difference if the Pi's Wireless was enabled. It looked as if the Pi was affected by any wireless traffic in the vicinity. A friend has suggested that the Pi uses a single "bus" for all data movements. This is entirely in keeping with what I saw. Download to the Indi server on a Laptop is 25s, Indi on Pi - 40s, CCDSoft on Windows - 17s. Once you are imaging, this isn't a huge overhead, but if you are finding, focusing and rotating, then it would add a significant amount of time.

I've been playing with this side of things. I don't have a complete solution yet, although I am down to fine tuning. Last night was my first "live" trial. The system was a Linux laptop at the mount. This had a 4 port usb hub plugged into it. An SBIG6303e camera, EQ6 mount, ZWO 120mc, and a Robofocus were all connected. These were all handled beautifully by an INDI server. Accessing the equipment can be done locally or remotely. For local control, I used KStars, EKOS and Cartes du Ciel. All of this was easy to install and configure. I can also access the system from anywhere with a network connection. At the simplest level, I can use remote desktop from inside the house. I also can use an INDI client (CCDCiel) from anywhere that is networked. For the network, I have used both wireless and I have also run a Cat5 cable out to the mount. Both work seamlessly. This all sounds very complicated, but has turned out to be much simpler to implement than I expected. I bought a Raspberry Pi3+ starter kit a couple of weeks ago (£59.00), and used it to try everything out. The Pi just doesn't move data quickly enough to be practical for handling large image files, but it does offer a cheap way to investigate this stuff. Installing on the laptop was easy after using the Pi. I hope that this makes sense.

Hello Gina, Have you done any more with this? I've been playing with a Raspberry and the Indi drivers although I've been using a Windows client. I'm very interested to see how you get on.

Wow!

That is a good one! Have you heard of UKMON? https://ukmeteornetwork.co.uk/ It might be worth sending them an e-mail.

" into my 911, which I had purposely driven, as it's more economical than my other cars " That comment made me smile. I look forward to seeing some images. Synta/Skywatcher have revolutionised amateur astronomy market in their sectors in the last 10 years. Are we seeing the same thing with the RC market?

So true. One must have huge respect for amateurs who took good astrophotos on film. My first image was taken with a 35mm SLR. It took over a week to get the developed photos back. It was a photo of Saturn, however I had no idea about image scale, FOV or focal length. These days, if I can get my stars that small I am pleased! I immediately bought one of those modern Digital SLRs and was able to learn about my mistakes much more quickly.

That's beautiful.