Date   

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

Paul Meesters
 

Wes,

I appreciate your efforts, but I'm giving up. I've had enough.
Thanks


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

Wes Mcdonald
 

Well you need to be sure.  Do what I told you. Load the configuration manager.  Then use it to find the connection.  The set that com port in The cm.  Then connect.  Then send the ESGv! Command to see if you are good. When that happens you know which comm port to set in the driver.  
--
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
 

On Sat, Oct 17, 2020 at 10:35 PM, Wes Mcdonald wrote:
Be sure to set the comm port in the properties for the Es ascom driver.
that field is filled in by default.. no clue if it's correct or not.


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

Paul Meesters
 

I tried several times, from Setup screen, from Hub screen, no difference.
Rebooted PC, no difference
Uninstalled and reinstalled Ascom platform & ES drivers, no difference

Mount cannot be reached.
Checked IP address - with ipconfig and got Autoconfiguration IPv4 Address. . : 169.254.62.57(Preferred)

But it seemed all a bit odd to me, submask seemed off (255.255.0.0), no gateway, (no expert in this)

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. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6060:7545:6179:3e39%5(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.62.57(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   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


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

Wes Mcdonald
 

Paul

Be sure to set the comm port in the properties for the Es ascom driver.   It needs to be the one the configuration manager could use to get the reply from the mount for ESGv! Command 

--
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

 

How many times did you click on 'connect'?

Some users (like me) need about three tries before it catches.   Not a consistent problem.  Some users have it, some don't.
My WAG (because reasons) is that it's Windows taking its time in setting up the COM port.   

On Sat, Oct 17, 2020, at 16:15, Paul Meesters wrote:
POTH says: "Error connecting to telescope"
I'm ready to give up and throw the towel


--
Mounts: ES PMC-8 EXOS2
Scopes: SV 102EDT, ZWO 60/280 Guide
Cameras:  Nikon D5300, Altair GPCAM2 290M
Software: ASCOM, CdC, AstroTortilla, BYN Pro, Sharpcap, PHD2
Computer:  Thinkpad x230, Win7Pro/64


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

Paul Meesters
 

POTH says: "Error connecting to telescope"
I'm ready to give up and throw the towel


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

Wes Mcdonald
 

After
--
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

Bob Trepiccione
 

I seem to recall seeing a couple errors when I installed, too.

Try it out, those errors might not necessarily mean it won't work.

Think positively...



Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Paul Meesters <p.h.meesters@...>
Date: 10/17/20 2:50 PM (GMT-05:00)
To: MAIN@ESPMC-Eight.groups.io
Subject: Re: [ESPMC-Eight] Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

I did find the 6.4 installer on Github, and installed it on a fresh Windows 10 laptop (hp pavilion).
The install succeeded but with 2 errors in the diagnostics with no indication of what to do to repair it :(

20:31:45.482 Error                     Error List
20:31:45.482 Error                     AstroUtilTests - ##### NOT Matched - DeltaUT value: -1,37904405763513 is outside the range: -1 to 1
20:31:45.482 Error                     AstroUtilTests - ##### NOT Matched - DeltaUT1 - Today value: -1,37904405875108 is outside the range: -0,9 to 0,9
 
Don't know why everything I do seems to end in disappointments
 


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

Paul Meesters
 

I did find the 6.4 installer on Github, and installed it on a fresh Windows 10 laptop (hp pavilion).
The install succeeded but with 2 errors in the diagnostics with no indication of what to do to repair it :(

20:31:45.482 Error                     Error List
20:31:45.482 Error                     AstroUtilTests - ##### NOT Matched - DeltaUT value: -1,37904405763513 is outside the range: -1 to 1
20:31:45.482 Error                     AstroUtilTests - ##### NOT Matched - DeltaUT1 - Today value: -1,37904405875108 is outside the range: -0,9 to 0,9
 
Don't know why everything I do seems to end in disappointments
 


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

James Everson
 

Jerry,

Yeah, that makes sense. Now that it looks like I got ASCOM and PHD2 running, though I need to see if it will calibrate, hopefully tracking will work now that it's running over serial.

With that out of he way, hopefully, what's the best way locate and slew to objects when using PHD2 and APT? I tried installing ExploreStars on my laptop but it seems to get stuck at "please wait".

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: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

Bob Trepiccione
 

Forgot the link, sorry ..


https://github.com/ASCOMInitiative/ASCOMPlatform/releases/tag/Build_2695


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Paul Meesters <p.h.meesters@...>
Date: 10/17/20 1:46 PM (GMT-05:00)
To: MAIN@ESPMC-Eight.groups.io
Subject: Re: [ESPMC-Eight] Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

[Edited Message Follows]

Wes,

This is getting way too complicated and technical for me :(.
Thanks for trying though :)


EDIT: 
Uninstall ascom.  Install ascom 6.4, not 6.5
I would not know where to get an older version of the Ascom platform. On https://ascom-standards.org/ I can't find anything. That download-center is a weird place, and not meant for mortal men it seems.


Thanks,
Paul.


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

Jerry Hubbell - Explore Scientific VP Engineering
 

On Sat, Oct 17, 2020 at 12:12 PM, James Everson wrote:
However, when I tried to slew N
You must realize that you cannot move north from the north celestial pole. All directions are south. You cannot move east or west either away from the north celestial pole (NCP)
 
--
Jerry Hubbell
Vice President of Engineering

Explore Scientific, LLC.
jrh at explorescientific.com

www.explorescientificusa.com
1010 S. 48th Street
Springdale, AR 72762
1-866-252-3811

Author: Scientific Astrophotography: How Amateurs Can Generate and Use Professional Imaging Data
             Remote Observatories for Amateur Astronomers: Using High-Powered Telescopes From Home


Mark Slade Remote Observatory (MSRO) IAU MPC W54 Equipment
Wilderness, VA
Mounts
: ES PMC-Eight G11 + Telescope Drive Master (TDM)
Scopes: ES 165 FPL-53 ED APO CF, ES 102 FCD100 ED APO CF
Cameras:  QHY174M-GPS + FW, QHY163C
Misc: 3-inch 0.7x Focal Reducer Field Flattener, Filters: Luminance,
Red, V-band Photometric, Diffuser, 200 lpmm Spectral Grating

Software: MaxIm DL 6, Cartes du Ciel, Astrometrica, AstroImageJ, AutoStakkert!


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

Bob Trepiccione
 

Hi Paul,

Here's a link to download 6.4

Scroll down to "assets" and you'll find the download.

Uninstalling 6.5 and Installing 6.4 solved all my issues...

Hope it helps.




Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Paul Meesters <p.h.meesters@...>
Date: 10/17/20 1:46 PM (GMT-05:00)
To: MAIN@ESPMC-Eight.groups.io
Subject: Re: [ESPMC-Eight] Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

[Edited Message Follows]

Wes,

This is getting way too complicated and technical for me :(.
Thanks for trying though :)


EDIT: 
Uninstall ascom.  Install ascom 6.4, not 6.5
I would not know where to get an older version of the Ascom platform. On https://ascom-standards.org/ I can't find anything. That download-center is a weird place, and not meant for mortal men it seems.


Thanks,
Paul.


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

Paul Meesters
 
Edited

Wes,

This is getting way too complicated and technical for me :(.
Thanks for trying though :)


EDIT: 
Uninstall ascom.  Install ascom 6.4, not 6.5
I would not know where to get an older version of the Ascom platform. On https://ascom-standards.org/ I can't find anything. That download-center is a weird place, and not meant for mortal men it seems.


Thanks,
Paul.


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

James Everson
 

OK. So it appears the it is moving.

Starting point:


End point:


After running this test I discovered something that I hope isn't an issue. This is what I ran into.

1. Set the position indicators back to the starting position. Set POTH to move 30 degrees per slew. E and W slew worked fine. However, when I tried to slew N, the log says it moved, but it didn't. I then tried to slew S and that worked. Then I tried to slew N again, and it did, returning back to where I started. I then tried to slew from the starting point again, it says it moved, but it didn't. The mount is balanced. I triple checked that.

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: Dec axis motor system faulty or newbie error?? #EXOS2

 

Paul,

You're most welcome !   Glad it got sorted out.  :-)

- Bob

On Sat, Oct 17, 2020, at 09:22, Paul Mogg wrote:
Well I fixed it, took me while as I'm not used to doing any mechanical stuff, and finding the right hex keys etc. but it was exactly as Robert had predicted, both of the set screws holding the large pulley in place on the DEC motor assembly were completely loose on their spindle, so the motor was turning but it wasn't turning the head.

Many thanks again to Robert for his help and instruction sheet, and to Tony for his helpful suggestions.

Paul

--
Location: southern Spain

Equipment:
Explore Scientific EOS-2 PMC-Eight mount
Skywatcher 200DPS Newtonian telescope
Telrad.
28mm 2" and 12mm 1.25" lenses.
2 and 5 x Barlows.
Macbook air 
Huawei Android T5 Tablet
Nikon D3200 DSLR
Software: ExploreStars Android & WIndows, Stellarium OSX & Android, AstroDSLR


--
Mounts: ES PMC-8 EXOS2
Scopes: SV 102EDT, ZWO 60/280 Guide
Cameras:  Nikon D5300, Altair GPCAM2 290M
Software: ASCOM, CdC, AstroTortilla, BYN Pro, Sharpcap, PHD2
Computer:  Thinkpad x230, Win7Pro/64


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

Doug Walker
 

Are the RA-Dec or Alt-Az numbers displayed in POTH moving as I described. This seems like it might be working. For an aiudible verification, do the 5000 pulse guide a bunch of times then park the mount, you should hear it move back.

On 10/17/2020 11:10 AM, James Everson wrote:
Doug,
I followed your steps. ASCOM connected over serial. POTH connected to PMC8. POTH controls move the mount. Connected PHD2 to POTH driver (camera also connected). Using the manual controls don't "appear" to move the mount, but the requests are logged by POTH.
Connected: True -> True (no change)
Name: POTH->Explore Scientific PMC-Eight ASCOM Driver
CanPulseGuide: True
CanSlew: True
CanSlewAsync: True
Declination: +89:50:30
SideOfPier: West
Slewing:  False  IsPulseGuiding:  False
PulseGuide: North, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: South, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: East, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: West, 5000: (done)
IsPulseGuiding:  False
This is using the original cable I have (non-FTLD). As you see, there are a lot of "False" messages here. Not sure if that is normal or not.
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
--
Explore Scientific iEXOS-100
Canon T1i (no mod)
Canon 18-55mm zoom lens
Canon 75-300mm zoom lens
Astromania 60mm guidescope
ZWO ASI 120MC-S
Lenovo m93 / Win10Pro
NINA, DSS, SiriL, GIMP, Phd2


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

James Everson
 

Doug,

I followed your steps. ASCOM connected over serial. POTH connected to PMC8. POTH controls move the mount. Connected PHD2 to POTH driver (camera also connected). Using the manual controls don't "appear" to move the mount, but the requests are logged by POTH.



Connected: True -> True (no change)
Name: POTH->Explore Scientific PMC-Eight ASCOM Driver
CanPulseGuide: True
CanSlew: True
CanSlewAsync: True
Declination: +89:50:30
SideOfPier: West
Slewing:  False  IsPulseGuiding:  False
PulseGuide: North, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: South, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: East, 5000: (done)
IsPulseGuiding:  False  Slewing:  False  IsPulseGuiding:  False
PulseGuide: West, 5000: (done)
IsPulseGuiding:  False

This is using the original cable I have (non-FTLD). As you see, there are a lot of "False" messages here. Not sure if that is normal or not.

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: Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

jrichard333 <jrichard333@hotmail.com>
 

Good day all,

 

I would suggest using the following website:  https://telescopius.com/?fromdsobrowser

 

No guess work on what’s up and when it goes down.

 

JR

 

 

From: MAIN@ESPMC-Eight.groups.io [mailto:MAIN@ESPMC-Eight.groups.io] On Behalf Of Patrick Maher via groups.io
Sent: Friday, October 16, 2020 4:31 PM
To: MAIN@ESPMC-Eight.groups.io
Subject: Re: [ESPMC-Eight] Non-Messier objects in ExploreStars #EXOS2 #ExploreStars

 

I agree with you about finding objects that aren't solar system objects or Messier objects.  This, in my opinion, is a weak area of the app.  What if someone doesn't know the names of things to view?  Wouldn't it be better if we could at least scroll through a list of viewable objects in the sky at the moment?  Obviously, a more graphical interface like we have for the Messier objects and the Solar System objects would be even better but just a list would be okay.  Maybe add-on packs for the app? 

I also use a Surface tablet with ExploreStars and I have no problems so there must be something wrong with your particular tablet/OS or you are doing something wrong (which is easy to do and expected for someone new to the system).  

As far as your other problem, it sounds like you might be losing connection with the mount.  The obvious reason is because you have your tablet set to "Always Connect to this Device" for your home's Wifi.  You must uncheck that option.  Even better, set your mount's Wifi to "Always Connect..."  

My guess is that will resolve the connection issue.

Patrick
--
Explore Scientific iEXOS-100 and EXOS-2GT (non-PMC)
Explore Scientific ED 102mm Refractor