Gemini_ASCOM_Driver

Re: G1 HC display intensity resets

brenatlilydale@... (Brendan) — Sun, 09 Feb 2025 14:07:32 -0800

Cheers Paul it’s not the problem of the century

Brendan

Re: G1 HC display intensity resets

yh@... (Paul Kanevsky) — Sun, 09 Feb 2025 08:43:29 -0800

On Fri, Feb 7, 2025 at 07:30 PM, Brendan wrote:

using G1, I have noted every time I use Gemini ASCOM advanced Gemini settings I set HC intensity (LED Brightness) to 53% and press apply ��..it’s uploaded. But once applied and uploaded the Advanced Gemini controller ASCOM settings immediately go back to 100% yet the HC change to 53% is applied ok

Hi Bren,

I've seen this behavior with G2, but not G1. There was a case where G2 would return an undocumented value for the brightness level, and the ASCOM driver defaulted to showing 100% in that case. A reset seemed to help, then. I'll have to check with a G1 to see if any of the recent changes affected brightness level for that version.

Regards,

-Paul

G1 HC display intensity resets

brenatlilydale@... (Brendan) — Fri, 07 Feb 2025 16:30:22 -0800

Hi paul

using G1, I have noted every time I use Gemini ASCOM advanced Gemini settings I set HC intensity (LED Brightness) to 53% and press apply ��..it’s uploaded. But once applied and uploaded the Advanced Gemini controller ASCOM settings immediately go back to 100% yet the HC change to 53% is applied ok

Cheers......non urgent

Brendan

Re: Stellarium 24.4 Qt6 Bug

chiplouie@... (Chip Louie) — Fri, 07 Feb 2025 07:58:51 -0800

Well that explains a lot!

Chip Louie Chief Daydreamer Imagination Hardware

Astrospheric - South Pasadena, CA

Re: Stellarium 24.4 Qt6 Bug

repast_twerps0r@... (Ryan Noonan) — Fri, 07 Feb 2025 06:29:56 -0800

The Stellarium team actually disabled ASCOM in the 24.4 QT6 build. They recommend using QT5 if you want to use ASCOM.

Re: Stellarium 24.4 Qt6 Bug

glasr@... (rglas) — Fri, 07 Feb 2025 03:57:27 -0800

Hi Chip,

Thank you for your valid request.

I am running Platform 7, Update 2, with the release # 7.0.2.4675.

Greets
Rainer

Re: Stellarium 24.4 Qt6 Bug

chiplouie@... (Chip Louie) — Thu, 06 Feb 2025 09:00:24 -0800

On Wed, Jan 8, 2025 at 06:32 AM, rglas wrote:

Greetings to you,

I use Stellarium as a planetarium software to control my G11 via ASCOM.
Yesterday I updated to version 24.4 Qt6.
Bad mistake.
Stellarium does not establish a connection via ASCOM with version 24.4 Qt_6_.
Unfortunately this is a bug especially for Qt6.

A new installation with version 24.4 Qt_5_ and everything works as usual.

Just for your information

/cheers
Rainer

Hi Rainer,

What version ASCOM do you have installed?

Chip Louie Chief Daydreamer Imagination Hardware

Astrospheric - South Pasadena, CA

Re: Help troubleshooting unexpected "safety limit" error

chiplouie@... (Chip Louie) — Thu, 23 Jan 2025 09:01:12 -0800

On Thu, Jan 23, 2025 at 05:30 AM, John Dias wrote:

Thanks Paul,

It is strange because previous flips with the same settings, limits and target were successful.

Anyway, is the calculation to determine if the slew is within limits shown in the logs somewhere? It would be helpful to see by how much the limit was blocking the slew.

Maybe CWD was not good or Gemini GPS and/or time was not right? The few times I've been told object cannot be reached or below horizon my location or time was off. And usually some app had pushed the wrong time or location data down to the Gemin 2 or the battery was marginal and it was COLD. Replacing the battery and resetting CWD fixed the issue and if not an HGM reset did the job.

Chip Louie Chief Daydreamer Imagination Hardware

Astrospheric - South Pasadena, CA

Re: Help troubleshooting unexpected "safety limit" error

yh@... (Paul Kanevsky) — Thu, 23 Jan 2025 06:10:48 -0800

On Thu, Jan 23, 2025 at 09:08 AM, John Dias wrote:

Oh, I see. Where is it actually done?

In Gemini firmware.

Re: Help troubleshooting unexpected "safety limit" error

jddias@... (John Dias) — Thu, 23 Jan 2025 06:08:23 -0800

Oh, I see. Where is it actually done?

