¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

Johan.v.K
 

I operate an orange C14 with G-11, autoguider and PHD2. The essential? remarks were already made. Still some comments.
For several years I used on-line guiding, because it worked and I did not want to experiment with software and special cables. However the guider needed two cables: one to the PC and one to the mount port. A C14 is big, and guarding the wires at night is a hassle. Every wire less is much better. Then it appeared that switching to direct PC guiding could be done by trhree mouse clicks. One wire less. All going through ASCOM. PHD2 knows were the mount is, so less PHD2 training. I think the guiding ports on ZWO and G-11 have no function anymore.

Op do 9 dec. 2021 om 23:57 schreef <ecarina42@...>:
I have an older (2007) Gemini system running a G-11 mount. I have recently purchased a ZWO ASI120MC-P which I intend using primarily as an autoguider.

What I need to know is what I should connect the ZWO guider port to so the PHD2 can find it and control the Gemini-1? Obviously, direct connection of the ZWO to the Autoguider port on the Gemini-1 cannot be seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port arrangement.

I suspect this is common knowledge to many, but as the technology is getting on a bit, it's seems to be getting harder to find. I've been advised by Brian at Losmandy support that ST4 pulse guiding would probably be best for my situation. What can anyone suggest?

Paul.


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

yep you?got it


On Thu, Dec 9, 2021 at 9:20 PM Paul Lloyd <ecarina42@...> wrote:
Brian,

You seem to be working late - I've just checked and it's after 9pm in CA! Thanks for your very useful input.

