5 replies to this topic

[LowcountryRonny]

Greetings everyone!

 

Please, in advance, forgive me if I have not found what I need here on CN, but I am at the end of my proverbial rope! <ggg>

 

I own a Meade LX90 8", new in 2023. Love it!  It works perfectly via serial cable (and USB adapter) to my Win11 (new in 2022) notebook.  I use Stellarium (x86; the x64 version doesn't talk well with the serial cable; learned that the hard way; that's another story) and Cartes Du Ciel.  No issues at all connecting and coordinating and aiming with my scope.

 

I also use Stellarium Mobile (paid) using my iPhone.

 

I purchased a WiFi adapter from Astro-Gadgets.  It connects and works perfectly with Stellarium Mobile on my iPhone.  No issues.

 

However, in order to try to use it on my Win11 notebook, I understand that I have to do a virtual serial port "bridge."  I get that all... no problem.  I understand that using HW Virtual Serial Port software is a good option.  Astro-Gadget suggested this software application, but provided no detailed instructions re: its use.

 

Yes, I can "see" the "AutoFi" WiFi item when searching for WiFi on my notebook... and I can connect to it successfully.  It uses IP4 - 192.168.2.1, port # 1234.

 

I know to use ASCOM as opposed to direct serial drivers when trying to use WiFi on software to wirelessly control my telescope.  I can configure both Stellarium and Cartes Du Ciel to control my telescope via direct serial cabling using ASCOM.  I get all of that.

 

That all said... I can't get this to work via WiFi/Win11 notebook/HW Virtual Serial Port.  I am assuming that I don't have the HW Virtual Serial Port software configured correctly, or I don't have ASCOM configured correctly, or both.

 

But... even though I am a retired tech coach at a large public school district (US), I am completely baffled as to what I need to do to get this accomplished via WiFi!  I have read and searched and snooped... but I get only partial "yeah I finally got it to work..." kind of info from folks in various places here and there... but no one spells out exactly what they did, step by step, to get it configured successfully.

 

So... OK, I will "eat my humble pie" and plead true ignorance here! <ggg>  What I would love to find is some "how to", step-by-step info, on how to configure WiFi control using either Stellarium or Cartes Du Ciel using WiFi with an Astro-Gadget WiFi unit (or any similar unit) for my Meade LX90, using the HW Virtual Serial Port software and ASCOM.  I just can't find step-by-step information anywhere!

 

Thanks a million for any step-by-step help here!

  Doug W.

 

(Yep I am OK understanding IP addresses, port #s, DNS details, etc.  I just need some step-by-step help!  Thanks all!)

 

PS:  If I get it all figured out, I will GLADLY organize my findings and post it here on CN for others to use!

 

[ButterFly]

Here is a walk through for Nexus DSC and ServoCAT.  The setup for vsp3 is the same.  Ignore everything after the middle of page 3 of 8.

 

 

The variables are:

1) the COM port, which your system decides.  That should be filled in automatically, and is available in your Device manager if it's not.  Use View -> Show hidden devices if it doesn't show up.  If it still doesn't show up, uninstall and reinstall vsp3.

2) The IP address of the device, which you need to find out.  Check your router for a list of connected devices if you don't know.

3) The port.  This is typically set by the device that is broadcasting the serial connection.  Check your device's set up page to figure that out.

 

The free version of HW VSP3 is limited to baud rates of 9600.  Make sure your mount's serial port is set to 9600, or else you cannot use the free version of HW VSP3.  If that is the case, there are other options.  It is most likely the case that it is at 9600, however, so you should be fine.

[ButterFly]

 

I know to use ASCOM as opposed to direct serial drivers when trying to use WiFi on software to wirelessly control my telescope.  I can configure both Stellarium and Cartes Du Ciel to control my telescope via direct serial cabling using ASCOM.  I get all of that.

 

This isn't necessarily correct.  When using vsp3, it is as though there is a virtual cable going from the mount to the PC.  You can connect to the mount otherwise than through ascom, as though there were an actual hard wire from the mount to the PC.  That is the whole point of a virtual COM port - you connect to the COM port as though it were actually hard wired.  You have the choice of using either ascom, or the mount's native drivers.  After all, ASCOM is simply connecting to your mount through its native drivers, then essentially presenting a translation service so software doesn't have to speak your mount specific language.

 

 

 

That all said... I can't get this to work via WiFi/Win11 notebook/HW Virtual Serial Port.  I am assuming that I don't have the HW Virtual Serial Port software configured correctly, or I don't have ASCOM configured correctly, or both.

 

 

ASCOM knows nothing about whether the COM port is real or virtual, nor do any other programs on your computer.  The virtual serial port is in every effect, any other serial port.

 

 

[ButterFly]

 

Yes, I can "see" the "AutoFi" WiFi item when searching for WiFi on my notebook... and I can connect to it successfully.  It uses IP4 - 192.168.2.1, port # 1234.

 

It appears as though you are in direct mode (not going through a router).  The .1 ending is probably the gateway address of the device's DCHP server.  Use the IP address assigned to your computer instead when using direct mode.  You can figure that out by running ipconfig from a command prompt in windows, for example.

 

If you were going through a router, you would use the IP address of the device that is broadcasting the serial connection.  For example, my router's gateway is 192.168.0.1.  The router assigns 192.168.0.2 to the device doing the broadcasting, and the router assigns 192.68.0.3 to my computer.  I would use the device's IP address in vsp3 - 192.168.0.2 - rather than my computer's.
 

[LowcountryRonny]

Greetings! Thank you so much for your information! I do apologize for my delay getting back to you… necessary travel obligations.

I am going to settle in and play with this again usung your info. Help me if I don’t have this correct:

1: I am connecting my Win11 notebook’s WiFi directly to the WiFi adapter connected to my scope. Its IP4 address is 192.168.2.1. All that part is successful. No I am not going through a router. So, when I set up a virtual COM port, I will use this SAME IP address, and assign the virtual VOM port software to an unused COM port #.

2: When I set up a new scope in Stellarium, I am going to use direct mode, using (in my case) Meade “talk.” Whrn I create a new scope in Stellarium, I will use the new COM port #.

Sooooo… how does this sound to you? Do I have this all correct in my brain? <smile>

If I am still missing something, I would sincerely love to hear from you with a bit more guidance. I am sure that there are others out there that want to work through this as am I.

Greatly appreciated!!! Doug W.

[ButterFly]

1: I am connecting my Win11 notebook’s WiFi directly to the WiFi adapter connected to my scope. Its IP4 address is 192.168.2.1.

 

 

Use the scope's IP address.

 

 

2: When I set up a new scope in Stellarium, I am going to use direct mode, using (in my case) Meade “talk.” Whrn I create a new scope in Stellarium, I will use the new COM port #.

 

Exactly.  It's the same as though a physical cable to the scope were on that COM port.