Date   

Re: DSLR on Mach2

Stone, Jack G
 

Shailesh,

 

Some often piggy back on the main scope.

There are sidereal options – IOptron is one that is less expensive by far for exposures < 2mins, others have achieved longer exposure times.

You could use Astrobin site for equipment search (DSLR w/GEM or Sidereal) – evaluate the setup and results.  And you can even email the submitters for more information and guidance.

 

Jack ~

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Shailesh Trivedi
Sent: Wednesday, January 19, 2022 3:06 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] DSLR on Mach2

 

Thank you, Joseph, Jeffc, Eric, and Jack. I am still consideringthe RST 135 E but am not fully convinced yet.

Shailesh


Re: DSLR on Mach2

Shailesh Trivedi
 

Thank you, Joseph, Jeffc, Eric, and Jack. I am still consideringthe RST 135 E but am not fully convinced yet.

Shailesh


Re: DSLR on Mach2

Stone, Jack G
 

Another perspective – that I found could be useful: Focusing fixture.

There are several representations on websites.

But adding the focus controller and belt drive to the lense focusing – with all that glass on longer exposures.

Just a thought!

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Eric Weiner
Sent: Wednesday, January 19, 2022 1:31 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] DSLR on Mach2

 

Similar to Jeff, a ADM D-series to Arca-Swiss for lenses which have feet (I actually use the V-series on my 135E), and a Arca-Swiss to Arca-Swiss bi-directional clamp for attaching the camera body (assuming you use an L-bracket) for lenses which don't have feet.

https://www.admaccessories.com/product/d2as-d-series-to-arca-swiss-adapter-converts-d-series-mounts-to-an-arca-swiss-series-mount/

https://www.amazon.com/Quick-Release-Subtend-Bidirectional-Double/dp/B08H5RKNSR/ref=sr_1_6?keywords=arca+swiss+90+degree+plate&qid=1642627714&sprefix=arca-swiss+90+d%2Caps%2C89&sr=8-6


Re: DSLR on Mach2

Eric Weiner
 

Similar to Jeff, a ADM D-series to Arca-Swiss for lenses which have feet (I actually use the V-series on my 135E), and a Arca-Swiss to Arca-Swiss bi-directional clamp for attaching the camera body (assuming you use an L-bracket) for lenses which don't have feet.

https://www.admaccessories.com/product/d2as-d-series-to-arca-swiss-adapter-converts-d-series-mounts-to-an-arca-swiss-series-mount/

https://www.amazon.com/Quick-Release-Subtend-Bidirectional-Double/dp/B08H5RKNSR/ref=sr_1_6?keywords=arca+swiss+90+degree+plate&qid=1642627714&sprefix=arca-swiss+90+d%2Caps%2C89&sr=8-6


Re: DSLR on Mach2

Jeffc
 

Sure.  

I use my Canon Ra (and 5Diii) on the Mach2 with the AP 130GT and many other OTAs.

 I presume when you say “hook up” you are referring to “mounting” the camera on the Mach2 for doing wide field with a camera lens.  

I have also used cameras with 1/4-20 mounts on the losmandy plates.   One solution I’ve had for a long time is a losmandy male-male plate, then a beefy losmandy 3-way camera mount.
ADM makes the same parts.   

An easier solution is to just use a standard tripod “head” (which you might already have) mounted to a regular dovetail plate.  
For example I have a bogen 3-way head w/ quick release… I mount this to a losmandy DUP plate.    The tripod heads are usually 3/8-16 (not 1/4-20) but I found there are enough holes in the dovetail plate to accommodate the tripod head. 

-jeff

On Jan 19, 2022, at 12:45 PM, Shailesh Trivedi <shailesh.trivedi@...> wrote:

I know it is an overkill, but is there a way I can hook up a DSLR to my Mach2?  Like perhaps purchasing a D to V ADM plate?

I am considering one of the RST135-E options for DSLRs and want an option to hook up AP130 or TEC160 but am getting close to my Losmandy FHD tripod option which I use on my Mach2, and have also used it for my AP1100AE.

