Date   

Re: APPM fails on ASTAP plate solve

Ray Gralak
 

Hi Bryan,

Thanks for reporting this! The Bin=2 plate solve failed because the image was never created. This issue is fixed in this new APCC Pro beta build:

https://www.apastrosoftware.com/apcc_download/APCC_Pro_BETA_Setup_1.9.1.3.exe

-Ray

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Worsel via groups.io
Sent: Friday, October 22, 2021 9:10 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM fails on ASTAP plate solve

While related to the recent beta version of APPC, I thought a separate topic would be cleaner.

I am trying to get the beta version (APPC 1.9.1.1) to plate solve with ASTAP. The zipped APPM and APCC log files are attached; although I think the former is the more informative. I tinkered with many settings without success; so I closed APPM and restarted and ran the following to produce the 'short and sweet' version.

AP 1100GT (non-AE)
Permanent pier installation
QHY 367C (36 MP full-frame CMOS)
16 GB PC. Win 10 (64-bit)

Pre-test
Capture a FITS file in SharpCap and solve directly with ASTAP. No problems. 1.1s

Start APPM from APPC
Setup Camera and Plate Solve settings. Bin 1, 4s exposure. Min-star size= 1.5
Connect mount and camera (via ASCOM)
Run "Image Link Test" from Plate Solve Settings in APPM. NO problems. 1.5s
Run "Plate Solve" in Run tab of APPM. Plate Solve fails. Log says System OutofMemory issue.
Change binning to 2 in ASCOM and Camera Settings, thinking smaller files might help; although Task Manager shows plenty of un-used memory.
Plate Solve fails. DIFFERENT error. See log

Close out APPM and zip logs

Any insight appreciated.

Bryan


Re: APPM and ASTAP #APCC

Bill Conrad
 

Aygen:

I have not had any luck adjusting the parameters.
The ImageLink Test also fails. When the ImageLink Test dialog pops up, ASTAP has computed a FOV twice what it should be. If I enter the correct FOV in the dialog then ImageLink Test is successful.
I too will try Ray's beta version, but I can't until the first week of Nov.

BC


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

You were banned from the forum, what was the reason ? I understand they might have some rules with regards to "ask for support". However, what's the purpose of having a forum then ?

Would be very nice if I could find someone using the same softwares. It couldn't hurt to exchange with people using the same gear / softwares. 

Something that I still don't understand (I am not a software developer, and still) : by changing the regional settings in W10, why am I no longer able to fully access all the setting of the automation software ? This sounds strange to me since people are using it all over the world. Again, I am not a soft developer, but I would have thought that by "tricking" the system with such regional settings, it could just work - but I am probably wrong.

Coming back to my initial issue, I will install later one of the former versions and give it a go. And then, we can take it from there. 

Thank you anyway for your kind advice, much appreciated !

Aygen

Le sam. 23 oct. 2021 à 16:37, ap@... <ap@...> a écrit :

Erkaslan Aygen wrote:

 

  • Yes, that's Voyager. Indeed, one of my first step was to ask for Voyager's support. They are always supportive, but they also told me that the issue is not related to Voyager but with the AP driver. Also, I was strongly advised not to change any regional settings.... anyway. Since I am not an expert, I am open to any help / suggestions. I can't just "sit and complain". That's why I am applying thoroghougly Ray's recommendations - at least I am trying someting :)


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

ap@CaptivePhotons.com
 

Erkaslan Aygen wrote:

 

  • Yes, that's Voyager. Indeed, one of my first step was to ask for Voyager's support. They are always supportive, but they also told me that the issue is not related to Voyager but with the AP driver. Also, I was strongly advised not to change any regional settings.... anyway. Since I am not an expert, I am open to any help / suggestions. I can't just "sit and complain". That's why I am applying thoroghougly Ray's recommendations - at least I am trying someting :)

_._,_._,_

I looked at Voyager briefly, asked where is the 64 bit version, and was instantly banned from the forums by Leo.   Let's say I am glad the support attitude at AP is more mature, as is NINA's.  😊

 

I wonder though if you can find someone in your same scenario (same gear, region) maybe on their forum.  I realize Leo is not receptive to support issues on the forum, but if you could find someone else using the same software and APPC and in the same region that is working, you might message them and ask if they can discuss with you outside the forums.   Or if you are on Astrobin, their search may let you find someone using both from their photos.

 

Voyager is pretty widely used, as is APCC, and it just seems likely someone else has either hit this problem, or by comparing notes you can find out what's different for you.

 

I wish I had better advice.  It does indeed sound frustrating.

 

Linwood

 


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Yes, that's Voyager. Indeed, one of my first step was to ask for Voyager's support. They are always supportive, but they also told me that the issue is not related to Voyager but with the AP driver. Also, I was strongly advised not to change any regional settings.... anyway. Since I am not an expert, I am open to any help / suggestions. I can't just "sit and complain". That's why I am applying thoroghougly Ray's recommendations - at least I am trying someting :)


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Thank you Ray, you're right regarding APCC - don't know why I uninstalled it (maybe due to some irritations...).

Keep you posted.

Regards,
Aygen

Le sam. 23 oct. 2021 à 01:10, Ray Gralak <iogroups@...> a écrit :
Hi Aygen,

First, you don't need to uninstall APCC, as it is not the problem. In fact, APCC identified a hidden problem!!

You can configure the ASCOM driver to communicate directly with the mount instead of APCC. This will take APCC completely out of the loop.

BTW, you might want to try each of these versions to see if any work with your Windows Enterprise o/s:

AstroPhysics V2 Setup v5.21.01
AstroPhysics V2 Setup v5.20.09

These two do not support TCP:
AstroPhysics V2 Setup v5.09.09
AstroPhysics V2 Setup v5.09.07

You can download those from here:

https://www.gralak.com/apdriver/

And that error message is generated when there is no network response from the mount. If you see one occasionally, it is probably just network congestion, and you can ignore it. However, if it happens often, it could be a sign that the local network is not very reliable.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Friday, October 22, 2021 3:35 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"
>
> So, all updates installed correctly.
>
> I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating.
> Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and
> as mentioned, by doing this, I have only limited access to my automated software.
>
> Honestly, I don't know what to do anymore. For the time being, I will test only with the AP driver (APCC
> uninstalled) and see what result I can get.
>
> Last, what might cause the below message (first time I got it) ?
>
>
>







APPM fails on ASTAP plate solve

Worsel
 

While related to the recent beta version of APPC, I thought a separate topic would be cleaner.

I am trying to get the beta version (APPC 1.9.1.1) to plate solve with ASTAP.  The zipped APPM and APCC log files are attached; although I think the former is the more informative.  I tinkered with many settings without success; so I closed APPM and restarted and ran the following to produce the 'short and sweet' version.

AP 1100GT (non-AE)
Permanent pier installation
QHY 367C (36 MP full-frame CMOS)
16 GB PC. Win 10 (64-bit)

Pre-test
Capture a FITS file in SharpCap and solve directly with ASTAP.  No problems. 1.1s

Start APPM from APPC
Setup Camera and Plate Solve settings. Bin 1, 4s exposure. Min-star size= 1.5
Connect mount and camera (via ASCOM)
Run "Image Link Test" from Plate Solve Settings in APPM.  NO problems. 1.5s
Run "Plate Solve" in Run tab of APPM. Plate Solve fails.  Log says System OutofMemory issue. 
Change binning to 2 in ASCOM and Camera Settings, thinking smaller files might help; although Task Manager shows plenty of un-used memory.
Plate Solve fails. DIFFERENT error.  See log

Close out APPM and zip logs

Any insight appreciated.

Bryan







Re: Mach2 DEC axis movement.

Wei-Hao
 

Hi,

I kind of wonder if an equivalent adjustment can be done for RA.


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Ray Gralak
 

Hi Aygen,

First, you don't need to uninstall APCC, as it is not the problem. In fact, APCC identified a hidden problem!!

You can configure the ASCOM driver to communicate directly with the mount instead of APCC. This will take APCC completely out of the loop.

BTW, you might want to try each of these versions to see if any work with your Windows Enterprise o/s:

AstroPhysics V2 Setup v5.21.01
AstroPhysics V2 Setup v5.20.09

These two do not support TCP:
AstroPhysics V2 Setup v5.09.09
AstroPhysics V2 Setup v5.09.07

You can download those from here:

https://www.gralak.com/apdriver/

And that error message is generated when there is no network response from the mount. If you see one occasionally, it is probably just network congestion, and you can ignore it. However, if it happens often, it could be a sign that the local network is not very reliable.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
Sent: Friday, October 22, 2021 3:35 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

So, all updates installed correctly.

I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating.
Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and
as mentioned, by doing this, I have only limited access to my automated software.

Honestly, I don't know what to do anymore. For the time being, I will test only with the AP driver (APCC
uninstalled) and see what result I can get.

Last, what might cause the below message (first time I got it) ?



Re: Setting Up APCC with Ethernet Only #APCC

Thomas Giannaccini
 

Thank you Dale

Tom

On Fri, Oct 22, 2021 at 6:59 PM Dale Ghent <daleg@...> wrote:

This VCP is still required for the A-P ASCOM driver to talk to APCC. It is then APCC that talks directly to the mount's CP over the chosen transport (USB/Serial, ethernet, wifi)

> On Oct 22, 2021, at 18:55, Thomas Giannaccini <tgiann3@...> wrote:
>
> I plan to only connect my laptop to my AP 1100 GTO w/ AE via Ethernet cable. Do I still need to create virtual COM ports in the initial setup? I'm guessing that I can easily change this later but am trying to keep things streamlined.
>
> Thank you in advance!
>
> Tom
> --
> CN: HasAnyoneSeenMyNeblua
>







--
CN: HasAnyoneSeenMyNeblua


Re: Setting Up APCC with Ethernet Only #APCC

Dale Ghent
 

This VCP is still required for the A-P ASCOM driver to talk to APCC. It is then APCC that talks directly to the mount's CP over the chosen transport (USB/Serial, ethernet, wifi)

On Oct 22, 2021, at 18:55, Thomas Giannaccini <tgiann3@...> wrote:

I plan to only connect my laptop to my AP 1100 GTO w/ AE via Ethernet cable. Do I still need to create virtual COM ports in the initial setup? I'm guessing that I can easily change this later but am trying to keep things streamlined.

Thank you in advance!

Tom
--
CN: HasAnyoneSeenMyNeblua


Setting Up APCC with Ethernet Only #APCC

Thomas Giannaccini
 

I plan to only connect my laptop to my AP 1100 GTO w/ AE via Ethernet cable. Do I still need to create virtual COM ports in the initial setup? I'm guessing that I can easily change this later but am trying to keep things streamlined. 

Thank you in advance!

Tom
--
CN: HasAnyoneSeenMyNeblua


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

ap@CaptivePhotons.com
 

Erkaslan Aygen wrote:

 

  • I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating. Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and as mentioned, by doing this, I have only limited access to my automated software. 

That's Voyager, right?  I am not a Voyager user, but I understand a lot of AP users are.  Have you asked Voyager support about the situation?  The data being rejected comes from Voyager, right?

 

 


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

So, all updates installed correctly. 

I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating. Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and as mentioned, by doing this, I have only limited access to my automated software. 

Honestly, I don't know what to do anymore. For the time being, I will test only with the AP driver (APCC uninstalled) and see what result I can get. 

Last, what might cause the below message (first time I got it) ?


Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Hi Ray,

I have some Windows updates pending and one pertaining to ".NET 4.8.... I am about to install them.

