开云体育

NINA Controlling Losmandy G11. Coordinate are not the same. Why?

Peter Boreland All Messages By This Member #68966 I'm hoping that someone can help with this problem. I'm control a Losmandy G11 using ACSOM driver for Gemini II. ? The picture shows of the problem. I've researched this but to no avail. ? NINA shows the coordinates for HD15629. The ASCOM control panel shows a slightly different set of coordinates after slewing to the NINA coordinates.? ? The white square is the camera's FOV in NINA. The small greenish circle offset in the white square is the center of where the mount is pointing. ? Why are they not the same?? ? Is there an offset that needs to be zeroed out in Gemini II? Its always the same.?
Brian Valente Member Profile All Messages By This Member #68967 It sounds like you just need to plate solve and sync the mount so they are in agreement toggle quoted message Show quoted text On Mon, Nov 30, 2020 at 8:20 AM pcboreland via <pcboreland=[email protected]> wrote: I'm hoping that someone can help with this problem. I'm control a Losmandy G11 using ACSOM driver for Gemini II. ? The picture shows of the problem. I've researched this but to no avail. ? NINA shows the coordinates for HD15629. The ASCOM control panel shows a slightly different set of coordinates after slewing to the NINA coordinates.? ? The white square is the camera's FOV in NINA. The small greenish circle offset in the white square is the center of where the mount is pointing. ? Why are they not the same?? ? Is there an offset that needs to be zeroed out in Gemini II? Its always the same.? -- Brian? Brian Valente portfolio
David C. Partridge Member Profile All Messages By This Member #68968 开云体育 My guess is that one piece of software is using J2000 epoch and the other is using JNow? ? Can you check that? Davi
Brian Valente Member Profile All Messages By This Member #68969 >>>My guess is that one piece of software is using J2000 epoch and the other is using JNow? That's a good one to check, David toggle quoted message Show quoted text On Mon, Nov 30, 2020 at 8:27 AM David C. Partridge <david.partridge@...> wrote: My guess is that one piece of software is using J2000 epoch and the other is using JNow? ? Can you check that? Davi -- Brian? Brian Valente portfolio
Sonny Edmonds #68985 A post that looks exactly the same showed up on Cloudy Nights. It appears that author found a way to correct the error by using JNOW. -- SonnyE (I suggest viewed in full screen)
Brian Valente Member Profile All Messages By This Member #68986 Sending J2000 when it expects JNOW? that'll do it :) glad it was an easy fix toggle quoted message Show quoted text On Tue, Dec 1, 2020 at 8:39 AM Sonny Edmonds <pedmondsjr@...> wrote: A post that looks exactly the same showed up on Cloudy Nights. It appears that author found a way to correct the error by using JNOW. -- SonnyE (I suggest viewed in full screen) -- Brian? Brian Valente portfolio
Sonny Edmonds #68991 I'm always interested in fixes for programs that give me a hard time. Which, come to think about it, is?EVERY?program. ;^) 8^) -- SonnyE (I suggest viewed in full screen)
Peter Boreland All Messages By This Member #69038 Edited Just to be clear. NINA was sending co-ordinate information to Gemini in J2000 format. Its failed to understand it correctly. Similarly other programs like Cartes de Ciel also had a similar error. I had selected in Gemini the J2000 format. When I deselected J2000 in Gemini, NINA defaulted to JNOW and things appeared to work OK. The fault seems to lie with Gemini. It has I think some serious problems. Right now I'm can not get it to do a meridian flip correctly. Either with NINA or using? the Gemini Telescope Application. It simply does not work. This is most surprising as I had much respect for the brand but not so much now. Interesting there are no Losmandy videos on this subject which may speak to the issue. I wonder if their software is perhaps in the hands of a third party.?
Brian Valente Member Profile All Messages By This Member #69040 hi pcboreland i think you may have confused things? Here is from the Gemini Telescope.net manual, talking about the J2000 OPTION (not default): Gemini Expects J2000 Coordinates –? By default Gemini expects epoch of the day (so called JNow) coordinates to be provided as a GoTo destination. Most planetarium software does send JNow coordinates, but if yours can only send J2000 then you need to set this parameter. This setting only affects coordinates sent to Gemini, all coordinates sent out by Gemini are JNow. By default, Gemini assumes that any coordinates you enter are for the epoch of the current date.? in other words, Gemini's default is JNOW.? you switched it to JNOW, and now it's working as expected, which sounds all correct to me Regarding meridian flip, lots of people have issues first setting it up, particularly with NINA (i don't know exactly what that is, defaults in NINA? it's free so the first package they use? dunno). It can be complicated and the flip not coordinated in the way people may think between the software and the mount (any mount really). it requires you to understand and set the values correctly. I suspect you may need to set your limits and western goto, here's the description of how they work and how to set them. One thing that's important to note is your telescope/mount setup has to be able to reach the intended target from both sides of the meridian. If the limits you set (or don't set) tell Gemini that target is not reachable, it will not do the flip? I know it's easy to blame software or the mount, but Gemini has been running fine for many years, many people including myself don't have any issues including sending goto, meridian flips, etc. I think Paul Kanevsky has done exceptional work in having the ascom driver be one of the most stable available today. hang in there, I think you'll get your settings correct and i predict all will be working Brian toggle quoted message Show quoted text On Thu, Dec 3, 2020 at 6:55 PM pcboreland via <pcboreland=[email protected]> wrote: [Edited Message Follows] Just to be clear. NINA was sending co-ordinate information to Gemini in J2000 format. Its failed to understand it correctly. Similarly other programs like Cartes de Ciel also had a similar error. I had selected in Gemini the J2000 format. When I deselected J2000 in Gemini, NINA defaulted to JNOW and things appeared to work OK. The fault seems to lie with Gemini. It has I think some serious problems. Right now I'm can not get it to do a meridian flip correctly. Either with NINA or using? the Gemini Telescope Application. It simply does not work. This is most surprising as I had mush respect for the brand but not so much now. Interesting there are no Losmandy videos on this subject which may speak to the issue. I wonder if their software is perhaps in the hands of a third party. -- Brian? Brian Valente portfolio
Jim Waters #69057 Edited Brian I am having similar or the same issue.? I am using the current release of NINA 1.10 HF2 Beta 06 and have a GM811G.? Goto using the Losmandy HC, the ASTAP plate-solving works as expected but after I do a meridian flip or change the side of pier using the HC ASTAP plate solving is always ~30 arc-seconds off.? Gemini Expects J2000... is OFF.? I am using the current release of Gemini.NET, ASCOM 6.5 SP1 and TheSkyX Pro. There's no problems doing the above with a CEM mount with ASCOM, NINA or TheSkyX.
Paul Kanevsky All Messages By This Member #69058 Jim, ASCOM driver and Gemini don't change precession settings after doing a meridian flip. Do you have a Gemini model built for both sides of the meridian??If you do a goto after a flip using the physical HC, does it center the object correctly? Regards, ? ?-Paul toggle quoted message Show quoted text On Fri, Dec 4, 2020 at 02:28 PM, Jim Waters wrote: Brian I am having similar or the same issue.? I am using the current release of NINA 1.10 HF2 Beta 06 and have a GM811G.? Goto using the Losmandy HC, the ASTAP plate-solving works as expected but after I do a meridian flip or change the side of pier using the HC ASTAP plate solving is always ~30 arc-seconds off.? Gemini Expects J2000... is OFF.? I am using the current release of Gemini.NET, ASCOM 6.5 SP1 and TheSkyX Pro. There's no problems doing the above with a CEM mount with ASCOM, NINA or TheSkyX.
Brian Valente Member Profile All Messages By This Member #69059 Hi Jim >>>HC ASTAP plate solving is always ~30 arc-seconds off.? 30 arcseconds? That is quite small? Are you able to solve and center to within your tolerance? My centering routines for SGP are larger than what you spec'd around 50"? usually if you are doing a meridian flip and it's slightly off, that is cone error.? if you feel like you want to open a ticket on this send an email to techsupport at losmandy dot com. We'll need the logs for NINA and ASCOM and probably TSX (assuming you have TSX ascom driver in the mix there).? toggle quoted message Show quoted text On Fri, Dec 4, 2020 at 11:30 AM Jim Waters <jimwaters@...> wrote: [Edited Message Follows] Brian I am having similar or the same issue.? I am using the current release of NINA 1.10 HF2 Beta 06 and have a GM811G.? Goto using the Losmandy HC, the ASTAP plate-solving works as expected but after I do a meridian flip or change the side of pier using the HC ASTAP plate solving is always ~30 arc-seconds off.? Gemini Expects J2000... is OFF.? I am using the current release of Gemini.NET, ASCOM 6.5 SP1 and TheSkyX Pro. There's no problems doing the above with a CEM mount with ASCOM, NINA or TheSkyX. -- Brian? Brian Valente portfolio
Jim Waters #69060 My modeling could be better but I don't see how that would cause issues with ASTAP plate-solving and incorrectly recentering the scope.? ASTAP successfully completes the plate solving according to the display but its always ~30 arc-seconds off after a meridian flip or changing the side of pier.? If I restart plate solving I get the same thing.? About 30 arc-seconds off.?
Brian Valente Member Profile All Messages By This Member #69061 ah I think i understand now what you're saying so if the result of centering is off. somewhere there is a setting that isn't correct. Something that small could be J2000 is set somewhere it shouldn't be.? Is there any way you can reduce the number of variables here - maybe use ASTAP to solve and manually sync?? FYI I use ASTAP nightly and it solves accurately for me toggle quoted message Show quoted text On Fri, Dec 4, 2020 at 12:06 PM Jim Waters <jimwaters@...> wrote: My modeling could be better but I don't see how that would cause issues with ASTAP plate-solving and incorrectly recentering the scope.? ASTAP successfully completes the plate solving according to the display but its always ~30 arc-seconds off after a meridian flip or changing the side of pier.? If I restart plate solving I get the same thing.? About 30 arc-seconds off.? -- Brian? Brian Valente portfolio
Jim Waters #69062 On Fri, Dec 4, 2020 at 01:06 PM, Jim Waters wrote: My m Brian - I am guessing the 30 arc-seconds.? It could be more.? When I first do a GoTo using the HC and running ASTAP there's no issues.? If the target is out of view ASTAP will plate solve and 'center' the target.? The object is in the cross hairs - 'dead-on'.? After I do a meridian flip or change side of pier things get funny.? Naturally the target needs to be recentered.? I see ASTAP making corrections to the mount and ASTAP completes.? Its always off, almost outside of the FOV.? ASTAP pointing Tolerance is 0.1 arcmin.
Jim Waters #69063 Thanks Paul and Brian for jumping in.
Brian Valente Member Profile All Messages By This Member #69064 What is the process you are using for goto/centering? i was surprised to see using the hand controller in there, so maybe i"m not understanding how you're going about it i can try to replicate here.? toggle quoted message Show quoted text On Fri, Dec 4, 2020 at 12:24 PM Jim Waters <jimwaters@...> wrote: On Fri, Dec 4, 2020 at 01:06 PM, Jim Waters wrote: My m Brian - I am guessing the 30 arc-seconds.? It could be more.? When I first do a GoTo using the HC and running ASTAP there's no issues.? If the target is out of view ASTAP will plate solve and 'center' the target.? The object is in the cross hairs - 'dead-on'.? After I do a meridian flip or change side of pier things get funny.? Naturally the target needs to be recentered.? I see ASTAP making corrections to the mount and ASTAP completes.? Its always off, almost outside of the FOV.? ASTAP pointing Tolerance is 0.1 arcmin. -- Brian? Brian Valente portfolio
Jim Waters #69065 Edited On Fri, Dec 4, 2020 at 01:28 PM, Brian Valente wrote: "i was surprised to see using the hand controller in there"? I know...? I haven't completely switched over to the new NINA usage model.? Maybe next month - New Years Resolution. Here's what I do. Turn on and set Gemini-2 Lat/Long and Time. Run PoleMaster and Polar Align. Model the mount.? I usually pick 2 stars in the West and 2 in the South.? Pine trees are in the way to the East. Turn on NINA and connect to everything.? Camera, Mount, Focuser, TheSkyX Pro...etc Use HC to slew to imaging target. Run NINA auto-focus. Run TheSkyX Pro and select / frame above target. Set up NINA imaging sequence and link to target reported by TheSkyX - import Lat/Long coordinates to NINA. Image target until meridian flip.? Mount does a meridian flip and NINA runs ASTAP to center target.? Target is always off center almost to edge of field.? I rerun ASTAP.? Same thing, ASTAP assumes its centered.? I need to use the HC to center the target. If I decide to select another target for step 9 on the other side of pier I have the same issue.? I use the HC to slew to the new target, change TheSkyX target and import the new target into NINA, ASTAP is always off. At first I thought the mount was shifting but ASTAP should still recenter the target based on the new plate solve.? One note:? The Lat/Long between NINA (Decimal format) and Gemini (Degrees, Hours, Minutes and Seconds) never agree.? NINA asked me which one to pick (Sync).? I pick Telescope To NINA. Example: Telescope Lat - 33.3166666667 Long - -111.9666666667 NINA Lat - 33.3333333333 Long - -11.9833333333 I plan to do more testing early next week.
Brian Valente Member Profile All Messages By This Member #69066 >>> I pick Telescope To NINA. if you are plate solving you should pick NINA to Telescope, assuming that's an option toggle quoted message Show quoted text On Fri, Dec 4, 2020 at 2:03 PM Jim Waters <jimwaters@...> wrote: On Fri, Dec 4, 2020 at 01:28 PM, Brian Valente wrote: "i was surprised to see using the hand controller in there"? I know...? I haven't completely switched over to the new NINA usage model.? Maybe next month - New Years Resolution. Here's what I do. Turn on and set Gemini-2 Lat/Long and Time. Run PoleMaster and Polar Align. Model the mount.? I usually pick 2 stars in the West and 2 in the South.? Pine trees are in the way to the East. Turn on NINA and connect to everything.? Camera, Mount, Focuser, TheSkyX Pro...etc Use HC to slew to imaging target. Run NINA auto-focus. Run TheSkyX Pro and select / frame above target. Set up NINA imaging sequence and link to target reported by TheSkyX - import Lat/Long coordinates to NINA. Image target until meridian flip.? Mount does a meridian flip and NINA runs ASTAP to center target.? Target is always off center almost to edge of field.? I rerun ASTAP.? Same thing, ASTAP assumes its centered.? I need to use the HC to center the target. If I decide to select another target for step 9 on the other side of pier I have the same issue.? I use the HC to slew to the new target, change TheSkyX target and import the new target into NINA, ASTAP is always off. At first I thought the mount was shifting but ASTAP should still recenter the target based on the new plate solve.? One note:? The Lat/Long between NINA (Decimal format) and Gemini (Degrees, Hours, Minutes and Seconds) never agree.? NINA asked me which one to pick (Sync).? I pick Telescope To NINA. Example: Telescope Lat - 33.3166666667 Long - -111.9666666667 NINA Lat - 33.3333333333 Long - -11.9833333333 -- Brian? Brian Valente portfolio
Jim Waters #69068 Plate solving always works the first time when I pick Telescope to NINA.? I have noticed that the Lat/Long on the HC always changes after connecting to NINA.? I will try NINA to Telescope this weekend.

Previous Topic Next Topic