Date   

Re: GTO CP3 Problem

Ray Gralak
 

Hi Josep,

Thanks for the explanation, I did try COM4 on the upper serial as well with no luck. Changing the serial driver chip
did not fix this.

Where can the problem be ? Something else I could try ?
If, when using the same cable, the bottom port works but the top port does not then unless someone else has a suggestion you may have to send the control box to Astro-Physics for repair.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of pepineus
Sent: Saturday, January 4, 2020 7:36 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 Problem

Hi Ray,

Thanks for the explanation, I did try COM4 on the upper serial as well with no luck. Changing the serial driver chip
did not fix this.

Where can the problem be ? Something else I could try ?

Thanks in advance,

Josep


Re: GTO CP3 Problem

pepineus
 

Hi Ray,

Thanks for the explanation, I did try COM4 on the upper serial as well with no luck. Changing the serial driver chip did not fix this.

Where can the problem be ? Something else I could try ?

Thanks in advance,

Josep


Re: GTO CP3 Problem

Ray Gralak
 

Hi Josep,

I got the new serial driver chip (MAX238CNG) for my CP3 and installed it. The
lower serial port seems to work ok, as I can find it at COM4 and connects
(remember I am trying to avoid this one
since I get many reliability issues). However I still cannot fins the upper
serial port at COMS 1-20 ! If I cannot solve
this I will not update the ROM on the CP3.
The COM port on the computer will not change if you disconnect the cable from the bottom port on the CP3 and connect it to the top port on the CP3.

So, after you plug the same cable into the top port try communicating on COM4. If the mount doesn't respond on COM4 then there is a problem with the top port.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of pepineus
Sent: Saturday, January 4, 2020 1:42 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 Problem

Hi everyone,

Happy new year,

I am reporting back on my problem. I got the new serial driver chip (MAX238CNG) for my CP3 and installed it. The
lower serial port seems to work ok, as I can find it at COM4 and connects (remember I am trying to avoid this one
since I get many reliability issues). However I still cannot fins the upper serial port at COMS 1-20 ! If I cannot solve
this I will not update the ROM on the CP3.

Josep


Re: #APCC PemPro3 Fail to lauch in APCC after PemPro update #APCC

Ray Gralak
 

Hi John,

Thanks, Ray. I uninstalled both v3 and v2.8. I reinstalled v3.00.27. It managed to keep the license. I then
launched APCC v1.7.1.4 Standard. The only difference now is I don't have a PemPro button under the AP RAPAS
radio button.
Into which folder was PEMPro V3 installed?

As I said previously, two Windows system environment variables (ProgramFiles and ProgramFiles(x86)) control the root folder where program files should be installed and also where APCC will look for PEMPro.

For example if:

ProgramFiles(x86)=C:\Program Files (x86)

Then APCC will look for PEMPro here:

C:\Program Files (x86)\CCDWare\PEMPro V3

BTW, one easy way to get the system environment variables is to open a command prompt shell ("cmd") and type "set".

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of John A. Sillasen
Sent: Friday, January 3, 2020 10:58 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC PemPro3 Fail to lauch in APCC after PemPro update

Thanks, Ray. I uninstalled both v3 and v2.8. I reinstalled v3.00.27. It managed to keep the license. I then
launched APCC v1.7.1.4 Standard. The only difference now is I don't have a PemPro button under the AP RAPAS
radio button.

What did I do to make that happen?

John Sillasen


Re: GTO CP3 Problem

pepineus
 

Hi everyone,

Happy new year,

I am reporting back on my problem. I got the new serial driver chip (MAX238CNG) for my CP3 and installed it. The lower serial port seems to work ok, as I can find it at COM4 and connects (remember I am trying to avoid this one since I get many reliability issues). However I still cannot fins the upper serial port at COMS 1-20 ! If I cannot solve this I will not update the ROM on the CP3.

Josep


Re: #APCC PemPro3 Fail to lauch in APCC after PemPro update #APCC

John A. Sillasen
 

Thanks,  Ray. I uninstalled both v3 and v2.8. I reinstalled v3.00.27. It managed to keep the license.  I then launched APCC v1.7.1.4 Standard. The only difference now is I don't have a PemPro button under the AP RAPAS radio button.

What did I do to make that happen?

John Sillasen 


Re: #APCC PemPro3 Fail to lauch in APCC after PemPro update #APCC

Ray Gralak
 

John,

1. You should not install PEMPro V3 in a beta folder. If you did that uninstall and reinstall it in the correct folder.
2. The location of PEMPro and other applications is controlled by the Windows environment variables defined on your computer. For example, on most computers the two relevant environment variables are defined like this:

ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)

