Date   

Re: Mount not working with PHD2 #pmc-eight #ASCOM #EXOS2 #astrophotography

Vlad Gherman
 

Hey Bob,

I've bought a serial to USB cable. I intend to use it tonight. Hopefully this will improve my experience.

Thank you for the advice!

Cheers,

Vlad


Re: EXplorestars and Android version 10

Tyler Bowman - Explore Scientific Customer Service
 

Hey Brian, can you send to me please that way I make sure I get this handled really quick. 
--

1458310636860_logo.png

 

Tyler Bowman - Customer Service

Office   +1(866) 252-3811 Ext: 516

Fax        +1(479) 717-2898


Re: EXplorestars and Android version 10

brian skinner
 


-Hi Tyler, thankyou. Ill send you a copy of my mail to Dan sent this morning. It contains the photos he requested. I'll send to your customer services address.
Thankyou, Brian-
Brian Skinner
iEXOS100
Canon 1300d dslr
Various lenses
ES Polar scope
Sequator image stacker
PIXR image editor


Re: Mount not working with PHD2 #pmc-eight #ASCOM #EXOS2 #astrophotography

 

Vlad,

No need look at the logs.  Wireless is convenient for visual users, but for astrophotography users, it's a "siren song", best avoided.

I'd suggest that you get a serial-usb cable with an FTDI chip, and go serial between the laptop and mount.

When you are guiding, you are constructing a near-real-time, closed-loop control system. 

Which is better, to include a communication layer in that loop that can have packet dropouts, latency, and even outright drops, or to use a high speed cable that is very reliable? Lots of posts on that here.

The visual user will seldom notice small reliability issues from wireless, but someone trying to guide, probably will.  You may find examples of people who have made wireless guiding work (there is one I know of), but they will be exceptions. 

Wireless for convenience, but cable for reliability when guiding.

Hope this helps! 

- Bob


On Thu, Mar 25, 2021, at 16:41, Vlad Gherman wrote:
Hello everyone,
 
I've started astrophotography in September last year with the following setup: 
 
Telescope: WO ZS 61
Mount: EXOS-2 PMC8 (wireless connection to the laptop)
Camera: ASI1600MM Pro
Software: APT/N.I.N.A
 
Had no problem with this equipment, taking mostly 60s subs (rarely 90s with round stars) without guiding.
 
So...heading to the problem...
 
Recently bought an ASI120mm camera with an Artesky guidescope. On the first night with this setup, I've managed to take approx. 5x300s in N.I.N.A. After that my mount got suddenly disconnected and then PHD2 never worked properly.
 
I'm struggling for more than 2 weeks...
 
Having the following issues on different nights:
 
1. PHD2 error messages:
- pulse guide command to mount has failed
- RA calibration failed star did not move enough
- PHD2 is not able to make sufficient corrections in RA
- PulseGuide command to mount has failed - guiding is likely to be ineffective
- Although I start calibration within +/- 10 degrees of celestial equator I get the following message: "Calibration this far from the celestial equator will be error prone. For best results calibrate at a declination of -20 to +20."
 
 2. The most recent one that happened 2 nights in a row without any error messages is that PHD2 loops infinitely when I start calibration. 
 
Tried the following "fixes":
- increasing calibration steps in PHD2
- using another USB Type-C cable (tried connecting guide camera to imaging camera and also tried connecting guide camera directly to the laptop)
- tried different USB slots
- rebalancing
- reinstalling all the software (ASCOM drivers, PHD2, N.I.N.A, APT, ZWO drivers)
 
I'm hopeless...
 
You can find my last PHD2 logs in the attachment.
 
Not sure if this is a mount issue that doesn't receive commands or a PHD2 issue.
I'm opened to any ideas, suggestions. 
 
Thank you in advance!
 
Cheers,
Vlad 

Attachments:
  • PHD2_DebugLog_2021-03-24_201800.txt
  • PHD2_GuideLog_2021-03-24_201800.txt


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


Re: Mount not working with PHD2 #pmc-eight #ASCOM #EXOS2 #astrophotography

Sebastian
 

What version of Nina and Phd2 do you ? Do you use an Ascom hub to guide with Nina and Phd2 at the same time ? Did you read the Phd2 troubleshoot manual from one of the developers ? 


