Date   

Re: Mach 1 not connecting

Bill Long
 

Or....

You have a cable that failed. If you are using a Mach 1 with CP4 and you are not using Ethernet... that would not be a wise decision. 

Still, give me a shout and we can poke at it. 🙂


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Monday, February 24, 2020 10:07 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 not connecting
 
I should add for the community that this sounds like a problem with user context in Windows. Meaning, you have something running in admin mode and standard user mode. At any rate it isnt hard to fix.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Monday, February 24, 2020 10:03 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 not connecting
 
You are welcome to call me and I can help. Hit me offline from the list at bill@... and if you have TeamViewer or AnyDesk I can help you solve it. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Jon Swanson <blackhawksjon@...>
Sent: Monday, February 24, 2020 9:31 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] Mach 1 not connecting
 
I had an odd experience tonight.  My Mach 1 just disconnected for some unknown reason and I cannot get it connected again.  The light is showing red.  I tried connecting through both SkyX and Maxim to no avail.  Shut down and restarted computer soft and hard as well as disconnecting all cables when doing it and unplugging power from mount.  Nothing.  ASCOM just spins and shows 12:00 and no connection.  ASCOM is up to date.  Any other ideas would be helpful.  


Re: Mach 1 not connecting

Bill Long
 

I should add for the community that this sounds like a problem with user context in Windows. Meaning, you have something running in admin mode and standard user mode. At any rate it isnt hard to fix.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Monday, February 24, 2020 10:03 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 not connecting
 
You are welcome to call me and I can help. Hit me offline from the list at bill@... and if you have TeamViewer or AnyDesk I can help you solve it. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Jon Swanson <blackhawksjon@...>
Sent: Monday, February 24, 2020 9:31 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] Mach 1 not connecting
 
I had an odd experience tonight.  My Mach 1 just disconnected for some unknown reason and I cannot get it connected again.  The light is showing red.  I tried connecting through both SkyX and Maxim to no avail.  Shut down and restarted computer soft and hard as well as disconnecting all cables when doing it and unplugging power from mount.  Nothing.  ASCOM just spins and shows 12:00 and no connection.  ASCOM is up to date.  Any other ideas would be helpful.  


Re: Mach 1 not connecting

Bill Long
 

You are welcome to call me and I can help. Hit me offline from the list at bill@... and if you have TeamViewer or AnyDesk I can help you solve it. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Jon Swanson <blackhawksjon@...>
Sent: Monday, February 24, 2020 9:31 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] Mach 1 not connecting
 
I had an odd experience tonight.  My Mach 1 just disconnected for some unknown reason and I cannot get it connected again.  The light is showing red.  I tried connecting through both SkyX and Maxim to no avail.  Shut down and restarted computer soft and hard as well as disconnecting all cables when doing it and unplugging power from mount.  Nothing.  ASCOM just spins and shows 12:00 and no connection.  ASCOM is up to date.  Any other ideas would be helpful.  


Mach 1 not connecting

Jon Swanson
 

I had an odd experience tonight.  My Mach 1 just disconnected for some unknown reason and I cannot get it connected again.  The light is showing red.  I tried connecting through both SkyX and Maxim to no avail.  Shut down and restarted computer soft and hard as well as disconnecting all cables when doing it and unplugging power from mount.  Nothing.  ASCOM just spins and shows 12:00 and no connection.  ASCOM is up to date.  Any other ideas would be helpful.  


Re: Apparent loss of tracking after dither command

Suresh Mohan
 

Roland !!,
        Nice to know you use phd 2 for guiding , it’s a vastly improved one now . The only other I’ve used is maxim dl however the former is more user friendly 


On 25-Feb-2020, at 12:48 AM, uncarollo2 <chris1011@...> via Groups.Io <chris1011@...> wrote:


It appears that RA is oscillating quite a bit. Possible reasons:

1) wrong calibration values - highly likely
2) mount is not balanced in RA - somewhat likely

Unfortunately your graph doesn't show the guide corrections which might help determining the cause. I would run Guide Assistant, there is a lot of information generated which will help you in your settings. The RA axis should not oscillate, unless the calibration values are way wrong for that part of the sky. It's happened to me when I fed the wrong focal length and pixel scale info to the guide program and had wild oscillations that did not go away until i reduced the aggressiveness to 10%. That was the clue that I had entered something wrong.

Rolando


-----Original Message-----
From: Peter Bresler via Groups.Io <PABresler@...>
To: main <main@ap-gto.groups.io>
Sent: Mon, Feb 24, 2020 11:35 am
Subject: Re: [ap-gto] Apparent loss of tracking after dither command

There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.


Re: Recommendation for Observatory PC

Dale Ghent
 

