Date   

Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

I suspect it's POTH that messes things up.
Force-closing POTH with the task manager unlocks Stellarium.
Force-closing Stellarium with the task manager does NOT unlock POTH


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Mikas
 

Hi Paul,

I'm sure it is not PMC-8 fault. For troubleshooting, you can install Termux on Android or iSH on iPhone. When outside connect to PMC-8 wifi with your mobile. On Termux command

ip a

scroll all the way down until you see a line starting with inet, must be something like 

inet 192.168.47.11/16

Then ping

ping -c 3 192.168.47.1

Must be something like

64 bytes from 192.168.47.1: icmp_seq=6 ttl=255 time=4.90 ms
64 bytes from 192.168.47.1: icmp_seq=7 ttl=255 time=12.0 ms
64 bytes from 192.168.47.1: icmp_seq=7 ttl=255 time=5.9 ms

If it is so, then definitely it is Windows fault.


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

Here's is the screen as is frozen forever:


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

Ooops,

I spoke too soon.
I indeed managed to slew to an object using Stellarium. And it is still tracking it (I hear the exos-2 motors spinning)
However..... Stellarium is now FROZEN. It accepts no commands, the "slew telescope to" dialog is still on screen, but I cannot close it.
Alt-Tabbing to POTH gives me an unresponsive window with an eternal spinning hourglass (well, the modern hourglass, the spinning circle), Cannot do anything in it. Cannot stop tracking, cannot park the mount. Cannot do anything.

so, my agony starts again.


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

After starting everything up this morning, I set the IP-address using the .bat file, configured POTH, configured Stellarium and tried it out.
It is working now as it should work.
I have no clue why yesterday everything went sideways :(

I will have to keep watch on why and when the PMC-8 decides to stop sending out the WiFi signal. I have a wifi analyzer running on my phone to check if the SSID is still there. The past 2 hours, it was up 100%

Thanks,
Paul


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

Good night. Try this when you get up


wes



--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

After rebooting the PMC-8, i could not connect to it.

Message:  "Unable to connect to this network"   one available button: Close.

I'm done for today, it's late (getting to 1am), and there is a time to say goodnight.


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

The term "ip" did not matter. The name of the wireless adapter was. it should not read "Wi-Fi" in my case, but "WiFi 2"
I managed to get the IP configuration correct, but now the PMC-8 SSID is nowhere to be found, so I cannot connect to it.

Wireless LAN adapter WiFi 2:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Wireless-AC 9461
   Physical Address. . . . . . . . . : B8-9A-2A-AB-8B-69
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6060:7545:6179:3e39%5(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.47.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.47.1
   DHCPv6 IAID . . . . . . . . . . . : 79206954
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-48-32-B5-E8-D8-D1-3F-4C-82
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

See, I told you, my name is Murphy. Everything that can go wrong, will go wrong, at the worst possible moment.


 


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

Paul

Once you get connected via WiFi you can run the configuration manager to set the mode to serial.   Then you can use ascom.

Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

Yes you need to set that to ipv4

Sorry.  Snake bit means things just go wrong all the time.   I thought you were the network guy. Sorry.  Glad you found the settings.   

So pick ipv4. Then change to static.  Then set the address, gateway, and net mask per my message.  That will fix your WiFi connection issue

Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 
Edited

snake bit ??
network guy ??

Dunno what you mean with those remarks. I'm not a native english speaker, so if that is some kind of idiom, I don't get it  :)

Anyway, the netsh command is invalid. There's no "netsh interface ip" version.
C:\Users\User>netsh interface /?
 
The following commands are available:
 
Commands in this context:
6to4           - Changes to the `netsh interface 6to4' context.
?              - Displays a list of commands.
dump           - Displays a configuration script.
help           - Displays a list of commands.
httpstunnel    - Changes to the `netsh interface httpstunnel' context.
ipv4           - Changes to the `netsh interface ipv4' context.
ipv6           - Changes to the `netsh interface ipv6' context.
isatap         - Changes to the `netsh interface isatap' context.
portproxy      - Changes to the `netsh interface portproxy' context.
set            - Sets configuration information.
show           - Displays information.
tcp            - Changes to the `netsh interface tcp' context.
teredo         - Changes to the `netsh interface teredo' context.
So, I guess I'll change ip into ipv4 (I'm sure the pmc doesn't use ipv6 yet)

EDIT: no, that doesn't work either, same error message


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

192.168.47.11, 192.168.47.1

Fat fingers small keyboards 
Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

You ate snake bit 


Ok you are a network guy


Click through to the network adapter setting.   Change it to static. Ip for pic to be 193.168.47.11.   Gateway 193.168.47.1

Mask 255.255.255.0

Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

The batchfile doesn't run for me :(
Remember, I am a little bit unlucky with everything ES :(

=============================
  Change WiFi mode for PMC8
  With Widows 10 Issues
=============================
 
 
 
What to do? Static or DHCP?Static
============================
   Setting IP to STATIC
============================
The filename, directory name, or volume label syntax is incorrect.
 
 
 
IP Mode set to Static
 
 
============================
 PMC8 Network Now Enabled
============================
 
Press Enter to quit


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

Exactly.  Paul, please stop thinking about what ought not to be the problem.  You need to believe there is a problem.  Someone told you you had the wrong IP address. That ip address is the windows default when the dhcp fails.   

Please do what we are telling you to do.  If you don’t you will remain in a messed up state.   

Wes

On Sat, Oct 17, 2020 at 5:39 PM Paul Meesters <p.h.meesters@...> wrote:

[Edited Message Follows]

I am on Windows Home 1909 on this specific laptop. That should not be impacted by the update issue.


EDIT: scratch that - this version IS listed as being affected


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 
Edited

I am on Windows Home 1909 on this specific laptop. That should not be impacted by the update issue.


EDIT: scratch that - this version IS listed as being affected


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

See message 1348 in mounts subgroup
--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Wes Mcdonald
 

A problem with windows update and the rn131 WiFi module.  See my latest post in mounts.  Load and run the bat file to make your pc a static up while using the pmc8
Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100
ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm no-name guide scope ~ 260mm FL
Polemaster, Orion ST-80 and SAG, ZWO 290MM, D5300 astro modified
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Paul Meesters
 

DHCP is enabled for this WiFi connection, so why doesn't it provide an IP ?


Re: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Mikas
 
Edited

Hi Paul

Your IP address is from another subnet, must be something like 192.168.47.11 you have a connection to wifi problem, try ping 192.168.47.1 (autoconfiguration means it failed to get an IP address from DHCP server in this situation your  PMC-Eight).

Last night I noticed that polar-finder reticle is way at of center on my brand new EXOS2 (when you rotate RA axis center cross shouldn't be moving in circles). Most likely because of that it almost missed M31 even after 3-star alignment. Can be the same with yours, just M31 is easy to see even if goto points poorly. I'm going to give a good centering adjustment tomorrow at day time.

p.s. Astrophotography is not sports shooting, you need lots of time and patience :)