I wasn't aware that the camera direct connection would be using the ST-4 protocol/method. Thanks for the heads-up on that, and yes, I'd prefer to make it as simple as possible, at least to start with. So, that means that I use Michael Herman's method, which ignores the use of the guider output port, and uses PHD2 to send instructions to the 'scope/Gemini-1 via Gemini Telescope.NET (ASCOM)/RS232 port. If this is right, then PHD2 is using the pulse method/protocol. (Michael's very extensive instructions does show a lot of useful info about the 'scope's alignment and its tracking/guiding behaviour.

Kind regards, and many thanks for your help so far.
Paul.



--
Brian?



Brian Valente
portfolio


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Brian,

You seem to be working late - I've just checked and it's after 9pm in CA! Thanks for your very useful input.

I wasn't aware that the camera direct connection would be using the ST-4 protocol/method. Thanks for the heads-up on that, and yes, I'd prefer to make it as simple as possible, at least to start with. So, that means that I use Michael Herman's method, which ignores the use of the guider output port, and uses PHD2 to send instructions to the 'scope/Gemini-1 via Gemini Telescope.NET (ASCOM)/RS232 port. If this is right, then PHD2 is using the pulse method/protocol. (Michael's very extensive instructions does show a lot of useful info about the 'scope's alignment and its tracking/guiding behaviour.

Kind regards, and many thanks for your help so far.
Paul.


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Hi Paul

At the risk of repeating myself, i really encourage you to avoid ST-4 (essentially Thierry's proposal) and instead use pulse guiding. Yes ST-4 can be easier to configure initially, but you will run into issues further down the line and you will probably be back for more help then.

Connecting the camera directly to the mount sounds good in theory, but in doing so you remove information about the mount's pointing position. PHD can adjust your guiding rate and even reverse guiding angles as needed when on opposite side of pier. However, ST-4 does not provide this information, so PHD does not know where in the sky you are, as a result, you have to recalibrate guiding for each target, and recalibrate guiding when you image in the opposite sky.?

If you are okay with doing all this extra work yourself, then by all means ST-4 might be for you. if that sounds like a lot of extra work you don't really need to do, i would agree with you. That's why i recommend pulse guiding

On Thu, Dec 9, 2021 at 7:08 PM Paul Lloyd <ecarina42@...> wrote:
Thierry,

Many thanks for that. My battery is on charge at the moment so I can't test out your suggestion. However, I would have thought that an autoguider would have the capability of sending standardized instructions directly to a mount controller. My only issue is whether my older controller (now 14 years) is capable of understanding them. All I need is a clear-enough night to try it out - we've had cloudy skies/rain for the past two weeks!

I noticed that when I select "On-camera" in my version of PHD2, the "Connect" button is greyed out/de-activated. Let's hope this is all it needs.

Paul.
(PS: I'm not familiar with the acronym, IMHO, but my wife suggested: In My Humble Opinion.)



--
Brian?



Brian Valente
portfolio


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Michael,

Thank you for your comprehensive instructions. I'm steadily working through them. I already have an ATEN cable and DB9-to-4 pin RJ, which you might have supplied me over 10 years ago, as I use the Gemini Control Center application. I have updated my ASCOM platform, and have the latest Gemini Telescope.NET driver installed. I have also taken the plunge to install Stellarium, which our club uses for its public open nights, so I need to become more familiar with it, and learning to drive a 'scope should be a good way of doing this.

If Thierry's suggestion works out, I probably won't need to progress with your autoguiding route, but I will keep it as an alternative method if it doesn't.

Cheers, and thanks, Paul.


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Thierry,

Many thanks for that. My battery is on charge at the moment so I can't test out your suggestion. However, I would have thought that an autoguider would have the capability of sending standardized instructions directly to a mount controller. My only issue is whether my older controller (now 14 years) is capable of understanding them. All I need is a clear-enough night to try it out - we've had cloudy skies/rain for the past two weeks!

I noticed that when I select "On-camera" in my version of PHD2, the "Connect" button is greyed out/de-activated. Let's hope this is all it needs.

Paul.
(PS: I'm not familiar with the acronym, IMHO, but my wife suggested: In My Humble Opinion.)


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

IMHO you should connect ZWO guider port to the Gemini then in
PHD2 use "On Camera Guiding" .. this way you don't need to seen the
Gemini in PHD2......

Thierry

On Thu, 2021-12-09 at 14:56 -0800, ecarina42@... wrote:
I have an older (2007) Gemini system running a G-11 mount. I have
recently purchased a ZWO ASI120MC-P which I intend using primarily as
an autoguider.

What I need to know is what I should connect the ZWO guider port to so
the PHD2 can find it and control the Gemini-1? Obviously, direct
connection of the ZWO to the Autoguider port on the Gemini-1 cannot be
seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port
arrangement.

I suspect this is common knowledge to many, but as the technology is
getting on a bit, it's seems to be getting harder to find. I've been
advised by Brian at Losmandy support that ST4 pulse guiding would
probably be best for my situation. What can anyone suggest?

Paul.


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Hi Paul,

See the attached PDF describing how to do this.

If you need a serial port to the G-1, contact me.??

Best regards,
Michael

On Thu, Dec 9, 2021, 2:57 PM <ecarina42@...> wrote:
I have an older (2007) Gemini system running a G-11 mount. I have recently purchased a ZWO ASI120MC-P which I intend using primarily as an autoguider.

What I need to know is what I should connect the ZWO guider port to so the PHD2 can find it and control the Gemini-1? Obviously, direct connection of the ZWO to the Autoguider port on the Gemini-1 cannot be seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port arrangement.

I suspect this is common knowledge to many, but as the technology is getting on a bit, it's seems to be getting harder to find. I've been advised by Brian at Losmandy support that ST4 pulse guiding would probably be best for my situation. What can anyone suggest?

Paul.


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

¿ªÔÆÌåÓý

Sorry, Brian, my confusion. I'll rectify that when I can find the message in the group.

Paul.

On 2021/12/10 09:57, Brian Valente wrote:

Hi Paul

Just to clarify, my recommendation was to use pulse guiding, and NOT to use ST-4

On Thu, Dec 9, 2021 at 2:57 PM <ecarina42@...> wrote:
I have an older (2007) Gemini system running a G-11 mount. I have recently purchased a ZWO ASI120MC-P which I intend using primarily as an autoguider.

What I need to know is what I should connect the ZWO guider port to so the PHD2 can find it and control the Gemini-1? Obviously, direct connection of the ZWO to the Autoguider port on the Gemini-1 cannot be seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port arrangement.

I suspect this is common knowledge to many, but as the technology is getting on a bit, it's seems to be getting harder to find. I've been advised by Brian at Losmandy support that ST4 pulse guiding would probably be best for my situation. What can anyone suggest?

Paul.


--
Brian?



Brian Valente
portfolio


Re: Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

Hi Paul

Just to clarify, my recommendation was to use pulse guiding, and NOT to use ST-4

On Thu, Dec 9, 2021 at 2:57 PM <ecarina42@...> wrote:
I have an older (2007) Gemini system running a G-11 mount. I have recently purchased a ZWO ASI120MC-P which I intend using primarily as an autoguider.

What I need to know is what I should connect the ZWO guider port to so the PHD2 can find it and control the Gemini-1? Obviously, direct connection of the ZWO to the Autoguider port on the Gemini-1 cannot be seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port arrangement.

I suspect this is common knowledge to many, but as the technology is getting on a bit, it's seems to be getting harder to find. I've been advised by Brian at Losmandy support that ST4 pulse guiding would probably be best for my situation. What can anyone suggest?

Paul.



--
Brian?



Brian Valente
portfolio


Connecting ZWO ASI autoguider to Gemini-1, using PHD2 #photo

 

I have an older (2007) Gemini system running a G-11 mount. I have recently purchased a ZWO ASI120MC-P which I intend using primarily as an autoguider.

What I need to know is what I should connect the ZWO guider port to so the PHD2 can find it and control the Gemini-1? Obviously, direct connection of the ZWO to the Autoguider port on the Gemini-1 cannot be seen by PHD2 - there has to be some RJ-11-to-RS232-to-RJ11 guider port arrangement.

I suspect this is common knowledge to many, but as the technology is getting on a bit, it's seems to be getting harder to find. I've been advised by Brian at Losmandy support that ST4 pulse guiding would probably be best for my situation. What can anyone suggest?

Paul.


Gemini Meridian Flip troubles

 

I'm hoping some gurus can assist with assisting me with what settings they are using for automated Meridian flips, specifically with Voyager software if possible.
I've gone through hours of previous posts and the voodoo that surrounds the mysterious meridian flip issues with Gemini and software commanded control.

I've run through simulated testing and thought I had this working for me, but in real world testing it's not working, and I'm stumped why. The only thing I have changed is installing the latest Gemini.net drivers.
My first question, is should I be using the latest drivers as yet. Are these supported for older Gemini G11 Version 1 mounts?

I'm using a Gemini 1 G11 Level 4, 1.
Through all the threads and previous hosts, it looks that tracking must be disabled to initiate a merdian flip with goto once past the Meridian, and I tested this in test environment and got this working, but running a custom script to disable tracking before initiating a goto when past the meridian.
I'm in the southern hemisphere, and have the old style mounted motors, so I've made sure that my Western limit is set to 93 degress. My goto limit is deafult zero. So this should be 2.5 degrees; which give a 2min period after passing meridian to the west, where a goto to the same target will flip the mount.
In Voyager it's set to initiate a meridian flip at 5mins past the meridian.

In the previous nights testing live, it got to 2mins before hittting limits, and Voyager commaned the meridian flip but nothing happended with the mount. Only just after it tried to slew to target and plate solve, and reposition where it put it 6mins of or mount limits and tried to goto to reposition based on the plate solve, and it then did do a meridian flip.
Here are some logs from the event time below; What I can't decipher in my head is the right settings to make this happen the way I want it to.

Also what is 99, 7 response?

I don't see this listed in the manual.


The only get return values I see in the manual are:

1: Telescope is
Aligned,
2: Modeling in use,
4: Object is selected,
8: GoTo operation is
performed,
16: RA limit reached,
32: Precess coordinates
from J2000.0
to the equinox of the
date

Ascom Logs
00:58:57.479 Serial Transmit?????????? TID:11 [0]: :hN#
00:58:57.485 Serial Transmit?????????? TID:11 [0]: :GR#:GD#:GA#:GZ#:Gv#
00:58:57.507 Serial wait for response? TID:11 [0]: :GR
00:58:57.521 Serial received:????????? TID:11 [0]: :GR, 05:26:02
00:58:57.522 Serial wait for response? TID:11 [0]: :GD
00:58:57.548 Serial received:????????? TID:11 [0]: :GD, -78:12:31
00:58:57.548 Serial wait for response? TID:11 [0]: :GA
00:58:57.646 Serial received:????????? TID:11 [0]: :GA, +43:36:17
00:58:57.646 Serial wait for response? TID:11 [0]: :GZ
00:58:57.718 Serial received:????????? TID:11 [0]: :GZ, 180:21:14
00:58:57.718 Serial wait for response? TID:11 [0]: :Gv
00:58:57.718 Serial received:????????? TID:11 [0]: :Gv, N
00:58:57.718 Serial Transmit?????????? TID:11 [0]: :GS#:Gm#<99:F#:h?#
00:58:57.739 Serial wait for response? TID:11 [0]: :GS
00:58:57.747 Serial received:????????? TID:11 [0]: :GS, 05:31:04
00:58:57.747 Serial wait for response? TID:11 [0]: :Gm
00:58:57.747 Serial received:????????? TID:11 [0]: :Gm, W
00:58:57.747 Serial wait for response? TID:11 [0]: <99:
00:58:57.747 Serial received:????????? TID:11 [0]: <99:, 7
00:58:57.747 Serial wait for response? TID:11 [0]: :h?
00:58:57.747 Serial received:????????? TID:11 [0]: :h?, 0
00:58:57.747 Serial Transmit?????????? TID:11 [0]: :Gv#
00:58:57.753 Serial wait for response? TID:11 [0]: :Gv
00:58:57.759 Serial received:????????? TID:11 [0]: :Gv, N
00:58:57.762 Serial Transmit?????????? TID:11 [0]: <509:z#
00:58:57.771 Serial wait for response? TID:11 [0]: <509:
00:58:57.780 Serial received:????????? TID:11 [0]: <509:, 0
00:58:57.868 Serial Transmit?????????? TID:11 [0]: <235:r#
00:58:57.877 Serial wait for response? TID:11 [0]: <235:
00:58:57.895 Serial received:????????? TID:11 [0]: <235:, 2207;294
00:58:57.895 Serial Transmit?????????? TID:11 [0]: <237:p#
00:58:57.904 Serial wait for response? TID:11 [0]: <237:
00:58:57.922 Serial received:????????? TID:11 [0]: <237:, 4500;4500
00:58:57.962 Serial Transmit?????????? TID:11 [0]: <235:r#
00:58:57.970 Serial wait for response? TID:11 [0]: <235:
00:58:57.988 Serial received:????????? TID:11 [0]: <235:, 2207;294
00:58:57.988 Serial Transmit?????????? TID:11 [0]: <237:p#
00:58:57.997 Serial wait for response? TID:11 [0]: <237:
00:58:58.016 Serial received:????????? TID:11 [0]: <237:, 4500;4500
00:58:58.016 Serial Transmit?????????? TID:11 [0]: :hW#
00:58:58.021 Serial Transmit?????????? TID:11 [0]: :GR#:GD#:GA#:GZ#:Gv#
00:58:58.044 Serial wait for response? TID:11 [0]: :GR
00:58:58.059 Serial received:????????? TID:11 [0]: :GR, 05:26:03
00:58:58.059 Serial wait for response? TID:11 [0]: :GD
00:58:58.085 Serial received:????????? TID:11 [0]: :GD, -78:12:31
00:58:58.085 Serial wait for response? TID:11 [0]: :GA
00:58:58.182 Serial received:????????? TID:11 [0]: :GA, +43:36:17
00:58:58.182 Serial wait for response? TID:11 [0]: :GZ
00:58:58.256 Serial received:????????? TID:11 [0]: :GZ, 180:21:17
00:58:58.256 Serial wait for response? TID:11 [0]: :Gv
00:58:58.257 Serial received:????????? TID:11 [0]: :Gv, T
00:58:58.257 Serial Transmit?????????? TID:11 [0]: :GS#:Gm#<99:F#:h?#
00:58:58.277 Serial wait for response? TID:11 [0]: :GS
00:58:58.285 Serial received:????????? TID:11 [0]: :GS, 05:31:05
00:58:58.285 Serial wait for response? TID:11 [0]: :Gm
00:58:58.285 Serial received:????????? TID:11 [0]: :Gm, W
00:58:58.285 Serial wait for response? TID:11 [0]: <99:
00:58:58.285 Serial received:????????? TID:11 [0]: <99:, 7
00:58:58.285 Serial wait for response? TID:11 [0]: :h?
00:58:58.285 Serial received:????????? TID:11 [0]: :h?, 0
00:58:58.285 Serial Transmit?????????? TID:11 [0]: :Gv#
00:58:58.290 Serial wait for response? TID:11 [0]: :Gv
00:58:58.297 Serial received:????????? TID:11 [0]: :Gv, T
00:58:58.367 Serial Transmit?????????? TID:11 [0]: <223:u#
00:58:58.377 Serial wait for response? TID:11 [0]: <223:
00:58:58.391 Serial received:????????? TID:11 [0]: <223:, 000d00
00:58:58.391 Serial Transmit?????????? TID:11 [0]: <220:v#
00:58:58.400 Serial wait for response? TID:11 [0]: <220:
00:58:58.422 Serial received:????????? TID:11 [0]: <220:, 098d00;093d00
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (degrees):, 0.5, 3, -8
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (hours):, 0.0333333333333333, 0.2, -0.533333333333333
00:58:58.423 IT:DestinationSideOfPier? TID:8 [1]: SiderealTime, ScopeHA, DesinationHA (hours):, 5.51805555555556, 0.0838888888888887, -0.109611448465088
00:58:58.423 Serial Transmit?????????? TID:11 [0]: <235:r#
00:58:58.432 Serial wait for response? TID:11 [0]: <235:
00:58:58.449 Serial received:????????? TID:11 [0]: <235:, 2207;294
00:58:58.449 Serial Transmit?????????? TID:11 [0]: <237:p#
00:58:58.459 Serial wait for response? TID:11 [0]: <237:
00:58:58.476 Serial received:????????? TID:11 [0]: <237:, 4500;4500
00:58:58.476 IT:DestinationSideOfPier? TID:8 [1]: From Region C to Region B, Retval: , pierEast
00:58:58.523 Serial Transmit?????????? TID:11 [0]: :Sr05:37:40#:ONPC Object#:Sd-69:09:41#:MS#
00:58:58.568 Serial wait for response? TID:11 [0]: :Sr05:37:40
00:58:58.568 Serial received:????????? TID:11 [0]: :Sr05:37:40, 1
00:58:58.568 Serial wait for response? TID:11 [0]: :Sd-69:09:41
00:58:58.597 Serial received:????????? TID:11 [0]: :Sd-69:09:41, 1
:
00:58:58.285 Serial wait for response? TID:11 [0]: <99:
00:58:58.285 Serial received:????????? TID:11 [0]: <99:, 7
00:58:58.285 Serial wait for response? TID:11 [0]: :h?
00:58:58.285 Serial received:????????? TID:11 [0]: :h?, 0
00:58:58.285 Serial Transmit?????????? TID:11 [0]: :Gv#
00:58:58.290 Serial wait for response? TID:11 [0]: :Gv
00:58:58.297 Serial received:????????? TID:11 [0]: :Gv, T
00:58:58.367 Serial Transmit?????????? TID:11 [0]: <223:u#
00:58:58.377 Serial wait for response? TID:11 [0]: <223:
00:58:58.391 Serial received:????????? TID:11 [0]: <223:, 000d00
00:58:58.391 Serial Transmit?????????? TID:11 [0]: <220:v#
00:58:58.400 Serial wait for response? TID:11 [0]: <220:
00:58:58.422 Serial received:????????? TID:11 [0]: <220:, 098d00;093d00
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (degrees):, 0.5, 3, -8
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (hours):, 0.0333333333333333, 0.2, -0.533333333333333
00:58:58.423 IT:DestinationSideOfPier? TID:8 [1]: SiderealTime, ScopeHA, DesinationHA (hours):, 5.51805555555556, 0.0838888888888887, -0.109611448465088
00:58:58.423 Serial Transmit?????????? TID:11 [0]: <235:r#
00:58:58.432 Serial wait for response? TID:11 [0]: <235:
00:58:58.449 Serial received:????????? TID:11 [0]: <235:, 2207;294
00:58:58.449 Serial Transmit?????????? TID:11 [0]: <237:p#
00:58:58.459 Serial wait for response? TID:11 [0]: <237:
00:58:58.476 Serial received:????????? TID:11 [0]: <237:, 4500;4500
00:58:58.476 IT:DestinationSideOfPier? TID:8 [1]: From Region C to Region B, Retval: , pierEast
00:58:58.523 Serial Transmit?????????? TID:11 [0]: :Sr05:37:40#:ONPC Object#:Sd-69:09:41#:MS#
00:58:58.568 Serial wait for response? TID:11 [0]: :Sr05:37:40
00:58:58.568 Serial received:????????? TID:11 [0]: :Sr05:37:40, 1
00:58:58.568 Serial wait for response? TID:11 [0]: :Sd-69:09:41
00:58:58.597 Serial received:????????? TID:11 [0]: :Sd-69:09:41, 1
00:58:58.597 Serial wait for response? TID:11 [0]: :MS
:
00:58:58.285 Serial wait for response? TID:11 [0]: <99:
00:58:58.285 Serial received:????????? TID:11 [0]: <99:, 7
00:58:58.285 Serial wait for response? TID:11 [0]: :h?
00:58:58.285 Serial received:????????? TID:11 [0]: :h?, 0
00:58:58.285 Serial Transmit?????????? TID:11 [0]: :Gv#
00:58:58.290 Serial wait for response? TID:11 [0]: :Gv
00:58:58.297 Serial received:????????? TID:11 [0]: :Gv, T
00:58:58.367 Serial Transmit?????????? TID:11 [0]: <223:u#
00:58:58.377 Serial wait for response? TID:11 [0]: <223:
00:58:58.391 Serial received:????????? TID:11 [0]: <223:, 000d00
00:58:58.391 Serial Transmit?????????? TID:11 [0]: <220:v#
00:58:58.400 Serial wait for response? TID:11 [0]: <220:
00:58:58.422 Serial received:????????? TID:11 [0]: <220:, 098d00;093d00
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (degrees):, 0.5, 3, -8
00:58:58.422 IT:DestinationSideOfPier? TID:8 [1]: GoTo Limit, West Limit, East Limit Meridian offset (hours):, 0.0333333333333333, 0.2, -0.533333333333333
00:58:58.423 IT:DestinationSideOfPier? TID:8 [1]: SiderealTime, ScopeHA, DesinationHA (hours):, 5.51805555555556, 0.0838888888888887, -0.109611448465088
00:58:58.423 Serial Transmit?????????? TID:11 [0]: <235:r#
00:58:58.432 Serial wait for response? TID:11 [0]: <235:
00:58:58.449 Serial received:????????? TID:11 [0]: <235:, 2207;294
00:58:58.449 Serial Transmit?????????? TID:11 [0]: <237:p#
00:58:58.459 Serial wait for response? TID:11 [0]: <237:
00:58:58.476 Serial received:????????? TID:11 [0]: <237:, 4500;4500
00:58:58.476 IT:DestinationSideOfPier? TID:8 [1]: From Region C to Region B, Retval: , pierEast
00:58:58.523 Serial Transmit?????????? TID:11 [0]: :Sr05:37:40#:ONPC Object#:Sd-69:09:41#:MS#
00:58:58.568 Serial wait for response? TID:11 [0]: :Sr05:37:40
00:58:58.568 Serial received:????????? TID:11 [0]: :Sr05:37:40, 1
00:58:58.568 Serial wait for response? TID:11 [0]: :Sd-69:09:41
00:58:58.597 Serial received:????????? TID:11 [0]: :Sd-69:09:41, 1
00:58:58.597 Serial wait for response? TID:11 [0]: :MS
00:58:58.612 Serial received:????????? TID:11 [0]: :MS, 0
00:58:58.612 Serial Transmit?????????? TID:11 [0]: :GR#:GD#:GA#:GZ#:Gv#
00:58:58.634 Serial wait for response? TID:11 [0]: :GR

Voyager Logs
2021/12/02 00:56:23 727 - INFO????? - [Sequence - Guide Calibration ] - [CALIBRATE_WAIT_Code????????????????????????? ] - Wait Calibration Command Settled for 3s
2021/12/02 00:56:24 426 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_StartGuiding???????????????????? ] - [PHD2] Received StartGuiding Event =>
2021/12/02 00:56:24 504 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_SettleBegin????????????????????? ] - [PHD2] Received SettleBegin Event =>
2021/12/02 00:56:25 721 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_SettleDone?????????????????????? ] - [PHD2] Received SettleDone Event =>Status=SUCCEDED;Error=
2021/12/02 00:56:26 736 - INFO????? - [PHD2Client?????????????????? ] - [ESEGUI_PHD2_StopCapture????????????????????? ] - [PHD2][CMD] Stop_Capture sent
2021/12/02 00:56:26 752 - INFO????? - [PHD2Client?????????????????? ] - [MANAGE_RispostaOK_StopCapture??????????????? ] - [PHD2][RESPONSE] Stop_Capture executed
2021/12/02 00:56:26 862 - INFO????? - [BroadcastEteroMessage??????? ] - [DeRegisterAction???????????????????????????? ] - Deregistered Broadcast Action => Sequence - Guide Calibration_6466c2a7-fe5b-4d4f-b9f5-f8c1797f75f8
2021/12/02 00:56:26 868 - INFO????? - [Sequence - Guide Calibration ] - [FINISH_Code????????????????????????????????? ] - Guiding Vector Data Log => Not Implemented !
2021/12/02 00:56:26 871 - INFO????? - [ATOMIC_GUIDE_CALIBRATION???? ] - [Funzione???????????????????????????????????? ] - Action Time [ATOMIC_GUIDE_CALIBRATION] => 2 [m] 35 [s]
2021/12/02 00:56:26 875 - INFO????? - [ATOMIC_GUIDE_CALIBRATION???? ] - [Funzione???????????????????????????????????? ] - Action Time Mobile Mean [ATOMIC_GUIDE_CALIBRATION] => 2 [m] 18 [s]
2021/12/02 00:56:26 975 - EVENTO??? - [Sequence???????????????????? ] - [MeridianCheck??????????????????????????????? ] - Voyager is Only Exposure Zone of Meridian Setting [0 - 5 - 5]!
2021/12/02 00:56:26 979 - WARNING?? - [Sequence???????????????????? ] - [MeridianCheck??????????????????????????????? ] - Entering Waiting Mode for right time to do Meridian Flip, reached action could flip the telescope in Only Exposure Zone.
2021/12/02 00:56:29 584 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_GuidingStopped?????????????????? ] - [PHD2] Received GuidingStopped Event =>
2021/12/02 00:56:29 599 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_LoopingExposuresStopped????????? ] - [PHD2] Received LoopingExposuresStopped Event =>
2021/12/02 00:56:29 603 - INFO????? - [BroadcastEteroMessage??????? ] - [SendBroadcastMsgToRegisteredQueue??????????? ] - Send Request for Broadcast EVENT => GUIDING_STOPPED
2021/12/02 00:56:29 615 - INFO????? - [PHD2Client?????????????????? ] - [EVENTO_PHD2_LockPositionLost???????????????? ] - [PHD2] Received LockPositionLost Event =>
2021/12/02 00:56:29 634 - INFO????? - [BroadcastEteroMessage??????? ] - [SendBroadcastMsgToRegisteredQueue??????????? ] - Send Request for Broadcast EVENT => GUIDING_LOCK_POSITION_LOST
2021/12/02 00:56:29 639 - EVENTO??? - [Sequence???????????????????? ] - [ManageBroadcast_GuidingStopped?????????????? ] - Event GUIDING STOPPED
2021/12/02 00:56:29 698 - EVENTO??? - [Sequence???????????????????? ] - [ManageBroadcast_GuidingLockLostPosition????? ] - Event GUIDING LOCK LOST POSITION
2021/12/02 00:56:56 952 - INFO????? - [Telescopio?????????????????? ] - [PushFunction???????????????????????????????? ] - PierSide= pierWest (DRV)(1) ; LastGotoPierSide= pierWest (DRV) ; FlipStatus= DA_FARE ; MeridianQuery= ONLY_EXPOSURE_MODE ; LST= 05:29:02 (DRV) ; RA= 05:26:02 ; LST-RA= 00:03:00(0.0499999999999998) ; AZ= 18
0¡ã 12' 43" ; ALT= 43¡ã 36' 25"
2021/12/02 00:57:56 936 - INFO????? - [Telescopio?????????????????? ] - [PushFunction???????????????????????????????? ] - PierSide= pierWest (DRV)(1) ; LastGotoPierSide= pierWest (DRV) ; FlipStatus= DA_FARE ; MeridianQuery= ONLY_EXPOSURE_MODE ; LST= 05:30:02 (DRV) ; RA= 05:26:02 ; LST-RA= 00:04:00(0.0666666666666664) ; AZ= 18
0¡ã 16' 57" ; ALT= 43¡ã 36' 22"
2021/12/02 00:58:26 935 - EVENTO??? - [Sequence???????????????????? ] - [MeridianCheck??????????????????????????????? ] - Voyager is Only Exposure Zone of Meridian Setting [0 - 5 - 5]!
2021/12/02 00:58:50 431 - EVENTO??? - [Sequence???????????????????? ] - [MeridianCheck??????????????????????????????? ] - Starting Meridian Flip
2021/12/02 00:58:50 457 - INFO????? - [PHD2Client?????????????????? ] - [ESEGUI_PHD2_GetConnected???????????????????? ] - [PHD2][CMD] Get_Connected sent
2021/12/02 00:58:50 465 - SUBTITLE? - [Sequence???????????????????? ] - [RESET_GUIDE_Code???????????????????????????? ] - Shutdown Guide
2021/12/02 00:58:50 473 - INFO????? - [PHD2Client?????????????????? ] - [MANAGE_RispostaOK_GetConnected?????????????? ] - [PHD2][RESPONSE] Get_Connected executed
2021/12/02 00:58:50 582 - INFO????? - [PHD2Client?????????????????? ] - [ESEGUI_PHD2_StopCapture????????????????????? ] - [PHD2][CMD] Stop_Capture sent
2021/12/02 00:58:50 598 - INFO????? - [PHD2Client?????????????????? ] - [MANAGE_RispostaOK_StopCapture??????????????? ] - [PHD2][RESPONSE] Stop_Capture executed
2021/12/02 00:58:56 704 - INFO????? - [Sequence - Shutdown Guide??? ] - [STOP_GUIDE_Code????????????????????????????? ] - Guide Stopped
2021/12/02 00:58:56 766 - INFO????? - [ATOMIC_GUIDE_MANAGER???????? ] - [Funzione???????????????????????????????????? ] - Action Time [ATOMIC_GUIDE_MANAGER] => 0 [m] 6 [s]
2021/12/02 00:58:56 797 - INFO????? - [ATOMIC_GUIDE_MANAGER???????? ] - [Funzione???????????????????????????????????? ] - Action Time Mobile Mean [ATOMIC_GUIDE_MANAGER] => 0 [m] 14 [s]
2021/12/02 00:58:56 853 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_RUN_EXTERNAL
2021/12/02 00:58:56 860 - EVENTO??? - [SEQUENCE???????????????????? ] - [EXEC_BEFORE_MERIDIAN_FLIP_Code?????????????? ] - Exec External Program/Script Before Meridian Flip ...
2021/12/02 00:58:56 875 - EVENTO??? - [Exec External Program/Script Before Meridian Flip] - [EXECUTE_EXE_Code???????????????????????????? ] - Starting Executable (disable-tracking.exe) => C:\Users\Dan\Documents\Voyager\Script\disable-tracking.exe
2021/12/02 00:58:56 880 - DEBUG???? - [Exec External Program/Script Before Meridian Flip] - [EXECUTE_EXE_Code???????????????????????????? ] - Arguments =>
2021/12/02 00:58:56 973 - DEBUG???? - [Exec External Program/Script Before Meridian Flip] - [EXECUTE_EXE_WAIT_Code??????????????????????? ] - Wait for time of => 10000[ms]
2021/12/02 00:58:57 847 - DEBUG???? - [Exec External Program/Script Before Meridian Flip] - [EXECUTE_EXE_WAIT_Code??????????????????????? ] - EXEC Output :
Connected to telescope now.. Disabling Tracking
2021/12/02 00:58:57 850 - EVENTO??? - [Exec External Program/Script Before Meridian Flip] - [EXECUTE_EXE_WAIT_Code??????????????????????? ] - EXEC finished OK
2021/12/02 00:58:57 853 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_CLEAR
2021/12/02 00:58:57 856 - INFO????? - [SEQUENCE???????????????????? ] - [EXEC_BEFORE_MERIDIAN_FLIP_WAIT_Code????????? ] - Program/Script executed
2021/12/02 00:58:57 862 - INFO????? - [ATOMIC_RUN_EXTERNAL????????? ] - [Funzione???????????????????????????????????? ] - Action Time [ATOMIC_RUN_EXTERNAL] => 0 [m] 1 [s]
2021/12/02 00:58:57 866 - INFO????? - [ATOMIC_RUN_EXTERNAL????????? ] - [Funzione???????????????????????????????????? ] - Action Time Mobile Mean [ATOMIC_RUN_EXTERNAL] => 0 [m] 10 [s]
2021/12/02 00:58:57 873 - SUBTITLE? - [Sequence???????????????????? ] - [MERIDIAN_PRECISE_GOTO_TARGET_Code??????????? ] - Meridian Flip with Precise Pointing to Target
2021/12/02 00:58:57 962 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_PRECISE_POINTING
2021/12/02 00:58:57 983 - INFO????? - [TelescopeGoto??????????????? ] - [CHECK_TELESCOPE_CONNECTION_Code????????????? ] - Actual Position (JNow) (RA=05 26 02.000? / DEC=-78 12 31.00 )
2021/12/02 00:58:57 993 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_TELESCOPE_GOTO
2021/12/02 00:58:58 056 - INFO????? - [Telescopio?????????????????? ] - [PushFunction???????????????????????????????? ] - PierSide= pierWest (DRV)(1) ; LastGotoPierSide= pierWest (DRV) ; FlipStatus= DA_FARE ; MeridianQuery= DO_FLIP ; LST= 05:31:04 (DRV) ; RA= 05:26:02 ; LST-RA= 00:05:02(0.0838888888888887) ; AZ= 180¡ã 21' 14"
; ALT= 43¡ã 36' 17"
2021/12/02 00:58:58 498 - EVENTO??? - [TelescopeGoto??????????????? ] - [CHECK_FLIP_MIRROR_DESTINATION_Code?????????? ] - Calculated Data for Dome is ALT=52 38 50.82 ;AZ=179 03 04.86 ;HA=-00:06:35;Latitude=-31 49 13.20 ;Pier=pierWest
2021/12/02 00:58:58 503 - INFO????? - [TelescopeGoto??????????????? ] - [CHECK_FLIP_MIRROR_DESTINATION_Code?????????? ] - Pier Flip Status After Last Slew = pierWest (DRV)(1)
2021/12/02 00:58:58 526 - INFO????? - [TelescopeGoto??????????????? ] - [CHECK_FLIP_MIRROR_DESTINATION_Code?????????? ] - Expected Pier Flip Status After Slew = pierWest (DRV)(1)
2021/12/02 00:58:58 530 - INFO????? - [TelescopeGoto??????????????? ] - [RUN_ASYNC_Code?????????????????????????????? ] - Slewing Async (JNow) RA=05 37 39.601? DEC=-69 09 41.40? ...
2021/12/02 00:58:58 933 - INFO????? - [TelescopeGoto??????????????? ] - [RUN_ASYNC_PREWAIT_Code?????????????????????? ] - PreWait of 10[ms] Checking Slew Finished
2021/12/02 00:59:08 945 - INFO????? - [TelescopeGoto??????????????? ] - [SETTLING_TIME_Code?????????????????????????? ] - Waiting Settling Time (6s)...
2021/12/02 00:59:14 981 - INFO????? - [TelescopeGoto??????????????? ] - [SETTLING_TIME_WAIT_Code????????????????????? ] - Mount Assert Stable (6s)...
2021/12/02 00:59:15 009 - INFO????? - [TelescopeGoto??????????????? ] - [FINISH_Code????????????????????????????????? ] - Actual Position (JNow) (RA=05 37 40.000? / DEC=-69 09 41.00 )
2021/12/02 00:59:15 012 - INFO????? - [ATOMIC_TELESCOPE_GOTO??????? ] - [Funzione???????????????????????????????????? ] - Action Time [ATOMIC_TELESCOPE_GOTO] => 0 [m] 17 [s]
2021/12/02 00:59:15 016 - INFO????? - [ATOMIC_TELESCOPE_GOTO??????? ] - [Funzione???????????????????????????????????? ] - Action Time Mobile Mean [ATOMIC_TELESCOPE_GOTO] => 0 [m] 20 [s]
2021/12/02 00:59:15 020 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_PRECISE_POINTING
2021/12/02 00:59:15 099 - INFO????? - [TelescopeGoto??????????????? ] - [Funzione???????????????????????????????????? ] - Reload Pier Flip Status After Slew = pierWest (DRV)(1)
2021/12/02 00:59:15 129 - EVENTO??? - [ServerClientWebSocket??????? ] - [SENDEVENTO_VOYAGER_Signal??????????????????? ] - [S00050] SEND EVENT => Signal = RUN_PLATE_SOLVING_ACTUAL_LOCATION