Re: EXplorestars and Android version 10

Tyler Bowman - Explore Scientific Customer Service
 

Brian, if you could also provide me a email with this information id greatly appreciate it. 

I would like a screenshot of the settings page, the app permissions page, and a screenshot of the SD card opened in a program that displays its location. A program like X-plore.

--

1458310636860_logo.png

 

Tyler Bowman - Customer Service

Office   +1(866) 252-3811 Ext: 516

Fax        +1(479) 717-2898


Mount not working with PHD2 #pmc-eight #ASCOM #EXOS2 #astrophotography

Vlad Gherman
 

Hello everyone,
 
I've started astrophotography in September last year with the following setup: 
 
Telescope: WO ZS 61
Mount: EXOS-2 PMC8 (wireless connection to the laptop)
Camera: ASI1600MM Pro
Software: APT/N.I.N.A
 
Had no problem with this equipment, taking mostly 60s subs (rarely 90s with round stars) without guiding.
 
So...heading to the problem...
 
Recently bought an ASI120mm camera with an Artesky guidescope. On the first night with this setup, I've managed to take approx. 5x300s in N.I.N.A. After that my mount got suddenly disconnected and then PHD2 never worked properly.
 
I'm struggling for more than 2 weeks...
 
Having the following issues on different nights:
 
1. PHD2 error messages:
- pulse guide command to mount has failed
- RA calibration failed star did not move enough
- PHD2 is not able to make sufficient corrections in RA
- PulseGuide command to mount has failed - guiding is likely to be ineffective
- Although I start calibration within +/- 10 degrees of celestial equator I get the following message: "Calibration this far from the celestial equator will be error prone. For best results calibrate at a declination of -20 to +20."
 
 2. The most recent one that happened 2 nights in a row without any error messages is that PHD2 loops infinitely when I start calibration. 
 
Tried the following "fixes":
- increasing calibration steps in PHD2
- using another USB Type-C cable (tried connecting guide camera to imaging camera and also tried connecting guide camera directly to the laptop)
- tried different USB slots
- rebalancing
- reinstalling all the software (ASCOM drivers, PHD2, N.I.N.A, APT, ZWO drivers)
 
I'm hopeless...
 
You can find my last PHD2 logs in the attachment.
 
Not sure if this is a mount issue that doesn't receive commands or a PHD2 issue.
I'm opened to any ideas, suggestions. 
 
Thank you in advance!
 
Cheers,
Vlad 


Re: Problem Exos 2 - Small component, big impact #EXOS2

Wes Mcdonald
 

Once I get them and evaluate I will post.  I believe someone else posted some time ago.

Wes


On Thu, Mar 25, 2021 at 12:14 PM Walter Vinci <wltvinci@...> wrote:
Thanks for sharing!

Would it be possible to share the specs and from where you order these replacements? It would be good as a reference for an upgrade I might try myself in the future.

Walter

On Mar 25, 2021, at 8:29 AM, Wes Mcdonald <wesmcd6@...> wrote:


Thanks Carsten!

I just ordered ceramic bearings myself.  Also some thrust bearings, which I fear will not be so good, as they have poor nn-axial load capability.  

Wes

On Thu, Mar 25, 2021 at 8:40 AM Akhet <garbage.t@...> wrote:
Since my English in speaking and writing is rather poor due to a lack of practice, I recorded the text in German and then sent it through the Google Translator. Please forgive me.
 
First of all thanks to Robert Hoskin for his document "Notes on Tuning the EXOS-2 / PMC8 Mount Hardware". It helped me a lot in solving my problem.
 
I would like to write to you here where the problem was with me and how I could solve it. Maybe it will help one or the other with their problems.
 
In my attempts to get the backlash of my RA axis under control, I tried various tips that I found on the Internet. With the result that my guiding got worse and worse. Until it finally looked like this two days ago.
<8B0868D1-6C89-4ADE-980A-EE4AC93BBCF2.jpeg>
Calibration
<7882B30E-439D-40EC-8FF0-CD11C650F80D.jpeg>

