Date   

Re: Hydrogen clouds of the Bubble Nebula

CurtisC
 

My observatory is under the flight path from L.A.-area airports to the southern states (AZ, TX, FL).  With the current Covid-19 shutdowns, there's been very little air traffic.  It won't always be that way, but this would be the time to try 1 hr subs, as soon as we get rid of the smoke.  Rolando probably benefits from the lack of air traffic from O'Hare & Midway.


Re: Hydrogen clouds of the Bubble Nebula

CurtisC
 

Oh!  I guess this is something possible under the Autosave tab, which I rarely use.  I use CCD Commander for 99.9% of my imaging, and it tells MaxIm what settings to use.  Could you get a similar result if you just used standard guiding procedures?  I realize that that's not the point of your project.  When/if I get a Mach2 (I'm on the "notify me" list), maybe I'll try something similar.   I was inspired by your Pelican images to shoot the Pelican with my own gear: 30 min subs, 5 sec guide exposures (but with immediate corrections), Mach1GTO and TEC140ED scope.  Seeing varied, of course, over the many nights to accumulate 19.5 hrs of data, but the result was pretty good.  


Re: Hydrogen clouds of the Bubble Nebula

Roland Christen
 

Nudge guiding is done while the mount modeling is adjusting the background tracking rate. Both RA and Dec axes have to move at a different rate than sidereal in order to accommodate atmospheric refraction and other effects. While the model can be quite accurate for 5 to 15 minutes time period, it might not work well enough for 1 hour exposures by itself. There will be some drifting just simply because the model points are not super accurate to the 1/10 arc second level. So, for 1 hour exposures some guiding is required if your scope has high resolution and you can record sub-arc sec detail.

In the guider screen shot below, notice that the tracking is quite good for periods of time with no guide commands going to the mount. Then as it drifts a bit beyond the Min Move setting, the mount gets a little nudge to ring it back. The nudges are very small, typically set to about 30% of the full blown command that would be sent if no background modeling was being applied. During this 1 hour imaging run shown below, the RA rate was calculated at -65 arc sec per hour and the Dec rate was +12 arc sec per hour. Almost all of the RA rate was caused by atmospheric refraction with a little bit of flexure added. If no modeling and no guiding was done, then the RA axis would have drifted by 1.1 arc sec per minute. If only modeling was used with no extra guiding, the drift in RA would have probably been around 4 to 5 arc seconds per hour (0.08 arc sec per minute).

This is the reality of imaging on a planet that has an atmosphere that you can breathe. :-))

Rolando



-----Original Message-----
From: CurtisC via groups.io <calypte@...>
To: main@ap-gto.groups.io
Sent: Wed, Sep 9, 2020 3:25 pm
Subject: Re: [ap-gto] Hydrogen clouds of the Bubble Nebula

On Wed, Sep 9, 2020 at 12:04 PM, uncarollo2 <chris1011@...> wrote:

The mount was run with modeling on and gentle "nudge guiding"
I'm baffled as to how you do this.


Re: Hydrogen clouds of the Bubble Nebula

CurtisC
 

On Wed, Sep 9, 2020 at 12:04 PM, uncarollo2 <chris1011@...> wrote:
The mount was run with modeling on and gentle "nudge guiding"
I'm baffled as to how you do this.


Re: Upgrading firmware on keypad

George
 

Ed,

 

You may wish to contact me directly.  

 

What control box do you have (CP1 or CP2) and what is the chip that is in it?   If you have a Windows PC, you may wish to use it.   There are mixed results using Macs.  

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-222-6538 (direct line)

Phone:  815-282-1513 (office)

Email:  george@...

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Edward Beshore via groups.io
Sent: Monday, September 07, 2020 4:22 PM
To: main@ap-gto.groups.io
Cc: Edward Beshore
Subject: [ap-gto] Upgrading firmware on keypad

 

Hi - 

 

After a 18 year hiatus, I am returning to amateur astronomy. I have a AP1200 mount running keypad firmware V3.06. Starting things back up, the keypad battery was dead and I replaced it.

 

