¿ªÔÆÌåÓý


Re: DEC: Heavy Duty TR alarm - G11

 
Edited

The funny thing is before I sent to HC back to Brendan to be fixed, I could pick the 4x gearing in the HC, although I don't know if it actually did anything as I saw no improvement in tracking, so removed before sending the HC back to Brendan- ???


Re: DEC: Heavy Duty TR alarm - G11

 

On Thu, May 15, 2025 at 08:24 PM, Trevor wrote:
response
?
is
?
8:23:38 AM [<400:] Response: 1;1
?
Ah.. that¡¯s the problem. Looks like the PIC Servo firmware is not updated.
?


Re: DEC: Heavy Duty TR alarm - G11

 
Edited

response
?
is
?
8:23:38 AM [<400:] Response: 1;1


Re: Gemini2 does not select solar system Objects

 

Thanks Paul, I'll give it a whirl,?
?
Robert


Re: DEC: Heavy Duty TR alarm - G11

 
Edited

HC fixed and sent back (express) all good working like new. ?Spanking new display fitted and some minor HC fixes.?

I tried Gemini ASCOM yes I see the ¡°4x¡± selection Paul described but that¡¯s with my MU!

Trevor needs to run Gemini ASCOM and see what return he gets with his MU. ?

edit. ?Ahhh I missed the boat I see Paul¡¯s seen the issue?
cheers
--
Brendan


Re: DEC: Heavy Duty TR alarm - G11

 

On Thu, May 15, 2025 at 10:26 AM, Trevor wrote:
try this one
Thanks, Trevor. That's the right file this time, but it's even more confusing :) What I see is that Gemini is reporting L6.12, which is one of the conditions for enabling the 4x encoder option. But, the command to ask for PIC Servo firmware is not in the log. I can't understand how that could even happen, but let's try to get the result another way.
?
Start Gemini.NET ASCOM driver, connect to Gemini. Then, go to Setup->Command Terminal. You'll see a blank window popup. Type this directly into this window and then press Enter key
?
<400:
?
?
When you see the result below this command, please share it here.?
?


Re: DEC: Heavy Duty TR alarm - G11

 

try this one


Re: DEC: Heavy Duty TR alarm - G11

 

On Wed, May 14, 2025 at 11:37 PM, Trevor wrote:
Sorry all new to this never had to do this before in over 15 years owning my mount :)
?
Still not a Gemini.NET log. Look for the file name that I mentioned. Starts with ASCOM.Gemini Telescope .NET.


Re: G11 tracking and parking problem

 

Great! Thanks Ryan. I will re-balance and adjust the knobs.


Art Trail
attrail1@...

On Wednesday, May 14, 2025, 11:52 PM, Ryan Noonan via groups.io <repast_twerps0r@...> wrote:

Found it: ?/g/Losmandy_users/message/83608

Chip Louie explains here better than I can.


Re: G11 tracking and parking problem

 

Found it: ?/g/Losmandy_users/message/83608

Chip Louie explains here better than I can.


Re: DEC: Heavy Duty TR alarm - G11

 

Sorry all new to this never had to do this before in over 15 years owning my mount :)


Re: DEC: Heavy Duty TR alarm - G11

 
Edited

On Wed, May 14, 2025 at 08:48 PM, Trevor wrote:
Attached log don't know if will help
?
Sorry, but that's not the log I was looking for. The log I'd like to see is from the Gemini.NET ASCOM driver. That will be on your PC, the name should be something like ASCOM.Gemini Telescope .NET.xxxx.xxxxxx.txt. Before you share it, open the driver HC, connect to Gemini, and bring up the Advanced Settings window, so I can see what Gemini is reporting to the driver. After you do this, go to virtual HC Setup->View Log Folder... menu and pick the latest log file you can find there and upload it to Files section in this group.
?


Re: Gemini2 does not select solar system Objects

 

Roboscope (what is your name?)
?
Connect Gemini to the mount and start using it. Gemini doesn't let you go to objects that are below the horizon. If you believe some of these should be visible, then double-check that your geo-coordinates are set correctly, time is set correctly, and time zone is set correctly. Other than that, everything sounds like it should work fine.
?
On Wed, May 14, 2025 at 08:25 PM, <roboscope31@...> wrote:

So I tried the screen calibration again,, following every step carefully, and it appears that calibration worked and the hand controller is functional. Then I went through all the buttons with a stylus and all the buttons appear to be functioning correctly. Except for one thing. I am doing this with the Gemini2 not connected to my scope I tried going through a mock goto selection of the moon, but the moon buttons was highlighted, as was the button for mercury, Venus,? Saturn, Pluto and Neptune.? Trying to select any of the highlighted object buttons nothing would happen. At the time of writing this post, it is 8:10 PM EST, the moon is 95% waning and rises at 11:05 PM. Is this why I cannot select the moon?? I can select the sun, but the sun button is not highlighted, and it is below the horizon right now and if the same is true for the moon, the sun should be highlighted too but is not. So there is still confusion on my part about whether these highlighted buttons mean there is a problem with the hand controller. Any feedback would be appreciated.


Re: DEC: Heavy Duty TR alarm - G11

 

Attached log don't know if will help


Re: Gemini2 does not select solar system Objects

 