OnLogic ML100G-50 or ML100G-51. Intel Whiskey Lake CPU that is quite powerful for its 15W TDP. Throw 16GB of RAM and a 1TB M.2 SSD in there and you have a good system that will handily run a DSO imaging system and suck down high framerates for solar/lunar/planetary photography and lucky imaging.

It's not rack-mount but, honestly, such small systems are so low-power and capable these days. Just get a 2U rack shelf and set this on it. One note of caution about the OnLogic systems, however: they absolutely do not accept anything but 12V DC. Don't even think of trying to juice it with anything higher. It's a design flaw, in my opinion, that they do not include a VRM on the DC power input. I had a ML100G-50 and I fried it by accidentally hooking it up to a 13.8V power source... so yeah a 1.8V overvoltage toasted it. That's my only real complaint about their units considering the cheaper Intel NUCs accept 12-19V input.

ref:
https://www.onlogic.com/ml100g-50/
https://www.onlogic.com/ml100g-51/

If you *must* go with a true rackmount unit, I would suggest the E300 series systems combined with their rackmount kit from SuperMicro which sport, Xeon-D CPUs. I use these at home for my NIC driver development and testing, and they're low power for what they are and compact. They come with both M.2 NMVe and mSATA and can take up to 128GB of RAM. Way overkill for running a observatory,

ref:
https://www.supermicro.com/en/products/system/Mini-ITX/SYS-E300-8D.cfm

The basic gist is that embedded x86 CPUs are more than capable of running a Windows-based observatory software stack these days, but finding embedded x86 CPUs in rackmount form factors is rare.... the logic there being that racks live in data centers and data centers are expensive, so you would not be tossing low-power systems into those rack units. The embedded systems are more appropriate for running in non- or minimally-conditioned environments though.

/dale

On Feb 24, 2020, at 6:25 PM, Barry Megdal <bmegdal@shbinstruments.com> wrote:

Ethernet, USB and RS-232 is enough – no need for WiFi. Don’t need a high end CPU, but something midrange would likely make everything run a bit smoother – a lot of processes going between roof control, weather, APCC, Maxim, ACP, Focusmax, etc.

- Barry

Dr. Barry Megdal

President
Shb Instruments, Inc.
19215 Parthenia St. Suite A
Northridge, CA 91324
www.shbinstruments.com
(818) 773-2000 (818)773-2005 fax
bmegdal@shbinstruments.com

Faculty (retired)
Dept. of Electrical Engineering
Caltech


Re: Recommendation for Observatory PC

 

Hi Barry

we opted for a fanless pc from onlogic.com

our remote observatory provider (Obstech) recommended fanless. you can configure it to suit your needs and budget. the build quality seems exceptional

they also included port stoppers: little rubber stoppers you put into ports that are not in use, to minimize dust and other contaminants from entry into the pc. so far it's worked like a charm

also our provider recommended backups on all power supplies fwiw

Brian


Re: Recommendation for Observatory PC

Barry Megdal
 

Ethernet, USB and RS-232 is enough – no need for WiFi.  Don’t need a high end CPU, but something midrange would likely make everything run a bit smoother – a lot of processes going between roof control, weather, APCC, Maxim, ACP, Focusmax, etc.

 

-          Barry

 

Dr. Barry Megdal

 

President

Shb Instruments, Inc.

19215 Parthenia St.  Suite A

Northridge, CA 91324

www.shbinstruments.com

(818) 773-2000  (818)773-2005 fax

bmegdal@...

 

Faculty (retired)

Dept. of Electrical Engineering

Caltech

 


Re: Close up of M81 without CCDT67

Robert Chozick
 

I ordered one. Thanks 

Robert 


On Feb 24, 2020, at 2:57 PM, Bill Long <bill@...> wrote:


You can still get the circle pattern while they are in stock:




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Robert Chozick via Groups.Io <rchozick@...>
Sent: Monday, February 24, 2020 12:54 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Close up of M81 without CCDT67
 
Wayne did you also adjust the primary?  Do you have an attachment to project a grid or circle on the wall?  I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts.   My Howie Glatter laser has the grid attachment but they no longer make the circle projection attachment.   You can make the grid attachment work ok. 

Robert 


On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:

Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Close up of M81 without CCDT67

Robert Chozick
 

I just looked it up and now they sell the circle projection attachment

Robert 


On Feb 24, 2020, at 2:54 PM, Robert Chozick via Groups.Io <rchozick@...> wrote:

Wayne did you also adjust the primary?  Do you have an attachment to project a grid or circle on the wall?  I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts.   My Howie Glatter laser has the grid attachment but they no longer make the circle projection attachment.   You can make the grid attachment work ok. 

Robert 


On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:

Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Close up of M81 without CCDT67

Bill Long
 

You can still get the circle pattern while they are in stock:




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Robert Chozick via Groups.Io <rchozick@...>
Sent: Monday, February 24, 2020 12:54 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Close up of M81 without CCDT67
 
