Date   

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



Re: Dec motor removal

CurtisC
 

Which mount?


Re: GTOCP3 and serial

 

haha yes, i guess i should have been more declarative ;)

APCC *has* a built-in terminal, and you could just click on it and open up the terminal window and begin typing in your commands directly to the mount 

Brian



On Tue, Sep 8, 2020 at 1:23 PM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Yes.

Rolando



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Tue, Sep 8, 2020 3:20 pm
Subject: Re: [ap-gto] GTOCP3 and serial

doesn't APCC have a built-in terminal? 



On Tue, Sep 8, 2020 at 1:19 PM drgert1 via groups.io <drgert1=yahoo.com@groups.io> wrote:
Ultimate plan is to use a serial Bluetooth dongle at the mount (AP1200 with GTOCP3 V2 chip).
But for now I just want to see that a text terminal program on the PC can talk to the GTOCP3 and get ASCII answers.

Cheers,
Gert


--
Brian 



Brian Valente



--
Brian 



Brian Valente


Re: GTOCP3 and serial

Roland Christen
 

Yes.

Rolando



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Tue, Sep 8, 2020 3:20 pm
Subject: Re: [ap-gto] GTOCP3 and serial

doesn't APCC have a built-in terminal? 



On Tue, Sep 8, 2020 at 1:19 PM drgert1 via groups.io <drgert1=yahoo.com@groups.io> wrote:
Ultimate plan is to use a serial Bluetooth dongle at the mount (AP1200 with GTOCP3 V2 chip).
But for now I just want to see that a text terminal program on the PC can talk to the GTOCP3 and get ASCII answers.

Cheers,
Gert


--
Brian 



Brian Valente


Re: GTOCP3 and serial

 

doesn't APCC have a built-in terminal? 



On Tue, Sep 8, 2020 at 1:19 PM drgert1 via groups.io <drgert1=yahoo.com@groups.io> wrote:
Ultimate plan is to use a serial Bluetooth dongle at the mount (AP1200 with GTOCP3 V2 chip).
But for now I just want to see that a text terminal program on the PC can talk to the GTOCP3 and get ASCII answers.

Cheers,
Gert



--
Brian 



Brian Valente


Re: GTOCP3 and serial

drgert1
 

Ultimate plan is to use a serial Bluetooth dongle at the mount (AP1200 with GTOCP3 V2 chip).
But for now I just want to see that a text terminal program on the PC can talk to the GTOCP3 and get ASCII answers.

Cheers,
Gert


Re: GTOCP3 and serial

Roland Christen
 

What are you testing?

Rolando

-----Original Message-----
From: drgert1 via groups.io <drgert1@...>
To: main@ap-gto.groups.io
Sent: Tue, Sep 8, 2020 2:01 pm
Subject: Re: [ap-gto] GTOCP3 and serial

Hi,

When I test this on the bench with the GOTCP3 (V2 chip) removed from the mount and disconnected from motors (AP1200), will it impair stored data on gear phase / PEM / disrupt operation once re-connected to the mount ??

Thanks,
Gert


Re: GTOCP3 and serial

drgert1
 

Hi,

When I test this on the bench with the GOTCP3 (V2 chip) removed from the mount and disconnected from motors (AP1200), will it impair stored data on gear phase / PEM / disrupt operation once re-connected to the mount ??

Thanks,
Gert


Re: GTOCP3 and serial

Roland Christen
 

Send :V# and you will get the version number back.

Rolando



-----Original Message-----
From: drgert1 via groups.io <drgert1@...>
To: main@ap-gto.groups.io
Sent: Mon, Sep 7, 2020 4:20 pm
Subject: [ap-gto] GTOCP3 and serial

Hello All,

I am in a mighty struggle with serial protocol. Esp. how many configurations there are that will make it not work.

Ultimate plan is to use a serial Bluetooth dongle at the mount (AP1200 with GTOCP3 V2 chip).

