Recently Browsing 0 members
No registered users viewing this page.
Since I live in a flat I do most of my imaging from my balcony... I purposely choose a top floor because of my astrophotography passion in order to have a decent field of view, but my balcony has walls on one side and on top.
So I decided to bring to Stellarium my own landscape and my FOV so I can know exactly which targets are on sight and at what time.
I have done some reading and watch videos but I still have a couple of questions before I begin and hopefully some people from here could help!
a) how should I take my photo... Me standing straight levelled with horizon or placing my camera on a tripod and place it like a telescope looking up in the sky towards North?
b) the famous cardinal points and the line angle_rotatez= in the ini file... Is there a secret of finding this number easy in order to match cardinal points to my photo or the only way is by trial and error....?
Thanks for reading
I have a few questions regarding mount control using stellarium that I can't seem to find elsewhere.
I have an EQ3 pro with with Syscan (handcontrol) and a laptop with stellarium.
The articles I've read refer either to EQMOD or ASCOM as a download requirement for Stellarium, is there any preference here for the EQ3?
I'm also struggling to find details of the correct cable to connect the mount straight into the computer via USB (and which port recieves this in the mount).
Thinking ahead, considering the requirement for the Guidscope and DSLR to be pugged into the computer, I will need to ensure this cable would be compatible with a "USB hub" (an area I havent done any research into yet). My computer has only 2 USB ports!
By Ade Turner
I’ve just bought a Skywatcher EQ6-R Pro. I’m trying to drive it from Stellarium using EQMOD but I’m running into a problem I haven’t the experience to solve.
This is my set up:
Windows 7 Laptop > 10m active USB 3.0 cable > 4 port powered Atolla USB 3.0 hub > Lynx Astro EQMOD cable > Mount (plugged directly into hand control socket)
When I first connected the mount to the laptop (a 2015 Dell Inspiron) Windows 7 searched for a serial/USB driver and installed it on COM 8 (according to Device Manager).
In Stellarium I created a profile for the mount but it wouldn’t autodetect the COM port. So I manually set it to 8.
When I try to connect to the mount it sits for a while and then tells me the connection has timed out.
Anyone have any suggestions as to where I should start to try and get the connection sorted please? Thanks.
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?