Wayne did you also adjust the primary?  Do you have an attachment to project a grid or circle on the wall?  I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts.   My Howie Glatter laser has the grid attachment but they no longer make the circle projection attachment.   You can make the grid attachment work ok. 

Robert 


On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:

Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Close up of M81 without CCDT67

Robert Chozick
 

Wayne did you also adjust the primary?  Do you have an attachment to project a grid or circle on the wall?  I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts.   My Howie Glatter laser has the grid attachment but they no longer make the circle projection attachment.   You can make the grid attachment work ok. 

Robert 


On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:

Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Close up of M81 without CCDT67

Bill Long
 

We'll see if my recent tip tilt adjustment solves my issues, once it clears here. That may have been the problem the whole time.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Wayne Hixson via Groups.Io <wayneh9026@...>
Sent: Monday, February 24, 2020 12:26 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Close up of M81 without CCDT67
 
Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Close up of M81 without CCDT67

Wayne Hixson
 

Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?


Re: Apparent loss of tracking after dither command

Roland Christen
 

It appears that RA is oscillating quite a bit. Possible reasons:

1) wrong calibration values - highly likely
2) mount is not balanced in RA - somewhat likely

Unfortunately your graph doesn't show the guide corrections which might help determining the cause. I would run Guide Assistant, there is a lot of information generated which will help you in your settings. The RA axis should not oscillate, unless the calibration values are way wrong for that part of the sky. It's happened to me when I fed the wrong focal length and pixel scale info to the guide program and had wild oscillations that did not go away until i reduced the aggressiveness to 10%. That was the clue that I had entered something wrong.

Rolando


-----Original Message-----
From: Peter Bresler via Groups.Io <PABresler@...>
To: main <main@ap-gto.groups.io>
Sent: Mon, Feb 24, 2020 11:35 am
Subject: Re: [ap-gto] Apparent loss of tracking after dither command

There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.


Re: Apparent loss of tracking after dither command

Dale Ghent
 

Assuming that the screenshot you provided was taken right after the erroneous event, the reason why guiding stopped in plainly-stated: Something external to PHD2 commanded the mount to slew while PHD2 was still guiding. In such a case, PHD2 will stop guiding and post a complaint.

You mentioned that you turned dithering on in SGP. Dithering is an operation that's normally handled by PHD2 - the sequencing application pauses between exposures, and through its direct connection to PHD2, orders PHD2 to begin a dither operation using either the provided parameters or PHD2's defaults. PHD2 executes this by sending pulse guide commands to the mount to move the field of view a few pixels in a random direction, then reacquires the guide star and resumes guiding. The sequence application observes through its direct connection to PHD2 that the dither op is completed, then starts the next exposure.

I don't know if this option is in SGP, but there is a "manual dither" feature that's common in sequencing apps, typically employed when there is no guide camera and no guiding app such as PHD2 operating, such as with an unguided setup. In such a case, it is the sequence application that tells the mount to move a little to effect the dither. Could it be that you have this feature on in SGP, and thus SGP is not coordinating the dithers through PHD2 at all? If this were the case, PHD2 would then see the guide star and mount move unexpectedly and produce the error you see in the screenshot you provided. This could be one possible explanation.

You didn't explain if you have had previous dither operations execute and succeed during your sequence. Doing your first dither 18 shots into a sequence is pretty late in the game to start doing it as, like I said, one normally sets up dithering to happen every 1-5 shots and no less frequent than that.

I would take Brian's advice and take this up on either the PHD2 or SGP forums.

On Feb 24, 2020, at 12:35 PM, Peter Bresler via Groups.Io <PABresler=aol.com@groups.io> wrote:

There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.

<guiding 2_23.jpg>


Re: Apparent loss of tracking after dither command

 

if you slew, guiding will stop. that's what it looks like happened here from your screen shot, but again you can get more details at PHD forums if you want to investigate further


On Mon, Feb 24, 2020 at 9:35 AM Peter Bresler via Groups.Io <PABresler=aol.com@groups.io> wrote:
There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.



--
Brian 



Brian Valente


Re: Apparent loss of tracking after dither command

Peter Bresler
 

There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.


Re: Notified!😍 #mach2gto #Mach2GTO

Luke Leege
 
Edited

https://ap-gto.groups.io/g/main/topic/upgrade_to_new_keypad_version/69318928?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,60,69318928
Must be used with GTOCP4 or GTOCP5 (CP5 is for Mach2GTO only). This is due to the more advanced command language and pointing precision that is only available in these control boxes. The software of the GTOCP4 itself will have to be updated, which can be done online. We will have more information regarding the downloadable upgrade when the time comes.


Re: Notified!😍 #mach2gto #Mach2GTO

Wayne Hixson
 

I meant Marj! Darn autocorrect!!

13861 - 13880 of 82438