I wanted to upgrade the keypad firmware to 4.19.3, using updater V 2.04. I have a USB to serial converter with the FTDI chip (Sabrent) and running Windows 10 on my MacBook Air under bootcamp (not a virtual machine, a native boot of Windows)

 

Got through the update process where the updater window got through 

.

.

Sending 5

9F87:0000 ACK > D? > C.4B73

RDY

 

Then heard a click out of keypad, updater window showed

 

Sending 6

...Lots of HEX digits fly by on keypad window

Sending 7

...Lots of HEX digits fly by on keypad window

Sending 8

Code Loded

Done

 

No version number on keypad, but see photo.

 

Got the wrap up checklist. After powering off for 30 seconds, applied power

and got blinking cursor in upper left corner of keypad. (No menu)

 

Did this twice with same result.

 

Your assistance and ideas will be appreciated!

 

Ed Beshore

 

 


Re: Hydrogen clouds of the Bubble Nebula

Richard Hennig
 

Mike, I agree that satellite’s or planes are more likely to show up in long sub-exposures. However, shouldn’t these trails go away when you stack your image using the median of each pixel or sigma-clipping? Those methods require that you have at least a few sub-exposures to stack. A bigger issue for long sub-exposures could be the risk of bumping the mount, gusts of wind, poor tracking that ruin the overall sub-exposure, which stacking cannot easily fix.

Cheers,
Richard

On Sep 9, 2020, at 1:39 PM, Mike Dodd <mike@mdodd.com> wrote:

On 9/9/2020 1:19 PM, uncarollo2 <chris1011@aol.com> via groups.io wrote:
Nothing says that you have to do 1 hour exposures.
I don't want to spend an hour on a single image that a passing satellite ruins in an instant. I too have made long exposures for testing, especially when I was tracking-down flexure), but my for-real imaging uses 10-minute subs.

My 160 refractor can take some temp changes
without changing focus. If your scope is more finicky, then take shorter
exposures and stack 'em.
I bought a temperature sensor for my Feather Touch focuser, and now FocusMax keeps the scope close to focus as temperature changes. I tell ACP to focus every 40 minutes, so I get a refocus every four subs. Probably could extend that to 60 minutes or more, now that I have the temperature compensation running.

FWIW, here's my latest image: <http://astronomy.mdodd.com/nebulae-02.html> Ten-minute subs under a bright waning Moon with Ha and Oiii filters and a one-shot color camera. On Monday night I managed to get 1.8 hours of full color before the moonlight got too bright.

Narrowband is great for imaging under a bright Moon! And it does a good job with a OSC camera.

--- Mike




Re: Hydrogen clouds of the Bubble Nebula

Mike Dodd
 

On 9/9/2020 1:19 PM, uncarollo2 <chris1011@aol.com> via groups.io wrote:
Nothing says that you have to do 1 hour exposures.
I don't want to spend an hour on a single image that a passing satellite ruins in an instant. I too have made long exposures for testing, especially when I was tracking-down flexure), but my for-real imaging uses 10-minute subs.

My 160 refractor can take some temp changes
without changing focus. If your scope is more finicky, then take shorter
exposures and stack 'em.
I bought a temperature sensor for my Feather Touch focuser, and now FocusMax keeps the scope close to focus as temperature changes. I tell ACP to focus every 40 minutes, so I get a refocus every four subs. Probably could extend that to 60 minutes or more, now that I have the temperature compensation running.

FWIW, here's my latest image: <http://astronomy.mdodd.com/nebulae-02.html> Ten-minute subs under a bright waning Moon with Ha and Oiii filters and a one-shot color camera. On Monday night I managed to get 1.8 hours of full color before the moonlight got too bright.

Narrowband is great for imaging under a bright Moon! And it does a good job with a OSC camera.

--- Mike


Re: [ap-ug] [ap-gto] Hydrogen clouds of the Bubble Nebula

Roland Christen
 