I also noticed the following error patterns.
1. Visible oscillation of the RA axis on the star. From east to west and back to east within 20 seconds.
2. With manual control of the RA axis on the star and a short impulse to the east, the RA axis moves visibly to the west. With long impulses to the east, the RA axis moves to the east. But immediately afterwards a short impulse to the east leads to a movement to the west again.
 
Quite frustrated, I went to look for a solution again and then found Robert's document. So everything was done as described and ... no improvement. Damn.
But paragraph 7.3 got me on the track. After disassembling the worm block I could see that the ball bearings are defective. I then used suitable ball bearings (6x12x4mm) from Carson (RC Cars) as spare parts and reassembled everything. Yesterday evening with a very dense high cloud cover then another test and the result now looks like this.
<D99FB077-C2AA-426A-B072-859545BDE539.jpeg>
Calibration
<9B747EBD-79B7-482A-B988-B513F47D4510.jpeg>

Apparently the periodic error has also decreased by replacing the ball bearings. Presumably the axis of the worm was not centered due to the defect in the ball bearings.
 
Above before below after replacing the ball bearings. The data from the picture above is from a month ago so I tried before my first adjustment.
<3397A2D8-3128-4339-A0B9-F5C8321CB820.jpeg>
I am very happy that it is now working again and I can now fine-tune it.
 
I hope the post will help others solve similar problems.
 
Greetings Carsten


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

--
———

Walter Vinci

ES EXOS2-GT PMC-Eight
ES ED80
Starfield 0.8 Field Flattener/Reducer.
ZWO ASI290mm-mini & Orion 50mm Guide Scope
Canon EOS Rebel SL1
SharpCap, APT, PHD2, SiriL, Stellarium


--
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: Problem Exos 2 - Small component, big impact #EXOS2

Walter Vinci
 

Thanks for sharing!

Would it be possible to share the specs and from where you order these replacements? It would be good as a reference for an upgrade I might try myself in the future.

Walter

On Mar 25, 2021, at 8:29 AM, Wes Mcdonald <wesmcd6@...> wrote:


Thanks Carsten!

I just ordered ceramic bearings myself.  Also some thrust bearings, which I fear will not be so good, as they have poor nn-axial load capability.  

Wes

On Thu, Mar 25, 2021 at 8:40 AM Akhet <garbage.t@...> wrote:
Since my English in speaking and writing is rather poor due to a lack of practice, I recorded the text in German and then sent it through the Google Translator. Please forgive me.
 
First of all thanks to Robert Hoskin for his document "Notes on Tuning the EXOS-2 / PMC8 Mount Hardware". It helped me a lot in solving my problem.
 
I would like to write to you here where the problem was with me and how I could solve it. Maybe it will help one or the other with their problems.
 
In my attempts to get the backlash of my RA axis under control, I tried various tips that I found on the Internet. With the result that my guiding got worse and worse. Until it finally looked like this two days ago.
<8B0868D1-6C89-4ADE-980A-EE4AC93BBCF2.jpeg>
Calibration
<7882B30E-439D-40EC-8FF0-CD11C650F80D.jpeg>

I also noticed the following error patterns.
1. Visible oscillation of the RA axis on the star. From east to west and back to east within 20 seconds.
2. With manual control of the RA axis on the star and a short impulse to the east, the RA axis moves visibly to the west. With long impulses to the east, the RA axis moves to the east. But immediately afterwards a short impulse to the east leads to a movement to the west again.
 
Quite frustrated, I went to look for a solution again and then found Robert's document. So everything was done as described and ... no improvement. Damn.
But paragraph 7.3 got me on the track. After disassembling the worm block I could see that the ball bearings are defective. I then used suitable ball bearings (6x12x4mm) from Carson (RC Cars) as spare parts and reassembled everything. Yesterday evening with a very dense high cloud cover then another test and the result now looks like this.
<D99FB077-C2AA-426A-B072-859545BDE539.jpeg>
Calibration
<9B747EBD-79B7-482A-B988-B513F47D4510.jpeg>

Apparently the periodic error has also decreased by replacing the ball bearings. Presumably the axis of the worm was not centered due to the defect in the ball bearings.
 
Above before below after replacing the ball bearings. The data from the picture above is from a month ago so I tried before my first adjustment.
<3397A2D8-3128-4339-A0B9-F5C8321CB820.jpeg>
I am very happy that it is now working again and I can now fine-tune it.
 