So, you can set them to wherever you want but be warned that starting with Windows Vista Microsoft does not want you to install programs outside of the Program Files folders because of security concerns.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of John A. Sillasen
Sent: Friday, January 3, 2020 11:42 AM
To: main@ap-gto.groups.io
Cc: karen@...
Subject: [ap-gto] #APCC PemPro3 Fail to lauch in APCC after PemPro update

Morning, Happy New Year, (Retry #4 at Karen’s request. Our apologies – especially to Ray Gralak – if this comes
through multiple times). What’s there to do on New Year’s Day? Update software that I don’t get to use often. I
knew of the APCC update from the forums so that was step 1.

Step 2 was an ASCOM Platform update to 6.4 Sp1. The AP ASCOM driver was current, so while I’m not
connected to a mount, let’s see if stuff works. APCC launches fine, as does RAPAS once past the no mount
warning stuff. Even Horizons was a 1st time play date for me. Worked through some of the ephemeris reqt’s for
funnsies. PEMPro, hmmm, have yet to try that even though it launches in v.2 and early Beta 3 fine. It worked but
told me it was a Beta and get the heck out of dodge and go get a new version. Okay, so I didn’t apply my license
but it launched, right? Got the new version, 3.00.27 and it installed right over the old beta in the same folder. This
time I put the license file key in. Ha, had to remember where I stored that 1st! That was a significant find.



So -no PEMPro 3 launch. Weird thing – it thinks it should be on C now. Ray, you and I worked through this mess
years ago – small C partition laptops with 1 GB D drives, right? What’s up with that small C stuff anyhow.


The message is attached.

Suggestions other than get a new laptop? I did by the way but now it’s learn and try time.

Thanks!

John A. Sillasen



#APCC PemPro3 Fail to lauch in APCC after PemPro update #APCC

John A. Sillasen
 

