¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Gemini_users
  2. Messages
Expanded Topics Messages Polls
Date
Re: Gemini 1 Automated Meridian Flip Settings

 

On Tue, Mar 28, 2023 at 07:11 AM, Brian Valente wrote:
There was some recent threads specifically regarding APT and meridian flips
?
you might try installing the latest beta for Gemini Telescope.net which seemed to help in several instances with similar setups to yours:
?
Hi Brian

Thanks for your response to y AMF/APT query.
I do actually already have the latest ,net beta ASCOM driver installed (v18) but failed to include this info in my post.
I've looked at the recent AMF/APT posts you suggested but these seem to be more involved with backlash issues preventing recentering after a flip (I think).
With regard to my interpretation of APT instructions for automating the Meridian Flip I need to test further. My only attempt thus far was partially successful in that APT paused the running plan 5 mins before the Meridian, then took a 10 secexposure, to solve as a record of where to recentre to after the filp, and then stopped the mount. Unfortunately the plate solve failed due to deteriation in the conditions. Had it succeeded in solving I believe it would have waited until the time for the meridian passing had lapsed and then done the flip. I'll attempt tp prove this behaviour on the next clear night which is forecast to be 4 days away. I'l report back on the results.

With regard to setting up my Gemini 1, after watching you excellent videos a few times, I felt relatively confident and was able to check and then enter both East and West Safety limits respectively 88 and 114 degs.Following the calculation, in the video, I arrived at my Western GOTO limit value 23 degrees. With Gemini 1 configured with these values I was unable to GOTO Regulus, which at the time was about 1 hr east of the Meridian, due to the `Interrupted' message being displayed on the Handset when I attempted to slew to Regulus..

What I am really struggling to get my head round is in adapting and applying the concepts and calculations, defined in the videos, to my Gemini 1. I am very confident with my Safety Limits which I am assumming will prevent any pier collisions and I plan not to change. I guess I'll just experiment with the Western GOTO Limit value. The calculate d23 deg did not seeming work resuting in the `interrupted' message, whereas changing this value to 95 did work ie no `interrupted message and an accurate slew to Regulus. I plan to experiment with this setting when possible, and note the results and hopefully refine from there - we'll see.

Regards

Terry (uk)
Re: Gemini 1 Automated Meridian Flip Settings

 

Hi Terry

There was some recent threads specifically regarding APT and meridian flips

you might try installing the latest beta for Gemini Telescope.net which seemed to help in several instances with similar setups to yours:








On Tue, Mar 28, 2023 at 1:24?AM Terry Pullen via <tpullen152=[email protected]> wrote:
Hello Group

Looking for advice on setting up Automated Meridian Fiip on my Gemini 1/G11/APT setup.

After watching Brian's various videos on automating the Meridian Flip I applied the the priciples to my own Gemini 1 and G11 setup.
Here are my derived measurements which I input to the Gemini 1 controller:-
Eastern Safety Limit = 88 deg, Western Safety Limit = 114 deg, Western GOTO Limit = 23 deg.

Last night we had our first brief spell of clear weather so thought I would try an Automated MF. Chose the star Regulus which was
about 1.25 hrs from transiting the Meridian. I also configured my aquisition software, APT, to automate the MF. Not sure I interpretted
APT's instructions correctly but set this up as "Flip Moment (mins)" to = 5 mins, "Delay Flip Move (mins)" = 8 mins and checked "Delay is counted
after Meridian passing".

I Cold Started Gemin1 and selected Regulus from the Bright Star List in the Hand Controller but the mount did not move and the Hand Controller
displayed "Interrupted'. Lots of double checking everything and reading the Gemini 1 Manual (should have done that earlier) and it would seem
that I have a problem with my Safety Limits. Following a statement in the G1 Manual I changed my 1Western GOTO Limit' from my calculated value of
23 deg to 95 deg and the mount went straight to Regulus.

APT seemed to behave as I concluded it should of by stopping 5 mins before the Meridian, taking a 10 sec image then attempting to Plate Solve it and use these coordinates after the flip to recentre but by this time the conditions had deteriated and the plate solve failed so APT left the mount with tracking off . I thouhgt I would try and get something from the evening so I tried a Manual Flip using the Gemini net ascom driver which was successful.? I then called it a night and read some more of the Gemini 1 Manual on the topics of
Safety Limits and Meridien Flips.

