Recently Browsing 0 members
No registered users viewing this page.
Below are consecutive raw pictures if the ring nebula I took with my canon 600da and RCT 8" with neq6 pro guided with sharpcaps polar alignment procedure on the 15th of this month at 1am. I have 20 of these all 1600 iso auto wb 2 minute exposures. The problem will become apparent when you closely examine them, tracking is almost completely broken. I only stacked about 8 of them as most of the frames are unusable, some are star trails, some are commas and some are double exposures. This has become standard and getting worse since I tampered with my mounts gears and backlash adjustment. I have never been able to get consecutive 3min exposures on this mount, and I got it new 6 years ago, and only used it less than 30 times. I have spent roughly 20 hours trying to get rid of the backlash, coffee grinding noise and knocking when I press the directional keys to no avail, when the keys are pressed I notice the image wobbles violently. The go-to is also not working to 100% efficiently, I have to do guess work if I want my image centred.
Hi all PHD2 seems to be playing up again and Iost a clear night again 🤬 Everything appeared to be fine and after polar aligning (separate camera to guide scope) I set up a new sequence. That started up and focused, plate solved and then guiding started but after a few seconds of perfect looking guiding the RA and Dec went off the scale massively ending up with a PHD error along the lines of "PHD2 is unable to make sufficient corrections in RA, check for cable snags, redo calibration...." Images obviously come out trailed. I have an RDP connection to the laptop at the mount so after happening a few times I went to check for snags etc but it all seemed fine. I set up the sequence again at the mount and the same thing happened. Restarting the apps, power cycling the kit and choosing different targets all resulted in the same issue so I packed it all away. It was also the same if I used PHD2 via NINA or if I just started PHD2 on its own and tried guiding separately.
I'm using an AZ-EQ6 with a WO guide scope and 120mm if it's relevant.
I checked everything was tight and have not looked at any logs yet but does anyone have any bright ideas what might be happening please?
Thanks in advance...
I am looking to purchase a new guide camera following the sad passing of my trusty Meade DSI III, which has stood me in good stead for guiding for over a decade. I will be using the new guide camera with a 60mm Altair Astro finder/guide scope. Any recommendations or advice to inform my search would be gratefully received.
With new mount and upgraded scope features, now looking to venture into imaging.
Before I start, I'm not looking to get feedback on polar alignment, mono guidecam, better imaging cameras, etc; this is more a 'dummies guide' setup discussion! I'm not expecting to get great images at this stage, just more the options available, getting over some issues, so that I can jump outside on a clear night with an ideal, foolproof(!), setup for either imaging or visual as time would permit and what may work best for me. As you may guess from the topic name, I'm a mac user (Macbook Pro) and would rather keep to this if possible (whilst I do have Windows (and Ubuntu) via parallels, I'd rather not use these).
I've got a setup which has worked well for visual, and obviously want to have a couple of 'staple' setups that I can use depending on expectations of night observing or imaging. So far, the best one for me has been the Skywatcher Wifi Synscan controller, which has worked a treat with my Android phone - I use the Synscan app to complete alignment and GOTO stars/planets/DSO etc, or Stellarium_plus after completing alignment. This removes the need for the Synscan Handset and any USB cables to the mount altogether. But I don't know if this will work for guiding.
That then brings me to my issue on mac - connecting USB(A) between Macbook and Handset, I've attempted to control the mount through Stellarium. Trying each of the available connections (/dev/tty.usbsetial-1420, /dev/cu.usbsetial-1420, and just for sake of it, the /dev/tty.Bluetooth-Incoming-Port and /dev/cu.Bluetooth-Incoming-Port) in the dropdown menu under DeviceSettings/SerialPort, I cannot get the mount to connect (well, more like selecting the telescope and clicking the "Start" on the TelescopeControl just results in the spinning icon and I have to Force-Quit Stellarium and start again with the same result each time. Annoyingly (for fellow mac users!), Parallels/Windows/Stellarium connects and controls the mount fine! As the mount is the newer "pro" type, I also have a USB connection directly under the hand-controller RJ45 and AutoGuider ST4 sockets, but using this still results in the same issue. Another issue I have seen is that when I unplug the USB from the computer when connected to the handset, the date on the controller jumps significantly - for example, last night at ~23:30, I was transported through the local wormhole galaxy to Jan 2048 according to Synscan! Obviously unplugging isn't going to happen during a genuine session, but just wondering if this is a possible issue somewhere?!
Any other mac users connecting USB directly to the SW 'Pro' mounts?
Software wise, would folks generally suggest steering away from Stellarium towards KStars or SkySafari(Plus) for controlling the mount?
Can the Wifi dongle be used for controlling mount from computer (any OS) or do I need to go USB either to handset or directly to mount?
Is there an issue in using Mac USB to the telescope compared to 'straight' Windows (i.e. PC/laptop with Windows instead of virtual)?
Anyway, back to topic... I've a Nikon DSLR to use for primary camera at this stage, which would be triggered independently from guiding software. PHD2 is my hopeful choice of guiding software (is EKOS with KStars similar?), with T7C guide-camera on 240mm f/4 guidescope, and at this stage, I can confirm PHD2 at least connects to the camera on OS-X. There is an ST4 port on the camera, but having read several topics, I think I want to pulse-guide directly - is this correct or is ST4 best for this setup? This sorta comes back to software and connections - my understanding is one of the following cable setups for guiding (as a minimum) :
Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => SynscanHandset => AZEQ6
Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => AZEQ6
Guiding-camera => USB(A) => Macbook => PHD2 => Wifi => SynscaWifi Adapter on AZEQ6
[using ST4: ST4_on_AZEQ6 => Guiding-camera => USB(A) => Macbook => PHD2] (no additional connections needed if ST4 is used)
Additionally, I'd like to use an observatory package, say Stellarium/KStars/SkySafari, to select objects and drive the mount, then use guiding software to keep good 'tracking'.
Where in this train does EQMac fit in, or when is it used?
What about the 2019 addition to EQMod (ASCOM Alpaca)? Can this be used or is it already in other packages?!
For Windows users, how does EQMod fit in (if I go down route of getting Windows laptop for controlling things, is the setup similar to above?
There may be bits in the above that repeat, and for that, I'm sorry, just want to get across the message that I'm new to the guiding but haven't quite settled down into the software/hardware I'm expecting to use for 'goto' and 'guiding'
For a mac user, what setup and software are folks using for guiding and observatory softwares for the newer USB-on-mount 'AZEQ6/EQ6-R Pro' mounts from SW?