Date   

Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Ray Gralak
 

Rodolphe,,

Line 5995: 0005995 2020-06-24 23:25:22.529: Error, ParseAndSaveDec, Invalid Dec: :Sd+60*30:48,3#
Line 5999: 0005999 2020-06-24 23:25:22.545: Error, ParseAndSaveRa, Invalid RA: :Sr22:37:23,71#
Line 6004: 0006004 2020-06-24 23:25:22.561: Error, SyncTarget, Valid Alt/Az, RA/Dec, or HA/Dec has not been received!

It looks like the Windows update may have changed the decimal point setting. Have you tried changing the Windows setting to swap "." and "," so that they are equivalent to what the mount expects? In the above log messages the mount will not understand a comma in the RA and declination values.

Also, I see network errors in the log for APCC trying to poll for the GTOCP4. You might want to check that your network settings are correct and disable any extra network adapters that are not connected to a LAN.

BTW, I suggest that you try using TCP as the protocol instead of UDP.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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 Rodolphe
Sent: Thursday, June 25, 2020 8:08 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
#Guiding #APCC

Hi Ray
Thanks for looking into it, really appreciated.
See zipped log files from the last 3 days here (onedrive link):
https://1drv.ms/u/s!AvO2KZoP803hortOULfxatSpxzXO2g?e=4eVEga
KR
Rodolphe


Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Rodolphe
 

Hi Ray
Thanks for looking into it, really appreciated.
See zipped log files from the last 3 days here (onedrive link): https://1drv.ms/u/s!AvO2KZoP803hortOULfxatSpxzXO2g?e=4eVEga
KR
Rodolphe


Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Ray Gralak
 

Rodolphe,

I'm out of luck - cannot uninstall it, too late (10 days have passed).
I'm sorry to hear that.

Going back to the list of problems:

1. When starting a new frame capture in SCG Pro, PHD2 sends out a warning "Please disable the Synchronous
PulseGuide option in the mount's ASCOM driver settings. Enabling the setting can cause unpredictable results".
--> But the ASCOM settings are "Synchronous PulseGuide calls" disabled (box unchecked).
Again the PHD2 warning is inaccurate. You can disable synchronous Pulseguide in the driver but that won't fix the bug in PHD2. Unfortunately despite my attempts I don't think any of the PHD2 developers understand or accept that the problem is in the way PHD2 is using COM interop. There is nothing that can be changed in the AP V2 ASCOM driver to fix this.

2,. When using APCC through its virtual ports, I get an error message slewing the mount (not after the initial slew,
but when SGP attempts to center the target) : "VPort2 / Fault / SyncTarget: Valid ALT/Az, RA/Dec, HA/Dec has not
been received!" - and the 3D view blinks in red.
Use APCC's log zipper utility to zip the APCC + ASCOM logs from the last night that you encountered the problem. Post here or email me privately a link to the zip file in dropbox, google drive, or one drive.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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 Rodolphe
Sent: Thursday, June 25, 2020 5:35 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
#Guiding #APCC

I'm out of luck - cannot uninstall it, too late (10 days have passed).
Would be interesting to see if other users face a similar problem.
Meanwhile, I will wait for a fix, I don't have the patience needed for reinstalling the full system now...
Thanks anyways.


Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Rodolphe
 

I'm out of luck - cannot uninstall it, too late (10 days have passed).
Would be interesting to see if other users face a similar problem.
Meanwhile, I will wait for a fix, I don't have the patience needed for reinstalling the full system now...
Thanks anyways.


Re: Mach2 Keypad

DFisch
 

Roland, will the new CP5 need updated once the keypads are received?

 

TJF ThinkPad1

 

From: uncarollo2 <chris1011@...> via groups.io
Sent: Wednesday, June 24, 2020 8:25 PM
Subject: Re: [ap-gto] Mach2 Keypad

 

Certainly. You will also have to load new software into the CP4, but that's real easy.

 

Rolando

 

 

 

-----Original Message-----
From: Michael Hambrick via groups.io <mike.hambrick@...>
To: main@ap-gto.groups.io
Sent: Wed, Jun 24, 2020 7:11 pm
Subject: Re: [ap-gto] Mach2 Keypad

Is it safe to assume that if we currently own a Keypad and CP4 that we will be able to download the new software to our existing Keypads ?


Best Regards

Michael Hambrick
ARLANXEO
TSR Global Manufacturing Support
PO Box 2000
Orange, TX 77631-2000
Phone: +1 (409) 882-2799
email: mike.hambrick@...

 


Re: NGC 5044 qne NGC 5054 galaxy group

Stuart <stuart.j.heggie@...>
 

Wonderful job Geoff!