I am confused by what I read in the Gemini Manual which mentions possible problems with setting your Western GOT Limit between 1 - 89 deg. It also talks about Western GOTO Limits with values of 2.5 and 95 deg which I find hard to equate with Brian's videos. I am starting to believe that Gemin 1 and Gemini 2, for which the videos were produced I believe, might handle the Meridian Flip differently, for example having to set the Weastern GOTO limit referenced from the CWD position hence angle such as 95 deg etc.

Any assistance or guidance on how to apply Brians AMF videos to a Gemini 1 setup would be very welcome and appreciated as would any APT users who have successfully configured APT's Automated Meridian Flip instructions.

Regards

Terry (uk)



--
Brian?



Brian Valente
astro portfolio?
portfolio
astrobin?
Gemini 1 Automated Meridian Flip Settings

 

Hello Group

Looking for advice on setting up Automated Meridian Fiip on my Gemini 1/G11/APT setup.

After watching Brian's various videos on automating the Meridian Flip I applied the the priciples to my own Gemini 1 and G11 setup.
Here are my derived measurements which I input to the Gemini 1 controller:-
Eastern Safety Limit = 88 deg, Western Safety Limit = 114 deg, Western GOTO Limit = 23 deg.

Last night we had our first brief spell of clear weather so thought I would try an Automated MF. Chose the star Regulus which was
about 1.25 hrs from transiting the Meridian. I also configured my aquisition software, APT, to automate the MF. Not sure I interpretted
APT's instructions correctly but set this up as "Flip Moment (mins)" to = 5 mins, "Delay Flip Move (mins)" = 8 mins and checked "Delay is counted
after Meridian passing".

I Cold Started Gemin1 and selected Regulus from the Bright Star List in the Hand Controller but the mount did not move and the Hand Controller
displayed "Interrupted'. Lots of double checking everything and reading the Gemini 1 Manual (should have done that earlier) and it would seem
that I have a problem with my Safety Limits. Following a statement in the G1 Manual I changed my 1Western GOTO Limit' from my calculated value of
23 deg to 95 deg and the mount went straight to Regulus.

APT seemed to behave as I concluded it should of by stopping 5 mins before the Meridian, taking a 10 sec image then attempting to Plate Solve it and use these coordinates after the flip to recentre but by this time the conditions had deteriated and the plate solve failed so APT left the mount with tracking off . I thouhgt I would try and get something from the evening so I tried a Manual Flip using the Gemini net ascom driver which was successful.? I then called it a night and read some more of the Gemini 1 Manual on the topics of
Safety Limits and Meridien Flips.

I am confused by what I read in the Gemini Manual which mentions possible problems with setting your Western GOT Limit between 1 - 89 deg. It also talks about Western GOTO Limits with values of 2.5 and 95 deg which I find hard to equate with Brian's videos. I am starting to believe that Gemin 1 and Gemini 2, for which the videos were produced I believe, might handle the Meridian Flip differently, for example having to set the Weastern GOTO limit referenced from the CWD position hence angle such as 95 deg etc.

Any assistance or guidance on how to apply Brians AMF videos to a Gemini 1 setup would be very welcome and appreciated as would any APT users who have successfully configured APT's Automated Meridian Flip instructions.

Regards

Terry (uk)
Gemini I setup checklist

 

Hello group,

Has anyone put together a step-by-step checklist/instruction sheet for Gemini I?

I have seen parts of the setup described here but I still seem to be missing something.?

Thanks,

Gary
Re: Problems with autoguiding with the declination axis from my G 11 mount of Losmandy.

 

Hello Hans,

Michael is great, a good guy and has helped a lot of people debug their mount and imaging systems. It is kind of interesting if common that the issue is in DEC. Keep us posted with your progress and what you did to resolve the problem. .?

--

Chip Louie Chief Daydreamer Imagination Hardware?

? ?Astropheric Weather for Imagers - Click on my sig!
Re: Problems with autoguiding with the declination axis from my G 11 mount of Losmandy.

Hans Verheijen
 

¿ªÔÆÌåÓý

Hello Chip Louie,

?

Thanks for your answer, I have been received a message from Michael Herman and he explained the most issues why there is a malfunction with autoguiding? in Declination, he gives me some tutorials to resolve this problem. My old dealer is still helping me, I show you a picture during taking a image with my SBIG STT 8300 M with a self guiding chip. You can easily seen the malfunction in the Y axis ( declination ).