Shailesh


Re: DSLR on Mach2

Joseph Beyer
 

ADM has a number of different DSLR camera mounting options including plates and clamps.

On Jan 19, 2022, at 12:45 PM, Shailesh Trivedi <shailesh.trivedi@...> wrote:

I know it is an overkill, but is there a way I can hook up a DSLR to my Mach2?  Like perhaps purchasing a D to V ADM plate?

I am considering one of the RST135-E options for DSLRs and want an option to hook up AP130 or TEC160 but am getting close to my Losmandy FHD tripod option which I use on my Mach2, and have also used it for my AP1100AE.

Shailesh


DSLR on Mach2

Shailesh Trivedi
 

I know it is an overkill, but is there a way I can hook up a DSLR to my Mach2?  Like perhaps purchasing a D to V ADM plate?

I am considering one of the RST135-E options for DSLRs and want an option to hook up AP130 or TEC160 but am getting close to my Losmandy FHD tripod option which I use on my Mach2, and have also used it for my AP1100AE.

Shailesh


Re: [ap-ug] Life after the Stowaway

Terri Zittritsch
 

Roland, I love my refractors but I have to admit that the commercial SCTs are the best bang for the buck of any telescopes I have.    I have an 8" meade ACF and an 11" Celestron edge and both perform, to my eyes, amazingly well given their price point.    Un-forked they're amazingly portable for the aperture and forked are incredibly versatile with excellent goto.     I have ordered a premium 7" refractor but I expect to keep my Meade for outreach.    Lots of WOW for the buck and the vast majority in this hobby can't afford the price tags for premium 10" optics even if they were available.

Terri 


Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

ap@CaptivePhotons.com
 

What can I say, breaking software is a gift.  Or a curse. 

Yes, now that I realize the cause, the solution is obvious.

I renamed them because I have two OTA's, and planned to reuse the models, and the names given by APPM are not meaningful.  I put the OTA type in the name, so I could know which was which.   It's sure easier than remember the date when I last created the refractor model, or the SCT model.

Linwood


Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

Ray Gralak
 

I was just guessing on the refraction issue. I haven't yet tried reproducing this, but I will as soon as I have some free time. I believe you are the first to run across this in all the years since APCC has been available, and there are a couple of obvious solutions, including:

1. Making sure the PNT file exists.
2. Disable tracking and pointing corrections.

And may I ask why you renamed the PNT file in the first place?

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, January 19, 2022 7:36 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

No, still running the released version of 6.5SP1, I tend to have enough stuff break around me without asking
for trouble with the latest version of ascom. But if you think it will help I can.

So it does not do this if you try it?

That would be a lot of refraction. :)

Linwood


Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

ap@CaptivePhotons.com
 

No, still running the released version of 6.5SP1, I tend to have enough stuff break around me without asking for trouble with the latest version of ascom.    But if you think it will help I can. 

So it does not do this if you try it? 

That would be a lot of refraction. :) 

Linwood


Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

Ray Gralak
 

That’s odd, all the terms are zero so I am not sure why a Dec value of 511 degrees would have been calculated, unless refraction has something to do with this.

 

By any chance have you updated the new ASCOM platform to 6.6? The release notes said something about fixing refraction.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, January 19, 2022 7:09 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

 

Sorry, Ray, when I say it was because of the model name, I meant it was because I renamed the model and the model name APCC was expecting was not present.

It's easily re-creatable for me.  Last night I was imaging with the model, and shut down normally.  To recreate this morning, before starting APCC I renamed the model to a new name.

For simplicity I started just APCC, no ASCOM, no NINA.  It auto-connected and and the model "loaded" all zeros (first two screen shots) 

I hand-keyed in the goto pane the uncorrected coordinates from the log you have (2d1m7.10s, 85d12m39.2s) and hit Goto.

