|
Re: Close up of M81 without CCDT67
Dale Ghent
I wouldn't use tape. It's prone to turning out to be a mess, has a high chance of not being perfectly circular, and yea the adhesive could have an effect on the coating.
toggle quoted messageShow quoted text
I would have a mask 3D printed and placed over the mirror, with it affixed to the inside wall of the OTA. A bunch of imagers I run with have started making these to mask out the mirror clips on their newtonians. If that's not doable, maybe work with a local sign maker who can accurately size and cleanly cut a mask from a rigid, thin material that does not shed particles. Should be easy if you just want to hide the edges.
On Feb 14, 2020, at 10:56 PM, Robert Chozick via Groups.Io <rchozick=aol.com@groups.io> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Robert Chozick
If I were to attempt to mask the edge what kind of tape can you use that wouldn’t harm the coatings?
toggle quoted messageShow quoted text
Robert
On Feb 14, 2020, at 8:40 PM, Robert Chozick via Groups.Io <rchozick@...> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Robert Chozick
Can you start making some smaller RC’s😀Thanks for the suggestion. One of the problems is how sensitive the CMOS cameras are. It is very easy to blow out stars. With my FSQ at f/5 I can’t shoot over 2 1/2 -3 minutes before bright stars are blown.
toggle quoted messageShow quoted text
I worked hard on my collimation and it seems to have paid off. I bought a focuser collimation ring and used a laser to collimate. Robert
On Feb 14, 2020, at 4:56 PM, uncarollo2 <chris1011@...> via Groups.Io <chris1011@...> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Roland Christen
I like the resolution on that Running Man image. Very nice.
Try masking down the outer 1/8 inch of the mirror, see if that reduces the spray of light around the brightest stars. If that works, think about adding a disc in front of the mirror with a diameter perhaps 1/4 inch smaller than the mirror.
I have seen this on all Russian RCs (RC Optical scopes) where a disc of slightly smaller aperture really helped. Most of the RC mirrors from Lomo had turned edge and were only spec'd to 95% of the full aperture. The very outer part produced a heavy spray of light around bright stars.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 3:47 pm Subject: Re: [ap-gto] Close up of M81 without CCDT67 So, would you say the new advantages of the small pixel CMOS cameras is that they bring high sensitivity to small pixels?
I also got a shot of the Running Man with the 1600mm setup:
I got M101 at 1600 but the seeing was worse and guiding not as good.
Robert
On Feb 14, 2020, at 3:10 PM, uncarollo2 via Groups.Io <chris1011@...> wrote:
You are running 0.6 arc sec per pixel, which to me is not oversampling for high resolution imaging. In fact, for galaxies i prefer 0.3 to 0.4 arc sec per pixel which really brings out fine detail. My 17"F8 astrograph and the QSI 683 has such pixel scale and really does a superb job on small faint galaxies, even here in Northern Illinois. You have to have good tracking, of course, and on the best nights I can get below 0.15 arc sec RMS with the 1600 encoder mount.
I see a lot of images that are way undersampled (3 to 4 arc sec per pixel) with poor guiding that produces thick stars and very little resolution. To me these images resemble Brownie camera snapshots versus images taken with an 8x10 view camera. (shows my age, doesn't it) :^))
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 2:14 pm Subject: Re: [ap-gto] Close up of M81 without CCDT67 Thanks Roland. My last dark sky outing was my first use of this scope and camera. I am really confused on the whole image scale question. I bought this camera because it has the largest pixels of any of the CMOS cameras. The image scale is .6 with this camera and 1600mm. My scale is about 1.8 with my FSQ 106 - 530mm. If the recommended guidance of a scale of 1-2 for image scale is used the 1600mm should be too small an image scale. Most CMOS cameras have only 2.5-3.5 micron pixels vs 4.63 on my ASI294. Is oversampling bad? The .6 scale in my image sure looks ok. What about .4 or .3? I intentionally did not get larger than a 1600mm focal length because of this issue (and yes, guiding issues are not as bad vs 2000 and over). Everyone asks why I got an 8 RC instead of a 10 or 12 inch RC. The above reason is why. Each new CMOS camera that comes out still has really small pixels. How good would 2.5 micron pixels look on a 2500 mm scope?
Robert
On Feb 14, 2020, at 1:18 PM, uncarollo2 via Groups.Io <chris1011@...> wrote:
That's really nice. Sharp and great color.
A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 12:06 am Subject: [ap-gto] Close up of M81 without CCDT67 I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
|
|
|
|
Re: 1200GTO worm gear thrust washer?
Roland Christen
Tighten it hand tight (do not apply too much pressure, we use between 10 and 15 inch-Lb.). Then add a drop of superglue on the outside of the threads.
If you ever need to loosen it for any reason, it will be easy to unscrew after applying a bit of acetone to the glue spot.
Rolando
-----Original Message-----
From: Mike Shade <mshade@q.com> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 3:32 pm Subject: [ap-gto] 1200GTO worm gear thrust washer? The flat washer, the one with
two holes on it at the end of the worm shaft (under the little screw on cover) continues
to loosen up causing some degree of backlash. It has done it for both RA and
DEC. Any ideas how to tighten this properly and prevent it from doing this in
the future?
Mike J. Shade: mshade@q.com
Mike J. Shade Photography:
In War: Resolution
In Defeat: Defiance
In Victory: Magnanimity
In Peace: Goodwill
Sir Winston Churchill
Already, in the gathering dusk, a few of the stars are turning
on their lights.
Vega, the brightest one, is now dropping towards the west. Can
it be half
a year since I watched her April rising in the east? Low in the
southwest
Antares blinks a sad farwell to fall...
Leslie Peltier, Starlight Nights
International Dark Sky Association: www.darksky.org
|
|
|
|
Re: Close up of M81 without CCDT67
Stuart <stuart.j.heggie@...>
Robert, these are both super shots but the Running Man is my favorite for sure. Stuart Heggie
On Fri, 14 Feb 2020 at 16:47, Robert Chozick via Groups.Io <rchozick=aol.com@groups.io> wrote:
--
Stuart http://www.astrofoto.ca/stuartheggie/
|
|
|
|
Re: Close up of M81 without CCDT67
Robert Chozick
So, would you say the new advantages of the small pixel CMOS cameras is that they bring high sensitivity to small pixels?
toggle quoted messageShow quoted text
I also got a shot of the Running Man with the 1600mm setup: I got M101 at 1600 but the seeing was worse and guiding not as good. Robert
On Feb 14, 2020, at 3:10 PM, uncarollo2 via Groups.Io <chris1011@...> wrote: You are running 0.6 arc sec per pixel, which to me is not oversampling for high resolution imaging. In fact, for galaxies i prefer 0.3 to 0.4 arc sec per pixel which really brings out fine detail. My 17"F8 astrograph and the QSI 683 has such pixel scale and really does a superb job on small faint galaxies, even here in Northern Illinois. You have to have good tracking, of course, and on the best nights I can get below 0.15 arc sec RMS with the 1600 encoder mount.
I see a lot of images that are way undersampled (3 to 4 arc sec per pixel) with poor guiding that produces thick stars and very little resolution. To me these images resemble Brownie camera snapshots versus images taken with an 8x10 view camera. (shows my age, doesn't it) :^))
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 2:14 pm Subject: Re: [ap-gto] Close up of M81 without CCDT67 Thanks Roland. My last dark sky outing was my first use of this scope and camera. I am really confused on the whole image scale question. I bought this camera because it has the largest pixels of any of the CMOS cameras. The image scale is .6 with this camera and 1600mm. My scale is about 1.8 with my FSQ 106 - 530mm. If the recommended guidance of a scale of 1-2 for image scale is used the 1600mm should be too small an image scale. Most CMOS cameras have only 2.5-3.5 micron pixels vs 4.63 on my ASI294. Is oversampling bad? The .6 scale in my image sure looks ok. What about .4 or .3? I intentionally did not get larger than a 1600mm focal length because of this issue (and yes, guiding issues are not as bad vs 2000 and over). Everyone asks why I got an 8 RC instead of a 10 or 12 inch RC. The above reason is why. Each new CMOS camera that comes out still has really small pixels. How good would 2.5 micron pixels look on a 2500 mm scope?
Robert
On Feb 14, 2020, at 1:18 PM, uncarollo2 via Groups.Io <chris1011@...> wrote:
That's really nice. Sharp and great color.
A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 12:06 am Subject: [ap-gto] Close up of M81 without CCDT67 I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
Robert Chozick
|
|
|
|
1200GTO worm gear thrust washer?
Mike Shade
The flat washer, the one with two holes on it at the end of the worm shaft (under the little screw on cover) continues to loosen up causing some degree of backlash. It has done it for both RA and DEC. Any ideas how to tighten this properly and prevent it from doing this in the future?
Mike J. Shade: mshade@q.com Mike J. Shade Photography:
In War: Resolution In Defeat: Defiance In Victory: Magnanimity In Peace: Goodwill Sir Winston Churchill Already, in the gathering dusk, a few of the stars are turning on their lights. Vega, the brightest one, is now dropping towards the west. Can it be half a year since I watched her April rising in the east? Low in the southwest Antares blinks a sad farwell to fall... Leslie Peltier, Starlight Nights
International Dark Sky Association: www.darksky.org
|
|
|
|
Re: Close up of M81 without CCDT67
Roland Christen
You are running 0.6 arc sec per pixel, which to me is not oversampling for high resolution imaging. In fact, for galaxies i prefer 0.3 to 0.4 arc sec per pixel which really brings out fine detail. My 17"F8 astrograph and the QSI 683 has such pixel scale and really does a superb job on small faint galaxies, even here in Northern Illinois. You have to have good tracking, of course, and on the best nights I can get below 0.15 arc sec RMS with the 1600 encoder mount.
I see a lot of images that are way undersampled (3 to 4 arc sec per pixel) with poor guiding that produces thick stars and very little resolution. To me these images resemble Brownie camera snapshots versus images taken with an 8x10 view camera. (shows my age, doesn't it) :^))
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 2:14 pm Subject: Re: [ap-gto] Close up of M81 without CCDT67 Thanks Roland. My last dark sky outing was my first use of this scope and camera. I am really confused on the whole image scale question. I bought this camera because it has the largest pixels of any of the CMOS cameras. The image scale is .6 with this camera and 1600mm. My scale is about 1.8 with my FSQ 106 - 530mm. If the recommended guidance of a scale of 1-2 for image scale is used the 1600mm should be too small an image scale. Most CMOS cameras have only 2.5-3.5 micron pixels vs 4.63 on my ASI294. Is oversampling bad? The .6 scale in my image sure looks ok. What about .4 or .3? I intentionally did not get larger than a 1600mm focal length because of this issue (and yes, guiding issues are not as bad vs 2000 and over). Everyone asks why I got an 8 RC instead of a 10 or 12 inch RC. The above reason is why. Each new CMOS camera that comes out still has really small pixels. How good would 2.5 micron pixels look on a 2500 mm scope?
Robert
On Feb 14, 2020, at 1:18 PM, uncarollo2 via Groups.Io <chris1011@...> wrote:
That's really nice. Sharp and great color.
A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 12:06 am Subject: [ap-gto] Close up of M81 without CCDT67 I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
|
|
|
|
Re: Close up of M81 without CCDT67
Roland Christen
In my experience when I was using my 10" F14 Mak-Cass under very good seeing conditions I was able to resolve tiny doubles separated by 0.8 arc seconds in a deep sky image with a 7.5 micron pixel camera (ST10). If that's the case, then the same aperture at F7 could do this with a 3.75 micron pixel camera.
That's close to a 1600mm focal length. To me that would be a sweet spot for imaging at high resolution.
Rolando
-----Original Message-----
From: Dale Ghent <daleg@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 1:37 pm Subject: Re: [ap-gto] Close up of M81 without CCDT67 Perhaps... probably would be fine. The 2.5-5um pixel size range of the common CMOS sensors these days will demand good seeing at that kind of focal length, but it's workable. What I would do is always image at 1x1and bin in post-processing (PixInsight's IntegerResample process, for example) on an as-needed basis if the pixel scale needs to be worked up a little due to the conditions. 1600 would be great for detail studies of all kinds of nebula, too. For reference, Robert's camera sports 4.63um pixels. I have the same one, but QHY's version of it, and its Sony IMX294 is a really nice and super clean 4/3 format, 14 bit sensor with dual gain modes. > On Feb 14, 2020, at 2:18 PM, uncarollo2 <chris1011@...> via Groups.Io <chris1011@...> wrote: > > That's really nice. Sharp and great color. > > A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies. > > Rolando > > > > -----Original Message----- > From: Robert Chozick via Groups.Io <rchozick@...> > To: main <main@ap-gto.groups.io> > Sent: Fri, Feb 14, 2020 12:06 am > Subject: [ap-gto] Close up of M81 without CCDT67 > > I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm. > > https://pbase.com/image/170419535 > > Robert Chozick > rchozick@... > > > >
|
|
|
|
Re: Close up of M81 without CCDT67
Dale Ghent
How good would 2.5um pixels look on a 2.5m focal length at 0.21"/pixel? Pretty good provided you have the extra time that will be required to expose the target and if "normal" seeing for you is also in the realm of "pretty good." You'll certainly have the roundest stars on the block, assuming your mount and other mechanics are also up to the task.
toggle quoted messageShow quoted text
Oversampling isn't inherently bad if you're blessed with time and stability. Most people in that situation would start at 2x2 binning, maybe 3x3... at which point you must ask yourself if you're really using the right tool for the job because you would be paying for a lot of sensor real estate that is being used just to make up for the time and conditions.
On Feb 14, 2020, at 3:14 PM, Robert Chozick via Groups.Io <rchozick=aol.com@groups.io> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Robert Chozick
Thanks Roland. My last dark sky outing was my first use of this scope and camera. I am really confused on the whole image scale question. I bought this camera because it has the largest pixels of any of the CMOS cameras. The image scale is .6 with this camera and 1600mm. My scale is about 1.8 with my FSQ 106 - 530mm. If the recommended guidance of a scale of 1-2 for image scale is used the 1600mm should be too small an image scale. Most CMOS cameras have only 2.5-3.5 micron pixels vs 4.63 on my ASI294. Is oversampling bad? The .6 scale in my image sure looks ok. What about .4 or .3? I intentionally did not get larger than a 1600mm focal length because of this issue (and yes, guiding issues are not as bad vs 2000 and over). Everyone asks why I got an 8 RC instead of a 10 or 12 inch RC. The above reason is why. Each new CMOS camera that comes out still has really small pixels. How good would 2.5 micron pixels look on a 2500 mm scope?
toggle quoted messageShow quoted text
Robert
On Feb 14, 2020, at 1:18 PM, uncarollo2 via Groups.Io <chris1011@...> wrote: That's really nice. Sharp and great color.
A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 12:06 am Subject: [ap-gto] Close up of M81 without CCDT67 I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
Robert Chozick
Robert Chozick
|
|
|
|
Re: Close up of M81 without CCDT67
Dale Ghent
Yeah, those are working out to be great sensors (the mono or color ~61mp IMX455, or the color-only 26.8mp IMX571, both with 3.76um pixels). I still keep dreaming that Sony (or someone) will release a mono, 16bit, BSI, APS-C format sensor. My 36mm filters would appreciate that because upgrading 3nm narrowbands to 50mm to suit a full-frame sensor such as the mentioned ones is a bit... oof.
toggle quoted messageShow quoted text
On Feb 14, 2020, at 2:52 PM, dvjbaja <jpgleasonid@gmail.com> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
dvjbaja
I would look seriously at the new 16bit cmos cameras from QHY and ZWO. Jg
On Fri, Feb 14, 2020, 11:37 AM Dale Ghent <daleg@...> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Dale Ghent
Perhaps... probably would be fine. The 2.5-5um pixel size range of the common CMOS sensors these days will demand good seeing at that kind of focal length, but it's workable. What I would do is always image at 1x1and bin in post-processing (PixInsight's IntegerResample process, for example) on an as-needed basis if the pixel scale needs to be worked up a little due to the conditions.
toggle quoted messageShow quoted text
1600 would be great for detail studies of all kinds of nebula, too. For reference, Robert's camera sports 4.63um pixels. I have the same one, but QHY's version of it, and its Sony IMX294 is a really nice and super clean 4/3 format, 14 bit sensor with dual gain modes.
On Feb 14, 2020, at 2:18 PM, uncarollo2 <chris1011@aol.com> via Groups.Io <chris1011=aol.com@groups.io> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Roland Christen
That's really nice. Sharp and great color.
A question: do you think that 1600mm is a sweet spot for all kinds of deep sky imaging, especially for high resolution work? Especially since the newer Cmos cameras have such small pixels and would be able to take advantage of a high resolution optic for small faint galaxies.
Rolando
-----Original Message-----
From: Robert Chozick via Groups.Io <rchozick@...> To: main <main@ap-gto.groups.io> Sent: Fri, Feb 14, 2020 12:06 am Subject: [ap-gto] Close up of M81 without CCDT67 I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
Robert Chozick
|
|
|
|
Re: PEMProV3 error message
steven ho
Please disregard my last email it was sent to the wrong group. Late night and no coffee.
steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of steven ho <StevenHoffman53@...>
Sent: Friday, February 14, 2020 9:41 AM To: main@ap-gto.groups.io <main@ap-gto.groups.io> Subject: Re: [ap-gto] PEMProV3 error message
Two things....
There is no way to make the PDF file available, I converted the PDF to a "picture" so it could be posted.
I could put a button to forward them to our website where they could get the PDF (but the website is not working yet).
In other words they cannot "easily" print off the form to mail in.
Second, we could pay $5 to have facebook promote the event to 500 people in the state of NY (nothing more local than that).
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Friday, February 14, 2020 7:41 AM To: main@ap-gto.groups.io <main@ap-gto.groups.io> Subject: Re: [ap-gto] PEMProV3 error message Ted,
> "Failure to write mount definitions: Access to path is denied" You might want to check permissions on the folders you mention. Here is a link to some other things to try: https://support.microsoft.com/en-us/help/2669244/windows-cannot-access-the-specified-device-path-or-file-error-when-you -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro V3: https://www.ccdware.com 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 Ted Mickle via Groups.Io > Sent: Thursday, February 13, 2020 8:41 AM > To: main@ap-gto.groups.io > Subject: [ap-gto] PEMProV3 error message > > Ray, > > I've used PEMProV3 from with APCC Pro in the past without difficulty but now am encountering an error message > when attempting to access the CCDWare website, check for updates, etc from within APCC Pro/PEMProV3: > > "Unable to open browser: access to path "C:\Users\Documents\CCDWare\PEMProV3\temp.htm" is denied > > Also, when I attempt to acquire data, set the image scale, etc, I encounter this error message: > > "Failure to write mount definitions: Access to path is denied" > > My guess is that a configuration has changed somewhere in Windows 10 -- any suggestions to remedy are > welcome. > > Thanks, > > Ted >
|
|
|
|
Re: PEMProV3 error message
steven ho
Two things....
There is no way to make the PDF file available, I converted the PDF to a "picture" so it could be posted.
I could put a button to forward them to our website where they could get the PDF (but the website is not working yet).
In other words they cannot "easily" print off the form to mail in.
Second, we could pay $5 to have facebook promote the event to 500 people in the state of NY (nothing more local than that).
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Friday, February 14, 2020 7:41 AM To: main@ap-gto.groups.io <main@ap-gto.groups.io> Subject: Re: [ap-gto] PEMProV3 error message Ted,
> "Failure to write mount definitions: Access to path is denied" You might want to check permissions on the folders you mention. Here is a link to some other things to try: https://support.microsoft.com/en-us/help/2669244/windows-cannot-access-the-specified-device-path-or-file-error-when-you -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro V3: https://www.ccdware.com 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 Ted Mickle via Groups.Io > Sent: Thursday, February 13, 2020 8:41 AM > To: main@ap-gto.groups.io > Subject: [ap-gto] PEMProV3 error message > > Ray, > > I've used PEMProV3 from with APCC Pro in the past without difficulty but now am encountering an error message > when attempting to access the CCDWare website, check for updates, etc from within APCC Pro/PEMProV3: > > "Unable to open browser: access to path "C:\Users\Documents\CCDWare\PEMProV3\temp.htm" is denied > > Also, when I attempt to acquire data, set the image scale, etc, I encounter this error message: > > "Failure to write mount definitions: Access to path is denied" > > My guess is that a configuration has changed somewhere in Windows 10 -- any suggestions to remedy are > welcome. > > Thanks, > > Ted >
|
|
|
|
Re: PEMProV3 error message
Ray Gralak
Ted,
"Failure to write mount definitions: Access to path is denied"You might want to check permissions on the folders you mention. Here is a link to some other things to try: https://support.microsoft.com/en-us/help/2669244/windows-cannot-access-the-specified-device-path-or-file-error-when-you -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro V3: https://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver -----Original Message-----
|
|
|
|
Close up of M81 without CCDT67
Robert Chozick
I got another shot of M 81 on the same trip as the M81-82 image, this time at f/8 1620mm.
Robert Chozick
|
|
|