I hope the post will help others solve similar problems.
 
Greetings Carsten


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

--
———

Walter Vinci

ES EXOS2-GT PMC-Eight
ES ED80
Starfield 0.8 Field Flattener/Reducer.
ZWO ASI290mm-mini & Orion 50mm Guide Scope
Canon EOS Rebel SL1
SharpCap, APT, PHD2, SiriL, Stellarium


Re: Problem Exos 2 - Small component, big impact #EXOS2

Wes Mcdonald
 

Thanks Carsten!

I just ordered ceramic bearings myself.  Also some thrust bearings, which I fear will not be so good, as they have poor nn-axial load capability.  

Wes

On Thu, Mar 25, 2021 at 8:40 AM Akhet <garbage.t@...> wrote:
Since my English in speaking and writing is rather poor due to a lack of practice, I recorded the text in German and then sent it through the Google Translator. Please forgive me.
 
First of all thanks to Robert Hoskin for his document "Notes on Tuning the EXOS-2 / PMC8 Mount Hardware". It helped me a lot in solving my problem.
 
I would like to write to you here where the problem was with me and how I could solve it. Maybe it will help one or the other with their problems.
 
In my attempts to get the backlash of my RA axis under control, I tried various tips that I found on the Internet. With the result that my guiding got worse and worse. Until it finally looked like this two days ago.
Calibration

I also noticed the following error patterns.
1. Visible oscillation of the RA axis on the star. From east to west and back to east within 20 seconds.
2. With manual control of the RA axis on the star and a short impulse to the east, the RA axis moves visibly to the west. With long impulses to the east, the RA axis moves to the east. But immediately afterwards a short impulse to the east leads to a movement to the west again.
 
Quite frustrated, I went to look for a solution again and then found Robert's document. So everything was done as described and ... no improvement. Damn.
But paragraph 7.3 got me on the track. After disassembling the worm block I could see that the ball bearings are defective. I then used suitable ball bearings (6x12x4mm) from Carson (RC Cars) as spare parts and reassembled everything. Yesterday evening with a very dense high cloud cover then another test and the result now looks like this.
Calibration

Apparently the periodic error has also decreased by replacing the ball bearings. Presumably the axis of the worm was not centered due to the defect in the ball bearings.
 
Above before below after replacing the ball bearings. The data from the picture above is from a month ago so I tried before my first adjustment.
I am very happy that it is now working again and I can now fine-tune it.
 
I hope the post will help others solve similar problems.
 
Greetings Carsten


--
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: Problem Exos 2 - Small component, big impact #EXOS2

 

Carsten,

You're most welcome - glad you were helped!

- Bob

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


Problem Exos 2 - Small component, big impact #EXOS2

Akhet
 

Since my English in speaking and writing is rather poor due to a lack of practice, I recorded the text in German and then sent it through the Google Translator. Please forgive me.
 
First of all thanks to Robert Hoskin for his document "Notes on Tuning the EXOS-2 / PMC8 Mount Hardware". It helped me a lot in solving my problem.
 
I would like to write to you here where the problem was with me and how I could solve it. Maybe it will help one or the other with their problems.
 
In my attempts to get the backlash of my RA axis under control, I tried various tips that I found on the Internet. With the result that my guiding got worse and worse. Until it finally looked like this two days ago.
Calibration

I also noticed the following error patterns.
1. Visible oscillation of the RA axis on the star. From east to west and back to east within 20 seconds.
2. With manual control of the RA axis on the star and a short impulse to the east, the RA axis moves visibly to the west. With long impulses to the east, the RA axis moves to the east. But immediately afterwards a short impulse to the east leads to a movement to the west again.
 
Quite frustrated, I went to look for a solution again and then found Robert's document. So everything was done as described and ... no improvement. Damn.
But paragraph 7.3 got me on the track. After disassembling the worm block I could see that the ball bearings are defective. I then used suitable ball bearings (6x12x4mm) from Carson (RC Cars) as spare parts and reassembled everything. Yesterday evening with a very dense high cloud cover then another test and the result now looks like this.
Calibration