The Weather in theNetherlands is at this moment very bad, and there is no change ?in the following days. I am not able to test the mount after some? repairs. I must waite for a clear evening.

No further help is needed from you, but I am very thankfull that you sent me a letter because of the problems with autoguiding in declination.

Kind regards,

?

Hans Verheijen.

?

?

Van: [email protected] <[email protected]> Namens Chip Louie
Verzonden: zaterdag 25 maart 2023 21:39
Aan: [email protected]
Onderwerp: Re: [Gemini_users_io] Problems with autoguiding with the declination axis from my G 11 mount of Losmandy.

?

Hello Hans,

Hmm, sounds like you may have developed a small issue in the DEC axis. Is this G11 the same mount you have been using all a long? If yes what version G11 is it and what version Gemini are you using with this setup???

Regardless of version I would have you start by confirming that the DEC fasteners are all still snug. Starting with the socket headed cap screws under the worm block plate that attach the worm blocks to the plate AND that there is no movement of the worm between the worm bearing blocks. Pay particular attention to the Oldham coupler grub screws which seem to go daft when it is least convenient. I also recommend that these grub screws receive a drop of removeable thread adhesive even if they are not loose. These are the most likely culprits along with the servo motor mounting screws and the gearbox screws.??

Keep us posted!


--

Chip Louie Chief Daydreamer Imagination Hardware?

? ?Astropheric Weather for Imagers - Click on my sig!

20230226_192249.jpg

Re: Problems with autoguiding with the declination axis from my G 11 mount of Losmandy.

 

Hello Hans,

Hmm, sounds like you may have developed a small issue in the DEC axis. Is this G11 the same mount you have been using all a long? If yes what version G11 is it and what version Gemini are you using with this setup???

Regardless of version I would have you start by confirming that the DEC fasteners are all still snug. Starting with the socket headed cap screws under the worm block plate that attach the worm blocks to the plate AND that there is no movement of the worm between the worm bearing blocks. Pay particular attention to the Oldham coupler grub screws which seem to go daft when it is least convenient. I also recommend that these grub screws receive a drop of removeable thread adhesive even if they are not loose. These are the most likely culprits along with the servo motor mounting screws and the gearbox screws.??

Keep us posted!


--

Chip Louie Chief Daydreamer Imagination Hardware?

? ?Astropheric Weather for Imagers - Click on my sig!
Problems with autoguiding with the declination axis from my G 11 mount of Losmandy.

Hans Verheijen
 

I am new on this Group. I have a serious problem with autoguiding in the declination axis. I use several cameras wit a self guiding chip, the SBIG ST 4000 XCM and the SBIG STT 8300 M. The program is CCDOPS from SBIG. In the past 15 years I have been no problems with autguiding. This year the problem with autoguiding in the declination axis started in begin of the month February 2023. The self guiding chip can not track very accurate., After beginning taking images the autoguider works perfect in all directions, but after 2 minutes the declination axis can not tracking correctly, it shows a value of 1,4 pixels of some more pixels and after 6 seconds it returns to 0,4 pixel, and after 2 minutes the same issue. I use a FSQ 106 mm F 5 with a focal lenght of 530 mm. The exposure time of teh self guiding chip is 0,5 seconds without? using a filter. When I used a dark filter, such as a Optolong L eXtreme 2 I must have set the exposure time longer, in this case 3 seconds, that is too much for the declination axis, The value rise to 2,5 pixel for 10 seconds and fall back to 0,4 pixel for some minutes and then again a value of 2,5 pixel and after 10 seconds 0,4 pixel again. I use the St 4000 XCM, the filter is placed before the self guiding chip, with my STT 8300 M the self guiding chip is before the filterwheel, so that I am able to the exposure time of the self guiding chip very short, 0,5 / 1 second. There is a drift again but it is short because the exposure time of the self guiding chip is short too.
The image looks very good with a short exposure time with the self guiding chip. My G 11 is correctly polar aligned with my polar finder, the values of CCDOPS are; minimum move 25 miiliseconds maximum move 25 milliseconds, agressiveness is 10. The calibration run shows a very accurate run: + X 5 -X 184 + Y 92 - Y 272. The Go To works perfect, The RA axis works also perfect. I place a picture that shows the malfunction of the declination axis during the expose of 720 seconds. I hope that somebody of your group can help me with this problem. I lubricated the mount past year completely. Thanks very much for your answers. I appreciated this very much and hopely the problem can be resolved.
Kind regards, Hans Verheijen / The Netherlands.
Re: Pulse Guiding Possible Wth Gemini 1

 

