APPM different with V1.9.0.9?


Rouz
 

Ok thank you Ray.

I pops up on some slews only. 

V1.9.0.11 is working perfectly for me too.

Thanks,

Rouz


Ray Gralak
 
Edited

Ok I just noticed it only appears with " Require high accuracy slews".
There is a tighter tolerance on coordinates when this checkbox is selected. There is no difference between 1.9.0.7 and 1.9.0.11 behavior in this regard. In fact, the final RA/Dec coordinates are returned up to 2 seconds sooner in 1.9.0.11. However, if they are slightly out of the tolerance (0.2 arc-secs) then the Slew Warning lasts as long as it always has since 1.9 was released. You probably didn't notice this when it happened before.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
Sent: Thursday, September 23, 2021 7:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM different with V1.9.0.9?

[Edited Message Follows]

Ok I just noticed it only appears with " Require high accuracy slews".

It takes 15 sec per point.
This is with V1.9.0.11.

Some points work fine and its only some point that have the warning.


Ray Gralak
 

Rouz,

I don’t see any warnings in the log snippet you included.

The SLEWUNSAFE commands are normal. A SLEWUNSAFE command is one that APCC should directly execute the slew without having to check for starting/ending counterweight position.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
Sent: Thursday, September 23, 2021 7:32 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM different with V1.9.0.9?

I'll be testing it tonight.

Does anyone know where these slew warnings come from:


0392354 2021-09-23 00:06:10.941: Info, ProcessVPortCommand, RX from VPort 1: :APCC,45352,GZ#
0392355 2021-09-23 00:06:10.941: Info, ProcessVPortCommand, APCC Seq= 45352, CMD=GZ#
0392356 2021-09-23 00:06:10.941: Info, VPortCheckVPort1(COM3), (RX: GZ#), TX:
APCC,13,45352,+343*30:59.7#
0392357 2021-09-23 00:06:10.942: Info, VPort1(COM3), RX:
:APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392358 2021-09-23 00:06:10.957: Info, ProcessVPortCommand, RX from VPort 1:
:APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392359 2021-09-23 00:06:10.957: Info, ProcessVPortCommand, APCC Seq= 45353,
CMD=*SLEWUNSAFE,15.5769238888889,78#
0392360 2021-09-23 00:06:10.965: Debug, Command Thread, TX=':GH#'|RX='07:00:25.79#'
0392361 2021-09-23 00:06:10.965: Debug, Command Thread, TX (High Priority) = ':RT3#'
0392362 2021-09-23 00:06:10.965: Debug, Command Thread, TX (High Priority) = ':RT2#'
0392363 2021-09-23 00:06:10.966: Debug, Command Thread, TX = ':pS#'
0392364 2021-09-23 00:06:10.973: Info, VPortCheckVPort1(COM3), (RX:
*SLEWUNSAFE,15.5769238888889,78#), TX:


Ray Gralak
 

Hi Rouz,

Do we know what causes the slew warning pause? Is that related to the bug.
Yes, as I mentioned earlier, an extra character in the RA response was causing an error converting RA to a useable value. Thus, even the mount slewed to the proper coordinates, the RA value (RA=0) did not match the expected RA value and, therefore, the "Slew Warning" and delay.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
Sent: Thursday, September 23, 2021 8:45 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM different with V1.9.0.9?

Hi Ray,

Glad to hear you found the bug.
I'll download the new one and try again when clear again.

Do we know what causes the slew warning pause? Is that related to the bug.

Thanks,

-Rouz,


Rouz
 
Edited

Ok I just noticed it only appears with " Require high accuracy slews".

It takes 15 sec per point.
This is with V1.9.0.11.

Some points work fine and its only some point that have the warning.


Rouz
 

I'll be testing it tonight.

Does anyone know where these slew warnings come from:

0392354 2021-09-23 00:06:10.941:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,45352,GZ#
0392355 2021-09-23 00:06:10.941:       Info, ProcessVPortCommand, APCC Seq=   45352, CMD=GZ#
0392356 2021-09-23 00:06:10.941:       Info, VPortCheckVPort1(COM3), (RX: GZ#), TX: APCC,13,45352,+343*30:59.7#
0392357 2021-09-23 00:06:10.942:       Info,    VPort1(COM3), RX: :APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392358 2021-09-23 00:06:10.957:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,45353,*SLEWUNSAFE,15.5769238888889,78#
0392359 2021-09-23 00:06:10.957:       Info, ProcessVPortCommand, APCC Seq=   45353, CMD=*SLEWUNSAFE,15.5769238888889,78#
0392360 2021-09-23 00:06:10.965:      Debug,  Command Thread, TX=':GH#'|RX='07:00:25.79#'
0392361 2021-09-23 00:06:10.965:      Debug,  Command Thread, TX (High Priority) = ':RT3#'
0392362 2021-09-23 00:06:10.965:      Debug,  Command Thread, TX (High Priority) = ':RT2#'
0392363 2021-09-23 00:06:10.966:      Debug,  Command Thread, TX = ':pS#'
0392364 2021-09-23 00:06:10.973:       Info, VPortCheckVPort1(COM3), (RX: *SLEWUNSAFE,15.5769238888889,78#), TX: 


R Botero
 

New version working just fine!
Thank you Ray.

Roberto


Bill Long
 

Nice and quick response to the issue! :) 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <iogroups@...>
Sent: Thursday, September 23, 2021 6:00 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM different with V1.9.0.9?
 
Hi Rouz,

Yes, there was a change to APPM to use the Real-time RADec feature to get the RA and Dec from the mount with less latency. The installed APCC Pro 1.9.0.9 has an extra character (":") in the RA string response, which is invalid, so it always returns RA=0. You can see this in the APPM logs.

This was confusing to me because this was a bug I had fixed before creating the release. When I retested this morning, I could reproduce the problem with the installer version of 1.9.0.9, but not with the debugger on my computer. They should have had the same behavior, so I think I must have missed a step in building the APPM release executable.

So, I apologize for the issue. I created a new version, 1.9.0.11, which I tested, fixes this issue:

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apastrosoftware.com%2Fapcc_download%2FAPCC_Pro_Setup_1.9.0.11.exe&amp;data=04%7C01%7C%7C63d31817c7e4488368bd08d97e921a8c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637679988244006680%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=k3%2FtMjarkmbSruortO0cyf%2BukA9febN%2Fo7%2BYADIP2q4%3D&amp;reserved=0

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
> Sent: Wednesday, September 22, 2021 9:32 PM
> To: main@ap-gto.groups.io
> Subject: [ap-gto] APPM different with V1.9.0.9?
>
> Hi Ray,
>
> Just installed V1.9.0.9 and running APPM again.
>
> The RA Delta figure getting larger and larger with every plateslove and then its fails.
>
> Im using ASTAP and NINA which working perfectly last week.
>
> I tried "Use last pate solve's offset as hint" on and off.
>
> I tried pointing model corrections on and off.
>
> Attached are the new APPM results:
>







 

>>> Is there a way you can cut/paste the east points data and not have to redo the entire thing?

afaik you can't add to or change a model (yet?) so you would need to rerun the model



On Thu, Sep 23, 2021 at 8:49 AM Rouz <rbidshahri@...> wrote:
Brian, glad it's working.

I wasn't able to finished the model before the clouds and just moved to the West Model before aborting.

Is there a way you can cut/paste the east points data and not have to redo the entire thing?


-Rouz,



--
Brian 



Brian Valente


Rouz
 

Brian, glad it's working.

I wasn't able to finished the model before the clouds and just moved to the West Model before aborting.

Is there a way you can cut/paste the east points data and not have to redo the entire thing?


-Rouz,


Rouz
 

Hi Ray,

Glad to hear you found the bug.
I'll download the new one and try again when clear again.

Do we know what causes the slew warning pause? Is that related to the bug.

Thanks,

-Rouz,


Mark Knogge
 

Ray,

That is exactly what I saw in the logs. Thanks for fixing so quickly.

Mark


 

Rouz thanks for chasing this one down

I went back and checked my model performance and you were right (obviously, since Ray issued an update)

I reloaded my model built with APPM 1.9.0.9 into 1.9.0.11 and it seems to be working correctly

Not sure if I need to rebuild the model though

On Thu, Sep 23, 2021 at 12:28 AM Rouz <rbidshahri@...> wrote:
I use a Dome but its a slave to Nina and not connected to APPM. So APPM doesn't really see the dome I believe.



--
Brian 



Brian Valente


Ray Gralak
 

Thank you for addressing this so fast. Will test the new version asap - possibly tonight.
Thank you, Roberto!

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of R Botero via groups.io
Sent: Thursday, September 23, 2021 6:03 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM different with V1.9.0.9?

Ray

Thank you for addressing this so fast. Will test the new version asap - possibly tonight.
Regards

Roberto


R Botero
 

Ray

Thank you for addressing this so fast.  Will test the new version asap - possibly tonight.
Regards

Roberto


Ray Gralak
 

Hi Rouz,

Yes, there was a change to APPM to use the Real-time RADec feature to get the RA and Dec from the mount with less latency. The installed APCC Pro 1.9.0.9 has an extra character (":") in the RA string response, which is invalid, so it always returns RA=0. You can see this in the APPM logs.

This was confusing to me because this was a bug I had fixed before creating the release. When I retested this morning, I could reproduce the problem with the installer version of 1.9.0.9, but not with the debugger on my computer. They should have had the same behavior, so I think I must have missed a step in building the APPM release executable.

So, I apologize for the issue. I created a new version, 1.9.0.11, which I tested, fixes this issue:

https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.9.0.11.exe

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
Sent: Wednesday, September 22, 2021 9:32 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM different with V1.9.0.9?

Hi Ray,

Just installed V1.9.0.9 and running APPM again.

The RA Delta figure getting larger and larger with every plateslove and then its fails.

Im using ASTAP and NINA which working perfectly last week.

I tried "Use last pate solve's offset as hint" on and off.

I tried pointing model corrections on and off.

Attached are the new APPM results:


Geoffrey Collins
 

I had similar trouble last month during the full moon when I was able to first test the new software version.  After a few nights when I could test before the moon rose, the mapping runs worked perfectly.  I have used the new tracking features and the tracking is better with the new software.


R Botero
 

Nothing to do with domes or specific setups. It’s a BUG in the new version of APPM. Stay with 1.9.0.7. 

Roberto


Rouz
 

I use a Dome but its a slave to Nina and not connected to APPM. So APPM doesn't really see the dome I believe.


Bill Long
 

Are any of you using domes? 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Rouz <rbidshahri@...>
Sent: Thursday, September 23, 2021 12:20 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM different with V1.9.0.9?
 
Yeah exactly the same issues here. 1.9.0.07 was working but unfortunately the clouds rolled in and I couldn't finished the model.

I was hoping on having the model done ready for the next session, clear nights are becoming rare now.