Re: Gemini 1 ASCOM and Maxim DL 6 - Nudge scope position

Howard
 

Thanks Andrew, I will be playing around next clear night and hopefully will have more to add. Will certainly try the guide tab.
Howard


Re: Gemini 1 ASCOM and Maxim DL 6 - Nudge scope position

 

I got a chance last night to give the Nudge a try.? How about that, North and South work but East and West gives the timeout error.? However, in the Guide tab there is a similar command and all four directions work.??
Software, good grief...
Andrew


Setting Goto Limit on Gemini 1

 

My question concerns the flavour of the month topic namely automated Meriden Flips using acquisition software such as APT and NINA.

I have a c2007 G11 with Gemini 1 controller with latest firmware. I am using APT as my mount control software and my goal is to be able to automate the Meridien Flip using APT.

I have watched Brian's excellent recent video based on the use of Gemini 2. I learned a lot from this video but need help with setting up the value of my mount's 'Goto Limit' setting. I have configured my Safety Limits following the video's guidance with the resulting values of Eastern Limit = 94 degrees and Western Limit = 121 degrees. From Brians video I subtract 90 from my Western Limit i.e. 121 = 31 degrees. I then subtract a buffer/padding value of 1 degree to get my actual 'Flip Allowable Range' of 30 degrees.