But for now I just want to see that a text terminal program on the PC can talk to the PC can talk to the GTOCP3 and get ASCII answers. And that's just my question. If I hook up the laptop to the GTOCP3 (the way I up to now always do) via serial cable and serial-to-USB adapter, is there a simple 'Hello' -> 'OK' conversation that I can have with the controller? Just so that I can see that communication is established. Something like an 'AT' ->'OK'. In plain ASCII. Using 'PuTTY' on the laptop. What's the procedure? I understand that the AP driver sends tons of data between the laptop and the mount. I don't even want to include the driver here. Just type on the keyboard, see the echo, hit a command + enter, and see the answer from the controller. (preferably a non-destructive command)

BTW, the BT adapter wants to know if the port is DCE or DTE. Can someone answer for the GTOCP3 ??

Thanks,
Gert


Re: Any feedback signal from a CP4 to APCC ?

Bill Long
 

Ive used APCC the entire time I have owned an AP mount. I got the standard edition with the coupon you get when you buy a new mount, and then upgraded it to pro. I have never found APCC to be lacking detail about error conditions at all. In fact it has thrown errors to me that pointed out some problems I caused quite a few times. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Joe Zeglinski <J.Zeglinski@...>
Sent: Monday, September 7, 2020 9:08 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Any feedback signal from a CP4 to APCC ?
 
Thanks Ray,
 
    You bring up some interesting conditions. However, there were no warning messages, since I would always immediately  react to them. In my case last night, I merely drifted along, thinking the mount was still tracking during the imaging, with no need to restart APCC.
 
    Seems like an easy way to pack up for the night – don’t even need to remember to Park the mount. Just set the “loss of mount comms” safety option for the mount to Park itself at its its usual Home position – and simply shut down Windows and walk away.
 
    But, you brought up some interesting nuances of the safety feature, which I was not aware of before, and will keep them in mind on future APCC sessions.
 
Joe Z.
 
From: Ray Gralak
Sent: Monday, September 7, 2020 8:03 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Any feedback signal from a CP4 to APCC ?
 
Hi Joe,

The mount could have stopped tracking if you had disconnected APCC from the mount for a while, then reconnected. The mount will stop tracking after the safety park timer expires unless you turn off Safety-Park in APCC. Reconnecting to the mount will then show the mount in the parked and "tracking off" state.

And you would have seen warning errors in APCC if it could not communicate with the mount. To see that behavior, try pulling the serial, USB, or Ethernet cable while APCC is running, assuming you are not using WiFi.

-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: Any feedback signal from a CP4 to APCC ?

Joe Zeglinski
 

Thanks Ray,
 
    You bring up some interesting conditions. However, there were no warning messages, since I would always immediately  react to them. In my case last night, I merely drifted along, thinking the mount was still tracking during the imaging, with no need to restart APCC.
 
    Seems like an easy way to pack up for the night – don’t even need to remember to Park the mount. Just set the “loss of mount comms” safety option for the mount to Park itself at its its usual Home position – and simply shut down Windows and walk away.
 
    But, you brought up some interesting nuances of the safety feature, which I was not aware of before, and will keep them in mind on future APCC sessions.
 
Joe Z.
 

From: Ray Gralak
Sent: Monday, September 7, 2020 8:03 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Any feedback signal from a CP4 to APCC ?
 
Hi Joe,

The mount could have stopped tracking if you had disconnected APCC from the mount for a while, then reconnected. The mount will stop tracking after the safety park timer expires unless you turn off Safety-Park in APCC. Reconnecting to the mount will then show the mount in the parked and "tracking off" state.

And you would have seen warning errors in APCC if it could not communicate with the mount. To see that behavior, try pulling the serial, USB, or Ethernet cable while APCC is running, assuming you are not using WiFi.

-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: Any feedback signal from a CP4 to APCC ?

Ray Gralak
 

Hi Joe,

The mount could have stopped tracking if you had disconnected APCC from the mount for a while, then reconnected. The mount will stop tracking after the safety park timer expires unless you turn off Safety-Park in APCC. Reconnecting to the mount will then show the mount in the parked and "tracking off" state.

