Date   

locked Re: #iEXOS-100 with ASIAIR stops tacking #iEXOS-100

Wes Mcdonald
 

Walter:
Welcome to the forum Walter

You should join the Applications subgroup, which is where the ASIAir questions get posted.

I don't know if this is your issue, but please set your "Continuous Track with loss of comms" to true in the UFCT.  This will keep the PMC8 going along even if all the apps give up.

Otherwise perhaps there is a setting in the air that is needed.

Wes.






Virus-free. www.avg.com

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Wes Mcdonald
 

Michael

Ok that’s great news.

Wes

--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


locked #iEXOS-100 with ASIAIR stops tacking #iEXOS-100

Walter Torres <walterftorres@...>
 

Hello everyone,
         Hoping there's a kind soul out there that has figured this out.  I just got my iExos-100 last week and have been struggling to keep the thing tracking.  I searched through the topics but didn't really find a solution to my problem.  Has anyone using this mount with an ASIAIR managed to keep it tracking for more than a few seconds after leaving the ASIAIR app or turning the screen off?  The only way the mount will track is if the phone is on and the app is on the foreground.  Even if a notification will make the mount stop tracking

I did update the firmware of the mount to the latest 20A01.1 this morning in hopes that was the problem but sadly it did not help at all.  I am using it with an ASIAIR Pro, on iPhone X, iOS 13.7.

Thank you,
Walter


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Michael Lunsford
 