My questions are:
1. Is this value 30 what I enter into my Gemini 1's 'GoTo Limit' using the Gemini menu of "Setup¡úMount
Parameters¡úSet Goto."?

2. The Gemini Manual in section 5.3.10.2.6 (p70) mentions subtracting 2.5 degrees! It does not appear to define this value and I am wondering if this is just a different/arbitrary size of Padding/Buffer or derived from something else - it seems very specific at 2.5?

In section 3.3.4 on p33 2.5 degrees is also mentioned.

3. The Gemini Manual also mentions (p70) examples of setting a Goto Limits of 90 or 95 degrees and it is these values differing by such a large amount that I find confusing where compared to Brian's 9 and my 30 degrees.

I am more or less confinced that I should be entering 30 degrees as my 'Goto Limit' but would appreciate some confirmation from those more familiar with this topic.

Many thanks

Terry [uk]


Re: Gemini 1 ASCOM and Maxim DL 6 - Nudge scope position

 

I have the same exact setup.? Forecast here is for clear skies tomorrow and Tuesday night.? I'll give the nudge command a try and report back

Andrew

On Sunday, November 21, 2021, 09:36:04 AM CST, Howard via groups.io <hmooers@...> wrote:


Hoping you can help me with an issue, which I assume is operator error, but I can't track it down. I am using Maxim DL6 with the ASCOM Gemini driver (v.1.0.75) on my Losmandy G-11. Scope connects as it should, syncs, and long slews are fine. However, in Maxim on the Telescope tab of the observatory control I want to "nudge" the scope by a few seconds of arc. It appears that all of the buttons, N S E W make the mount "nudge" in the same direction and it moves far beyond the 1-2 seconds I specify. If I open the Gemini hand control in the ASCOM driver, I am able to move the scope in very small increments using the guide or center slewing speeds; everything works as it should. Going back to Maxim, still not working in the Nudge commands.