And you would have seen warning errors in APCC if it could not communicate with the mount. To see that behavior, try pulling the serial, USB, or Ethernet cable while APCC is running, assuming you are not using WiFi.

-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 Joe Zeglinski
Sent: Monday, September 7, 2020 3:03 PM
To: ap-gto.groups.io
Subject: [ap-gto] Any feedback signal from a CP4 to APCC ?

Hi Ray,

Last night, for the first time, I found myself with my AP-1200 “Emergency Parked” while I was using SKY
CHARTS to position the mount for a photo. When I happened to glance at the bottom of the APCC window, I
noticed that Tracking was turned OFF. It must have been sitting at its last work position for quite a while. My first
thought was that I had photographed streaks from one of Elon Musks swarms in orbit. I assume it was the result
of “Loss of comms” CP4 time-out, with APCC – so the CP4 safely shut down the mount where it was. There was
nothing actually wrong with the CP4, and Unparking it let me retake the shot, and run the rest of the night problem
& error free..

We have been advised in the past, that the Handpad is a plain “send-only” comms terminal device, and doesn’t
receive data from the controller. However, I wonder if there is any other ( perhaps indirect) way of the APCC
realizing that it wasn’t being heard any longer by a CPx controller, so that the control program could flash up a
User Emergency Warning of this state. Perhaps a CPx “mount not-ready” signal. That would save a long night of
futile imaging, when nothing is permanently wrong.

Joe Z.


Re: GTOCP3 and serial

michaeljhanson@...
 

Hi Gert,

Since a PC is the "terminal", so the CPx is the data communications equipment, DCE.  A standard straight-through RS-232 cable is used from a computer or USB-to-serial-converter, to the unit.

We use dumb data terminal programs like TeraTerm and HyperTerm *ALL* the time, in exactly the manner you describe.  The command set has it's origins in the old LX200 textual command set, so it is easy to issue them manually for diagnostic purposes.  The command set is published on the AP web-site.  However, examples of commands I use regularly to determine if a unit is alive, "reachable", and that I am even using the correct comm port in the computer, include "read version"  :V# (three characters), and "read local time"  :GL# (4 characters).  You'll want the terminal emulator "local echo" enabled as the CPx does not "echo".

The moment you power up the unit, it will transmit a single character, "1".  That way you know the unit is powered and the embedded software is actually trying to doing something.  This may be the single most powerful diagnostic feature. The serial communication parameters are also published on the AP website.  But to summarize here for ease in setting up the terminal emulator:
9600 baud, No Parity, 8 bits, 1 stop bit, No handshake.  Occasionally, folks "complain" about the lack of parity, but the serial interface remains the most reliable by far.

Happy Hacking!

Regards,
Mike Hanson


Any feedback signal from a CP4 to APCC ?

Joe Zeglinski
 

Hi Ray,
 
    Last night, for the first time, I found myself with my AP-1200 “Emergency Parked” while I was using SKY CHARTS to position the mount for a photo. When I happened to glance at the bottom of the APCC window, I noticed that Tracking was turned OFF. It must have been sitting at its last work position for quite a while. My first thought was that I had photographed streaks from one of Elon Musks swarms in orbit.  I assume it was the result of “Loss of comms” CP4 time-out,  with APCC – so the CP4 safely shut down the mount where it was. There was nothing actually wrong with the CP4, and Unparking it let me retake the shot, and run the rest of the night problem & error free..
 
    We have been advised in the past, that the Handpad is a plain “send-only” comms terminal device, and doesn’t receive data from the controller. However, I wonder if there is any other ( perhaps indirect) way of the APCC realizing that it wasn’t being heard any longer by a CPx controller, so that the control program could flash up a User Emergency Warning of this state. Perhaps a CPx “mount not-ready” signal. That would save a long night of futile imaging, when nothing is permanently wrong.
 
Joe Z.

8301 - 8320 of 81313