Apparently the periodic error has also decreased by replacing the ball bearings. Presumably the axis of the worm was not centered due to the defect in the ball bearings.
 
Above before below after replacing the ball bearings. The data from the picture above is from a month ago so I tried before my first adjustment.
I am very happy that it is now working again and I can now fine-tune it.
 
I hope the post will help others solve similar problems.
 
Greetings Carsten


Re: EXplorestars and Android version 10

Tyler Bowman - Explore Scientific Customer Service
 

Here is something that could help Brian and anyone else having an issue let me know if this fixes the issue.

Here is the process that I have used to make sure that everything is mounted correctly: (I am not sure exactly which step actually fixes the problem.)

 

  1. Force stop ExploreStars
  2. Clear the cache and storage
  3. Uninstall ExploreStars
  4. Unmount and physically remove the SD card
  5. Reinstall the SD card
  6. Check that the files are accessible (Open one of the ExploreStars images in a File Explorer App)
  7. Install ExploreStars
  8. Enable the Location and Storage permissions
  9. Start ExploreStars (You may need to do this twice, sometimes it does not acknowledge the permissions the first time.)
  10. Check the Data location in ExploreStars. It can be found on the “Settings Page”. It should be something like “Data: /storage/F8B6-6D59/ExploreStars/” This should correspond to the SD card found by your file explorer app
--

1458310636860_logo.png

 

Tyler Bowman - Customer Service

Office   +1(866) 252-3811 Ext: 516

Fax        +1(479) 717-2898


Re: EXplorestars and Android version 10

Wes Mcdonald
 

Patrick

This is a new bump in the road which is temporary I expect.  But I will also say the iPad version is great too.  So far no such issues.

Appreciate the feedback in this.  Something is amiss.

Wes



On Wed, Mar 24, 2021 at 1:27 PM Patrick Maher via groups.io <pwmaher=yahoo.com@groups.io> wrote:
I didn't want to go the Android route but with the updated Android version of ExploreStars and because everyone claims it works great on a cheap Android tablet, I went out and purchased a cheap Lenovo Tab M8 with Android 10.  I've spent hours trying to get the tablet to recognize the SQLite file to no avail.  I've formatted the card every which way, installed the database and sqlite file every which way...  still nothing.  I've tried every way that has been described in a few posts here in this group and no method resulted in success.

If I format the SD card in my tablet, no matter which way I choose to format it, Windows cannot/won't copy files to the card.  If I format the SD card in Windows, I can copy the necessary folder (unzipped) to the card but then I get the sqlite failure when I open ExploreStars.  And, yes, I've mounted the card and allowed the necessary permissions in the Android settings.  

Everything else on the tablet works as expected even Skysafari, Stellarium, Skeye, and I tried Synscan Pro.  I know the tablet is fine.

I had planned to purchase an EXOS2-GT PMC-8 as an upgrade to my EXOS2-GT but, t this point, I'm just going to cut my losses and instead upgrade to a new Synscan mount and put this stuff behind me.

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


--
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: EXplorestars and Android version 10

Patrick Maher
 

I didn't want to go the Android route but with the updated Android version of ExploreStars and because everyone claims it works great on a cheap Android tablet, I went out and purchased a cheap Lenovo Tab M8 with Android 10.  I've spent hours trying to get the tablet to recognize the SQLite file to no avail.  I've formatted the card every which way, installed the database and sqlite file every which way...  still nothing.  I've tried every way that has been described in a few posts here in this group and no method resulted in success.

If I format the SD card in my tablet, no matter which way I choose to format it, Windows cannot/won't copy files to the card.  If I format the SD card in Windows, I can copy the necessary folder (unzipped) to the card but then I get the sqlite failure when I open ExploreStars.  And, yes, I've mounted the card and allowed the necessary permissions in the Android settings.  

Everything else on the tablet works as expected even Skysafari, Stellarium, Skeye, and I tried Synscan Pro.  I know the tablet is fine.

I had planned to purchase an EXOS2-GT PMC-8 as an upgrade to my EXOS2-GT but, t this point, I'm just going to cut my losses and instead upgrade to a new Synscan mount and put this stuff behind me.

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


Re: Sqlite failure message

Aaron Thompson
 