It took off counterclockwise again (I think I said clockwise somewhere, sorry).   I stopped it after about 100 degrees or so, you can see in the 3D where I stopped it.  Notice also the custom rate; at this point if I go to the tracking correction status it shows -18000.00 sec/hour.  The log shows the corrected slew of +511*15:55.2 again.

At that point (having stopped the slew, but nothing else, no restart) I went to Model, loaded the (now) proper name, and immediately the numbers all changed to something sensible.  Without changing it I hit the goto button again and it properly slewed back to where it should be.

It really seems like it is just as simple as removing a model from where APCC expects it to be when it starts up causes this, no special situation that I can see. I must be the only one that likes meaningful names.  :) 

Obviously I won't be doing that any more.  

Thanks for looking at it. 

Linwood







Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

ap@CaptivePhotons.com
 

Sorry, Ray, when I say it was because of the model name, I meant it was because I renamed the model and the model name APCC was expecting was not present.

It's easily re-creatable for me.  Last night I was imaging with the model, and shut down normally.  To recreate this morning, before starting APCC I renamed the model to a new name.

For simplicity I started just APCC, no ASCOM, no NINA.  It auto-connected and and the model "loaded" all zeros (first two screen shots) 

I hand-keyed in the goto pane the uncorrected coordinates from the log you have (2d1m7.10s, 85d12m39.2s) and hit Goto.

It took off counterclockwise again (I think I said clockwise somewhere, sorry).   I stopped it after about 100 degrees or so, you can see in the 3D where I stopped it.  Notice also the custom rate; at this point if I go to the tracking correction status it shows -18000.00 sec/hour.  The log shows the corrected slew of +511*15:55.2 again.

At that point (having stopped the slew, but nothing else, no restart) I went to Model, loaded the (now) proper name, and immediately the numbers all changed to something sensible.  Without changing it I hit the goto button again and it properly slewed back to where it should be.

It really seems like it is just as simple as removing a model from where APCC expects it to be when it starts up causes this, no special situation that I can see. I must be the only one that likes meaningful names.  :) 

Obviously I won't be doing that any more.  

Thanks for looking at it. 

Linwood







Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

Ray Gralak
 

Hi Linwood,

I am a bit puzzled by those delays, as the amount of time referenced (about 7-8 seconds) does not seem
represented by the time stamps on either those lines, or even relative to the 'giving up line'.
Messages and responses are all queue-driven within APCC. The time values are measured from the time a response was returned from the mount until they are dequeued and processed by another thread in APCC. If another application is using significant CPU time, then that thread may not get a chance to finish processing the responses expediently.

But regardless... I think this shows APCC did the run-away due to the model name, and not due to CPU
competition?
Not really the model name, but APCC should have disabled the model when it could not load the PNT file. I'm still looking into the reason for the crazy coordinates that were used when this situation occurred. Can you post a screenshot of the pointing terms when APCC is in this state?

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Tuesday, January 18, 2022 1:33 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

Thanks, Ray. Several things to digest here. And I have a different slant on the theories below after more
research.

First, I was indeed doing a test of a new star analysis program on NINA. It is quite compute intensive. I am
not quite sure why it would be running though, since it needed to slew before it could take the image to
analyze. But it is quite a coincidence this was the first time I used it live. So it seems the most likely culprit,
but maybe not...

The model:

On 1/14 I built a new 200 (+/-) point model. I assumed it was being loaded each night since then by default,
however I think I screwed up.

I renamed the model (since "ApPointData-2022-01-14-183708.pnt" is not exactly meaningful and I have two
OTA's). I did the rename that evening while APCC was still running (assuming it was already loaded, Indeed I
reviewed a bunch of target/corrected slews from that night, all good).

The 17th is the next night I imaged, when the runaway happened. APCC tried to load the file name by which it
knew the model and failed (because I had renamed it). I should have manually loaded and activated it, but it
had been 3 days and my attention span is about 3 minutes so I did not.

