Date   

Re: AP driver V2 - getting runtime errors from Setup_Telescope

Ray Gralak
 

Well, that's odd because I have installed Windows 10 many times, including the exact version you mention, so I am guessing ASCOM 6.6 is installing a different version of one of those controls.

BTW, you should apply ALL updates to Windows 10, which may take a day or two for them to come through. Until then you should follow that link to the list of VB6 controls and check for duplicates using the Everything application. Multiple VB6 controls with different versions is the cause for the 50003 error.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
Sent: Thursday, February 17, 2022 10:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope

windows 10

On Thu, Feb 17, 2022 at 10:32 PM Ray Gralak <iogroups@...> wrote:


Which O/S did you install?

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 10:26 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> Hmm. I re-installed the OS then only ASCOM 6.6 and the AP driver. The same error is generated when I
start the
> Telescope Setup program.
>
>
> On Thu, Feb 17, 2022 at 8:53 PM David Fischer <dkn.fischer@...> wrote:
>
>
> Ray,
>
> I did not resolve the issue by deleting most of the programs on my computer. I will try the last few but
since
> these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to
be the
> solution.
>
> I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.
>
>
> I need to ask a stupid question: Is there some way for me to generate a list of all DLLs used by the AP
driver
> and then search the computer for other DLLs having the same name ?
>
> Is there some other procedure that can be recommended prior to completely wiping the OS ?
>
> Advice would be appreciated.
>
> - David F.
>
>
>
>
> On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:
>
>
> > Run-time error '50003': Unexpected error
>
> Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously
> installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You
could try
> uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.
>
> -Ray
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> > Sent: Thursday, February 17, 2022 4:41 PM
> > To: main@ap-gto.groups.io; David Fischer
> > Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
> >
> > On my new laptop I installed ASCOM 6.6 and the AP driver V2. This machine has Windows 10
with
> .NET 3.5
> > activated.
> >
> > When I tried to run Setup Telescope I get these errors:
> >
> > APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX
> component.
> >
> > Then after clearing that dialog box, another pops up:
> > Run-time error '50003': Unexpected error
> >
> > = = = =
> >
> > My other 2 laptops have had the AP driver successfully installed for a long time. I have not
seen this
> error on
> > either one.
> >
> > As a sanity check, I just downloaded and installed the same files on my desktop Windows 10
> machine. On it
> > the Setup Telescope installed and ran correctly with no errors.
> >
> > Could somebody please tell me what I've done wrong ?
> >
> >
>
>
>
>
>
>
>
>
>









Re: AP driver V2 - getting runtime errors from Setup_Telescope

David Fischer
 

more specifically 
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042


On Thu, Feb 17, 2022 at 10:34 PM David Fischer <dkn.fischer@...> wrote:
windows 10

On Thu, Feb 17, 2022 at 10:32 PM Ray Gralak <iogroups@...> wrote:
Which O/S did you install?

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 10:26 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> Hmm.  I re-installed the OS then only ASCOM 6.6 and the AP driver.  The same error is generated when I start the
> Telescope Setup program.
>
>
> On Thu, Feb 17, 2022 at 8:53 PM David Fischer <dkn.fischer@...> wrote:
>
>
>       Ray,
>
>       I did not resolve the issue by deleting most of the programs on my computer.  I will try the last few but since
> these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the
> solution.
>
>       I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.
>
>
>       I need to ask a stupid question:  Is there some way for me to generate a list of all DLLs used by the AP driver
> and then search the computer for other DLLs having the same name ?
>
>       Is there some other procedure that can be recommended prior to completely wiping the OS ?
>
>       Advice would be appreciated.
>
>       - David F.
>
>
>
>
>       On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:
>
>
>               > Run-time error '50003':  Unexpected error
>
>               Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously
> installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try
> uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.
>
>               -Ray
>
>               > -----Original Message-----
>               > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
>               > Sent: Thursday, February 17, 2022 4:41 PM
>               > To: main@ap-gto.groups.io; David Fischer
>               > Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>               >
>               > On my new laptop I installed ASCOM 6.6 and the AP driver V2.  This machine has Windows 10 with
> .NET 3.5
>               > activated.
>               >
>               > When I tried to run Setup Telescope I get these errors:
>               >
>               > APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX
> component.
>               >
>               > Then after clearing that dialog box, another pops up:
>               > Run-time error '50003':  Unexpected error
>               >
>               > = = = =
>               >
>               > My other 2 laptops have had the AP driver successfully installed for a long time.  I have not seen this
> error on
>               > either one.
>               >
>               > As a sanity check, I just downloaded and installed the same files on my desktop Windows 10
> machine.  On it
>               > the Setup Telescope installed and ran correctly with no errors.
>               >
>               > Could somebody please tell me what I've done wrong ?
>               >
>               >
>
>
>
>
>
>
>
>
>







