The camera is an ASI6200mm pro, and the frame size is already set to center 1/2. Just to be clear, this setup
has been working since the mount was installed here in August. Last night was the first problem occurrence.
I can try 1/3 and 1/4 Tuesday and report.

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of legendtrail via groups.io
Sent: Monday, March 7, 2022 7:46 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] PEMPro error msgs

Hello Ray,
The camera is an ASI6200mm pro, and the frame size is already set to center 1/2. Just to be clear, this setup
has been working since the mount was installed here in August. Last night was the first problem occurrence.
I can try 1/3 and 1/4 Tuesday and report.

Brian,

How much memory do you have on your machine?

I have experienced the same issue and unfortunately use Pempro only on a mission critical task of identifying the periodic error and programming the mount.  Even then, it is a huge hassle only using my ZWO 183 which has substantially less memory needs.   I recently upgraded my computer with more memory.  That may help.   Not sure.  I switched to Sharpcap for polar alignment. I was unsuccessful in getting Pempro to work with the 183.  Interesting thing is that it works until the last step or two where it fails.    The 183 works fine with sharpcap.

Maybe one day this whole industry will realize 64 bit is here to stay and adopt it. I wish Microsoft would do what
Apple did, and just declare 32 bit dead and move on. But every astro vendor points to every other vendor and
says "but see, most everyone is 32 bit, and we want to be sure we stay compatible". Makes me wonder ASCOM is
not still mostly 16 bit. And only supports Film. :(

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Tuesday, March 8, 2022 8:16 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] PEMPro error msgs

On Tue, Mar 8, 2022 at 11:06 AM, Emilio J. Robau, P.E. wrote:


I have experienced the same issue and unfortunately use Pempro only on a mission critical task of
identifying the periodic error and programming the mount. Even then, it is a huge hassle only using my ZWO 183
which has substantially less memory needs. I recently upgraded my computer with more memory. That may help.
Not sure. I switched to Sharpcap for polar alignment. I was unsuccessful in getting Pempro to work with the 183.
Interesting thing is that it works until the last step or two where it fails. The 183 works fine with sharpcap.

I was able, once, to push my way through using Pempro with the 2600 for PE, but was never able to get it to go all
the way through for polar alignment, even with smallest ROI and maximum binning, I had to continually
disconnect and reconnect as I went through steps, but near the last one it would fail and not be able to be
restarted.

Like APPM, Pempro will let you use another applications camera. i have not tried this, but if you have other
software that can control the camera, it may work around Pempro's memory limitations. I was able to use that with
32 bit TSX when I first got APPM, before it could use the 64 bit NINA (or now 64 bit TSX). See the dropdown
below.

Maybe one day this whole industry will realize 64 bit is here to stay and adopt it. I wish Microsoft would do what
Apple did, and just declare 32 bit dead and move on. But every astro vendor points to every other vendor and
says "but see, most everyone is 32 bit, and we want to be sure we stay compatible". Makes me wonder ASCOM is
not still mostly 16 bit. And only supports Film. :(

But should we REALLY need a 64-bit process to load an image with any amateur astro-ccd camera today? :-)

Well, it would appear the answer is "yes".  :) 

Oh... you said "should".  If we're going to ask how thing SHOULD work instead of how they DO work, can we discuss the US Tax code, Congress, and why refrigerators now need to be cloud connected?   :)  :) 

But time passes, technology improves.  When I first was writing programs we were cramming every tiny bit of information we could into minimal data size because a 60megabyte disk drive was the size of a washing machine.  As time went on, and we had gigabytes then terabytes, we stopped paying so much attention.  Efficiency went WAY down because the tricks and talent needed to keep being that efficient was no longer cost effective.   In just the last decade or two the average PC went from under 1GB to 8GB, maybe even now 16GB; my little NUC used for capture has 32GB, and it wasn't expensive.  Why limit each program to 2GB memory?

I'd argue that time has passed for 32 bit programs.  ZWO probably just thinks "what is wrong with these guys, who cares if it uses a gigabyte or not".  They are wrong, but they are getting less wrong all the time (if that's really their thought process as opposed to just being sloppy, which is where I would bet money).  And this ignores the fact many 32 bit programs DO work with ZWO big cameras. 

Astrophotography programs are still a bit stuck in the past.  Notice how practically everything still says "CCD" when very few (certainly new entrants into the field) have CCD's.  Lots of cottage industries that do not want to re-engineer software or hardware - I get it, it's expensive. Wouldn't surprise me to run across some program still written in Fortran or Cobol. 

But wouldn't it nice to never have people run into these memory issues?  

My 2 cents, worth probably much less than that.  :) 

Linwood

But wouldn't it nice to never have people run into these memory issues?

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Tuesday, March 8, 2022 6:38 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] PEMPro error msgs

On Tue, Mar 8, 2022 at 09:10 PM, Ray Gralak wrote:


But should we REALLY need a 64-bit process to load an image with any amateur astro-ccd camera today?
:-)

Well, it would appear the answer is "yes". :)

Oh... you said "should". If we're going to ask how thing SHOULD work instead of how they DO work, can we
discuss the US Tax code, Congress, and why refrigerators now need to be cloud connected? :) :)

But time passes, technology improves. When I first was writing programs we were cramming every tiny bit of
information we could into minimal data size because a 60megabyte disk drive was the size of a washing machine.
As time went on, and we had gigabytes then terabytes, we stopped paying so much attention. Efficiency went
WAY down because the tricks and talent needed to keep being that efficient was no longer cost effective. In just
the last decade or two the average PC went from under 1GB to 8GB, maybe even now 16GB; my little NUC used
for capture has 32GB, and it wasn't expensive. Why limit each program to 2GB memory?

I'd argue that time has passed for 32 bit programs. ZWO probably just thinks "what is wrong with these guys, who
cares if it uses a gigabyte or not". They are wrong, but they are getting less wrong all the time (if that's really their
thought process as opposed to just being sloppy, which is where I would bet money). And this ignores the fact
many 32 bit programs DO work with ZWO big cameras.

Astrophotography programs are still a bit stuck in the past. Notice how practically everything still says "CCD"
when very few (certainly new entrants into the field) have CCD's. Lots of cottage industries that do not want to re-
engineer software or hardware - I get it, it's expensive. Wouldn't surprise me to run across some program still
written in Fortran or Cobol.

But wouldn't it nice to never have people run into these memory issues?

My 2 cents, worth probably much less than that. :)

Linwood