Nothing says that you have to do 1 hour exposures. I do it for test purposes and because I can. My 160 refractor can take some temp changes without changing focus. If your scope is more finicky, then take shorter exposures and stack 'em.

Your 1100 mount is fully capable of unguided imaging with modeling, as well as hybrid imaging with modeling and nudge guiding.

Rolando

-----Original Message-----
From: dvjbaja <jpgleasonid@...>
To: main@ap-gto.groups.io
Cc: main@ap-ug.groups.io <main@ap-ug.groups.io>
Sent: Wed, Sep 9, 2020 12:11 pm
Subject: Re: [ap-ug] [ap-gto] Hydrogen clouds of the Bubble Nebula

Lovely shot.  The only problems I have had with 1 hour subs is temp change, resulting in focus change during the long sub-exposures or running into the dreaded "mount flip" before the exposure is completed.   Well... I have less than 24 hours to decide if I want the Mach 2.  My 1100 has been amazing, and doesn't want me looking at another woman. 

-jg

On Wed, Sep 9, 2020 at 10:04 AM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Hi All,

Just posted my new project of the Bubble nebula region. This first image is just the H-a portion to which I will eventually add OIII and SII for a narrowband color image. The exposure is 8 hours with 1 hour subs.

The mount was run with modeling on and gentle "nudge guiding" using an off-axis Lodestar guide camera. Guiding was done once every 15 seconds with 5 sec exposure times. The mount model was running in the background with custom tracking in both axes. The images were taken over 4 nights, some of which were very good seeing and some had poor seeing. On the good nights I was getting less than 0.1 RMS guide star motions and star images measuring around 1.3 arc sec FWHM.

"Nudge Guiding" is a kind of hybrid between full unguided and full guided. It has the advantage of smooth axis motions of an unguided imaging run plus the overall accuracy of guiding over long periods of time. The guide settings can be made so that only a very small guide pulse is sent to the mount every once in a while so that the mount is never being asked to chase the seeing.


Rolando


Re: Hydrogen clouds of the Bubble Nebula

dvjbaja
 

Lovely shot.  The only problems I have had with 1 hour subs is temp change, resulting in focus change during the long sub-exposures or running into the dreaded "mount flip" before the exposure is completed.   Well... I have less than 24 hours to decide if I want the Mach 2.  My 1100 has been amazing, and doesn't want me looking at another woman. 

-jg

On Wed, Sep 9, 2020 at 10:04 AM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Hi All,

Just posted my new project of the Bubble nebula region. This first image is just the H-a portion to which I will eventually add OIII and SII for a narrowband color image. The exposure is 8 hours with 1 hour subs.

The mount was run with modeling on and gentle "nudge guiding" using an off-axis Lodestar guide camera. Guiding was done once every 15 seconds with 5 sec exposure times. The mount model was running in the background with custom tracking in both axes. The images were taken over 4 nights, some of which were very good seeing and some had poor seeing. On the good nights I was getting less than 0.1 RMS guide star motions and star images measuring around 1.3 arc sec FWHM.

"Nudge Guiding" is a kind of hybrid between full unguided and full guided. It has the advantage of smooth axis motions of an unguided imaging run plus the overall accuracy of guiding over long periods of time. The guide settings can be made so that only a very small guide pulse is sent to the mount every once in a while so that the mount is never being asked to chase the seeing.


Rolando


Hydrogen clouds of the Bubble Nebula

Roland Christen
 

Hi All,

Just posted my new project of the Bubble nebula region. This first image is just the H-a portion to which I will eventually add OIII and SII for a narrowband color image. The exposure is 8 hours with 1 hour subs.

The mount was run with modeling on and gentle "nudge guiding" using an off-axis Lodestar guide camera. Guiding was done once every 15 seconds with 5 sec exposure times. The mount model was running in the background with custom tracking in both axes. The images were taken over 4 nights, some of which were very good seeing and some had poor seeing. On the good nights I was getting less than 0.1 RMS guide star motions and star images measuring around 1.3 arc sec FWHM.