My further guess is that somehow having failed to load it, it proceeded to build a garbage model as opposed
to turning off the model altogether. I reproduced it today in daylight, and there is no indication of failure in
APCC itself, the model comes up with no data (all zeros). HOWEVER, pointing and tracking corrections are
turned on, and when I did the same slew from NINA, DEC ran away again, and in the APCC log I see this:



0042829 2022-01-18 16:24:29.881: Debug, Pointing Corrector, Slew - Target Slew: RA = 02:01:07.10, Dec
= +85*12:39.2, East Model = True

0042830 2022-01-18 16:24:29.886: Debug, Pointing Corrector, Slew - Corrected Slew: RA = 18:56:30.47,
Dec = +511*15:55.4

So it is pretty easy to reproduce just from renaming the model file, and forgetting to load the model file the
next time you start APCC. APCC does something internally that results in wacky calculations in that situation.

Without closing APCC, I loaded the right model, had NINA re-issue the slow, and it worked perfectly.

So I am going to speculate that whatever happened with the delayed poll response was unrelated to the wacky
slew (since in my test there were no competing CPU processes now in daylight).

I am a bit puzzled by those delays, as the amount of time referenced (about 7-8 seconds) does not seem
represented by the time stamps on either those lines, or even relative to the 'giving up line'.

But regardless... I think this shows APCC did the run-away due to the model name, and not due to CPU
competition?

Linwood




Re: MGBox V2, GPS tab in APCC Pro can't get working

Ray Gralak
 

ASCOM.MGBox.ObservingConditions appeared as one of the selectable drivers, just as Ray observed it
The real problem was probably the MGBoxV2 ASCOM driver's name. For GPS, APCC expects the driver name to be "ASCOM.MGBox.ObservingConditions".

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of nx6a
Sent: Tuesday, January 18, 2022 10:08 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] MGBox V2, GPS tab in APCC Pro can't get working

I contacted Martin and he was kind enough to send me the older application (2.2.2) and MGBox_ASCOM
driver (1.6). With these installed the error went away! Yea! I then reinstalled the new application (2.3.0) and
MGBox_ASCOM_Server (6.5.1.0) and the error returned. I then kept the new application (2.3.0) and reinstalled
the MGBox_ASCOM driver (1.6) and the error again went away. I'll be sticking with application (2.3.0) and
MGBox_ASCOM driver (1.6) for now. Also, with MGBox_ASCOM driver (1.6)
ASCOM.MGBox.ObservingConditions appeared as one of the selectable drivers, just as Ray observed it
should. Martin said there was no need to roll back the firmware to 1.0 from 1.1 since the bug fix in 1.1 only
contains a bug fix which has no influence on the ASCOM-Driver or the windows application.

Another note - in order to install the ASTROMI.CH software I had to disable Auto-Protect in Norton 360 during
the installation. Norton and Microsoft griped during the entire installation process. Once installed, I enabled
Norton 360 Auto-Protect without issues.

Clear Skies,
Dan


Re: Ted Talk and Oscar's super nova

Sam
 

Hi Roland

Thank you for sharing these amazing experiences.

The unaided eye discovery of a supernova is a tremendous accomplishment which we will likely never see again, at least in our lifetimes, especially with all the new large telescopes being installed to systematically scan / image the sky, 

On the other hand, we are so fortunate to have technology on our side which gives us the capability to image DSO’s which amateurs could not have dreamed of a few decades ago.  My first telescope was a criterion rv6 which I used with a camera and hand processed film with manual Guiding.  In those days, who would have thought that we could take automated 20 minute subs with sensitive cameras that allow us to capture objects as faint as Palomar could see back then?

The ability to travel to southern dark skies is also a blessing which a few centuries would have been only a dream.  Such sights would have been impossible for Northern Hemisphere dwellers, except for the likes of navigators such as Ferdinand Magellan.
I consider myself tremendously fortunate to have visited Chile twice and experienced Las Campanas, and used the AP equipment at the Hacienda Los Andes.

Once again my appreciation for sharing these inspiring experiences.

