6 replies to this topic

[SwissCheese]

After trying many things, I got it to work Basically, I used an Android emulator, installed SkyPortal in the Android emulator, and can now control the telescope from there!

 

So in detail (I'm using Windows 10):

 

- First, set up the Telescope Wifi mode to Access Point (it's explained in the Appendix B there: http://www.celestron...TION_Manual.pdf). You'll need to connect to the telescope using a mobile phone or tablet for this. Once it's done, you won't need the phone/tablet anymore.

- Install Andyroid (Android emulator, the installation might take a while): http://www.andyroid.net

- Before running Andy, go to Andy installation folder, launch HandyAndy. It will now be available in the icon tray of the taskbar on the bottom right. Right click on HandyAndy, and then click on "Andy VM Launcher". There, go in "Set VM options", and change "network mode" from "NAT" to "bridged".

- Download SkyPortal: I downloaded both apk and obb files on the Windows side from there: http://apk-dl.com/skyportal/, then moved them to the shared folder: C:\Users\My Name\Andy

- Launch Andy, install SkyPortal (see the explanation there: https://youtu.be/gGJyXzAq5FI )

- It's probably also OK to download and install SkyPortal from within Andy.

- Run SkyPortal, connect to the telescope, and that's it!

 

So, a bit complicated... but quite happy that it finally works

 

Edit: Two messages below, there is a detailed description how to install NexRemote and how to control the mount using FireCapture

Edited by SwissCheese, 03 March 2017 - 02:35 PM.

[thl04]

Basically, I used an Android emulator, installed SkyPortal in the Android emulator, and can now control the telescope from there!

 

(see the explanation there: https://youtu.be/gGJyXzAq5FI )

Interesting find, thanks, I am too new to my Evo9 yet but all downloaded to try later

 

Bamboozled by his vid. though ! I much pref. written stuff that can be studied and thought about at leisure, not at his (familiarity) speed

[SwissCheese]

So, finally got what I really wanted! (After a lot of googling, trying, and failing most of the time... )

 

So now NexRemote is working through the WiFi connection, and I can steer the mount in FireCapture. Haven't tested the autoguiding yet because of the bad weather though.

 

Actually it's not so dramatically complicated, the issue is that you can't find the complete information anywhere (or I missed it...). So I'm writing here in detail how I got it to work.

 

First download:

- NexRemote (hand control): http://www.celestron...onomy/nexremote
- SkyQLink (virtual com port): http://www.celestron...nk-pc-installer
- The ASCOM drivers: http://ascom-standards.org/
- The Celestron ASCOM drivers: http://ascom-standar...copeDrivers.htm

 

I made the connection in Access Point mode (on the home WiFi), because I did not manage to connect to the scope own WiFi from my PC. And besides, I want to keep internet access on the computer. So it will work from the terrace, but obviously it won't work elsewhere.

 

Connecting the mount to the home WiFi:
- Start the mount and be sure the WiFi switch is in "up" position. It's the tiny switch below "AUX2".
- Install SkyPortal on a smartphone/tablet.
- Connect to the telescope WiFi with the smartphone.
- Start SkyPortal and go to Settings -> Telescope -> Communication.
- Select "Use Direct Connect", then in SkyPortal main screen, connect to the telescope
- Go back to Settings -> Telescope -> Communication
- Click on "Configure Access Point"
- Enter the home WiFi parameters
- Click on "Send Configuration to WiFi module"
- Change the WiFi switch position to down (the mount may need to be restarted)
- Reconnect the home WiFi on the smartphone
- Select “Use Access Point” (SkyPortal may need to be restarted)
- Check that the connection with the telescope is working

 

The IP address of the telescope is needed next.

 

If the IP address is delivered automatically (DHCP), one way to find the IP address of the telescope is to check the router:
- Open a browser and type 192.168.1.1, then enter name and password (if it was never changed, it’s typically “admin” and “password”)
- Check the IP addresses of the connected devices and find the telescope

Another way is to use the command prompt:
- Type ipconfig, find the IP address of the default gateway
- Type “ping 192.168.1.1” (if it is the IP address of the default gateway)
- Type “arp –a” and hope that you find the IP address of the telescope in the output list

 

Install and setup SkyQLink:
- If the install does not work directly, right-click on the executable, select properties, and in compatibility, change compatibility mode to Windows 7.
- Launch SkyQLink
- Enter the IP address of the telescope for “Sky Q Link IP”
- Enter 2000 in TCP Port
- Choose an available COM Port
- Connect

 

Install NexRemote:
- If it does not work directly, right-click on the executable, select properties, and in compatibility, change compatibility mode to Windows 7.
- Under PC Port, select the new COM port from SkyQLink
- Select the mount model (or All Models)
- Choose the same Firmware as the actual Hand Control (NXS for the Evolution mount)
- Choose a Virtual Port
- OK
- Test it

 

Setup the ASCOM drivers (NexRemote has to be running):
- Install the ASCOM drivers and those for Celestron
- Launch “ASCOM Diagnostics”
- Choose Device -> Choose and Connect to Device
- On the first line: Select Device Type -> Telescope -> Choose -> Celestron Telescope Driver -> Properties
- There, select the port (same as Virtual Port in NexRemote) and the Track mode and click OK
- Back in the Device Connection Tester, click on Connect
- It should work fine

 

Run FireCapture, connect to the mount using the “ASCOM Compatible Mount”, it should work fine.

 

Edited by SwissCheese, 03 March 2017 - 02:29 PM.

[vagrom]

SwissCheese, no holes in that instructional post 

 

I have had success with this, although autoguiding with PHD2 was extremely unreliable. Would cause ASCOM driver to crash and then you have to restart everything including NexRemote, which means you lose your alignment and must start the night over.

 

I use C2A for planetarium software and it works well with both the ASCOM Celestron Driver and with a direct connection to the mount.

[SwissCheese]

So, had to buy a wifi repeater/extender, without that, the connection was not good enough on the terrace.

 

The autoguiding on FireCapture has been a failure so far, I could not find settings that really maintain the planet in the center of the window. Actually it typically tries very hard to make the planet flee from the window

 

But guiding manually using NexRemote works fantastic! It's much more precise than using the hand control, very easy to keep the planet centered. I can finally select windows tightly fitting the planets and get higher frame rates.

[santafe retiree]

SwissCheese --

 

GREAT post!  I used your instructions as a guide and after a few attempts I got it to work!  

 

One discovery is that you can use the SkyQ Link software to configure a static IP address for the mount rather than having to use the SkyPortal software.

 

Just click “Cancel” to stop the auto connect that SkyQLink will try to run and then right click on the virtual hand controller box and select “Configure SkyQ Link Settings”.  That brings up a dialog box to set the new IP for the mount.

 

Thanks for your  work!

[netwolf]

Just what I was looking for thx SwissCheese, have you tried it with Autoguide via Firecapture?

 

Want to do this to avoiding having to constantly recenter the planet while imaging. 

 

Also you could setup your router to assign the same IP to the MAC address of your scope. Most routers will allow this and even show you the MAC address of currently connected devices. Another way is to use the Android app Fing it scans your network and will identify various devices, should not be to hard to guess which one is the Evolution mount.