Re: Fast question: APCC history

Ray Gralak
 

In 2009 there were no APCC licenses given out with mounts.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of michael mccann via groups.io
Sent: Thursday, February 17, 2022 7:14 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Fast question: APCC history

Yeah I was hoping there was APCC license related to this mount, but if the previous owner bought it in 2009, I don’t
believe APCC was even around, so there might not be any license to transfer. ( he can’t remember)
On Feb 17, 2022, at 20:10, Dale Ghent <daleg@...> wrote:

Chipping your CP3 with a V2 ROM will get you full functionality with APCC Pro, and that includes modeling. APCC
cannot work with any older version than that, so you're doing the right thing by upgrading it.

As for APCC history, Ray probably knows that quite well ;)

On Feb 17, 2022, at 22:03, michael mccann via groups.io <mmccawsprojects@...> wrote:

As in when did it first version was released to the Astro-physic mount owners. The earliest version I can find on
the internet was 2014. I bought a 2009 AP900, CP3GTO which doesn’t even have a USB Jack nor Ethernet (
where’s that guy playing the world’s smallest violin :) )

so two questions: which rs232 to usb cable works best? Is APCC much use here? I did order the V chip. The
one in there has a “Q” on it.


Cheers







Re: AP driver V2 - getting runtime errors from Setup_Telescope

David Fischer
 

windows 10


On Thu, Feb 17, 2022 at 10:32 PM Ray Gralak <iogroups@...> wrote:
Which O/S did you install?

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 10:26 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> Hmm.  I re-installed the OS then only ASCOM 6.6 and the AP driver.  The same error is generated when I start the
> Telescope Setup program.
>
>
> On Thu, Feb 17, 2022 at 8:53 PM David Fischer <dkn.fischer@...> wrote:
>
>
>       Ray,
>
>       I did not resolve the issue by deleting most of the programs on my computer.  I will try the last few but since
> these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the
> solution.
>
>       I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.
>
>
>       I need to ask a stupid question:  Is there some way for me to generate a list of all DLLs used by the AP driver
> and then search the computer for other DLLs having the same name ?
>
>       Is there some other procedure that can be recommended prior to completely wiping the OS ?
>
>       Advice would be appreciated.
>
>       - David F.
>
>
>
>
>       On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:
>
>
>               > Run-time error '50003':  Unexpected error
>
>               Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously
> installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try
> uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.
>
>               -Ray
>
>               > -----Original Message-----
>               > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
>               > Sent: Thursday, February 17, 2022 4:41 PM
>               > To: main@ap-gto.groups.io; David Fischer
>               > Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>               >
>               > On my new laptop I installed ASCOM 6.6 and the AP driver V2.  This machine has Windows 10 with
> .NET 3.5
>               > activated.
>               >
>               > When I tried to run Setup Telescope I get these errors:
>               >
>               > APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX
> component.
>               >
>               > Then after clearing that dialog box, another pops up:
>               > Run-time error '50003':  Unexpected error
>               >
>               > = = = =
>               >
>               > My other 2 laptops have had the AP driver successfully installed for a long time.  I have not seen this
> error on
>               > either one.
>               >
>               > As a sanity check, I just downloaded and installed the same files on my desktop Windows 10
> machine.  On it
>               > the Setup Telescope installed and ran correctly with no errors.
>               >
>               > Could somebody please tell me what I've done wrong ?
>               >
>               >
>
>
>
>
>
>
>
>
>







Re: AP driver V2 - getting runtime errors from Setup_Telescope

Ray Gralak
 

Which O/S did you install?

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
Sent: Thursday, February 17, 2022 10:26 PM
To: main@ap-gto.groups.io; David Fischer
Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope

Hmm. I re-installed the OS then only ASCOM 6.6 and the AP driver. The same error is generated when I start the
Telescope Setup program.


On Thu, Feb 17, 2022 at 8:53 PM David Fischer <dkn.fischer@...> wrote:


Ray,

I did not resolve the issue by deleting most of the programs on my computer. I will try the last few but since
these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the
solution.

I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.


I need to ask a stupid question: Is there some way for me to generate a list of all DLLs used by the AP driver
and then search the computer for other DLLs having the same name ?

Is there some other procedure that can be recommended prior to completely wiping the OS ?

Advice would be appreciated.

- David F.




On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:


> Run-time error '50003': Unexpected error

Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously
installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try
uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 4:41 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> On my new laptop I installed ASCOM 6.6 and the AP driver V2. This machine has Windows 10 with
.NET 3.5
> activated.
>
> When I tried to run Setup Telescope I get these errors:
>
> APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX
component.
>
> Then after clearing that dialog box, another pops up:
> Run-time error '50003': Unexpected error
>
> = = = =
>
> My other 2 laptops have had the AP driver successfully installed for a long time. I have not seen this
error on
> either one.
>
> As a sanity check, I just downloaded and installed the same files on my desktop Windows 10
machine. On it
> the Setup Telescope installed and ran correctly with no errors.
>
> Could somebody please tell me what I've done wrong ?
>
>









Re: PEMPRO

Ray Gralak
 

Hi Luke,

As Brian said, the ZWO drivers are horribly inefficient memory hogs. A single 46MP image uses over 1GB of memory, which is over the limit for a 32-bit WinForms application like PEMPro. I've asked ZWO to take a look at making their driver more efficient but they don't seem to care. At some point there will be a 64-bit version of PEMPro, but that will come with its own issues, like requiring 64-bit drivers for all devices (some devices only have 32-bit drivers).

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Luke Dodd
Sent: Thursday, February 17, 2022 7:45 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] PEMPRO

Not sure this is the best place for this post, so I apologise in advance;


Had a frustrating time using PEMPRO for the very first time on my AP1200 GTO 3 last night.
Mount connected to PEMPRO without issue.

Unsure which camera / scope to use I tried an ASI2600MC with my AP refractor 1000mm f.l. Thinking a greater field
of view and F.L. may produce a better result.

I connected to the camera in PEMPRO via the Ascom driver for the camera. Ran calibration wizard which produced
the star trails image pop up screen. I clicked on the start /finish of 3 trails and moved on. Went to mount calibration
screen and PEMPRO would not download this image, received the error message as shown in attachment.

I then decided to try the enhanced PHD2 option. Ultimately gave up as PHD2 was not working with the 2600MC,
multiple issues, integration time would randomly change and the sensitivity of the camera didn’t make sense, every
image after looping revealed few stars to actually guide on, and the star intensity dropped significantly between
integrations.

In frustation swapped to my 60mm guidescope (360mm fl) and ASI178MC guide camera.

Again using the enhanced PHD2 option in PEMPRO failed to work. I constantly received “could not acquire
guidestar” error message, so I abandoned PHD2 enhanced.

I went back to the calibration wizard in PEMPRO. All went by the book from there. PEMPRO produced images from
the MC178 to allow the star trail image scale routine to work, then the mount calibration of directions worked first
time (using same field as the failed attempt in PHD2). Clicked acquire data and off I went, 7 worm cycles created a
PE curve, uploaded, tested, native 2.5 arcsec error reduced to about a virtually a flat graph.

If I had of used PEMPRO and the guidescope/MC178 to start with would have been super easy, absolutely a joy to
use. (maybe the lesson is there)

Obviuosly I am a first time user of PEMPRO I may have made a few mistakes. Anyone care to comment. Thanks


Re: Fast question: APCC history

michael mccann
 

Looks like the key alignment has something to do with dot above the V.  Ok.

thanks


Re: AP driver V2 - getting runtime errors from Setup_Telescope

David Fischer
 

Hmm.  I re-installed the OS then only ASCOM 6.6 and the AP driver.  The same error is generated when I start the Telescope Setup program.


On Thu, Feb 17, 2022 at 8:53 PM David Fischer <dkn.fischer@...> wrote:
Ray,

I did not resolve the issue by deleting most of the programs on my computer.  I will try the last few but since these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the solution.

I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.

I need to ask a stupid question:  Is there some way for me to generate a list of all DLLs used by the AP driver and then search the computer for other DLLs having the same name ?

Is there some other procedure that can be recommended prior to completely wiping the OS ?

Advice would be appreciated.

- David F.



On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:
> Run-time error '50003':  Unexpected error

Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 4:41 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> On my new laptop I installed ASCOM 6.6 and the AP driver V2.  This machine has Windows 10 with .NET 3.5
> activated.
>
> When I tried to run Setup Telescope I get these errors:
>
> APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX component.
>
> Then after clearing that dialog box, another pops up:
> Run-time error '50003':  Unexpected error
>
> = = = =
>
> My other 2 laptops have had the AP driver successfully installed for a long time.  I have not seen this error on
> either one.
>
> As a sanity check, I just downloaded and installed the same files on my desktop Windows 10 machine.  On it
> the Setup Telescope installed and ran correctly with no errors.
>
> Could somebody please tell me what I've done wrong ?
>
>







Re: AP driver V2 - getting runtime errors from Setup_Telescope

Ray Gralak
 

This link has a list of the VB6 DLLs that you can check for duplicates in your system using an app like "Everything" (https://www.voidtools.com/):

https://forums.malwarebytes.com/topic/104494-run-time-error-50003-fixed/

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
Sent: Thursday, February 17, 2022 8:54 PM
To: main@ap-gto.groups.io; David Fischer
Subject: Re: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope

Ray,

I did not resolve the issue by deleting most of the programs on my computer. I will try the last few but since these
are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the
solution.

I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.


I need to ask a stupid question: Is there some way for me to generate a list of all DLLs used by the AP driver and
then search the computer for other DLLs having the same name ?

Is there some other procedure that can be recommended prior to completely wiping the OS ?

Advice would be appreciated.

- David F.




On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:


> Run-time error '50003': Unexpected error

Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously installed
product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try
uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 4:41 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> On my new laptop I installed ASCOM 6.6 and the AP driver V2. This machine has Windows 10 with .NET
3.5
> activated.
>
> When I tried to run Setup Telescope I get these errors:
>
> APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX component.
>
> Then after clearing that dialog box, another pops up:
> Run-time error '50003': Unexpected error
>
> = = = =
>
> My other 2 laptops have had the AP driver successfully installed for a long time. I have not seen this error
on
> either one.
>
> As a sanity check, I just downloaded and installed the same files on my desktop Windows 10 machine. On
it
> the Setup Telescope installed and ran correctly with no errors.
>
> Could somebody please tell me what I've done wrong ?
>
>









Re: Fast question: APCC history

Jeffc
 

Ps.. here’s a couple photos of the transplant…

image1.jpeg

image2.jpeg

On Feb 17, 2022, at 8:14 PM, michael mccann via groups.io <mmccawsprojects@...> wrote:

Thanks Jeff 
I too am concerned about those “control flight into ground”, borrowing an FAA phrase.  Even though I got a great deal, I don’t have any extra to replace damaged equipment.  Thanks for sharing your experiences.  I’m glad the kit comes with a tool. I remember changing these sort of chips back in the 90s Cisco network eqpt , without a tool one could damage the socket carrier. I’ll just wait till the upgrades come. Maybe imaging by the next new moon. ( that or the clouds will come and I’ll really catch hell by my Astro neighbors)

Cheers 


On Feb 17, 2022, at 20:39, Jeffc <jeffcrilly@...> wrote:




On Thu, Feb 17, 2022 at 7:03 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

As in when did it first version was  released to the Astro-physic mount owners. The earliest version I can find on the internet was 2014.  I bought a 2009 AP900, CP3GTO which doesn’t even have a USB Jack nor Ethernet ( where’s that guy playing the world’s smallest violin   :) )

so two questions: which rs232 to usb cable works best? Is APCC much use here?  I did order the V chip. The one in there has a “Q” on it. 