Sam



Re: MGBox V2, GPS tab in APCC Pro can't get working

Ray Gralak
 

Another note - in order to install the ASTROMI.CH software I had to disable Auto-Protect in Norton 360 during
the installation. Norton and Microsoft griped during the entire installation process. Once installed, I enabled
Norton 360 Auto-Protect without issues.
It's probably because the installer is not "signed" and thus untrusted. The author should go through the procedure to get an Authenticode Code Signing Certificate and code-sign the installer and the applications it installs. Once the installers are code-signed, they will be at a much higher trust level, and any attempt to modify them can be detected.

BTW, the AP V2 ASCOM driver and APCC installers and all of the applications installed by them are code-signed.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of nx6a
Sent: Tuesday, January 18, 2022 10:08 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] MGBox V2, GPS tab in APCC Pro can't get working

I contacted Martin and he was kind enough to send me the older application (2.2.2) and MGBox_ASCOM
driver (1.6). With these installed the error went away! Yea! I then reinstalled the new application (2.3.0) and
MGBox_ASCOM_Server (6.5.1.0) and the error returned. I then kept the new application (2.3.0) and reinstalled
the MGBox_ASCOM driver (1.6) and the error again went away. I'll be sticking with application (2.3.0) and
MGBox_ASCOM driver (1.6) for now. Also, with MGBox_ASCOM driver (1.6)
ASCOM.MGBox.ObservingConditions appeared as one of the selectable drivers, just as Ray observed it
should. Martin said there was no need to roll back the firmware to 1.0 from 1.1 since the bug fix in 1.1 only
contains a bug fix which has no influence on the ASCOM-Driver or the windows application.

Another note - in order to install the ASTROMI.CH software I had to disable Auto-Protect in Norton 360 during
the installation. Norton and Microsoft griped during the entire installation process. Once installed, I enabled
Norton 360 Auto-Protect without issues.

Clear Skies,
Dan


Re: MGBox V2, GPS tab in APCC Pro can't get working

Ray Gralak
 

It's not using ActiveX, so this must be something that is coming from APCC.
That's incorrect. It has nothing to do with APCC. All native ASCOM drivers use ActiveX under the hood. It is the Microsoft technology for COM interop (the "COM" in "ASCOM" :-) ).

https://en.wikipedia.org/wiki/ActiveX

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of nx6a
Sent: Tuesday, January 18, 2022 10:13 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] MGBox V2, GPS tab in APCC Pro can't get working

Here is Martin's response to the solution:

Hi Dan

Thanks for that interesting feedback. I can't think of anything that would make the new ASCOM-Driver behave
like that. It's not using ActiveX, so this must be something that is coming from APCC.
Maybe it's the fact that the driver has a different name that is causing this issue....

Anyways, happy to hear that it works as expected.

Best regards
Martin


Any chance APCC can take a look at that possible driver name change issue? Here's hoping!

Clear Skies,
Dan


Re: [ap-ug] Life after the Stowaway

W Hilmo
 

Now you are just teasing us :)

On 1/18/22 7:51 PM, Roland Christen via groups.io wrote:

...For me, I like quartz optics in a reflector. Would not make them any other way. Quartz holds its shape even when the mirror is very thin and light weight. My 17" Quartz Cassegrain astrograph has a mirror that is only 12.5mm thick at the edges. I can hold it up in my right hand....
Rolando




Re: MGBox V2, GPS tab in APCC Pro can't get working

nx6a <danrprice@...>
 

Here is Martin's response to the solution:

Hi Dan

Thanks for that interesting feedback. I can't think of anything that would make the new ASCOM-Driver behave like that. It's not using ActiveX, so this must be something that is coming from APCC.
Maybe it's the fact that the driver has a different name that is causing this issue....

Anyways, happy to hear that it works as expected.

Best regards
Martin 


Any chance APCC can take a look at that possible driver name change issue?  Here's hoping!

Clear Skies,
Dan

3841 - 3860 of 88034