I was on an older firmware version. I updated the firmware and driver, did a lot of troubleshooting, and finally got everything working. I was finally able to slew the scope using Stellarium (I've been using ExploreStars on a tablet until now). Thanks for your help!


Re: iexos-100 ASCOM Errorr 40040407 - GetRAMotorPosition #iEXOS-100

Wes Mcdonald
 

Phil

Having some issues with this myself.  Looking into it tomorrow.  Late here.

Wes


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: iexos-100 ASCOM Errorr 40040407 - GetRAMotorPosition #iEXOS-100

Wes Mcdonald
 

Phil

Oh. Interesting

In will give this a go tomorrow and see what I find.  

I think you are making an error in the way you set the mount but I don’t think that is messing you up.  After booting the pmc8 boot the UFCT.  Set the comm port and press get configuration.  The. Change the mount to iexos, and press say configuration.   This will reboot the pmc8 with iexos set as the mount type.  If you press the reboot and show splash screen you should then see in one of the last few lines the detected WiFi to be the esp32.

I will let you know what I find out about WiFi ascom in your afternoon.

Wes



--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


iexos-100 ASCOM Errorr 40040407 - GetRAMotorPosition #iEXOS-100

Phil Knowles
 

Apologies if this is something that has already been covered, but I've spent the last hour and while I have found a few 'similar issues' on the group/google I have not found a solution.

I Upgraded my PMC-8 to 20A01.1 yesterday - the easier wifi channel swap and Dual Wifi/serial was a big sell for me.

As it happens I started the install process from fresh windows 10 laptop

Having gone through the process I ultimately have ended up not being able to connect to the PMC-8 via in ASCOM

I've setup the properties:



But When I test the connection in Ascom diagnostics I get an Error  Ascom.notconnectedException: Get RAMotorPosition.

If I swap to "enable serial port" in the properties and use one of those wirey things, it's all good and I can even use POTH to connect and control....so wires work!
I do not have any issues using explore stars via wifi on my tablet either.

If I go into the PMC8 Configuration manager utility, I can select TCP connection and test the "GET RA Position" successfully.

I verified IP address gateway with IPconfig so I don't think there is an issue there.
I have disabled both my bitdefender firewall and the windows firewall. To rule them out.

Have I forgot to do something in ascom? I have 6.5 SP1. 

One thing that slightly worried me was in the new firmware configuration tool, I selected the mount type as "iEXOS100"

But when I did " Get current configuration" the message view shows:

Mount Type Error!:Please Select G11 or EXOS2 Mount,

             and Press SET New Configuration

And the Wifi Type is shown as RN131 at the top (was expecting to perhaps see the ESP device instead like in the Splash ???)

I was reluctant to change the Mount type given iEXOS100 is in the mount type list - why else would it be there....

Any pointers would be appreciated.

It's bed time for me now (UK), so please don't think I'm ignoring any responses.

 

Cheers

 

Phil

 

 

 


Re: ESOS-II GS Mount confusion #EXOS2

 

Jeff,

 

I’m glad you have cleared that hurdle! But I think I’m the wrong one to help you with 2- or 3- star alignments. My backyard has a very limited area of sky , and I can’t see anything below 45 degrees elevation…and even then, over only a small azimuth. So, I’ve never tried that alignment method. My solution, since I can see at least the eastern part of the region around Polaris, was to obtain a small guide scope and camera, and to use SharpCap to do the polar alignment. That made a huge difference; I can now slew to a selected star and be pretty close. A plate-solve will center it quickly. I am using a tripod-mounted P.C. (one of the inexpensive “mini-computers”) with a short serial connection to the PMC-8 box. I’ve got a small monitor & wireless keyboard/mouse plugged into the P.C.  Once I’m set up and running, I can switch over to Remote Desktop and monitor the guiding and exposure sequencing from inside the house. Other systems like Asiair, and Raspberry PI should be similar. Getting that stuff working was easier than expected, and it seems to have paid off with a big bang-for-the -buck.

 

You are a couple steps away from that level of complexity…maybe one of the helpers here on the forum can advise you on a 2/3 star alignment, or even a simple drift alignment. But hang on; each of these challenges has a solution or two, and the learning process is a lot of fun.

 

Chuck  

 

   

 

From: MAIN@ESPMC-Eight.groups.io <MAIN@ESPMC-Eight.groups.io> On Behalf Of Jeff
Sent: Saturday, October 16, 2021 4:47 PM
To: MAIN@ESPMC-Eight.groups.io
Subject: Re: [ESPMC-Eight] ESOS-II GS Mount confusion #EXOS2

 

Chuck,

You da man!  I was able to finally get out and test your theory.  Although I wasn't able to precisely align my scope due to just using the view finder of my camera, it slew to the general positions 
that I chose from the catalog.  I assume that I will have to do a 3-star or 2-star alignment each and every time?  I think once I get a real scope mounted on, I can better align the mount.
But, yeah, before turning the PMC on, I made sure to match up the arrows, then turn on the PMC.  Oh, and I did turn auto alignment off.  Should I always have this setting off?

Are there any tricks when performing a 3-star or 2-star alignment?  I'm not opposed to doing things the hard way, but if you (or others) recommend that I purchase any software and equipment for that purpose, I would love to hear any recommendations.

Again, thank you and the rest of the group for helping me get over what I'm sure is my first hurdle.  :)

Jeff

--
Mounts: EXOS-II GS, PMC-Eight
Cameras:  ZWO ASI 290MC, Canon 7D
Scope: ES-ED0806-01 (Backordered)
Software: ExploreStars (iPad)


--
Scope: Explore Scientific AR-102, Astro-Tech AD72ED, Nikon kit lenses
Mounts: Exos2GT-PMC8, Homebrew barndoor tracker
Camera: Nikon D7000, QHY5III-462C
S/W:  APT, DeepSkyStacker, Stellarium, CdC, PHD2, Sharpcap Pro, Gimp, RawTherapee, StarTools


Re: ESOS-II GS Mount confusion #EXOS2

Wes Mcdonald
 

Jeff

2-3 alignment only needed when first setting up.  If you move your mount, redo it.

When you do the 2-3 it’s very important to align on the correct star.  So to help in vein go sure you have the correct one you will need a res dot finder.  It is the easiest to use because it shows you the entire sky which you can compare to a sky chart to see which of the stars in the constellation is the correct one.  I use SkySafari and use it to see what star is what relative to the one used by Explorestars.  

Auto align off of what you want.  It allows you to keep moving the through the list of bright stars until you come to one that is visible and you can identify in the sky without question.

Once you move the mount so the star is in the center of the res dot, you then center the star in a medium power eyepiece.  It must be very close to center.  

Once you have completed the 2-3 star go to a star and after you center it hit the SYNC button.  This removes most of the residual errors.  This can be done also when you do a goto to a deep space object that you cannot see to center.  Do a goto to a nearby star thst you can see and center it.  Then SYNC.  The. Do a goto to the DSO. It will be dead center.  

Wes



--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: ESOS-II GS Mount confusion #EXOS2

Jeff
 

Chuck,

You da man!  I was able to finally get out and test your theory.  Although I wasn't able to precisely align my scope due to just using the view finder of my camera, it slew to the general positions 
that I chose from the catalog.  I assume that I will have to do a 3-star or 2-star alignment each and every time?  I think once I get a real scope mounted on, I can better align the mount.
But, yeah, before turning the PMC on, I made sure to match up the arrows, then turn on the PMC.  Oh, and I did turn auto alignment off.  Should I always have this setting off?

Are there any tricks when performing a 3-star or 2-star alignment?  I'm not opposed to doing things the hard way, but if you (or others) recommend that I purchase any software and equipment for that purpose, I would love to hear any recommendations.

Again, thank you and the rest of the group for helping me get over what I'm sure is my first hurdle.  :)

Jeff

--
Mounts: EXOS-II GS, PMC-Eight
Cameras:  ZWO ASI 290MC, Canon 7D
Scope: ES-ED0806-01 (Backordered)
Software: ExploreStars (iPad)


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Wes Mcdonald
 

Michael

1.  What version of firmware are you using.  It’s important to know to help you.


2.  Your IP address are messed up.   The pc up address must be 192.168.47.11 for WiFi connection to work

3.  The gateway address must be 192.168.47.1

4.  The pmc8 will only communicate over 47.11.  But it will assign ips to other devices that try to connect, all in sequence.   Thus all devices not your desired laptop or tablet must not connect wirelessly to the pmc8 , at least not before the desired device does.   That means that you might have to reboot the pmc8 to clear its connection table if the wrong device connects first.  Also if you reboot your pc you probably should reboot the pmc8 also.


I don’t know what you are trying to do.  Please read my post on upgrading to the new firmware and do so if you have not.  If you have done so then you do not need to be using the Configuration manager which is basically a PITA when it comes to connecting.  Use the UFCT.

Wes


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Micheal
 

Michael

   When I go back to connection setting from advance tab I always do a Refresh or when I push the find current connection it doesn't work.

On 10/16/2021 12:43 PM, Michael Lunsford wrote:
Thank you! I couldn't see a "find connection" command in the Advanced tab, so I tried the command to switch to serial (after choosing serial as the communication method), but regardless of what command I send, it gets an empty response:

2       Mount appears to be connected on UDP
1       Received:
0       Sending via Serial: ESX!

For further testing, I tried the other communication methods on the advanced tab. TCP gave me an error and UDP seemed to create a loopback where it would say it "received" the command I just sent. Also note that the green "connection" light on the mount itself turns on and off intermittantly as I'm poking around in CM. Windows firewall and anti-virus are disabled. The loopback on UDP makes it feel like an IP issue, so here's the IP config when I'm connected to the PMC Eight network:

Windows IP Configuration


Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::911c:4198:c767:1b9c%17
   IPv4 Address. . . . . . . . . . . : 192.168.57.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::d3c:eb9:c79f:943%8
   IPv4 Address. . . . . . . . . . . : 192.168.47.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::408f:bd3c:8252:b750%7
   IPv4 Address. . . . . . . . . . . : 192.168.47.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.47.1

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

On Sat, Oct 16, 2021 at 9:17 AM Micheal <mpreston182p@...> wrote:

Michael

Just reviewed your steps

I would make sure all the connection are made to the mount and computor before you power the mount on.

Then In Configuration Manager  make sure COM port selected. After your Step 6  go to the advance tab and make sure serial is selected then send the command to find the connection method, should get message mount appear to be connected on serial. Go back to connection tab and click on "do It" for Serial.  Hope this helps.

Micheal


On 10/15/2021 10:39 PM, michael.lunsford80@... wrote:
Sorry for the necro, let me know if I should start a new thread. I've owned the IEXOS-100 mount for a few months now and I've been using it with the ExploreStars app on my tablet. I'd really like to try connecting it via ASCOM, but I keep hitting a brick wall. Here's my steps:
  1. Plug in mount (red light comes on)
  2. Connect to mount WIFI from laptop
  3. Connect USB cable from laptop to mount
  4. Start Configuration Manager (Wifi indicator green, mount connection red)
  5. Change mount type to IEXOS-100
  6. Change COM port to 7 (as indicated by "Find")
  7. Click Find Currenction Connection (Connection method goes Green, says UDP)
  8. "Via Wireless ASCOM (TCP)" becomes enabled, Serial/UDP both disabled
  9. Click Do It next to TCP, it disconnects and reconnects wifi, both indicators go green, says I'm on mount Wifi and connected via TCP and Serial/TCP "Do It" buttons enable
  10. If I click "Do It" for Serial, it says the mount is busy
  11. If I click "Do It" next to Find Current Connection, it says I'm really connected to UDP, not TCP
I'm sure it's a PC issue, but I can't figure out what it is. It's about a 5 year old Dell laptop.


Re: EXOS2-GT Mount auto meridian flip #astrophotography

Micheal
 

Jennifer

   Thanks for the feed back. I moved it around by hand and didn't see any problem but wasn't sure if I was creating other problems.

Thanks Jennifer and clear skies

Micheal

On 10/16/2021 10:40 AM, Jennifer Shelly via groups.io wrote:
Michael:

I have noticed the same same thing with the Exos-2 and there is nothing wrong with what you are doing.  I have done the same thing in the past.
--
Sincerely,

Jennifer Shelly
AstroPorch, VA

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


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Michael Lunsford
 

Thank you! I couldn't see a "find connection" command in the Advanced tab, so I tried the command to switch to serial (after choosing serial as the communication method), but regardless of what command I send, it gets an empty response:

2       Mount appears to be connected on UDP
1       Received:
0       Sending via Serial: ESX!

For further testing, I tried the other communication methods on the advanced tab. TCP gave me an error and UDP seemed to create a loopback where it would say it "received" the command I just sent. Also note that the green "connection" light on the mount itself turns on and off intermittantly as I'm poking around in CM. Windows firewall and anti-virus are disabled. The loopback on UDP makes it feel like an IP issue, so here's the IP config when I'm connected to the PMC Eight network:

Windows IP Configuration


Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::911c:4198:c767:1b9c%17
   IPv4 Address. . . . . . . . . . . : 192.168.57.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::d3c:eb9:c79f:943%8
   IPv4 Address. . . . . . . . . . . : 192.168.47.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::408f:bd3c:8252:b750%7
   IPv4 Address. . . . . . . . . . . : 192.168.47.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.47.1

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :


On Sat, Oct 16, 2021 at 9:17 AM Micheal <mpreston182p@...> wrote:

Michael

Just reviewed your steps

I would make sure all the connection are made to the mount and computor before you power the mount on.

Then In Configuration Manager  make sure COM port selected. After your Step 6  go to the advance tab and make sure serial is selected then send the command to find the connection method, should get message mount appear to be connected on serial. Go back to connection tab and click on "do It" for Serial.  Hope this helps.

Micheal


On 10/15/2021 10:39 PM, michael.lunsford80@... wrote:
Sorry for the necro, let me know if I should start a new thread. I've owned the IEXOS-100 mount for a few months now and I've been using it with the ExploreStars app on my tablet. I'd really like to try connecting it via ASCOM, but I keep hitting a brick wall. Here's my steps:
  1. Plug in mount (red light comes on)
  2. Connect to mount WIFI from laptop
  3. Connect USB cable from laptop to mount
  4. Start Configuration Manager (Wifi indicator green, mount connection red)
  5. Change mount type to IEXOS-100
  6. Change COM port to 7 (as indicated by "Find")
  7. Click Find Currenction Connection (Connection method goes Green, says UDP)
  8. "Via Wireless ASCOM (TCP)" becomes enabled, Serial/UDP both disabled
  9. Click Do It next to TCP, it disconnects and reconnects wifi, both indicators go green, says I'm on mount Wifi and connected via TCP and Serial/TCP "Do It" buttons enable
  10. If I click "Do It" for Serial, it says the mount is busy
  11. If I click "Do It" next to Find Current Connection, it says I'm really connected to UDP, not TCP
I'm sure it's a PC issue, but I can't figure out what it is. It's about a 5 year old Dell laptop.


Re: EXOS2-GT Mount auto meridian flip #astrophotography

Jennifer Shelly
 

Michael:

I have noticed the same same thing with the Exos-2 and there is nothing wrong with what you are doing.  I have done the same thing in the past.
--
Sincerely,

Jennifer Shelly
AstroPorch, VA

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


Re: Struggling with firmware update #FIRMWARE

Wes Mcdonald
 

Michael

Ok that’s great.  Others have also reported the stop button on the poth does not work.   I keep meaning to look into it  it somehow always do something else🥴

So I think you told us the hub stop button works.   

Ok thanks.  I’ll try to see why poth isn’t stopping, but if it isn’t sending a date command there isn’t anything that we can do about it.  I wonder what would have changed between ascom versions?

Wes




--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Struggling with firmware update #FIRMWARE

Micheal
 

Wes

  I was using Poth under ASCOM 6.4 until two week ago. In updating all my Software accept ASCOM, Poth stop button stopped working. I would push direction button in CDC it would just go for every and not stop. Sharpcap, Apt, and Phd2 mount controls all seem to work fine Phd3 wouldn't always display stars after using Sharpcap. I then updated to ASCOM6.5 sp1 and same thing with Poth. I just changed it over to Device HUB and everything seem to be working as before all the updates when testing indoors do to clouds. The next couple night looking good so will have a chance to try it under the stars.

Micheal

IExos-100 and EXOS 2GT both running PMC-Eight version 20A01.1
Svbony 503 80MM f7 w/ Orion 0.8 field flattener
Celestron 150mm C6n f7 w/motor focuser w/ FCUSB Motor Controller
Cameras Canon T7, ZWO 224, ZWO 120mm ,ZWO 120 MC
Svbony 50 mm guide scope on 80mm Scope
Svbony 60 mm guide Scope on 150 mm Scope
On order DewBuster controller
ASCOM 6.5 with Poth. Cartes Du Ciel for mount control, SharpCap for
Polar alignment and planetary photos
Astro Photography Tool, platesolve2, PHD2 for guiding, and Stellarium
for object framing only.

On 10/16/2021 9:18 AM, Wes Mcdonald wrote:
TJB

Hub does.   Heck Jerry has used it all along.   I also have tested it and use it during development of firmware changes.  

It has a slower inquiry rate to the mount for position than Poth has.  This used to flub the watchdog time out in the firmware which would stop the mount from tracking.  The new firmware addresses this in two ways, one by increasing the watchdog time out significantly, and the second by allowing you configure the mount to continue tracking in the face of lost comms, obviating and concern for what the query rate is for an app.   

Anyhow it seems fine now.  I would interested in hearing if others are using the hub with the 20A01.1  code version and what their experience is.

Wes


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Wes Mcdonald
 

Michael

I would suggest you load the newest firmware 20A01.1.  It has simultaneous WiFi and serial connectivity.  After you load it and configure it using the new firmware configuration tool (UFCT) (not the old configuration manager) you can just plug in the serial port and boot poth etc for ascom.  Load the firmware using the advanced or firmware tab on the olde configuration manager, then configure it and you will be good to go.

The new UFCT makes all the other setting s a snap to manipulate once you load the new firmware.   Really this is a huge step up in ease of use and you should go with it.

Download the installation pack from the pmc8 software page in the Es web site, unzip it and do the steps instructed in the pdf doc included in the install pack.   Note you will also get a new ascom driver that works with the new firmware.  Please read and follow the instructions and your upgrade should go fine.



Wes


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: Struggling with firmware update #FIRMWARE

Wes Mcdonald
 

TJB

Hub does.   Heck Jerry has used it all along.   I also have tested it and use it during development of firmware changes.  

It has a slower inquiry rate to the mount for position than Poth has.  This used to flub the watchdog time out in the firmware which would stop the mount from tracking.  The new firmware addresses this in two ways, one by increasing the watchdog time out significantly, and the second by allowing you configure the mount to continue tracking in the face of lost comms, obviating and concern for what the query rate is for an app.   

Anyhow it seems fine now.  I would interested in hearing if others are using the hub with the 20A01.1  code version and what their experience is.

Wes


--
Wes, Southport NC
EXos2-GT PMC-8, iExos 100, ESG11
ES ED 127+MoonLite Focuser, 10" LX200GPS+ MoonLite focuser+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, ASI071 cooled OSC, ASI MM290 guide camera
Nina, Bootcamped Mac Mini control computer, RDP to iMAC
110 amp hour lead acid deep discharge battery for field power
Electrical Engineer, Retired


Re: One beginner's guide to getting EXOS2/PMC8 fully operational with ASCOM, Stellarium, SharpCap, ASPS, and ASCOMPAD

Micheal
 

Michael

Just reviewed your steps

I would make sure all the connection are made to the mount and computor before you power the mount on.

Then In Configuration Manager  make sure COM port selected. After your Step 6  go to the advance tab and make sure serial is selected then send the command to find the connection method, should get message mount appear to be connected on serial. Go back to connection tab and click on "do It" for Serial.  Hope this helps.

Micheal


On 10/15/2021 10:39 PM, michael.lunsford80@... wrote:
Sorry for the necro, let me know if I should start a new thread. I've owned the IEXOS-100 mount for a few months now and I've been using it with the ExploreStars app on my tablet. I'd really like to try connecting it via ASCOM, but I keep hitting a brick wall. Here's my steps:
  1. Plug in mount (red light comes on)
  2. Connect to mount WIFI from laptop
  3. Connect USB cable from laptop to mount
  4. Start Configuration Manager (Wifi indicator green, mount connection red)
  5. Change mount type to IEXOS-100
  6. Change COM port to 7 (as indicated by "Find")
  7. Click Find Currenction Connection (Connection method goes Green, says UDP)
  8. "Via Wireless ASCOM (TCP)" becomes enabled, Serial/UDP both disabled
  9. Click Do It next to TCP, it disconnects and reconnects wifi, both indicators go green, says I'm on mount Wifi and connected via TCP and Serial/TCP "Do It" buttons enable
  10. If I click "Do It" for Serial, it says the mount is busy
  11. If I click "Do It" next to Find Current Connection, it says I'm really connected to UDP, not TCP
I'm sure it's a PC issue, but I can't figure out what it is. It's about a 5 year old Dell laptop.

581 - 600 of 11143