Date   

Re: polar-finder reticle not centred #polaralignment

 

Hi Mikka, mine isn’t exactly centred either and if you apply too much pressure it moves slightly as well. Saying that, since I have had mine calibrated it as been very good. I think people think it as been callibrated at the factory but after I checked mine it was miles out. I use an app on my iPhone called PS Allign Pro and use the inverted image. If you can see the other stars in the image then you’ve got much better skies than I have so i have to rotate as close as I can. The calibration made a massive difference, and I get my targets reasonably central in my field of view. I just polar align and go straight to my first target where I may have to toggle LRUD sometimes. I use ExploreStars at the moment and use it for astrophotography with short exposures, usually 30-60 seconds with good results. 


On 18 Oct 2020, at 22:12, Mikas <mikas.sakalauskas@...> wrote:



I'm struggling with polarfinder alignment with the mount itself.

On my new EXOS-2 field and center of the reticle were moving in circles when RA axis rotated. After struggling with centering adjustment I have removed the reticle glass itself. Apparently, the center cross itself is not centered, and not the glass is exactly round. On the instruction manual, it looks perfectly centered. Is it supposed to be like that or I got a bad reticle?
 

<SCAN0019_01.jpg>
 
<SCAN0021.jpg>


--
Michael Whitaker
Wakefield, UK. 
MOUNTS. Exos-2 PMC Eight..
SCOPE: RVO Horizon 72ed. 
CAMERA: Not Applicable. 
SOFTWARE: Just iPad at moment. 


polar-finder reticle not centred #polaralignment

Mikas
 
Edited

I'm struggling with polarscope alignment with the mount itself. (sorry about the wrong title, cannot be changed)

On my new EXOS-2 field and center of the reticle were moving in circles when RA axis rotated. After struggling with centering adjustment I have removed the reticle glass itself. Apparently, the center cross itself is not centered, and not the glass is exactly round. On the instruction manual, it looks perfectly centered. Is it supposed to be like that or I got a bad reticle?
  


Re: PHD2 stopped talking to my mount #EXOS2 #OpenGOTO #pmc-eight #ASCOM

James Everson <jeverson.biz@...>
 

Jennifer,

I was looking into your suggestion and just wanted to give you a heads up...

"Note that Stellarium supports ASCOM telescopes natively since version 0.19.3. There’s no need to use StellariumScope in order to use your ASCOM telescopes with Stellarium anymore. Users should consider switching to the native Stellarium ASCOM option going forward rather than using StellariumScope. StellariumScope continues to work with Stellarium 0.20.x if you need the extra features that StellariumScope provides."

Thanks

--
Mounts: Explore Scientific EXOS II GT, iEXOS-100, Celestron AVX
Scope: Explore Scientific AR102, AR152, FirstLight 152mm Mak-Cassegrain, SpaceCat 51
Guide Scope: Astromania 50mm Guidescope (190mm focal length)
Guide Camera: ZWO ASI120MM Mini Monochrome
Camera: Canon RP (IR modification)
Software: PHD2, ASCOM, and APT


Re: PHD2 stopped talking to my mount #EXOS2 #OpenGOTO #pmc-eight #ASCOM

James Everson <jeverson.biz@...>
 

Jennifer,

Thanks, I will look into that. I was able to calibrate and guide with PHD2 last night, so I think that is good to go. I do have another question, but it may be better suited for the APT or PHD2 forums. I tried to use dithering for the first time last night but it didn't seem to work. I pointed APT to PHD2 and the log showed that had started dithering, but after 15 min it still hadn't resumed imaging. Any ideas?

Thanks again


--
Mounts: Explore Scientific EXOS II GT, iEXOS-100, Celestron AVX
Scope: Explore Scientific AR102, AR152, FirstLight 152mm Mak-Cassegrain, SpaceCat 51
Guide Scope: Astromania 50mm Guidescope (190mm focal length)
Guide Camera: ZWO ASI120MM Mini Monochrome
Camera: Canon RP (IR modification)
Software: PHD2, ASCOM, and APT


Re: PHD2 stopped talking to my mount #EXOS2 #OpenGOTO #pmc-eight #ASCOM

Jennifer Shelly
 

James:

If you want to have a visual aid will need a planetarium program to use with APT such as Stellarium or Cartes de Ciel.  Once you choose your program you will have to configure APT for the program.  If you choose Stellarium you will need to use Stellarium Scope as well.  If you do not care about a visual aid then APT does have its own catalog that you can use that are called Objects.  You would need to select the Object on the main tab, slew to it, and plate solve.  Or you can use Point Craft and do the same.  I hope that makes sense.

Jennifer
--
Sincerely,

Jennifer Shelly
AstroPorch, VA

Mounts
: ES PMC-8 G-11, ES PMC-8 EXOS-2
Scopes: ES ED127 FCD-100, ES Levy Comet Hunter, ES N208CF, QHY Mini Guide Scope, Solomark F60 Guide Scope
Cameras: QHY600M, QHY128C, QHY168C
Misc: MoonLite CFL 2.5 / High Res Stepper / V2 Mini Controller, Baader SteelTrack NT / SteelDrive II, Baader UFC, Optolong 2" L-Pro / L-eNhance, QHY CFW3-L, Baader 2” LRGBSHO CCD
Imaging Software:  NINA, APT, SharpCap Pro
Processing Software: PixInsight, Lightroom, Premiere Elements


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

Wes Mcdonald
 

Paul

Poth used to crash on my tablet occasionally.  After I replaced the tablet (got ruined by dew) I don’t think it has happened again.  

Suggest you get going in serial mode and see how that compares. 

I assume you have the pc set to not connect to any other WiFi  network?  I won’t but it might try anyhow.  

But think of the progress you have made.

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
 

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

4001 - 4020 of 12496