Have others experienced this? Am I just missing some setting in either the Gemini driver or Maxim?
Would appreciate any suggestions.


Gemini 1 ASCOM and Maxim DL 6 - Nudge scope position

Howard
 

Hoping you can help me with an issue, which I assume is operator error, but I can't track it down. I am using Maxim DL6 with the ASCOM Gemini driver (v.1.0.75) on my Losmandy G-11. Scope connects as it should, syncs, and long slews are fine. However, in Maxim on the Telescope tab of the observatory control I want to "nudge" the scope by a few seconds of arc. It appears that all of the buttons, N S E W make the mount "nudge" in the same direction and it moves far beyond the 1-2 seconds I specify. If I open the Gemini hand control in the ASCOM driver, I am able to move the scope in very small increments using the guide or center slewing speeds; everything works as it should. Going back to Maxim, still not working in the Nudge commands.

Have others experienced this? Am I just missing some setting in either the Gemini driver or Maxim?
Would appreciate any suggestions.


Re: Losmandy G11 disconnects after meridian flip

 

Paul thank you so much? for your time and? work on Gemini ASCOM Driver ,?
I let you know that I am very happy with your work on Gemini driver and make possible Meridian Flip with my simple Gemini1 Controller .
I tried flip my mount so many times and working good ,? I am just ignoring this timeout error warnings .
Thanks again for support .
Cheers?
Roman


Re: G11 Flip successful

 

Robert , we need read messages from groups and I found answer here not long time ago :
/g/Gemini_users/message/32544?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2CGemini+1+driver%2C20%2C2%2C0%2C83192797
So this is driver behavior not NINA? .
I am not ready for V 1.11? just do not feel it .
Thanks for help .
Cheers?
Roman


Re: G11 Flip successful

 

Hi Roman,
you should upgrade NINA to the v1.11. It has the extra flip detail in it. The max minutes is based on how far pas the meridian you have set the safety limits to. Do you know this value? ?It can be read and set from the computer Gemini software.?

Oh yes. Also watch that video. It explains all regarding the meridian flip and settings.?

Regards,
Robert