"Nudge Guiding" is a kind of hybrid between full unguided and full guided. It has the advantage of smooth axis motions of an unguided imaging run plus the overall accuracy of guiding over long periods of time. The guide settings can be made so that only a very small guide pulse is sent to the mount every once in a while so that the mount is never being asked to chase the seeing.

https://www.astrobin.com/qq9mmt/
https://www.astrobin.com/full/qq9mmt/0/

Rolando


Re: Pillars of M16

Roland Christen
 

Anything over 20 minutes would be guided. However, it is "nudge guided" with modeling running in the background. This is the most accurate way that allows the mount to move at a smooth custom rate and not chase the seeing.

Rolando



-----Original Message-----
From: johnrogerjennings@...
To: main@ap-gto.groups.io
Sent: Wed, Sep 9, 2020 10:12 am
Subject: Re: [ap-gto] Pillars of M16

Are these guided or unguided 1 hour images with APCC Pro and the Mach 2?


Re: APCC app crash when parking mount (Mach1) - event viewer details #APCC

Joe Zeglinski
 

Hi Ray,
 
    FYI. To your point #4, no need to find one. Recall that there is a Windows provided off-line memory test – under START->ADMINISTRATIVE TOOLS –> “Windows Memory Diagnostic”.
 
    The user can run a single pass which would take something like 20 minutes depending on memory size, or change the on-screen  option for multiple reruns, perhaps for hours, until (maybe) a failure finally comes up, due to maybe a memory module  or case temperature heat. The results of the run will pop up shortly after the program reboots Windows, and will also be found inside the Notifications icon.
 
Joe Z.
 

From: Ray Gralak
Sent: Wednesday, September 9, 2020 9:31 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC
 
Hi Rodolphe,

> Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152

Your info indicates the crash occurred in ntdll.dll, an operating system DLL, which means it is not actually APCC that caused the crash.

Windows potentially is out of date, or corrupted. It also could be your system memory could have had an error (one or more bits changed).

1. Which version of Windows are you running? (run from a command prompt: "WinVer")

2. Run cmd.exe "as administrator", then check your O/S by typing "sfc.exe /scannow"

3. Run Windows update and apply all updates.

4. Find and download a memory checker to determine if there is a problem with memory on your system. If there is a problem, you should try reseating your dynamic RAM modules.

5. Many of the links with ntdll.dll crashes suggest to try unregistering and re-registering the ntdll.dll. For example:

https://answers.microsoft.com/en-us/windows/forum/all/faulting-module-name-ntdlldll/82a80b07-6d81-40f7-8aa6-b11f00098480

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


Re: Pillars of M16

johnrogerjennings@...
 

Are these guided or unguided 1 hour images with APCC Pro and the Mach 2?


Re: AP1100 vs mach2 decision #Mach2GTO #Absolute_Encoders

Karen Christen
 

Hello,

 

The Mach2GTO and the 1100GTO are both in production at present, and each has a notification list.  We do not know how many people on the notification lists will actually purchase a mount, therefore it’s a challenge to estimate wait times for either.  In general I would venture to say the wait will be shorter for the 1100GTO.  I’m sorry this is not more definitive.  If you have an interest, it does not hurt to add your name to the lists via the Notify Me button on each product – it costs nothing.  When we get to your name on the list you can decide whether you’d like to purchase or pass.  Thank you for your interest.

 

Karen C

AP

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of sprinkledo via groups.io
Sent: Wednesday, September 9, 2020 1:43 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1100 vs mach2 decision #Mach2GTO #Absolute_Encoders

 

What is the difference in wait time for the 1100 vs the mach2 ? 


--
Karen Christen
Astro-Physics


Re: AP1100 vs mach2 decision #Mach2GTO #Absolute_Encoders

Suvowner
 

What is the difference in wait time for the 1100 vs the mach2 ? 


Re: APCC app crash when parking mount (Mach1) - event viewer details #APCC

Ray Gralak
 

Rodolphe,