Re: Help troubleshooting unexpected "safety limit" error

yh@... (Paul Kanevsky) — Thu, 23 Jan 2025 06:06:53 -0800

On Thu, Jan 23, 2025 at 08:30 AM, John Dias wrote:

Thanks Paul,

It is strange because previous flips with the same settings, limits and target were successful.

Anyway, is the calculation to determine if the slew is within limits shown in the logs somewhere? It would be helpful to see by how much the limit was blocking the slew.

The computation of what's accessible or not after a flip is done by Gemini, only the result is reported by Gemini.NET driver.

Re: Help troubleshooting unexpected "safety limit" error

jddias@... (John Dias) — Thu, 23 Jan 2025 05:30:05 -0800

Thanks Paul,

It is strange because previous flips with the same settings, limits and target were successful.

Anyway, is the calculation to determine if the slew is within limits shown in the logs somewhere? It would be helpful to see by how much the limit was blocking the slew.

Re: Help troubleshooting unexpected "safety limit" error

yh@... (Paul Kanevsky) — Thu, 23 Jan 2025 04:51:23 -0800

On Wed, Jan 22, 2025 at 01:47 PM, John Dias wrote:

I could use a hand getting to the bottom of this one. Background:

Last night I was imaging Lower's Nebula in NINA. All was going well, until after the meridian flip at 22:45:50 (log reference time). After the flip, NINA attempted to recenter and was denied due to a safety limit error. My eastern limit is 94d 21m so I figured maybe that was too tight. I bumped it to 98d 21m, but that didn't help. I parked at CWD and then tried to slew from there, same thing, safety limit.

The ASCOM log only says "Target unreachable!" so I don't understand what all is going on there. I don't think my safety limit is too conservative, as I've run flips with that before. Thoughts on this one? I'm scratching my head.

Hi John, "target unreachable" indicates that the combination of both safety limits is preventing the mount from reaching the target RA/DEC coordinates from the other side of the mount. I'd double check your limit settings and make sure they are not overly conservative.

Re: Help troubleshooting unexpected "safety limit" error

ThirdRockAstronomy@... (Third Rock Astronomy) — Wed, 22 Jan 2025 14:22:36 -0800

On Wed, Jan 22, 2025 at 02:18 PM, Third Rock Astronomy wrote:

ngSorry here are the setting Jim gave me the new limits the above limits are what were set I assume from Losmandy after Level 6 upgrade. Still no issue with meridian flips

Re: Help troubleshooting unexpected "safety limit" error

jddias@... (John Dias) — Wed, 22 Jan 2025 14:21:20 -0800

Thanks, I'll try that out.

Re: Help troubleshooting unexpected "safety limit" error

ThirdRockAstronomy@... (Third Rock Astronomy) — Wed, 22 Jan 2025 14:18:49 -0800

A long time ago Jim helped with with this issue an gave me these safety limits. Ever since Nina has always cooperated with meridian flips. Hope this helps

Help troubleshooting unexpected "safety limit" error

jddias@... (John Dias) — Wed, 22 Jan 2025 10:47:59 -0800

I could use a hand getting to the bottom of this one. Background:

Last night I was imaging Lower's Nebula in NINA. All was going well, until after the meridian flip at 22:45:50 (log reference time). After the flip, NINA attempted to recenter and was denied due to a safety limit error. My eastern limit is 94d 21m so I figured maybe that was too tight. I bumped it to 98d 21m, but that didn't help. I parked at CWD and then tried to slew from there, same thing, safety limit.

The ASCOM log only says "Target unreachable!" so I don't understand what all is going on there. I don't think my safety limit is too conservative, as I've run flips with that before. Thoughts on this one? I'm scratching my head.

Re: Park at Zenith Command

chiplouie@... (Chip Louie) — Mon, 20 Jan 2025 08:55:16 -0800

That is not relevant to the way the mount positions the head for a goto Zenith command. I think this is also true for a Home command and any stored home positions.

Chip Louie Chief Daydreamer Imagination Hardware

Astrospheric - South Pasadena, CA

Re: Park at Zenith Command

manu.oliva.6e23@... (Ma Ol) — Mon, 20 Jan 2025 05:43:58 -0800

Check your location (latitude, longitude, altitude), timezone in setting.

Re: Ethernet connection error?

yh@... (Paul Kanevsky) — Sat, 18 Jan 2025 18:40:33 -0800

Thank you for the update, masami! Glad to hear you got it working again.

Regards,

-Paul

On Fri, Jan 17, 2025 at 10:44 PM, YAMADA masami wrote: