festoon

Thanks @newbie alert, the mount is a heq5

Thanks @Skipper Billy. Yes I’m using an tracking equatorial mount. I can understand the point that if I need to guide at a rate of say 1s exposures then they need to be different cameras. In my case my exposure is usually 30s and my stars are still not blurred during this time. Good point @vlaiv about the software. Yes I don’t know what software would do this, and was part of the reason behind posting here if it would even be feasible.

If I am using a CMOS camera for deep sky imaging at a focal length of 412mm. I usually take many exposures of 30s length and stacking. Each sub there is no noticeable drift of the star or blurring. However after maybe 2-3 subs there is a noticeable shift in the framing of the image. At this point all I would like to do is re frame the image. In this scenario is it possible to use the same camera for guiding and imaging? Probably better described as correcting the tracking and imaging using the same camera.

It took me a few attempts flying using the force and failing! but when I just used the numbers to guide me I docked successfully

Thanks Mike, I noticed that too about the lens potentially being at an angle. Not sure how to fix that as the lens screws into the threaded mount on the camera and the focus is achieved by rotating the lens in the housing. Thanks for the info on the arecont and Fujinon lenses I'll take a look at them.

Thanks @paul mc c. It was taken using my ASI224MC with the wide angle lens with an exposure of about 25 seconds. The image was auto stretched using AllSkEye which is a fantastic piece of software for all sky cameras.

Just testing out my ASI224MC camera last night with the wide angle lens that came with it. I noticed how the stars in the centre of the field were focused but the stars towards the edge were out of focus. Is this common to see this much spherical aberration with a wide angle lens with the one supplied by ZWO? Also any recommendations for a lens that gives better results would be much appreciated.

Hi Steve, no it can only be controlled electronically

hi @RadekK and @Stu Todd sorry if you thought I was complaining - far from it. Just trying to get my sw mount and indi to work well together

I found the same issue as @stash_old...with the sw az indi there was no way to park the scope at north and level. When I tried park north it sent the Ota on a merry go round and I had to pull the plug to stop it hitting the mount legs. and if I use the sw gti driver with indi it only parks at the north celestrial pole

This is fantastic - well done!

I see this has also been asked on the pi camera forum. So it’s not just you https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=272658&start=50 Might be worth asking it again in an alternative thread as no one has answered yet

Is it with the new HQ camera of pi v1 or v2 camera?

Have you tried sudo apt update and sudo apt full-upgrade?

Assuming these values are correct, if you bin the IMX477 at 4x4 the sensitivity would be 2732mV with a pixel size of 6.2x6.2um and an image resolution of 1012x760 which for the price is pretty impressive And just to confirm what @WimH posted last week...... 200s exposures can be achieved with this camera module

Good stuff @Dan13....the video is great stuff and a helpful tutorial. The only difference here that the user needs to follow is 1) Open Synscan app on windows. Connect to mount in synscan app. And instead of selecting EQMOD ASCOM Simulator on the ASCOM telescope chooser dialogue just select SynscanMobile Telescope on the drop down list

Thanks @Dan13. For me I found for an AZ GTI you need to connect using the SynscanMobile telescope and the app needs to be connected otherwise this doesn't work.

Yes you use the app as a connection bridge. Once the mount is connected to PC with the app you can use the SynscanMobile Telescope ASCOM driver in any suitable program. Then you can happily control the mount in software like stellarium

With the synscan app for windows you need to leave the app open and left connected to the mount. Once this is achieved you can then control the mount with any program that uses ASCOM using the SynscanMobile Telescope ASCOM driver In Stellarium, go to configuration window. The go to plug-ins. The select telescope control. Then configure. Then add a "Telescope controlled by" ASCOM. Under ASCOM settings below press choose ASCOM telescope. Then select SynscanMobile Telescope. Give the scope a name an press OK. You can then press connect and the status should change to connected. The important step is to ensure you keep synscan open and connected to use any other ASCOM connections (using the driver Synscanmobile telescope) with other software e.g. stellarium, Sharpcap

The next thing you need to do is using Synscan app for windows, go to connect settings and select Serial and ensure the correct port number is selected I did not have to play with any baud rate settings (the driver installed itself when I inserted the cable for the first time, and I did not alter the settings baud 9600, data bits 8, parity none). If you can confirm that using the app you can connect to the mount and move it using the app then this would be very helpful diagnosing the problem

I have this set up and all works fine in az mode can you confirm you have this cable https://www.firstlightoptics.com/sky-watcher-mount-accessories/lynx-astro-ftdi-eqdir-usb-adapter-for-sky-watcher-az-gti-mounts.html

If it works in indi, can do 30 secs exposure and sensitive then it will be a very cool gadget for all all sky cam

Completely agree Rasbian would be fine just for connect to over network. However, the advantage I found is that using INDI allows you to work with AllSkEye across the network on another PC.

PS this is what I built at the weekend for a project with my kids as an all sky camera (I know its terrible...but the kids loved the project). If I could replace my QHY5L-ii (with 2.5mm FL IR 1:1.2 (F1.2) lens) with this new Pi camera it would be fantastic. The Pi is running indigosky this has the drivers for the QHY5. The pi is connected to the house wifi whilst in the garden so I can connect to it from indoors. But I doubt INDI it would have the drivers for a new Pi camera...so I guess I have to stick to astro cameras

One of the big down sides to this not being a dedicated asto cam is the lack of ASCOM or INDI support. FOr instance if I was to use this for a all sky camera, I'd want it to be compatible with INDI so I could use it with my Pi and the run AllSkEye from my laptop,