I just got a Mesu 200 MKII mount that I will be installing in a remote observatory with Voyager. I tested the system last night and it performed very well. The only thing I could not manage to do is to dial in the Meridian Flip configuration. I have been using Voyager for a few months now and had no issue at all with both a CEM 60 and a MyT. So I guess it has to do with the Sitech Ascom driver.
What I observe is that, whenever the time for a Meridian flip comes, the mount does not respond to the slew commands.
I had tried this also indoor with the same result.
I wonder if there is any Voyager user who is using the Mesu 200 who can help me dial in the right configuration.
I tested the MF indoors today and it is clearly a limits setup issue. The last version of the ASCOM driver (0.94N) works fine with Voyager as long as the limits setup in SiTechExe allows Voyager to manage the MF.
I have set the Meridian Limit West (Degs) to 0/-180 and the Meridian Limit East (Degs) to 0/180. So the limits after which the mount should stop tracking are precisely at the meridian. Some people leave some extra margin, but I think that this is not really important, since the key parameter is the Track Past Meridian Overlap (Degrees) . This is the region past the meridian limit where you allow the mount to keep on tracking. More importantly, it is the region where a GoTo will actually produce a MF.
So I set the Track Past Meridian Overlap to a little bit more of my maximum exposure in Voyager. If this value is set to zero then the mount stops tracking at the meridian limit.
Finally I left the GEM Auto Flip GoTo checked.
In such a way the mount will continue tracking the value of Track Past Meridian Overlap degrees past the Meridian Limits (which in my case are set precisely at the meridian) and while in this overlap region it will flip whenever Voyager issues the MF GoTo.
In Voyager all the time setting in the Mount Setup panel and the Session Meridian Flip tab must be within the Track Past Meridian Overlap region.
So ready to do my first full session with this new mount.
Thanks a lot for your help,
Note: I deleted my previous post since I found out I made a mistake in the Meridian Limits Under the Pole which could result in a pier crash. The signs were inverted.
The latest version is currently 95H, but this isn’t shown on the Sitech website.
If you go to the groups.io website and search for the Sitech forum, you will be able to find a link to download the latest.
For some reason, the version on the website isn’t updated very often, and the latest shared on the groups.io Sitech forum is always considered beta.
Strange, but I guess they (he) have their reasons.
A very useful insight into how to set up a Mesu 200 in Voyager.
I had been trying to flip the pier before the mount was in the Track Past Meridian Overlap zone. I changed the config file to something similar to what you have. It worked immediately under NINA, but still failed under Voyager.
Looking at the Voyager log file it looks as though when the meridian flip was actioned, the mount decided that it was already on the right side and so did not flip. So I guess either Voyager or SiTech.exe are confused as to which side of the pier the telescope is.
How do you set Voyager to pick up pier side?
The relevant extract from the log file is here:
2020/12/08 15:40:47 940 - EVENTO - [Sequence - Safety Run ] - [MeridianCheck ] - Starting Meridian Flip
2020/12/08 15:40:47 972 - INFO - [PHD2Client ] - [ESEGUI_PHD2_GetConnected ] - [PHD2][CMD] Get_Connected sent
2020/12/08 15:40:47 987 - INFO - [PHD2Client ] - [MANAGE_RispostaOK_GetConnected ] - [PHD2][RESPONSE] Get_Connected executed
2020/12/08 15:40:47 987 - SUBTITLE - [Sequence - Safety Run ] - [RESET_GUIDE_Code ] - Shutdown Guide
2020/12/08 15:40:48 081 - INFO - [PHD2Client ] - [ESEGUI_PHD2_StopCapture ] - [PHD2][CMD] Stop_Capture sent
2020/12/08 15:40:48 097 - INFO - [PHD2Client ] - [MANAGE_RispostaOK_StopCapture ] - [PHD2][RESPONSE] Stop_Capture executed
2020/12/08 15:40:54 237 - INFO - [Sequence - Shutdown Guide ] - [STOP_GUIDE_Code ] - Guide Stopped
2020/12/08 15:40:54 284 - INFO - [ATOMIC_GUIDE_MANAGER ] - [Funzione ] - Action Time [ATOMIC_GUIDE_MANAGER] => 0 [m] 6 [s]
2020/12/08 15:40:54 284 - INFO - [ATOMIC_GUIDE_MANAGER ] - [Funzione ] - Action Time Mobile Mean [ATOMIC_GUIDE_MANAGER] => 0 [m] 13 [s]
2020/12/08 15:40:54 347 - SUBTITLE - [Sequence - Safety Run ] - [MERIDIAN_PRECISE_GOTO_TARGET_Code ] - Meridian Flip with Precise Pointing to Target
2020/12/08 15:40:54 393 - INFO - [TelescopeGoto ] - [CHECK_TELESCOPE_CONNECTION_Code ] - Actual Position (JNow) (RA=20 35 58.549 / DEC=05 15 06.29 )
2020/12/08 15:40:54 425 - EVENTO - [TelescopeGoto ] - [CHECK_FLIP_MIRROR_DESTINATION_Code ] - Calculated Data for Dome is ALT=41 57 12.62 ;AZ=181 25 10.03 ;HA=00:04:14;Latitude=53 17 26.00 ;Pier=pierEast
2020/12/08 15:40:54 425 - INFO - [TelescopeGoto ] - [CHECK_FLIP_MIRROR_DESTINATION_Code ] - Pier Flip Status After Last Slew = pierWest (DRV)(0)
2020/12/08 15:40:54 440 - INFO - [TelescopeGoto ] - [CHECK_FLIP_MIRROR_DESTINATION_Code ] - Expected Pier Flip Status After Slew = pierEast (DRV)(0)
2020/12/08 15:40:54 440 - EVENTO - [TelescopeGoto ] - [CHECK_FLIP_MIRROR_DESTINATION_Code ] - PIER FLIP DETECTED During Slew
2020/12/08 15:40:54 440 - INFO - [TelescopeGoto ] - [RUN_ASYNC_Code ] - Slewing Async (JNow) RA=20 35 00.458 DEC=05 15 06.88 …
2020/12/08 15:40:54 706 - INFO - [TelescopeGoto ] - [SETTLING_TIME_Code ] - Waiting Settling Time (10s)…
2020/12/08 15:41:04 737 - INFO - [TelescopeGoto ] - [SETTLING_TIME_WAIT_Code ] - Mount Assert Stable (10s)…
2020/12/08 15:41:04 753 - INFO - [BroadcastEteroMessage ] - [SendBroadcastMsgToRegisteredQueue ] - Send Request for Broadcast EVENT => GUIDING_MERIDAN_FLIP_HAPPEN
2020/12/08 15:41:04 768 - INFO - [TelescopeGoto ] - [FINISH_Code ] - Actual Position (JNow) (RA=20 35 45.391 / DEC=05 18 42.34 )
2020/12/08 15:41:04 768 - INFO - [ATOMIC_TELESCOPE_GOTO ] - [Funzione ] - Action Time [ATOMIC_TELESCOPE_GOTO] => 0 [m] 10 [s]
2020/12/08 15:41:04 784 - INFO - [ATOMIC_TELESCOPE_GOTO ] - [Funzione ] - Action Time Mobile Mean [ATOMIC_TELESCOPE_GOTO] => 0 [m] 15 [s]
2020/12/08 15:41:04 784 - WARNING - [Sequence - Safety Run ] - [ManageBroadcast_MeridianFlipHappen ] - MERIDIAN FLIP DONE , Broadcast Event incoming
2020/12/08 15:41:04 784 - INFO - [TelescopeGoto ] - [Funzione ] - Reload Pier Flip Status After Slew = pierWest (DRV)(0)
2020/12/08 15:41:05 050 - INFO - [CameraShot ] - [EXPOSE_START_Code ] - Exposing 10 [s] ; Filter=** No Filter ** ; Type=LIGHT ; Binning=1
2020/12/08 15:41:11 863 - INFO - [Telescopio ] - [PushFunction ] - PierSide= pierWest (DRV)(0) ; LastGotoPierSide= pierWest (DRV) ; FlipStatus= DA_FARE ; MeridianQuery= DO_FLIP ; LST= 20:39:32 (SW) ; RA= 20:35:53 ; LST-RA= 00:03:39(0.0609362358196783) ; AZ= 181° 13’ 37" ; ALT= 42° 00’ 55"
In your case the mount not do the meridian flip (slew time is zero) … nothing related to Voyager.
Your mount report meridian is to do and the mount passed from 3 minutes and 39 seconds the meridian.
Allow mount to do meridian flip in interval you have chosen or simple to do meridian flip if the mount have passed also for 1s the meridian … allow and not done itself. This is your problem ! Voyager doesn’t force the meridian flip because is really to dangerous and use a normal goto !!
As in SiTech.exe I leave more than half an hour of overlap and my exposures are never that long, with these settings I make sure Voyager manages the MF before the SiTech.exe flip range passes.
I have not checked the logs, but can do it next time I image.
One thing I would recommend though, is not to do your Initial Offset Init at the zenith. It can be ambiguous regarding the side of the pier you are in. SiTech.exe expects by default that the Telescope is pointing WEST at the Offset Init. So wat I do is to place the telescope with the counterweights down but the scope pointed to Azimuth 270 degrees.
Then I open Skyview and do the Offset Init on the West horizon (check that the blue pop up window shows an Azimuth of roughly 270).
After this I immediately STOP the mount and SetPark at that position.
Jose, if the driver report the pier side like what i see from other users and from log above I suggest to use the ASCOM mode for Meridian manage instead from the scope, this allow more control. Thanks for sharing your settings but the solution is in the driver settings.
Forgive my lack of experience with Voyager, but is there a method to make Voyager wait for a time for the Mesu mount to auto-flip and then restart with a platesolve and centering of the target? Is that something I need to do in Dragscript?
Voyager reports the time remaining until meridian. Can I use that to pause operations and restart after a meridian flip? It would be useful because then I know the safe control of the mount is done by the SiTech software adn hardware and there is less risk of conflict.
Voyager take care of meridian flip since 2009 and this is not the scope of an automation software to loose control of things but if you want you can put a long time in after meridian Do Flip After Mount Passing Meridian by:
Activate autoflip in your mount and in the sequence activate the ABORT Exposure if Meridian Flip occurs outside Voyager and FORCE EXECUTE Meridian Flip Operations
And please read careful the indication about you have this:
Thanks for the tip. I will select ASCOM instead of From The Scope.
As per settings. It is a SiTech.exe settings issue, ofcourse, but as far as I experienced, theSiTech.exe settings must be consistent with the Voyager ones. That’s what I meant in my answer to old_eyes. In my case I set the SiTech.exe limit long enough for my longest exposure to be able to finish before the flip, but still short enough to avoid a pier crash.
Thanks again for tour quick reply. It is a fantastic level of customer service. Best Regards,