On Fri, Mar 17, 2023 at 09:26 AM, Paul Kanevsky wrote:
Certainly you can pulse-guide with L4. In the ASCOM driver be sure to turn off "high precision guiding" option in Telescope Settings as that didn't work with L4.

Paul

That's good to know. Many thanks for the clarification.

Regards

Terry
Re: Pulse Guiding Possible Wth Gemini 1

 

Hi Terry,

Certainly you can pulse-guide with L4. In the ASCOM driver be sure to turn off "high precision guiding" option in Telescope Settings as that didn't work with L4.

Regards,

? ?-Paul
Pulse Guiding Possible Wth Gemini 1

 

Hello Group

Looking for advice on auto-guiding my G11 which I would like to start using.

I have a Gemini 1 Controller with what I believe to be the latest firmware Level 4, V1.05.
I connect to the Gemini 1 using Ascom and a Serial to usb cable to my laptop and can control the G11 mount with this arrangement.
I think I saw somewwhere that it wasn't possible to use pulse guiding using PHD2 with the Gemini 1
and that I would have to use the `back in the day' ST4 hookup. Is anyone using PHD2 with a Gemini 1 and has any tips on setting it up if possible.
I have seen Brian's document on getting a `base line' PHD calibration but not sure if this also applies to Gemini 1 controller.
Many thanks for any advice from the more experienced users here.

Regards

Terry (uk)
Re: COM error during meridian flip (Titan 50, Geminin 1 L4)

 

Paul

Got home about an hour ago and it wasn't raining...? I discovered on Friday evening that the mount didn't like the replacement serial cable.? I swapped back to the old cable and plugged in/unplugged a few times, blew out the dust etc. from the socket and then reconnected the serial cable.? I just run a test in daylight (hence focus, centre etc. fails) with no com errors - indeed no errors at all in the Ascom Gemin log file.? I slewed to several targets, NINA did a meridian flip, i used the app hand controller to trigger a meridian flip and then parked the scope.? NINA and gemini logs attahced along with a video of the session. Sounds promising for me too now after the issues of Friday...

I took a screen capture video of the whole session too which I have not uploaded as it is a very large file...

Thanks for all the help on this!

Regards

Mark

20230312-164315-2.1.0.9001.6148.log
20230312-164315-2.1.0.9001.6148.log
ASCOM.Gemini Telescope .NET.1638.403120.txt
ASCOM.Gemini Telescope .NET.1638.403120.txt

Re: COM error during meridian flip (Titan 50, Geminin 1 L4)

 

Mark, please use this update, as it should help with L4 support for the "Flip using Goto" feature:

/g/Gemini_ASCOM_Driver/message/5061

Regards,

? ?-Paul
Re: COM error during meridian flip (Titan 50, Geminin 1 L4)

 

Progress in this - I just discovered NINA has a Reconnect trigger - so if the 1.1.18 fix doesn¡¯t work for me, when my Gemini 1 disconnects during the meridian flip, the NINA reconnect trigger will reconnect the mount. ?Hopefully covered either way now ?
Re: COM error during meridian flip (Titan 50, Geminin 1 L4)

 

Hi Mark,

There are timeout exceptions shown in the ASCOM log after the request to do a meridian flip. Gemini might be busy with the start of the meridian flip or something else might be going. Gemini-1 L4 was a bit underpowered when processing a lot of complex commands while slewing in both axis, which is what would normally happen during a meridian flip.

That said, I just posted a test version of the driver in the ASCOM driver group that allows you to use a different mechanism for causing meridian flips. I suggest you give it a try, just in case the different mechanism might have a different interaction with NINA, driver, and Gemini:

/g/Gemini_ASCOM_Driver/message/5047

Let me know if this helps (or not)!

Regards,

? ? -Paul


On Thu, Mar 9, 2023 at 07:25 AM, madastro wrote:
Hi

I am using NINA for remote control of my observatory.? A couple of times recently, during the meridian flip, I am getting a COM error.? From that point, NINA seems to think the mount is disconnected even though in reality it is still acceting commands.? The evidence for this is in the logs - but physically - the mount parks on instruction (despite NINA saying it tried 3 times) before closing the roof.? The mount did park and the roof didn;t crash into the scope which is a relief.? I have a ROR setup.? The error I get is:

ASCOM.Gemini
20:40:18.248 Serial wait for response? TID:11 [0]: :Mf#
20:40:18.283 Serial received:? ? ? ? ? TID:11 [0]: :Mf#, G#
20:40:18.284 Serial wait for response? TID:11 [0]: 
20:41:48.383 Exception? ? ? ? ? ? ? ? ?TID:11 [Error]: System.TimeoutException: ReadTo[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.ReadTo(Char terminate) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 935[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.GetCommandResultSerial(CommandItem command, Boolean bResyncOnError, Boolean& bReturn) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 733
20:41:48.419 Serial Transmit? ? ? ? ? ?TID:11 [0]: 
20:41:48.419 Serial wait for response? TID:11 [0]: 
20:41:48.423 Serial received:? ? ? ? ? TID:11 [0]: , G

NINA Log at same time:
2023-03-07T20:40:13.4753|INFO|MeridianFlipTrigger.cs|ShouldTrigger|226|Meridian Flip - Remaining Time is between minimum and maximum flip time. Minimum time remaining 00:00:00, maximum time remaining 01:03:15. Flip should happen now
2023-03-07T20:40:13.4753|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: MeridianFlipTrigger
2023-03-07T20:40:13.4892|INFO|MeridianFlipVM.cs|DoMeridianFlip|163|Meridian Flip - Initializing Meridian Flip.?
Current target coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
Remaining wait time: 00:00:00
Pause Time Before Meridian: 0
Minutes After Meridian: 2
Max Minutes After Meridian: 69
AutoFocus After Flip: True
Recenter: True
Use SideOfPier: True
Settle Time: 15
2023-03-07T20:40:13.4932|INFO|MeridianFlipVM.cs|StopAutoguider|345|Meridian Flip - Stopping Autoguider
2023-03-07T20:40:16.5561|INFO|MeridianFlipVM.cs|PassMeridian|254|Meridian Flip - Stopping tracking to pass meridian
2023-03-07T20:40:17.8132|INFO|MeridianFlipVM.cs|PassMeridian|266|Meridian Flip - Resuming tracking after passing meridian
2023-03-07T20:40:18.0773|INFO|MeridianFlipVM.cs|DoFlip|127|Meridian Flip - Scope will flip to coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
2023-03-07T20:40:18.1687|INFO|AscomTelescope.cs|MeridianFlip|501|Setting pier side to pierEast
2023-03-07T20:41:08.2856|ERROR|DeviceUpdateTimer.cs|Start|103
ASCOM.DriverAccessCOMException (0x80131505): RightAscensionRate ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: RightAscensionRate
? ?--- End of inner exception stack trace ---
? ?at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
? ?at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 242
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
? ?at ASCOM.DriverAccess.Telescope.get_RightAscensionRate() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 919
? ?at Castle.Proxies.Invocations.ITelescopeFacade_get_RightAscensionRate.InvokeMethodOnTarget()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.Proxies.ITelescopeFacadeProxy.get_RightAscensionRate()
? ?at NINA.Equipment.Equipment.MyTelescope.AscomTelescope.get_TrackingRate() in E:\Projects\nina\NINA.Equipment\Equipment\MyTelescope\AscomTelescope.cs:line 976
? ?at NINA.WPF.Base.ViewModel.Equipment.Telescope.TelescopeVM.GetTelescopeValues() in E:\Projects\nina\NINA.Core.WPF\ViewModel\Equipment\Telescope\TelescopeVM.cs:line 680
? ?at NINA.Core.Utility.DeviceUpdateTimer.<<Start>b__21_0>d.MoveNext() in E:\Projects\nina\NINA.Core\Utility\DeviceUpdateTimer.cs:line 87
2023-03-07T20:42:01.9506|INFO|AscomTelescope.cs|MeridianFlip|505|Slewing to coordinates RA: 07:39:21; Dec: 65¡ã 33' 45"; Epoch: JNOW. Attempt 1 / 20
2023-03-07T20:42:16.6128|INFO|AscomTelescope.cs|MeridianFlip|511|Finished slewing to coordinates. Slew was successful. Setting pier side was successful

From that moment onwards in NINA, when it cintinues to check for a meridian flip being required, I get:
2023-03-07T20:46:15.3060|ERROR|MeridianFlipTrigger.cs|ShouldTrigger|193|Meridian Flip - Telescope is not connected to evaluate if a flip should happen!

Until NINA trie to do a 'Centre on drift' command which fails and the the script proceeds to close down the obs.

Both logs are attached - search for {} which I have inserted in the log files at the key points as I see them - saves you searching!

As far as I can see, the mount remained available, but NINA seems to think it dropped connection.??

What can I learn from that COM error?? Given the meridian flip worked, the target recentred as part of the flip process in NINA, only after that did NINA think the scope disconnected?? Is this likely a cabling issue given wiring looms being moved around as the scope flips over - or could it be something else?

Many thanks in advance!

Regards

Mark

?On Thu, Mar 9, 2023 at 07:25 AM, madastro wrote:
Hi

I am using NINA for remote control of my observatory.? A couple of times recently, during the meridian flip, I am getting a COM error.? From that point, NINA seems to think the mount is disconnected even though in reality it is still acceting commands.? The evidence for this is in the logs - but physically - the mount parks on instruction (despite NINA saying it tried 3 times) before closing the roof.? The mount did park and the roof didn;t crash into the scope which is a relief.? I have a ROR setup.? The error I get is:

ASCOM.Gemini
20:40:18.248 Serial wait for response? TID:11 [0]: :Mf#
20:40:18.283 Serial received:? ? ? ? ? TID:11 [0]: :Mf#, G#
20:40:18.284 Serial wait for response? TID:11 [0]: 
20:41:48.383 Exception? ? ? ? ? ? ? ? ?TID:11 [Error]: System.TimeoutException: ReadTo[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.ReadTo(Char terminate) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 935[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.GetCommandResultSerial(CommandItem command, Boolean bResyncOnError, Boolean& bReturn) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 733
20:41:48.419 Serial Transmit? ? ? ? ? ?TID:11 [0]: 
20:41:48.419 Serial wait for response? TID:11 [0]: 
20:41:48.423 Serial received:? ? ? ? ? TID:11 [0]: , G

NINA Log at same time:
2023-03-07T20:40:13.4753|INFO|MeridianFlipTrigger.cs|ShouldTrigger|226|Meridian Flip - Remaining Time is between minimum and maximum flip time. Minimum time remaining 00:00:00, maximum time remaining 01:03:15. Flip should happen now
2023-03-07T20:40:13.4753|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: MeridianFlipTrigger
2023-03-07T20:40:13.4892|INFO|MeridianFlipVM.cs|DoMeridianFlip|163|Meridian Flip - Initializing Meridian Flip.?
Current target coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
Remaining wait time: 00:00:00
Pause Time Before Meridian: 0
Minutes After Meridian: 2
Max Minutes After Meridian: 69
AutoFocus After Flip: True
Recenter: True
Use SideOfPier: True
Settle Time: 15
2023-03-07T20:40:13.4932|INFO|MeridianFlipVM.cs|StopAutoguider|345|Meridian Flip - Stopping Autoguider
2023-03-07T20:40:16.5561|INFO|MeridianFlipVM.cs|PassMeridian|254|Meridian Flip - Stopping tracking to pass meridian
2023-03-07T20:40:17.8132|INFO|MeridianFlipVM.cs|PassMeridian|266|Meridian Flip - Resuming tracking after passing meridian
2023-03-07T20:40:18.0773|INFO|MeridianFlipVM.cs|DoFlip|127|Meridian Flip - Scope will flip to coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
2023-03-07T20:40:18.1687|INFO|AscomTelescope.cs|MeridianFlip|501|Setting pier side to pierEast
2023-03-07T20:41:08.2856|ERROR|DeviceUpdateTimer.cs|Start|103
ASCOM.DriverAccessCOMException (0x80131505): RightAscensionRate ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: RightAscensionRate
? ?--- End of inner exception stack trace ---
? ?at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
? ?at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 242
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
? ?at ASCOM.DriverAccess.Telescope.get_RightAscensionRate() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 919
? ?at Castle.Proxies.Invocations.ITelescopeFacade_get_RightAscensionRate.InvokeMethodOnTarget()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.Proxies.ITelescopeFacadeProxy.get_RightAscensionRate()
? ?at NINA.Equipment.Equipment.MyTelescope.AscomTelescope.get_TrackingRate() in E:\Projects\nina\NINA.Equipment\Equipment\MyTelescope\AscomTelescope.cs:line 976
? ?at NINA.WPF.Base.ViewModel.Equipment.Telescope.TelescopeVM.GetTelescopeValues() in E:\Projects\nina\NINA.Core.WPF\ViewModel\Equipment\Telescope\TelescopeVM.cs:line 680
? ?at NINA.Core.Utility.DeviceUpdateTimer.<<Start>b__21_0>d.MoveNext() in E:\Projects\nina\NINA.Core\Utility\DeviceUpdateTimer.cs:line 87
2023-03-07T20:42:01.9506|INFO|AscomTelescope.cs|MeridianFlip|505|Slewing to coordinates RA: 07:39:21; Dec: 65¡ã 33' 45"; Epoch: JNOW. Attempt 1 / 20
2023-03-07T20:42:16.6128|INFO|AscomTelescope.cs|MeridianFlip|511|Finished slewing to coordinates. Slew was successful. Setting pier side was successful

From that moment onwards in NINA, when it cintinues to check for a meridian flip being required, I get:
2023-03-07T20:46:15.3060|ERROR|MeridianFlipTrigger.cs|ShouldTrigger|193|Meridian Flip - Telescope is not connected to evaluate if a flip should happen!

Until NINA trie to do a 'Centre on drift' command which fails and the the script proceeds to close down the obs.

Both logs are attached - search for {} which I have inserted in the log files at the key points as I see them - saves you searching!

As far as I can see, the mount remained available, but NINA seems to think it dropped connection.??

What can I learn from that COM error?? Given the meridian flip worked, the target recentred as part of the flip process in NINA, only after that did NINA think the scope disconnected?? Is this likely a cabling issue given wiring looms being moved around as the scope flips over - or could it be something else?

Many thanks in advance!

Regards

Mark
COM error during meridian flip (Titan 50, Geminin 1 L4)

 

Hi

I am using NINA for remote control of my observatory.? A couple of times recently, during the meridian flip, I am getting a COM error.? From that point, NINA seems to think the mount is disconnected even though in reality it is still acceting commands.? The evidence for this is in the logs - but physically - the mount parks on instruction (despite NINA saying it tried 3 times) before closing the roof.? The mount did park and the roof didn;t crash into the scope which is a relief.? I have a ROR setup.? The error I get is:

ASCOM.Gemini
20:40:18.248 Serial wait for response? TID:11 [0]: :Mf#
20:40:18.283 Serial received:? ? ? ? ? TID:11 [0]: :Mf#, G#
20:40:18.284 Serial wait for response? TID:11 [0]: 
20:41:48.383 Exception? ? ? ? ? ? ? ? ?TID:11 [Error]: System.TimeoutException: ReadTo[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.ReadTo(Char terminate) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 935[0D][0A]? ?at ASCOM.GeminiTelescope.GeminiHardwareBase.GetCommandResultSerial(CommandItem command, Boolean bResyncOnError, Boolean& bReturn) in C:\Users\ypa\Documents\Ascom.Gemini.Telescope\GeminiTelescope\Connection.cs:line 733
20:41:48.419 Serial Transmit? ? ? ? ? ?TID:11 [0]: 
20:41:48.419 Serial wait for response? TID:11 [0]: 
20:41:48.423 Serial received:? ? ? ? ? TID:11 [0]: , G

NINA Log at same time:
2023-03-07T20:40:13.4753|INFO|MeridianFlipTrigger.cs|ShouldTrigger|226|Meridian Flip - Remaining Time is between minimum and maximum flip time. Minimum time remaining 00:00:00, maximum time remaining 01:03:15. Flip should happen now
2023-03-07T20:40:13.4753|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: MeridianFlipTrigger
2023-03-07T20:40:13.4892|INFO|MeridianFlipVM.cs|DoMeridianFlip|163|Meridian Flip - Initializing Meridian Flip.?
Current target coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
Remaining wait time: 00:00:00
Pause Time Before Meridian: 0
Minutes After Meridian: 2
Max Minutes After Meridian: 69
AutoFocus After Flip: True
Recenter: True
Use SideOfPier: True
Settle Time: 15
2023-03-07T20:40:13.4932|INFO|MeridianFlipVM.cs|StopAutoguider|345|Meridian Flip - Stopping Autoguider
2023-03-07T20:40:16.5561|INFO|MeridianFlipVM.cs|PassMeridian|254|Meridian Flip - Stopping tracking to pass meridian
2023-03-07T20:40:17.8132|INFO|MeridianFlipVM.cs|PassMeridian|266|Meridian Flip - Resuming tracking after passing meridian
2023-03-07T20:40:18.0773|INFO|MeridianFlipVM.cs|DoFlip|127|Meridian Flip - Scope will flip to coordinates RA: 07:37:07 Dec: 65¡ã 36' 39" Epoch: J2000
2023-03-07T20:40:18.1687|INFO|AscomTelescope.cs|MeridianFlip|501|Setting pier side to pierEast
2023-03-07T20:41:08.2856|ERROR|DeviceUpdateTimer.cs|Start|103
ASCOM.DriverAccessCOMException (0x80131505): RightAscensionRate ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: RightAscensionRate
? ?--- End of inner exception stack trace ---
? ?at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
? ?at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 242
? ?at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 287
? ?at ASCOM.DriverAccess.Telescope.get_RightAscensionRate() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 919
? ?at Castle.Proxies.Invocations.ITelescopeFacade_get_RightAscensionRate.InvokeMethodOnTarget()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.DynamicProxy.AbstractInvocation.Proceed()
? ?at Castle.Proxies.ITelescopeFacadeProxy.get_RightAscensionRate()
? ?at NINA.Equipment.Equipment.MyTelescope.AscomTelescope.get_TrackingRate() in E:\Projects\nina\NINA.Equipment\Equipment\MyTelescope\AscomTelescope.cs:line 976
? ?at NINA.WPF.Base.ViewModel.Equipment.Telescope.TelescopeVM.GetTelescopeValues() in E:\Projects\nina\NINA.Core.WPF\ViewModel\Equipment\Telescope\TelescopeVM.cs:line 680
? ?at NINA.Core.Utility.DeviceUpdateTimer.<<Start>b__21_0>d.MoveNext() in E:\Projects\nina\NINA.Core\Utility\DeviceUpdateTimer.cs:line 87
2023-03-07T20:42:01.9506|INFO|AscomTelescope.cs|MeridianFlip|505|Slewing to coordinates RA: 07:39:21; Dec: 65¡ã 33' 45"; Epoch: JNOW. Attempt 1 / 20
2023-03-07T20:42:16.6128|INFO|AscomTelescope.cs|MeridianFlip|511|Finished slewing to coordinates. Slew was successful. Setting pier side was successful

From that moment onwards in NINA, when it cintinues to check for a meridian flip being required, I get:
2023-03-07T20:46:15.3060|ERROR|MeridianFlipTrigger.cs|ShouldTrigger|193|Meridian Flip - Telescope is not connected to evaluate if a flip should happen!

Until NINA trie to do a 'Centre on drift' command which fails and the the script proceeds to close down the obs.

Both logs are attached - search for {} which I have inserted in the log files at the key points as I see them - saves you searching!

As far as I can see, the mount remained available, but NINA seems to think it dropped connection.??

What can I learn from that COM error?? Given the meridian flip worked, the target recentred as part of the flip process in NINA, only after that did NINA think the scope disconnected?? Is this likely a cabling issue given wiring looms being moved around as the scope flips over - or could it be something else?

Many thanks in advance!

Regards

Mark

MF Error - 20230307-190937-2.1.0.9001.17888.log
MF Error - 20230307-190937-2.1.0.9001.17888.log
ASCOM.Gemini Telescope .NET.1911.516640.txt
ASCOM.Gemini Telescope .NET.1911.516640.txt

Re: Can I force Gemini L4 to park with the scope on the east side

 

Quick update and thanks!? I set the home position using the hand controller as suggested and all seems ok.? After several sessions now, the mount has parked reliably on the right side.? Thanks to all who responded!
Re: Random behavior Gemini 1

 

¿ªÔÆÌåÓý

Excellent news ¡­

?

From: [email protected] <[email protected]> On Behalf Of laurent Brouillac via groups.io
Sent: 09 February 2023 06:29
To: [email protected]
Subject: Re: [Gemini_users_io] Random behavior Gemini 1

?

Hi Brendan,

As David and you told me I fixed my power cable and everything sounds great now.
Thank you very much.

Laurent?

Re: Random behavior Gemini 1

 

Hi Brendan,

As David and you told me I fixed my power cable and everything sounds great now.
Thank you very much.

Laurent?
Re: Gemini 1 repairs anyone?

 

And best wishes to him!
--
Brendan
721 - 740 of 34077