Morning, Happy New Year, (Retry #4 at Karen’s request. Our apologies – especially to Ray Gralak – if this comes through multiple times).  What’s there to do on New Year’s Day? Update software that I don’t get to use often.  I knew of the APCC update from the forums so that was step 1.

Step 2 was an ASCOM Platform update to 6.4 Sp1.  The AP ASCOM driver was current, so while I’m not connected to a mount, let’s see if stuff works.  APCC launches fine, as does RAPAS once past the no mount warning stuff.  Even Horizons was a 1st time play date for me.  Worked through some of the ephemeris reqt’s for funnsies.  PEMPro, hmmm, have yet to try that even though it launches in v.2 and early Beta 3 fine.  It worked but told me it was a Beta and get the heck out of dodge and go get a new version.  Okay, so I didn’t apply my license but it launched, right?  Got the new version, 3.00.27 and it installed right over the old beta in the same folder.  This time I put the license file key in.  Ha, had to remember where I stored that 1st!  That was a significant find.

 

So -no PEMPro 3 launch.  Weird thing – it thinks it should be on C now.  Ray, you and I worked through this mess years ago – small C partition laptops with 1 GB D drives, right?  What’s up with that small C stuff anyhow.


The message is attached.

 Suggestions other than get a new laptop? I did by the way but now it’s learn and try time.

 Thanks!

John A. Sillasen



Re: Cannot Seem to Keep the Same Virtual Ports

eckhard.voelcker@...
 

I just had the same or a similar problem.

The virtual ports in APCC were Com20, Com21 and Com22. The ASCOM Driver is configured to use Com20. Yesterday the ASCOM driver could not connect to APCC. The driver configuration showed Com20 but the APCC configuration showed no virtual port. Com20, Com21, and Com 22 were not listed in the dropdown box where you set the virtual ports so I could not set these anymore. 

The Devicemanager showed under COM / LPT three virtual com ports (20, 21 and 22). These ports were being installed independently of APCC as these appeared after a reboot without starting APCC. I used the Devicemanager to uninstall these virtual com ports. Afterwards APCC would see these ports as being available again and I could select Com20, Com21 and Com22 as virtual ports. The ASCOM driver connects and is happy again.

It looks as if some Windows or another install routine has seen these ports and decided to install a permanent driver / setting for those ports (I use an external USB hub). So  APCC is seeing Com20, 21 and 22 as already taked ("in use") and thus the error.

Maybe you have a similar issue, Jerome. 

Best,
Eckhard


Re: Cannot Seem to Keep the Same Virtual Ports

Jerome A Yesavage
 

Ray,

Perhaps ACP is not shutting down perfectly cleanly.  It is, however, right at the top of the shutdown script. 

I will give this added attention and watch it. 

I have the startup delays at 30s, with a second delay of 20s after Maxim starts, before the system connects to FocusMax. 

It goes:

PowerOn-delay30s->APCC delay20s-> Maxim (same AP driver) ->FocusMax (was ACP Telescope Hub (ASCOM))  

Both Maxim and FocusMax use the mount.  I noticed that FM was using an ACP driver?  I changed this to the AP driver... maybe this was an issue. 

I'll monitor this carefully and see if I can get a consistent picture. 


Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

Worsel
 

Thanks, Dale!

I use BYEOS.  It integrates well with Astrotortilla and supports multiple EOS cameras.  In fact, the only reason I would move away from it is that it cannot do drift correction, hence my interest in APPC-Pro and APPM

I will give SGP a trial test.

Bryan


Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

Worsel
 

Ray

Thanks

I will give SGP a trial test

Bryan


Re: APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

Martin G <martin.artem14@...>
 

Hi Peter,

When you have the setup Celestron Edge HD 1100 + 0.7x reducer, then the focal length of your EDGE HD is changed to  280mm / 1960mm
and not to 2030 as stated in your email !


Good luck and you can actually calculate the FOV of your setup here http://astronomy.tools/calculators/field_of_view/


Martin

grafik.png




Am Fr., 3. Jan. 2020 um 17:42 Uhr schrieb Ray Gralak <groups3@...>:

> I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
> The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
> camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?

If SGPro is reporting 4.1 arc-sec/pixel and you think it should be close to 0.5, then that is a bad plate solve. APPM did the right thing by rejecting the plate solve.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3:  https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Bresler via Groups.Io
> Sent: Friday, January 3, 2020 8:22 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?
>
> I had exactly the same experience with APPM, and actually to date have not been successful in generating a point
> model. My plate solves in SGP, fortunately, usually work or I would not be able to find anything with my Celestron
> Edge HD 1100 with the focal reducer, which has a narrow FOV. Using the Hyperstar, with a wide FOV, APPC is
> sufficiently accurate, but it by itself is not at the high focal length.
>
> I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
> The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
> camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?
>





Re: APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

Wayne Hixson
 

Per your specs, it should be about 0.5

306*4.7/2030=0.47

On Jan 3, 2020, at 8:42 AM, Ray Gralak <groups3@...> wrote:



I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?
If SGPro is reporting 4.1 arc-sec/pixel and you think it should be close to 0.5, then that is a bad plate solve. APPM did the right thing by rejecting the plate solve.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Bresler via Groups.Io
Sent: Friday, January 3, 2020 8:22 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

I had exactly the same experience with APPM, and actually to date have not been successful in generating a point
model. My plate solves in SGP, fortunately, usually work or I would not be able to find anything with my Celestron
Edge HD 1100 with the focal reducer, which has a narrow FOV. Using the Hyperstar, with a wide FOV, APPC is
sufficiently accurate, but it by itself is not at the high focal length.

I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?



Re: APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

Ray Gralak
 

I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?
If SGPro is reporting 4.1 arc-sec/pixel and you think it should be close to 0.5, then that is a bad plate solve. APPM did the right thing by rejecting the plate solve.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Bresler via Groups.Io
Sent: Friday, January 3, 2020 8:22 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

I had exactly the same experience with APPM, and actually to date have not been successful in generating a point
model. My plate solves in SGP, fortunately, usually work or I would not be able to find anything with my Celestron
Edge HD 1100 with the focal reducer, which has a narrow FOV. Using the Hyperstar, with a wide FOV, APPC is
sufficiently accurate, but it by itself is not at the high focal length.

I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1.
The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro
camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?


Re: APPM 'BAD X SCALE' Error and Appropriate Troubleshooting?

Peter Bresler
 

I had exactly the same experience with APPM, and actually to date have not been successful in generating a point model. My plate solves in SGP, fortunately, usually work or I would not be able to find anything with my Celestron Edge HD 1100 with the focal reducer, which has a narrow FOV. Using the Hyperstar, with a wide FOV, APPC is sufficiently accurate, but it by itself is not at the high focal length. 

I originally entered 0.5 as the scale in the camera settings in SGP, but after doing plate solves it appears as 4.1. The focal length for the scope with the 0.7 focal reducer is 2030mm and the pixel size for my ZWO 294MC Pro camera is 4.7.. What scale setting should I be entering in APPM, and where do you enter it?


Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

Ray Gralak
 

I downloaded trial versions of APCC-Pro and PinPoint from DC3. In the process of testing these, it appears that
PinPoint can only use FIT files for plate solving. As I image mostly with a DSLR, this presents a barrier, since
APPM links to PinPoint in order to build a sky-model.
If your camera does not have an ASCOM driver then you will need an intermediary camera control application like MaximDL, SkyX Pro (with Camera add on), or Sequence Generator Pro. MaximDL and SkyX both have excellent automation interfaces and work with many different cameras including DSLRs. Sequence Generator Pro also works but its automation interface is not as rich.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Worsel via Groups.Io
Sent: Thursday, January 2, 2020 10:45 PM
To: main@ap-gto.groups.io
Subject: Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

I downloaded trial versions of APCC-Pro and PinPoint from DC3. In the process of testing these, it appears that
PinPoint can only use FIT files for plate solving. As I image mostly with a DSLR, this presents a barrier, since
APPM links to PinPoint in order to build a sky-model.

While I can convert the Raw images to FIT manually, this obviously negates the advantages of automatic mapping.

Have I missed something? Is PinPoint (and therefore APPM) capable of reading Raw or even JPG files?

Before I go through the process of downloading, installing, and tinkering with SGP, does it allow the use of DSLR
Raw or JPG files for PlateSolve2? SGP can capture images from a DSLR, but I cannot tell if it can use Raw
images for PlateSolve2.

I use AstroTortilla now for platesolving vias ANSVR. Is it possible for APPM to connect directly to ANSVR? rather
than go through PinPpoint or PlateSolve2?

Bryan

Thanks.

Bryan


Re: APCC v1.7.1.4 - slews not being reported as fully complete #APCC #ASCOM_V2_Driver

R Botero
 

Thank you Ray. Looking forward to the new release of APCC. 
Roberto


Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

Dale Ghent
 


Which app do you normally use to drive your camera and imaging sessions? Do you not use SGP, but something else? What does your normal imaging workflow involve?

Because of the proprietary formats of DSLR cameras (Canon CR2/CR3, Nikon NEF, etc) apps typically need an ancillary program or library to convert those formats into a more common format that it can make better use of, such as converting the camera raw image a basic bitmap and then on to FITS, JPEG, PNG, TIFF, and the like. Individual plate solver apps such as Platesolve2, ASTAP, and others generally do not include these libraries (which must be constantly updated to support new cameras as they are released)  so typically only accept inputs of what we call Well-Known Formats, such as the aforementioned. For this, you need a surrogate program which can manage the raw camera files, which SGP and other apps can do, but of those APPM only gets along with SGP at the moment.

I'm under the impression that SGP will just do the right thing when it comes to DSLR raw files and sending them to a configured platesolver such as Platesolve2. Under the camera options for Canon EOS or Nikon, the default option is to save the image data as FITS. It's this data that is used to send on to the configured plate solver in SGP. See the attached screenshot.


/dale

On Jan 3, 2020, at 1:45 AM, Worsel via Groups.Io <bryancashion@...> wrote:

I downloaded trial versions of APCC-Pro and PinPoint from DC3.  In the process of testing these, it appears that PinPoint can only use FIT files for plate solving.  As I image mostly with a DSLR, this presents a barrier, since APPM links to PinPoint in order to build a sky-model.

While I can convert the Raw images to FIT manually, this obviously negates the advantages of automatic mapping.

Have I missed something?  Is PinPoint (and therefore APPM) capable of reading Raw or even JPG files?

Before I go through the process of downloading, installing, and tinkering with SGP, does it allow the use of DSLR Raw or JPG files for PlateSolve2?  SGP can capture images from a DSLR, but I cannot tell if it can use Raw images for PlateSolve2.

I use AstroTortilla now for platesolving vias ANSVR.  Is it possible for APPM to connect directly to ANSVR? rather than go through PinPpoint or PlateSolve2?

Bryan

Thanks.

Bryan


Re: Upgrade to new keypad version (was RE: [ap-gto] Unguided imaging with Mach2) #Keypad

Worsel
 

I downloaded trial versions of APCC-Pro and PinPoint from DC3.  In the process of testing these, it appears that PinPoint can only use FIT files for plate solving.  As I image mostly with a DSLR, this presents a barrier, since APPM links to PinPoint in order to build a sky-model.

While I can convert the Raw images to FIT manually, this obviously negates the advantages of automatic mapping.

Have I missed something?  Is PinPoint (and therefore APPM) capable of reading Raw or even JPG files?

Before I go through the process of downloading, installing, and tinkering with SGP, does it allow the use of DSLR Raw or JPG files for PlateSolve2?  SGP can capture images from a DSLR, but I cannot tell if it can use Raw images for PlateSolve2.

I use AstroTortilla now for platesolving vias ANSVR.  Is it possible for APPM to connect directly to ANSVR? rather than go through PinPpoint or PlateSolve2?

Bryan

Thanks.

Bryan