I just replaced an L chip in a CP3 with a V2 chip.   (I have another CP3 mount and I'll probably update that one also.)

I take no responsibility for you replacement job.. however here's something I learned along the way:
1. When taking off the CP3 cover, use a plastic shim (like the ones for removing car dashboard parts), and lever the cover STRAIGHT UP.   Don't allow it to "hinge" against the front edge.
IIRC that cover has a machined part that goes straight down.  The one I had was a very tight fit.
2.  Read the instructions for removing the old chip.  A tool is supplied.   My concern was cracking the carrier.   I ended up doing some sort of contortion with my thumb and fingers such that I was not applying pressure to the carrier when prying the chip out.   Also... do a tiny bit at a time alternating on the two corners.   Read the instructions.

As for the USB cable...  I've used various (I think they have to be ftdi based).   Last time I got one I got this:  https://www.amazon.com/Tripp-Lite-Keyspan-High-Speed-USA-19HS/dp/B0000VYJRY/ref=sr_1_3?keywords=tripp+light+usb+to+serial&qid=1645154662&sprefix=triplight+USB%2Caps%2C137&sr=8-3

After using APCC with the Mach2, I think there is some value in APCC with the non-encoder mount.  

One thing I found out... after the upgrade... I tried APCC with the CP3 mount.   I also had a keypad attached.  (Used to do this all the time with the V2 driver.)
I'm not sure they play well together.   When I went to park the mount in park 4 (with the keypad), and the RA was off by about 30 degrees.
I havent RTFM , but perhaps there is something in there about not using the keypad simultaneously.  I dunno.   I just had it on APCC for one session.  Normally I use the keypad with that mount.
That said... the other minor concern I have about APCC and the non-encoder mount is the mount getting "lost", and resulting in an errant slew into the pier.   Probably me just being paranoid.

-jeff 


Re: Looking for GPS Device Recommendations for APCC

Jeffc
 

Fwiw.. I use one of these….  It seems to “just work”.
I bit pricey , but also has environmental sensors.  

https://www.tolgaastro.com/mgpbox.html

On Feb 17, 2022, at 9:29 PM, Ben Koltenbah <benjamin.e.c.koltenbah@...> wrote:

Thank you all for the great suggestions!  I will look into them.  I was fishing for products and software ideas, and I hauled in a good catch from you all!

I did not specify that I am anticipating occasions when I will be traveling and away from internet access.  Therefore, I'd prefer a device that can get me both the location and time sync.  I suppose my cell phone would also work for manual entry, however I also anticipate not always having cell signal.  (Question: can a cell phone still provide accurate GPS and time without a cellular connection?)

I'm fully aware, of course, that I would only need to fetch the location and time once at the beginning of a session.  I would not need to continuously update unless my mount were sliding down a mountain while crossing into a new time zone.  But, I'd likely lose polar alignment under those conditions anyway.

Thanks again!

Ben


Re: Looking for GPS Device Recommendations for APCC

Ben Koltenbah
 

Thank you all for the great suggestions!  I will look into them.  I was fishing for products and software ideas, and I hauled in a good catch from you all!

I did not specify that I am anticipating occasions when I will be traveling and away from internet access.  Therefore, I'd prefer a device that can get me both the location and time sync.  I suppose my cell phone would also work for manual entry, however I also anticipate not always having cell signal.  (Question: can a cell phone still provide accurate GPS and time without a cellular connection?)

I'm fully aware, of course, that I would only need to fetch the location and time once at the beginning of a session.  I would not need to continuously update unless my mount were sliding down a mountain while crossing into a new time zone.  But, I'd likely lose polar alignment under those conditions anyway.

Thanks again!

Ben


Re: AP driver V2 - getting runtime errors from Setup_Telescope

David Fischer
 

Ray,

I did not resolve the issue by deleting most of the programs on my computer.  I will try the last few but since these are widely used apps (MS Office, CCDSTACK, PixInsight, PHD2. I am not expecting their removal to be the solution.

I'm trying to avoid a complete re-installation of the OS if possible, holding that for last.

I need to ask a stupid question:  Is there some way for me to generate a list of all DLLs used by the AP driver and then search the computer for other DLLs having the same name ?

Is there some other procedure that can be recommended prior to completely wiping the OS ?

Advice would be appreciated.

- David F.



On Thu, Feb 17, 2022 at 5:38 PM Ray Gralak <iogroups@...> wrote:
> Run-time error '50003':  Unexpected error

Unfortunately that is a bad sign that you probably have mismatched DLLs because of a previously installed product on your computer. It may be difficult to fix as it is not something specific to the driver. You could try uninstalling other products one at a time and then reinstalling the driver, until you find the culprit application.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fischer
> Sent: Thursday, February 17, 2022 4:41 PM
> To: main@ap-gto.groups.io; David Fischer
> Subject: [ap-gto] AP driver V2 - getting runtime errors from Setup_Telescope
>
> On my new laptop I installed ASCOM 6.6 and the AP driver V2.  This machine has Windows 10 with .NET 3.5
> activated.
>
> When I tried to run Setup Telescope I get these errors:
>
> APSetup: Error when trying to create 'AstroPhysicsV@.Telescope': Cannot create ActiveX component.
>
> Then after clearing that dialog box, another pops up:
> Run-time error '50003':  Unexpected error
>
> = = = =
>
> My other 2 laptops have had the AP driver successfully installed for a long time.  I have not seen this error on
> either one.
>
> As a sanity check, I just downloaded and installed the same files on my desktop Windows 10 machine.  On it
> the Setup Telescope installed and ran correctly with no errors.
>
> Could somebody please tell me what I've done wrong ?
>
>







Re: PEMPRO

Emilio J. Robau, P.E.
 

Interesting,
After multiple failures, with my 900, I became suspicious of the camera.   I actually just alter the download speed and funny as it seems I have actually pumped it up to get it to work as well as set it at the lowest setting.   I am not quite ready to buy the cord as the issue because my cord is high quality USB3 and pretty short, say 6 ft.   Not too short but certainly not near the aleged limit of 10.  Something going on with the camera.  I ultimately prevailed, but think I can do better with the PE I ended up with which is about 1.5 arc sec after PEM.  My 1600 is practically zero.


Re: PEMPRO

Emilio J. Robau, P.E.
 

I have gone through the exact same thing and can't figure out what is going on.  Curious to see the answer for that error screen.   I have spent quite a bit of time on it and can seem to cure the screen by changing the download speed of my ZWO 183.   Maybe I am just fooling myself.


Re: Fast question: APCC history

michael mccann
 

Thanks Jeff 
I too am concerned about those “control flight into ground”, borrowing an FAA phrase.  Even though I got a great deal, I don’t have any extra to replace damaged equipment.  Thanks for sharing your experiences.  I’m glad the kit comes with a tool. I remember changing these sort of chips back in the 90s Cisco network eqpt , without a tool one could damage the socket carrier. I’ll just wait till the upgrades come. Maybe imaging by the next new moon. ( that or the clouds will come and I’ll really catch hell by my Astro neighbors)

Cheers 


On Feb 17, 2022, at 20:39, Jeffc <jeffcrilly@...> wrote:




On Thu, Feb 17, 2022 at 7:03 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

As in when did it first version was  released to the Astro-physic mount owners. The earliest version I can find on the internet was 2014.  I bought a 2009 AP900, CP3GTO which doesn’t even have a USB Jack nor Ethernet ( where’s that guy playing the world’s smallest violin   :) )

so two questions: which rs232 to usb cable works best? Is APCC much use here?  I did order the V chip. The one in there has a “Q” on it. 



I just replaced an L chip in a CP3 with a V2 chip.   (I have another CP3 mount and I'll probably update that one also.)

I take no responsibility for you replacement job.. however here's something I learned along the way:
1. When taking off the CP3 cover, use a plastic shim (like the ones for removing car dashboard parts), and lever the cover STRAIGHT UP.   Don't allow it to "hinge" against the front edge.
IIRC that cover has a machined part that goes straight down.  The one I had was a very tight fit.
2.  Read the instructions for removing the old chip.  A tool is supplied.   My concern was cracking the carrier.   I ended up doing some sort of contortion with my thumb and fingers such that I was not applying pressure to the carrier when prying the chip out.   Also... do a tiny bit at a time alternating on the two corners.   Read the instructions.

As for the USB cable...  I've used various (I think they have to be ftdi based).   Last time I got one I got this:  https://www.amazon.com/Tripp-Lite-Keyspan-High-Speed-USA-19HS/dp/B0000VYJRY/ref=sr_1_3?keywords=tripp+light+usb+to+serial&qid=1645154662&sprefix=triplight+USB%2Caps%2C137&sr=8-3

After using APCC with the Mach2, I think there is some value in APCC with the non-encoder mount.  

One thing I found out... after the upgrade... I tried APCC with the CP3 mount.   I also had a keypad attached.  (Used to do this all the time with the V2 driver.)
I'm not sure they play well together.   When I went to park the mount in park 4 (with the keypad), and the RA was off by about 30 degrees.
I havent RTFM , but perhaps there is something in there about not using the keypad simultaneously.  I dunno.   I just had it on APCC for one session.  Normally I use the keypad with that mount.
That said... the other minor concern I have about APCC and the non-encoder mount is the mount getting "lost", and resulting in an errant slew into the pier.   Probably me just being paranoid.

-jeff 


Re: PEMPRO

Mike Dodd
 

On 2/17/2022 10:44 PM, Luke Dodd wrote:
If I had of used PEMPRO and the guidescope/MC178 to start with would have been super easy, absolutely a joy to use. Anyone care to comment.
I had a similar "could not acquire image" problem with my ASI1600MC Pro camera. Unfortunately, I don't remember exactly what the problem was, but I think it was related to the USB 3.0 interface.

I use MaxIm DL to acquire images, and sometimes MaxIm hangs up while reading the camera.

The ASI cameras are pretty sensitive to less-than-perfect USB 3.0. I've tried powered USB 3.0 extenders (my PC is nine feet away), and experienced frequent hangups. Ultimately I bought an Icron Raven four-port extender (big bucks), and that solved the problem.

Another factor is the USB speed setting in the ZWO ASCOM camera driver. It MUST be set to the lowest possible value, typically 40. Anything higher seems to cause download hangups.

HTH.

--- Mike


Re: PEMPRO

 

Hi Luke

it's a good instinct to use the longer fl for PEC

I think the problem lies in the ZWO ASCOM driver that has a memory issue with the larger chip 2600 and 6200 cameras. If you bin them or otherwise reduce the image size (center frame crop, etc.), or if you use it via an image acquisition program like Sequence Generator, you can get around that issue

Brian

On Thu, Feb 17, 2022 at 7:45 PM Luke Dodd <lkdodd@...> wrote:
Not sure this is the best place for this post, so I apologise in advance;

Had a frustrating time using PEMPRO  for the very first time on my AP1200 GTO 3 last night. 
Mount connected to PEMPRO without issue.
 
Unsure which camera / scope to use I tried an ASI2600MC with my AP refractor 1000mm f.l. Thinking a greater field of view and F.L. may produce a better result.
 
I connected to the camera in PEMPRO via the Ascom driver for the camera. Ran calibration wizard which produced the star trails image pop up screen. I clicked on the start /finish of 3 trails and moved on. Went to mount calibration screen and PEMPRO would not download this image, received the error message as shown in attachment.
 
I then decided to try the enhanced PHD2 option. Ultimately gave up as PHD2 was not working with the 2600MC, multiple issues, integration time would randomly change and the sensitivity of the camera didn’t make sense, every image after looping revealed few stars to actually guide on, and the star intensity dropped significantly between integrations.
 
In frustation swapped to my 60mm guidescope (360mm fl) and ASI178MC guide camera.
 
Again using the enhanced PHD2 option in PEMPRO failed to work. I constantly received “could not acquire guidestar” error message, so I abandoned PHD2 enhanced.

I went back to the calibration wizard in PEMPRO. All went by the book from there. PEMPRO produced images from the MC178 to allow the star trail image scale routine to work, then the mount calibration of directions worked first time (using same field as the failed attempt in PHD2). Clicked acquire data and off I went, 7 worm cycles created a PE curve, uploaded,  tested, native 2.5 arcsec error reduced to about a virtually a flat graph.
 
If I had of used PEMPRO and the guidescope/MC178 to start with would have been super easy, absolutely a joy to use. (maybe the lesson is there)
 
Obviuosly I am a first time user of PEMPRO I may have made a few mistakes. Anyone care to comment. Thanks



--
Brian 



Brian Valente


PEMPRO

Luke Dodd
 

Not sure this is the best place for this post, so I apologise in advance;

Had a frustrating time using PEMPRO  for the very first time on my AP1200 GTO 3 last night. 
Mount connected to PEMPRO without issue.
 
Unsure which camera / scope to use I tried an ASI2600MC with my AP refractor 1000mm f.l. Thinking a greater field of view and F.L. may produce a better result.
 
I connected to the camera in PEMPRO via the Ascom driver for the camera. Ran calibration wizard which produced the star trails image pop up screen. I clicked on the start /finish of 3 trails and moved on. Went to mount calibration screen and PEMPRO would not download this image, received the error message as shown in attachment.
 
I then decided to try the enhanced PHD2 option. Ultimately gave up as PHD2 was not working with the 2600MC, multiple issues, integration time would randomly change and the sensitivity of the camera didn’t make sense, every image after looping revealed few stars to actually guide on, and the star intensity dropped significantly between integrations.
 
In frustation swapped to my 60mm guidescope (360mm fl) and ASI178MC guide camera.
 
Again using the enhanced PHD2 option in PEMPRO failed to work. I constantly received “could not acquire guidestar” error message, so I abandoned PHD2 enhanced.

I went back to the calibration wizard in PEMPRO. All went by the book from there. PEMPRO produced images from the MC178 to allow the star trail image scale routine to work, then the mount calibration of directions worked first time (using same field as the failed attempt in PHD2). Clicked acquire data and off I went, 7 worm cycles created a PE curve, uploaded,  tested, native 2.5 arcsec error reduced to about a virtually a flat graph.
 
If I had of used PEMPRO and the guidescope/MC178 to start with would have been super easy, absolutely a joy to use. (maybe the lesson is there)
 
Obviuosly I am a first time user of PEMPRO I may have made a few mistakes. Anyone care to comment. Thanks


Re: Fast question: APCC history

Jeffc
 



On Thu, Feb 17, 2022 at 7:03 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

As in when did it first version was  released to the Astro-physic mount owners. The earliest version I can find on the internet was 2014.  I bought a 2009 AP900, CP3GTO which doesn’t even have a USB Jack nor Ethernet ( where’s that guy playing the world’s smallest violin   :) )

so two questions: which rs232 to usb cable works best? Is APCC much use here?  I did order the V chip. The one in there has a “Q” on it. 



I just replaced an L chip in a CP3 with a V2 chip.   (I have another CP3 mount and I'll probably update that one also.)

I take no responsibility for you replacement job.. however here's something I learned along the way:
1. When taking off the CP3 cover, use a plastic shim (like the ones for removing car dashboard parts), and lever the cover STRAIGHT UP.   Don't allow it to "hinge" against the front edge.
IIRC that cover has a machined part that goes straight down.  The one I had was a very tight fit.
2.  Read the instructions for removing the old chip.  A tool is supplied.   My concern was cracking the carrier.   I ended up doing some sort of contortion with my thumb and fingers such that I was not applying pressure to the carrier when prying the chip out.   Also... do a tiny bit at a time alternating on the two corners.   Read the instructions.

As for the USB cable...  I've used various (I think they have to be ftdi based).   Last time I got one I got this:  https://www.amazon.com/Tripp-Lite-Keyspan-High-Speed-USA-19HS/dp/B0000VYJRY/ref=sr_1_3?keywords=tripp+light+usb+to+serial&qid=1645154662&sprefix=triplight+USB%2Caps%2C137&sr=8-3

After using APCC with the Mach2, I think there is some value in APCC with the non-encoder mount.  

One thing I found out... after the upgrade... I tried APCC with the CP3 mount.   I also had a keypad attached.  (Used to do this all the time with the V2 driver.)
I'm not sure they play well together.   When I went to park the mount in park 4 (with the keypad), and the RA was off by about 30 degrees.
I havent RTFM , but perhaps there is something in there about not using the keypad simultaneously.  I dunno.   I just had it on APCC for one session.  Normally I use the keypad with that mount.
That said... the other minor concern I have about APCC and the non-encoder mount is the mount getting "lost", and resulting in an errant slew into the pier.   Probably me just being paranoid.

-jeff 

4001 - 4020 of 89029