BTW, I am currently running some tests since I upgraded one of my refractor and guess what ? My automation software is triggering error messages following the regional settings change ! This is just insane and irritating :(

Fingers crossed that W10 updates / .NET 4.8 could solve all this mess.

Regards,
Aygen



Le ven. 22 oct. 2021 à 15:42, Ray Gralak <iogroups@...> a écrit :
Hi Aygen,

> the AP driver using decimal comas rather than a normal "." while sending command, then :

Thank you for summarizing and agreeing with my original assessment of the issue. I will be looking into the globalization issue with the specific version of Windows Enterprise that you are using.

BTW, have you applied all available updates to Windows and the .NET 4.8 Framework? If not, it is essential that you do. The AP V2 ASCOM driver is written in VB6, and there have been issues with some Windows updates that have been fixed in later updates. Here is one example:

https://www.zdnet.com/article/microsoft-these-windows-10-updates-fix-broken-visual-basic-apps-but-not-for-1903/

-Ray


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Friday, October 22, 2021 1:15 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"
>
> Good morning all,
>
> Finally my problem seems to be solved. Should you ever happen to experience similars issues, i.e. the AP
> driver using decimal comas rather than a normal "." while sending command, then :
>
>
>
> 1.    Simply open the regional settings and change the region. In my case, I live in Switzerland. What I did, I
> choose "USA".
> 2.    By doing so, Windows will automatically update the regional settings, including "replacing the comas
> with a dot".
>
> As per my yesterday tests, the problem seemed to be solved since no error message was shown in APCC nor
> in Voyager !
>
> Thank you all for your kind support.
>
> Regards,
> Aygen
>







Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Dale Ghent
 


Big thanks to Ray for implementing this option. I'm going to be fleshing out the dec-arc integration for my NINA plugin over the next week.




On Oct 22, 2021, at 15:15, Seb@stro <sebastiendore1@...> wrote:

Hello Ray,

Re 3D viewer, a quick test confirmed it now tracks the movements on my Mach2 (FW: VCP5-P02-10 if that matters) with clutches disengaged. 

Will test the APPM/ASTAP enhancement next time I get a chance to do a real mapping run, but I can already tell the solving time I now get with the NINA camera simulator (which shouldn't be that much different with my own camera assuming correct exposure and solver settings) has improved by 10 times, from 5 sec to 0.5 sec per point ! 🙂

Also I don't know if it has something to do with it (or if a recent intempestive Win10 update or something else fixed it) but I also got the "Refresh COM Ports" in APCC working with this version, which never did for me before (always had to restart APCC when I managed to create COM ports conflicts somehow). 

That plus the continued DEC-Arc modeling integration effort with NINA's feature set makes very good reasons for that version to be loved, as far as I am concerned.

Thanks for this update. I for one much appreciate it. 

Sébastien


Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Sébastien Doré
 

Hello Ray,

Re 3D viewer, a quick test confirmed it now tracks the movements on my Mach2 (FW: VCP5-P02-10 if that matters) with clutches disengaged

Will test the APPM/ASTAP enhancement next time I get a chance to do a real mapping run, but I can already tell the solving time I now get with the NINA camera simulator (which shouldn't be that much different with my own camera assuming correct exposure and solver settings) has improved by 10 times, from 5 sec to 0.5 sec per point ! 🙂

Also I don't know if it has something to do with it (or if a recent intempestive Win10 update or something else fixed it) but I also got the "Refresh COM Ports" in APCC working with this version, which never did for me before (always had to restart APCC when I managed to create COM ports conflicts somehow). 

That plus the continued DEC-Arc modeling integration effort with NINA's feature set makes very good reasons for that version to be loved, as far as I am concerned.

Thanks for this update. I for one much appreciate it. 

Sébastien


Re: APPM and ASTAP #APCC

Erkaslan Aygen
 

Hi Ray,

This was with the official version (not the beta). I could give it try tonight with the beta.

Aygen

Le ven. 22 oct. 2021 à 15:48, Ray Gralak <iogroups@...> a écrit :
Hi Aygen,

> I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
> using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.

Is this with version 1.9.0.11, or the new version 1.9.1.1 beta with a fix?

https://www.apastrosoftware.com/apcc_download/APCC_Pro_BETA_Setup_1.9.1.1.exe

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Friday, October 22, 2021 1:23 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM and ASTAP #APCC
>
> Hi Bill,
>
> Did you have any success while changing the settings ?
>
> I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
> using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.
>
> I did increase the "min star" size to 1.5 (for example), but it didn't change my situation.
>
> As for my equipment :
>
>
> *     ASI 2600 MM PRO used with a TAK FSQ 85 (2.73 resolution)
>
> Cheers,
> Aygen
>







Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Thank you, Ray, for your kind suggestions regarding W10 updates. I need to have look at just to make sure that I have the key updates.

Aygen


Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Ray Gralak
 

Thanks, Linwood, for giving the beta a try! I'm glad the new APPM version solved the ASTAP problem.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Thursday, October 21, 2021 5:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Ray Gralak wrote:



APCC Pro - APPM - Add check box to ASTAP plate solve configuration to use FITS header for RA, Dec,
and image scale.



I had a bit of time waiting for dark so I ran the prior and beta through 2-3 points in a "run" from APPM (not just
the plate solve).



As best I can tell it worked perfectly. Here is the log in the old version:



0000390 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, Solve() called.

0000391 2021-10-21 19:37:46.472: Error, ASTAP Plate Solve, Failed to get FITS dimensions
(NAXIS1/NAXIS2)

0000392 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, StartSolve: application path: c:/program
files/astap/astap.exe

0000393 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, StartSolve: arguments: -f
"C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-193634.txt-0002-RA_20.213-
DEC_-41.000.fit" -ra 20.1891585182137 -spd 48.9385895224573 -fov 0 -s 1000 -r 5

0000394 2021-10-21 19:37:46.488: Info, ASTAP Plate Solve, ASTAP is still running.

0000395 2021-10-21 19:37:46.640: Info, State Machine, Entering State=PlateSolveWait

0000396 2021-10-21 19:37:46.702: Info, ASTAP Plate Solve, ASTAP is still running.

0000397 2021-10-21 19:37:46.905: Info, ASTAP Plate Solve, ASTAP is still running.

0000398 2021-10-21 19:37:47.109: Info, ASTAP Plate Solve, ASTAP is still running.

0000399 2021-10-21 19:37:47.311: Info, ASTAP Plate Solve, ASTAP is still running.

0000400 2021-10-21 19:37:47.514: Info, ASTAP Plate Solve, ASTAP is still running.

0000401 2021-10-21 19:37:47.718: Info, ASTAP Plate Solve, ASTAP has exited.

0000402 2021-10-21 19:37:47.718: Info, ASTAP Results, Results Filename =
C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-193634.txt-0002-RA_20.213-
DEC_-41.000.ini

0000403 2021-10-21 19:37:47.719: Info, ASTAP Results, PLTSOLVD=T

0



Note the "-fov 0" which causes a couple of extra loops, and the "failed to get FITS dimensions".



In the new version:



0000531 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Init

0000532 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Solve() called.

0000533 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Image scale (arc-secs/pixel): X =
0.793280434129994, Y = 0.793280434129994

0000534 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, NAXIS1/NAXIS2 (pixels) = 4784 / 3194, Image
dimensions X/Y (degrees) = 1.03062828266667 / 0.688090872666667

0000535 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, StartSolve: application path: c:/program
files/astap/astap.exe

0000536 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, StartSolve: arguments: -f
"C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-194002.txt-0001-RA_20.468-
DEC_26.570.fit" -ra 20.4524913831812 -spd 116.499133899902 -fov 0.688090872666667 -s 1000 -r 5

0000537 2021-10-21 19:40:50.160: Info, ASTAP Plate Solve, ASTAP is still running.

0000538 2021-10-21 19:40:50.334: Info, State Machine, Entering State=PlateSolveWait

0000539 2021-10-21 19:40:50.365: Info, ASTAP Plate Solve, ASTAP is still running.

0000540 2021-10-21 19:40:50.568: Info, ASTAP Plate Solve, ASTAP is still running.

0000541 2021-10-21 19:40:50.771: Info, ASTAP Plate Solve, ASTAP has exited.

0000542 2021-10-21 19:40:50.771: Info, ASTAP Results, Results Filename =
C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-194002.txt-0001-RA_20.468-
DEC_26.570.ini

0000543 2021-10-21 19:40:50.772: Info, ASTAP Results, PLTSOLVD=T



In this it has a calculated fov and no error. The solve time was fast in both cases, but did improve from 1.25s
to 0.62s.



I didn't have time to do a full model but let it run a couple points and all looked good.



Thank you.



Linwood



6441 - 6460 of 88836