Hello Brian, 

Honestly I am not sure what it is that is causing your problem and the app to not work. What I was trying to do was to remove any " Weird or unknown " glitches from my tests.  To start from complete scratch in a way that makes darn sure that there was nothing missed or some other piece of software that became part of the problem.  To remove all guessing. 

I agree that this is a bit extreme for those that have lots of other stuff on their tablet that they do not want to lose.  I back up my tablet often; all of my content is on a desktop as well. With this in mind I could just open the settings, i went to backup and reset, and pulled the trigger!  :-)   NOTE: the Factory reset does not wipe your SD Card. I deleted the ExploreStars Database folder before I ran the factory reset.  I then redownloaded the Database files just to make sure that what i was using were the same as what you have access to. 

My tests did not use a tablet that is as new as yours. I could not figure out what the source of your issue is.   When I run into this kind of problem the "nuclear" option becomes a path that is actually less work and pain then the error checking.  Trying to be sherlock homes is exhausting.   LOL 

After I setup my email address with the tablet after the " Factory Reset "  I went straight onto the play store and downloaded the app and ran it.  Expecting the SQL error as the database was missing. I then killed the app from running and placed the Folder back on the SD card.  Reran the app and I was back in business.  This process took me about 15 minutes total.  Again I did not have to back up any other data. 

If the Catalogue works for you at this point remember to go into settings and set yourself up again!  :-)

Maybe this will help? Wish you luck. 

 

 

 

 


EXplorestars and Android version 10

Wes Mcdonald
 

Folks:

Is anyone using the latest Explorestars App release with Android 10?  If so is it trouble free?  Are there any issues?  Some have been reported but we are trying to establish if the reported issues are related to specific tablets or the combination of Android 10 and the new App.  

Also, is there anyone running Android 10 with the prior version of Explorestars?

Thanks,
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: Sqlite failure message

brian skinner
 

Hi Aaron, many thanks for this. Basically, as I understand it, you successfully got the latest app to open the latest database by doing a Tablet factory reset? How is this done please? It sounds extreme!
Kind regards, Brian
--
Brian Skinner
iEXOS100
Canon 1300d dslr
Various lenses
ES Polar scope
Sequator image stacker
PIXR image editor


Re: Sqlite failure message

Aaron Thompson
 

Hello, 

DB Verson of 2.3 [ 85643 ] 
is what displays for me on 2 different tablets.  I have factory reset both tablets and reinstalled explore stars on both apps. 
the tablets are as follows. 
Tab A sm-T350 android 7.1.1
Tab A sm-T113 android 4.4.4

I used the app on both devices before the ExploreStars Db was copied to their SD cards so I could get the same SQL error that Brian has been getting. 

I then used the PMC8 Configuration manager to download the SD card version of the database using the radio button, extracted the zip file, and then copied that database to each tablet. 

They both loaded and worked as expected.  All catalogue items did appear, I could the details for and slew to objects in any category. 

I did notice that the DB display on the about us page would show DB Ver 1.0 [0] until after I force closed the App and then restarted it. 

 

Issues like this can be very hard to track down. Hoping for the best. 

 

 

 

 


Re: Sqlite failure message

Wes Mcdonald
 

Brian

I am using 8.1

Look in security and make sure the application has access to the sd card.  Apparently every app has a separate security setting in Android.

Wes


On Tue, Mar 23, 2021 at 12:29 PM brian skinner <brianjimskinner@...> wrote:

---------- Forwarded message ---------
From: brian skinner <brianjimskinner@...>
Date: Tue, 23 Mar 2021, 08:45
Subject: Sqlite failure message
To: wes McDonald <wesmcd6@...>


Hi Wes, I have taken a photograph of the Sqlite file failure notice from my Android10 tablet which is showing the database as ver 1.0 (0). My older tablet lists the database as ver 2.3  (85643) which I guess is correct. Both tablets have the same updated app.
My older tablet app crashes if anything other than a solar object is selected, same as one of the other guys has reported.....
Thankyou, Brian

--
Brian Skinner
iEXOS100
Canon 1300d dslr
Various lenses
ES Polar scope
Sequator image stacker
PIXR image editor


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

541 - 560 of 9972