Also, can you use APCC's log zipper to zip your logs and place them in the files section, or post a link to a dropbox or other folder?

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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, September 9, 2020 12:37 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the
session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:

* [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
* [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
* [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
* [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel: Transferring view to the data
model...
* [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
* [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object
reference not set to an instance of an object.
* at r7.cf(String& A_0)
* [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking
Telescope! See logs.
* [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and
observatory...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to
False
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state,
not supported by scope...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
* {"method": "get_app_state", "id": 1001}
*
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message
complete...
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...



Here are the details from the Windows event viewer:


Log Name: Application
Source: Application Error
Date: 09-Sep-20 4:57:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
<EventRecordID>6374</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>NUC_Astro</Computer>
<Security />
</System>
<EventData>
<Data>AstroPhysicsCommandCenter.exe</Data>
<Data>1.8.3.0</Data>
<Data>5ed3b195</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.423</Data>
<Data>6e329152</Data>
<Data>c00000fd</Data>
<Data>00075027</Data>
<Data>1f38</Data>
<Data>01d6860dfbb3abca</Data>
<Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


Re: APCC app crash when parking mount (Mach1) - event viewer details #APCC

Ray Gralak
 

Hi Rodolphe,

Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Your info indicates the crash occurred in ntdll.dll, an operating system DLL, which means it is not actually APCC that caused the crash.

Windows potentially is out of date, or corrupted. It also could be your system memory could have had an error (one or more bits changed).

1. Which version of Windows are you running? (run from a command prompt: "WinVer")

2. Run cmd.exe "as administrator", then check your O/S by typing "sfc.exe /scannow"

3. Run Windows update and apply all updates.

4. Find and download a memory checker to determine if there is a problem with memory on your system. If there is a problem, you should try reseating your dynamic RAM modules.

5. Many of the links with ntdll.dll crashes suggest to try unregistering and re-registering the ntdll.dll. For example:

https://answers.microsoft.com/en-us/windows/forum/all/faulting-module-name-ntdlldll/82a80b07-6d81-40f7-8aa6-b11f00098480

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
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, September 9, 2020 12:37 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC app crash when parking mount (Mach1) - event viewer details #APCC

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the
session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:

* [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
* [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
* [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
* [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel: Transferring view to the data
model...
* [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
* [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object
reference not set to an instance of an object.
* at r7.cf(String& A_0)
* [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking
Telescope! See logs.
* [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and
observatory...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to
False
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state,
not supported by scope...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
* [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
* {"method": "get_app_state", "id": 1001}
*
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message
complete...
* [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...



Here are the details from the Windows event viewer:


Log Name: Application
Source: Application Error
Date: 09-Sep-20 4:57:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
<EventRecordID>6374</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>NUC_Astro</Computer>
<Security />
</System>
<EventData>
<Data>AstroPhysicsCommandCenter.exe</Data>
<Data>1.8.3.0</Data>
<Data>5ed3b195</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.423</Data>
<Data>6e329152</Data>
<Data>c00000fd</Data>
<Data>00075027</Data>
<Data>1f38</Data>
<Data>01d6860dfbb3abca</Data>
<Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


Re: Dec motor removal

thefamily90 Phillips
 

AP 1200 GOTO
I’ve owned it for something like 20 years and purchased it used.

Jim


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of CurtisC via groups.io <calypte@...>
Sent: Tuesday, September 8, 2020 7:37:03 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Dec motor removal
 
Which mount?


APCC app crash when parking mount (Mach1) - event viewer details #APCC

Rodolphe
 

Hello
Yesterday evening I experienced a mount crash; when SGP command issued to park the mount at the end of the session, apparently APCC crashed.
SGP log and Windows event viewer follow below.
Please let me now if more details are needed.
Thanks

SGP Log at the time of event:
  • [09/09/20 04:53:17.438][DEBUG][Main Thread][SQ;PK;] Monitoring system shutdown...
  • [09/09/20 04:53:17.439][DEBUG][Main Thread][SQ;PK;] SequenceEnds complete...
  • [09/09/20 04:53:17.439][DEBUG][Sequence Thread][SQ;PK;] Restoring system standby state...
  • [09/09/20 04:53:20.303][DEBUG][Main Thread][PK;] PopulateDataModel:  Transferring view to the data model...
  • [09/09/20 04:53:20.325][DEBUG][MF Update Thread][PK;] Performing serialize...
  • [09/09/20 04:58:26.183][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Error in ParkTel! : Object reference not set to an instance of an object.
  •    at r7.cf(String& A_0)
  • [09/09/20 04:58:26.183][ERROR][Telescope Thread][PK;] Error parking telescope: Error in Parking Telescope! See logs.
  • [09/09/20 04:58:26.184][INFO][Telescope Thread][PK;] Attempting to emergency stop mount and observatory...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Setting tracking state to False
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] ASCOM Telescope: Cannot set tracking state, not supported by scope...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Attempting to stop PHD2 guiding...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Checking PHD2 state...
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Pre-Wait : Stopped
  • [09/09/20 04:58:26.184][DEBUG][Telescope Thread][PK;] Sending to PHD2:
  • {"method": "get_app_state", "id": 1001}
  •  
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 GetPhdStatus - Post-Wait: Stopped
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] PHD2 Guider is already stopped.
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][PK;] Autoguider (PHD2) stopped Successfully
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] SGM_TELESCOPE_PARK message complete...
  • [09/09/20 04:58:26.284][DEBUG][Telescope Thread][NONE] Telescope thread is IDLE...


Here are the details from the Windows event viewer:


Log Name:      Application
Source:        Application Error
Date:          09-Sep-20 4:57:42 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NUC_Astro
Description:
Faulting application name: AstroPhysicsCommandCenter.exe, version: 1.8.3.0, time stamp: 0x5ed3b195
Faulting module name: ntdll.dll, version: 10.0.19041.423, time stamp: 0x6e329152
Exception code: 0xc00000fd
Fault offset: 0x00075027
Faulting process id: 0x1f38
Faulting application start time: 0x01d6860dfbb3abca
Faulting application path: C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1ab35bb-1ce7-4ea4-9e53-49dad106c709
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-09-09T02:57:42.5982470Z" />
    <EventRecordID>6374</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>NUC_Astro</Computer>
    <Security />
  </System>
  <EventData>
    <Data>AstroPhysicsCommandCenter.exe</Data>
    <Data>1.8.3.0</Data>
    <Data>5ed3b195</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.19041.423</Data>
    <Data>6e329152</Data>
    <Data>c00000fd</Data>
    <Data>00075027</Data>
    <Data>1f38</Data>
    <Data>01d6860dfbb3abca</Data>
    <Data>C:\Program Files (x86)\Astro-Physics\APCC Standard\AstroPhysicsCommandCenter.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>b1ab35bb-1ce7-4ea4-9e53-49dad106c709</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


Upgrading firmware on keypad

Edward Beshore
 

Hi - 

After a 18 year hiatus, I am returning to amateur astronomy. I have a AP1200 mount running keypad firmware V3.06. Starting things back up, the keypad battery was dead and I replaced it.

I wanted to upgrade the keypad firmware to 4.19.3, using updater V 2.04. I have a USB to serial converter with the FTDI chip (Sabrent) and running Windows 10 on my MacBook Air under bootcamp (not a virtual machine, a native boot of Windows)

Got through the update process where the updater window got through 
.
.
Sending 5
9F87:0000 ACK > D? > C.4B73
RDY

Then heard a click out of keypad, updater window showed

Sending 6
...Lots of HEX digits fly by on keypad window
Sending 7
...Lots of HEX digits fly by on keypad window
Sending 8
Code Loded
Done

No version number on keypad, but see photo.

Got the wrap up checklist. After powering off for 30 seconds, applied power
and got blinking cursor in upper left corner of keypad. (No menu)

Did this twice with same result.

Your assistance and ideas will be appreciated!

Ed Beshore


3721 - 3740 of 76746