On Wed, 24 Jun 2020 at 23:32, Geoff Smith <ghsmith45@...> wrote:
I was finally able to emerge from travel restrictions and get to my dark sky site--as expected the clouds didn't cooperate but I managed to get a few hours.

Image is here

https://www.astrobin.com/06krol/
with a larger version here

Tech details:

Plane Wave 12.5"CDK telescope with FLI Proline 16803 camera on AP900 mount.

Processed in PixInsight.

FOV 49' x 49'

It seems that NGC 5054 is not part of the galaxy group around the large elliptical galaxy NGC 5044. However, at some time in the past, NGC 5054 passed right through the group.
 


--

Stuart
http://www.astrofoto.ca/stuartheggie/


NGC 5044 qne NGC 5054 galaxy group

Geoff Smith
 

I was finally able to emerge from travel restrictions and get to my dark sky site--as expected the clouds didn't cooperate but I managed to get a few hours.

Image is here

https://www.astrobin.com/06krol/
with a larger version here

Tech details:

Plane Wave 12.5"CDK telescope with FLI Proline 16803 camera on AP900 mount.

Processed in PixInsight.

FOV 49' x 49'

It seems that NGC 5054 is not part of the galaxy group around the large elliptical galaxy NGC 5044. However, at some time in the past, NGC 5054 passed right through the group.
 


Re: Mach2 Keypad

Roland Christen
 

Certainly. You will also have to load new software into the CP4, but that's real easy.

Rolando



-----Original Message-----
From: Michael Hambrick via groups.io <mike.hambrick@...>
To: main@ap-gto.groups.io
Sent: Wed, Jun 24, 2020 7:11 pm
Subject: Re: [ap-gto] Mach2 Keypad

Is it safe to assume that if we currently own a Keypad and CP4 that we will be able to download the new software to our existing Keypads ?


Best Regards

Michael Hambrick
ARLANXEO
TSR Global Manufacturing Support
PO Box 2000
Orange, TX 77631-2000
Phone: +1 (409) 882-2799
email: mike.hambrick@...


Re: Mach2 Keypad

Michael Hambrick <mike.hambrick@...>
 

Is it safe to assume that if we currently own a Keypad and CP4 that we will be able to download the new software to our existing Keypads ?


Best Regards

Michael Hambrick
ARLANXEO
TSR Global Manufacturing Support
PO Box 2000
Orange, TX 77631-2000
Phone: +1 (409) 882-2799
email: mike.hambrick@...


Re: APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help! #ASCOM_V2_Driver

Ray Gralak
 

That popup window is not something that APCC would ever show. APCC has a built-in OEM license to the virtual ports so it will never ask you for a license for the virtual ports.

So maybe you have something else installed that is overwriting APCC's virtual ports. Sorry I don't know what that would be.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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 dnakic via groups.io
Sent: Wednesday, June 24, 2020 3:53 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help!

Thanks Ray, I did do an uninstall and install and the same issue is presented. Note, the uninstall was just using
windows uninstall process. If there is a specific uninstall process or other ideas I would appreciate it.


Re: Weird tracking artifacts - Gone

Roland Christen
 

Great! Glad to hear it's working.

Rolando


-----Original Message-----
From: Hemant Hariyani <hemanthariyani@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Wed, Jun 24, 2020 5:41 pm
Subject: Re: [ap-gto] Weird tracking artifacts

Thank you once again Roland. Indeed my encoders were disabled - no idea how and when that happened? Can APCC update do this?

Enabling encoders from APCC did the trick - I do not see PE anymore. Still trailing but linear as expected. Trailing is minimal near zenith - quite a bit about 45 degrees down. I will build a model and give this a shot again - and may be autogude.

Regards
Hemant



On Sat, Jun 20, 2020 at 3:18 PM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
If the encoders are turned off, then yes, you will have PE. Drift is not something the encoders can fix.
We have a utility that allows you to turn the encoders on or off. Also you can do it in APCC. You have to, of course have the encoders plugged in, and that may not be the case. If they are not plugged in and operating, the mount will simply revert to non-encoder mode and display a but of PE. Check the encoders to see if the light is blue or green. If the light is not on or shows red, then the encoders are not plugged in, or not working.

Rolando



-----Original Message-----
From: Hemant Hariyani <hemanthariyani@...>
To: main@ap-gto.groups.io
Sent: Sat, Jun 20, 2020 3:02 pm
Subject: Re: [ap-gto] Weird tracking artifacts

Hello Roland,

Thanks a lot. That is interesting. So I guess this is PE with drift. I do have encoders on the mount though. Is it possible that encoders are not working?

Regards
Hemant

On Sat, Jun 20, 2020 at 2:29 PM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Classic periodic error. Every mount has that to some extent (except for encoder mounts), is well known by imagers. Can be mostly eliminated with periodic error correction using a program like PEMPro - the gold standard of PE programs.