So I tried the screen calibration again,, following every step carefully, and it appears that calibration worked and the hand controller is functional. Then I went through all the buttons with a stylus and all the buttons appear to be functioning correctly. Except for one thing. I am doing this with the Gemini2 not connected to my scope I tried going through a mock goto selection of the moon, but the moon buttons was highlighted, as was the button for mercury, Venus,? Saturn, Pluto and Neptune.? Trying to select any of the highlighted object buttons nothing would happen. At the time of writing this post, it is 8:10 PM EST, the moon is 95% waning and rises at 11:05 PM. Is this why I cannot select the moon?? I can select the sun, but the sun button is not highlighted, and it is below the horizon right now and if the same is true for the moon, the sun should be highlighted too but is not. So there is still confusion on my part about whether these highlighted buttons mean there is a problem with the hand controller. Any feedback would be appreciated.


Re: Platesolving not as accurate

 

This is correct.

NINA internally works on the basis of J2000. Basically, anything that comes from a static database of coordinates - plate solve results, planetarium apps, NINA's own internal object database, the coordinates saved in targets and sequences - are all J2000. When telling the mount to slew to those coordinates, they are precessed, or transformed, accordingly based on what the mount driver advertises as its EquatorialSystem (that's the name of the ASCOM driver property). The precession is done via the widely-used routines that are part of the USNO's NOVAS library ().

On May 14, 2025, at 08:05, Paul Kanevsky <yh@...> wrote:

On Tue, May 13, 2025 at 11:43 PM, Chip Louie wrote:
I'm wondering how it can GOTO the same place with the J2000 on or off?
That is actually how it's supposed to work with NINA. The ASCOM driver tells NINA what precession coordinates are expected by Gemini, and NINA tries to ensure that the correct coordinates are sent. This may not work if some of the other apps settings are changed after they are connected to NINA, or if the apps are not reporting their precession settings correctly for some reason. It's a complex problem with many moving parts, all coordinated (pun not intended!) by NINA.


Re: HC not connecting to Gemini

 

Thank you for taking time to answer my question.? Here are answers to specific questions in previous posts:?
?
  • I do not have another G2, I was able to test the motors using one of my Gemini I units.? The motors work fine.? The G2 unit appears to start up properly, but the G2 hand controller gets hung up after the RESET screen.
  • I don not have a second G2 hand controller, nor do I have access to one.
  • I have not used the ethernet connection to connect G2 directly to my computer.? I haven't had a G2 in several years, so I'll have to learn how to do that again.? I know there's a YouTube video for that. :-)
  • I did remove the back cover of the hand controller to check the mini-SD card, but I didn't remove the end "plate".? Hopefully I didn't do any damage to the RJ jack, but I'll check.?
  • I hope I don't have to rewrite the SD card, one more thing to learn for a mount which will be sold soon.? :-)
Off to remind myself how to connect via ethernet...? Hopefully it's just baud rate.?


Re: Platesolving not as accurate

 

?
Oh right, duh!? I used to know that when I used PC apps under ASCOM.? With ASIAIR's planned community ecosystem I have basically forgotten all of the issues that need to be looked at every time you change or add something to the system.??
?
I think this is a major positive to having a single brand system in this regard.? All the internal arguments are settled within that single app.? Even so it still seems that people have had and continue to have issues with the ASIAIR controller with certain brands of mounts, even the ZWO strain wave gearbox mounts.? It's a wonder that a 33+ year old mount with a 25 year old GOTO controller works at all let alone nearly perfectly with the ASIAIR and ASIAIR app.??
?
Honestly I'm not missing chasing down this kind of minutiae to get my imaging gear to work.? Granted putting up with that is part of the hobby, for some part of the fun of getting to pick and choose your hardware but I really can't complain about the ZWO hardware other than the color and the fact that everyone else is using the same gear.??
?
--

Chip Louie Chief Daydreamer Imagination Hardware?

Astrospheric - South Pasadena, CA?


Re: G11 tracking and parking problem

 

Wow! Why have I not read this or seen it it any videos. I have been through all Losmandy?docs and videos that I know of. Maybe I ignored it but I don¡¯t think so.
Thanks Ryan! I will definitely change my clutch tension.


Art Trail
attrail1@...

On Wednesday, May 14, 2025, 12:29 AM, Ryan Noonan via groups.io <repast_twerps0r@...> wrote:

That's what I thought for a long time.?
Turns out, cranking down on the clutches can put excessive loads on your bearings and cause irregular wear on your shaft. It can also mess with your tracking and lead to larger tracking excursions. Super tight clutches can create problems in the long run.
?
I'll see if I can find the thread that discusses it and I'll post the link. Basically I now roll the elevation to zero (with the scope off), then put the scope on, and then balance the counterweights on the RA axis and the fore/aft position on the Dec axis very carefully. Personally I then put a piece of painters tape on my losmandy bar and mark a line even with the center of my Losmandy Mount clamp on the top of the mount so I can easily reposition the OTA. Then I remove the OTA, set the elevation back to match my lattitude, replace the OTA and I'm off to the races.?

With a properly balanced OTA, I literally just turn the clutch till it makes contact with the pad and stop, but I'm using Michael Herman's high friction clutch disks. With a clean stock disk you can probably got 1/8 or 1/4 turn past contact and stop. I can easily push my mount around in both RA and DEC without loosening the clutches.?


Re: G11 tracking and parking problem

 

¿ªÔÆÌåÓý

Hmm. ?Sounds peculiar¡­.

On May 13, 2025, at 9:58?PM, Art Trail via groups.io <attrail1@...> wrote:

?
The temp dropped about 20 degrees F between sunset and when the problem occurred. I suppose the clutche(s) could be slipping even if the knobs are tight. I have had the scope for 4 years. Maybe I should have a clutch cleaning party with the scope. I will play around with it tomorrow while I'm checking into some other things.