Date   

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


Re: Mach1 problem please assist

Cheng-Yang Tan
 

Hi Ron,
   Thanks for the photos. I see that you wiped off the grease on the worm and the large spur gear, is that right? And left the small gears alone, right?

cytan

On Wednesday, June 24, 2020, 01:38:37 PM CDT, Ron Kramer <ronkramer1957@...> wrote:


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) ?
Also link to some of my re-greasing photos videos are at...     https://www.facebook.com/Ron.R.Kramer/ 
 



On Mon, Jun 22, 2020 at 4:18 PM Christopher Erickson <christopher.k.erickson@...> wrote:
Divide and conquer. Always my favorite troubleshooting approach!

If you have a CP4 or a CP3 with a later firmware chip, you should be able to download the PEM data from the CP3/4 using PEMpro and then simply look at it's graph for any spurious data points.


-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Mon, Jun 22, 2020, 5:01 AM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
If you are trying to chase down a problem and think it might be the mount, the best way to approach it is to disconnect every program from the mount and run it without any external inputs. That means no guider connections of any kind. Bring up your guider program and just watch the guidestar motion and take a screen shot.

Rolando

-----Original Message-----
From: DiscoDuck <montagoo@...>
To: main@ap-gto.groups.io
Sent: Sun, Jun 21, 2020 7:49 pm
Subject: Re: [ap-gto] Mach1 problem please assist

Hi Rolando, 
I have been getting similar spikes and was about to re-grease. But this sounds intriguing. Can I ask which log Andrew spotted this move in? I'd like to double check in my case and see if it could be the same issue before chasing mechanical things.
Best regards,
Paul



--


Re: Mach1 problem please assist

Ron Kramer
 

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) ?
Also link to some of my re-greasing photos videos are at...     https://www.facebook.com/Ron.R.Kramer/ 
 



On Mon, Jun 22, 2020 at 4:18 PM Christopher Erickson <christopher.k.erickson@...> wrote:
Divide and conquer. Always my favorite troubleshooting approach!

If you have a CP4 or a CP3 with a later firmware chip, you should be able to download the PEM data from the CP3/4 using PEMpro and then simply look at it's graph for any spurious data points.


-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Mon, Jun 22, 2020, 5:01 AM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
If you are trying to chase down a problem and think it might be the mount, the best way to approach it is to disconnect every program from the mount and run it without any external inputs. That means no guider connections of any kind. Bring up your guider program and just watch the guidestar motion and take a screen shot.

Rolando

-----Original Message-----
From: DiscoDuck <montagoo@...>
To: main@ap-gto.groups.io
Sent: Sun, Jun 21, 2020 7:49 pm
Subject: Re: [ap-gto] Mach1 problem please assist

Hi Rolando, 
I have been getting similar spikes and was about to re-grease. But this sounds intriguing. Can I ask which log Andrew spotted this move in? I'd like to double check in my case and see if it could be the same issue before chasing mechanical things.
Best regards,
Paul




Re: Mach2 Keypad

Roland Christen
 

The newest keypad version will work with CP4/CP5 controllers.

Rolando



-----Original Message-----
From: Dean Jacobsen <deanjacobsen@...>
To: main@ap-gto.groups.io
Sent: Wed, Jun 24, 2020 11:53 am
Subject: Re: [ap-gto] Mach2 Keypad

Will the new update be backward compatible with the older mounts as well?  For instance, if I update my existing keypad to work with the CP5, then can it also be used with my CP3 equipped 900GTO?
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


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

Joe Zeglinski
 

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: Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver #Guiding #APCC

Dean Jacobsen
 

On Wed, Jun 24, 2020 at 09:54 AM, Ray Gralak wrote:
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.
If this is in fact the cause of Rodolphe's problem then having a Windows update take down the mount driver and ruining an imaging trip is frustrating.    The only Windows computer I own is my imaging computer.

Ray, what is a good strategy for setting up the WIndows 10 upgrade/maintenance settings so that you aren't blindsided by a Windows compatibility issue?
 
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


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

Ray Gralak
 

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rodolphe
Sent: Wednesday, June 24, 2020 8:36 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 the response, here are additional details (sorry for the long message).



See screenshots below and narratives further down, including an other oddity found in APCC.



1. APCC version

<blob:https://ap-gto.groups.io/ae5b0613-487f-4d6b-b6fc-b69fabb21a24>



2. Mount firmware version

<blob:https://ap-gto.groups.io/a3f9ea8b-7e6c-4c1a-a602-f99806bc1433>



3. ASCOM driver version

<blob:https://ap-gto.groups.io/188c1c79-db34-4d10-bac6-c5442a2fb14d>



4. Ascom driver – test connection through IP address

<blob:https://ap-gto.groups.io/7727424e-ca88-4ead-9d6f-4434bae9f697>



5. Ascom driver – test connection through APCC virtual port

<blob:https://ap-gto.groups.io/4c4b4f87-fe72-462f-9c67-682670a2de5b>



6. APCC connection through serial port (COM/USB)

<blob:https://ap-gto.groups.io/0c8cdd6e-8c4f-4dd2-ab1a-bdd20095d90b>



7. APCC connection through IP (wifi)

<blob:https://ap-gto.groups.io/132650fb-047a-46c7-ac1c-00ec10240cad>



As you can see it from above:

I’m connected via wifi to the mount ; more specifically:

· CP4 is the control box

· CP4 connected to the mount, checked connections OK – it obviously responds to the commands

· CP4 connected to a local PC, an Intel NUC, through wifi (192.168.1.xxx) – using the same access point –
connection tested OK

· CP4 also connected to the same local PC with a COM/USB adapter, as a backup connection – connection
tested OK

· I drive the mount/local PC remotely through MSFT remote desktop (Win10 Pro on the local PC) – using wifi



I found an additional issue: APCC can’t seem to find the CP4 on the network:



<blob:https://ap-gto.groups.io/d46f5c67-0ea1-45d2-9fe3-848d14ffba07>



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)



<blob:https://ap-gto.groups.io/c986e74d-b066-414b-a88e-ff1ba02aa27b>


Re: Mach2 Keypad

Dean Jacobsen
 

Will the new update be backward compatible with the older mounts as well?  For instance, if I update my existing keypad to work with the CP5, then can it also be used with my CP3 equipped 900GTO?
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


Re: Mach2 Keypad

Roland Christen
 

The main delay now is the instruction manual. It is very lengthy to cover all the old and new features in both the CP5 and the keypad. We have a number of our staff working on it. The shutdown caused a bit of a delay which we are trying to catch up with.

Rolando



-----Original Message-----
From: Masera, David <DAMASERA@...>
To: main@ap-gto.groups.io
Sent: Wed, Jun 24, 2020 10:05 am
Subject: [ap-gto] Mach2 Keypad

Hi A-P,

Just wondering when the keypads for the Mach2 mount will be ready to ship.  I am fortunate to have received my Mach2 mount recently - Quite a work of art.  I have been reading A-P is finalizing some Keypad updates that appeal to the astro-imagers in the group before sending them out the door.  I am a visual observer who will set up in the field.  I do not want to drag my computer and table out to the site, or use a phone based app to interface with the mount.  I am sure the keypad will do everything a visual observer will ask of it, and more.  Perhaps if the Keypads are 95% complete in their programming, you could send them out.  I know the visual observers in the group will appreciate it.  You can always follow up with a software update to get the keypad programming up to 100% complete. 

David 


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

Rodolphe
 
Edited

Hi Ray

Thanks for the response, here are additional details (sorry for the long message).
As the groups doesn't allow embedding images, I have stored them onlive (onedrive), here:
https://1drv.ms/u/s!AvO2KZoP803hortC4RuDAyEGdXKWGQ?e=lF2mD5

  • APCC version (image001.png)
  • Mount firmware version (...004)
  • ASCOM driver version (...012)
  • Ascom driver – test connection through IP address (...013)
  • Ascom driver – test connection through APCC virtual port (...014)
  • APCC connection through serial port (COM/USB) (...015)
  • APCC connection through IP (wifi) (...016)

As you can see it from above:

I’m connected via wifi to the mount ; more specifically:

·         CP4 is the control box

·         CP4 connected to the mount, checked connections OK – it obviously responds to the commands

·         CP4 connected to a local PC, an Intel NUC, through wifi (192.168.1.xxx) – using the same access point – connection tested OK

·         CP4 also connected to the same local PC with a COM/USB adapter, as a backup connection – connection tested OK

·         I drive the mount/local PC remotely through MSFT remote desktop (Win10 Pro on the local PC) – using wifi

 
I found an additional issue: APCC can’t seem to find the CP4 on the network. (...017)

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) (...018)

 I hope this is useful.
Thanks


Mach2 Keypad

Masera, David
 

Hi A-P,

Just wondering when the keypads for the Mach2 mount will be ready to ship.  I am fortunate to have received my Mach2 mount recently - Quite a work of art.  I have been reading A-P is finalizing some Keypad updates that appeal to the astro-imagers in the group before sending them out the door.  I am a visual observer who will set up in the field.  I do not want to drag my computer and table out to the site, or use a phone based app to interface with the mount.  I am sure the keypad will do everything a visual observer will ask of it, and more.  Perhaps if the Keypads are 95% complete in their programming, you could send them out.  I know the visual observers in the group will appreciate it.  You can always follow up with a software update to get the keypad programming up to 100% complete. 

David 


Re: What is the diameter and thread on the Pasil.4 polar scope?

Tom Blahovici
 

32 tpi.
Going to try tomorrow.
Tom


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

Ray Gralak
 

Hi Rodolfe,

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).
That's the PHD2 developers' attempt to blame the AP V2 ASCOM driver for a COM interop threading issue in the PHD2 code. :-)

Disabling "Synchronous PulseGuide Calls" does not resolve the threading issue in PHD2, but it might make it less likely to occur.

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.
--> I thus bypassed APCC as a temporary solution, going straight through the ASCOM driver, until I find a
reason/fix for it.
That means APCC is having trouble communicating with either the mount or the driver.

How are you connecting to the mount?

Which control box are you using? (e.g. GTOCP4)

What version of firmware?

What version of APCC?

-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: Tuesday, June 23, 2020 2:37 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
#Guiding #APCC

Hello
I observed in my recent sessions several issues - not sure if they are connected or not.

Running Win10 Pro, 8GB Ram, plenty of disk space.

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

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.
--> I thus bypassed APCC as a temporary solution, going straight through the ASCOM driver, until I find a
reason/fix for it.

Has anyone an idea?
If more details are needed, happy to provide.
Thanks in advance for your support.
Rodolphe


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

Rodolphe
 

Hello
I observed in my recent sessions several issues - not sure if they are connected or not.

Running Win10 Pro, 8GB Ram, plenty of disk space.

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

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.
--> I thus bypassed APCC as a temporary solution, going straight through the ASCOM driver, until I find a reason/fix for it.

Has anyone an idea?
If more details are needed, happy to provide.
Thanks in advance for your support.
Rodolphe

7681 - 7700 of 79037