Rolando



-----Original Message-----
From: Hemant Hariyani <hemanthariyani@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Sat, Jun 20, 2020 2:24 pm
Subject: [ap-gto] Weird tracking artifacts

Hello all,

I am using a Meade 16 inch f/8 (FL - 3250 mm) on AP1600 GTO with AE. I am seeing some weird tracking artifacts in my images. I cannot go beyond a minute or so unguided.

A couple of nights ago, I tried live stack of m57 with 30s sub exposures.

As you can see in m57_livestack.jpg, there seems to be a "wavy" drift in the image. I saved individual images (30s x 20) and after stacking in PixInsight, the same error is seen on noise (m57_stacked.jpg) - but the pattern is clearer because of smaller structures.

Each 30s exposure itself was just fine as you can see from cleaned up m57.jpg. Guiding was not enabled. If this was polar alignment error, I would have thought it'd follow a more linear drift.

Any ideas on what could be causing this?

Regards
Hemant





Re: APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help! #ASCOM_V2_Driver

dnakic@...
 

Thanks Ray, I did do an uninstall and install and the same issue is presented.  Note, the uninstall was just using windows uninstall process.  If there is a specific uninstall process or other ideas I would appreciate it.


Re: Weird tracking artifacts

Hemant Hariyani
 

Thank you once again Roland. Indeed my encoders were disabled - no idea how and when that happened? Can APCC update do this?

Enabling encoders from APCC did the trick - I do not see PE anymore. Still trailing but linear as expected. Trailing is minimal near zenith - quite a bit about 45 degrees down. I will build a model and give this a shot again - and may be autogude.

Regards
Hemant



On Sat, Jun 20, 2020 at 3:18 PM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
If the encoders are turned off, then yes, you will have PE. Drift is not something the encoders can fix.
We have a utility that allows you to turn the encoders on or off. Also you can do it in APCC. You have to, of course have the encoders plugged in, and that may not be the case. If they are not plugged in and operating, the mount will simply revert to non-encoder mode and display a but of PE. Check the encoders to see if the light is blue or green. If the light is not on or shows red, then the encoders are not plugged in, or not working.

Rolando



-----Original Message-----
From: Hemant Hariyani <hemanthariyani@...>
To: main@ap-gto.groups.io
Sent: Sat, Jun 20, 2020 3:02 pm
Subject: Re: [ap-gto] Weird tracking artifacts

Hello Roland,

Thanks a lot. That is interesting. So I guess this is PE with drift. I do have encoders on the mount though. Is it possible that encoders are not working?

Regards
Hemant

On Sat, Jun 20, 2020 at 2:29 PM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Classic periodic error. Every mount has that to some extent (except for encoder mounts), is well known by imagers. Can be mostly eliminated with periodic error correction using a program like PEMPro - the gold standard of PE programs.

Rolando



-----Original Message-----
From: Hemant Hariyani <hemanthariyani@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Sat, Jun 20, 2020 2:24 pm
Subject: [ap-gto] Weird tracking artifacts

Hello all,

I am using a Meade 16 inch f/8 (FL - 3250 mm) on AP1600 GTO with AE. I am seeing some weird tracking artifacts in my images. I cannot go beyond a minute or so unguided.

A couple of nights ago, I tried live stack of m57 with 30s sub exposures.

As you can see in m57_livestack.jpg, there seems to be a "wavy" drift in the image. I saved individual images (30s x 20) and after stacking in PixInsight, the same error is seen on noise (m57_stacked.jpg) - but the pattern is clearer because of smaller structures.

Each 30s exposure itself was just fine as you can see from cleaned up m57.jpg. Guiding was not enabled. If this was polar alignment error, I would have thought it'd follow a more linear drift.

Any ideas on what could be causing this?

Regards
Hemant





Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Ray Gralak
 

Hi Joe,

Yes, I believe you do have a choice to not install feature updates. Here's a link to some things you can do.

https://www.techradar.com/how-to/how-to-stop-a-windows-10-update

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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 Joe Zeglinski
Sent: Wednesday, June 24, 2020 10:16 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
#Guiding #APCC

Ray,

Do we have a choice in NOT upgrading? I thought Microsoft forces us to accept the latest upgrade – unlike in
previous OS’s.
IIRC, we can only hold it off for 7 days.

Joe

From: Ray Gralak
Sent: Wednesday, June 24, 2020 12:54 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
#Guiding #APCC

Rodolphe,

This is weird, because it used to work perfectly before. Before what? I can’t determine any major changes to my
setup except maybe the recent Win10 update (feature update version 2004)
I've heard there have been some compatibility issues with Windows 10 v2004, so you might want to revert
Windows to the previous version you had running. If reverting to the old Windows 10 version solves the problems
then you might want to hold off upgrading until 2004 has become more refined.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver



Re: APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help! #ASCOM_V2_Driver

Ray Gralak
 

It sounds like maybe your anti-virus software or a registry "cleaner" may have damaged the APCC installation.

Try uninstalling APCC and then reinstalling, making sure to enable the option to reinstall the virtual ports when reinstalling.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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 dnakic via groups.io
Sent: Wednesday, June 24, 2020 2:21 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help!

Running, I'm running into a problem with running APCC and get the error message about Virtual Port, image of
issue enclosed. I tried running both Normal and as Administrator and issue persists. I worked with George and
installed APPC Pro V1.8.3.1. V2 Driver is v5.30.10. ASCOM is 6.4SP1. I can't get past the Active X warning
issue.


Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Rodolphe
 

I've heard there have been some compatibility issues with Windows 10 v2004, so you might want to revert Windows to the previous version you had running. If reverting to the old Windows 10 version solves the problems then you might want to hold off upgrading until 2004 has become more refined.

-Ray Gralak
I've not tried to undo the 2004 update yet - but I tried reinstalling APCC and the ASCOM driver - same issues.
Will undo the 2004 tomorrow and report back here.


APCC Virtual Port Error Message #ASCOM_V2_Driver - Ray Help! #ASCOM_V2_Driver

dnakic@...
 

Running, I'm running into a problem with running APCC and get the error message about Virtual Port, image of issue enclosed.  I tried running both Normal and as Administrator and issue persists.  I worked with George and installed APPC Pro V1.8.3.1.   V2 Driver is v5.30.10.  ASCOM is 6.4SP1.  I can't get past the Active X warning issue.


Re: Mach2 power consumption #Mach2GTO

Christopher Erickson
 

Actually ALL of the power consumed eventually is released as heat. Since energy can't be created or destroyed. Energy and mass can be converted but not created or destroyed.

If your power supply is feeding 100.000 watts to your system, 100.000 watts of heat is ultimately radiated from that system, at different points. Some from the power supply, some from the wires, some from the motors, some from the electronics, some from lights, etc.

Energy is always a net sum game. Always flowing from a high side to a low side. Disregarding the comparatively-trivial amount of heat generated in the core of the earth by nuclear fission of heavy metals, the earth radiates exactly as much energy back into space as it receives from the sun (and that core fission.) If it did not, it would be a planetary disaster.

On Wed, Jun 24, 2020 at 5:43 AM Rodolphe <rodolgo@...> wrote:
I guess you mean 5 to 20% of the consumption is generated by the PS as heat anyways, depending on the PS efficiency.
The remaining 80 to 95% is used by the consumer, ie the powered device including the power line, which will transform it into mechanical power, and a bit into heat as well.
Correct?


Re: Mach1 problem please assist

Worsel
 

Ron

PEMPro will give you better PEM in all aspects.  Here is what the A-P manual says about using the basic PEM functionality in APPC Pro

Use APCC to Record PEM

NOTE: Like the Keypad method below, using APCC to record PEM will use the GTOCP3's servorecording capabilities, and will only record a single worm cycle. DO NOT replace a good PEMPro correction model with this single cycle model. Think of this as an emergency tool for getting a quick PEcurve into the mount, NOT as an ideal way to program your PEM, or as a way to improve on a PEMPro model!

Bryan


Thanks Christopher.  problem SOLVED.  Just recorded a new PEC in APCC.  I don't really know how to use PEMpro.  I tried it when I first got it but was told I did it wrong. 
What will pempro do for me that will make it better and worthy of the hassle vs recording PEC in APCC (pro) ?
 


Re: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Cheng-Yang Tan
 

Hi Joe,
   Win10 2004 is a feature update and not a security update so, at least for now, you don't have to accept it. I've left mine sitting there for 2 weeks now and it's not forcing me to update. And I've made one security update in the mean time.

cytan

On Wednesday, June 24, 2020, 12:16:21 PM CDT, Joe Zeglinski <j.zeglinski@...> wrote:


Ray,
 
    Do we have a choice in NOT upgrading? I thought Microsoft forces us to accept the latest upgrade – unlike in previous OS’s.
IIRC, we can only hold it off for 7 days.
 
Joe
 
From: Ray Gralak
Sent: Wednesday, June 24, 2020 12:54 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC
 
Rodolphe,

> This is weird, because it used to work perfectly before. Before what? I can’t determine any major changes to my
> setup except maybe the recent Win10 update (feature update version 2004)

I've heard there have been some compatibility issues with Windows 10 v2004, so you might want to revert Windows to the previous version you had running. If reverting to the old Windows 10 version solves the problems then you might want to hold off upgrading until 2004 has become more refined.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3:  https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

10021 - 10040 of 81390