Telescope aperture vignetting caused by 1 degree dome azimuth command resolution

[dolphinzilla]

Due to the 1 degree default azimuth command resolution, telescopes with large apertures can experience vignetting of the aperture by the edge of the dome slit as the telescope/mount moves continuously but the dome only moves on 1 degree changes. For astronomers doing non-differential photometry this issue creates discontinuities in the light curves that are difficult to correct for. Problem observed with a Celestron C14 EdgeHD with a 0.7 reducer.

TA.Nexdome.Server-2019-11-30-MSI_dolphinzilla-MSI.log
TA.Nexdome.Server-2019-11-29-MSI_dolphinzilla-MSI.log

[dolphinzilla]

PHD Log exhibits steps in the star SNR curve on the 1 degree dome moves

[NameOfTheDragon]

Proposal

• The existing @GAR "Goto azimuth degrees" command remains unchanged for backward compatibility.
• Introduce a new firmware command, @GSR,sssss "Goto step position". This allows the rotator to be moved to an exact whole step position. The firmware protocol was not designed to include floating point numbers so the proposal is to accept a step position and not an azimuth. The target whole step position must be computed by the driver or application plug-in.
• There are 55,080 whole steps per revolution, so this gives a theoretical positioning resolution of 360/55080 = 0.00654 degrees.
• Driver or application can compute the step position for a given azimuth as circumference / 360 * target azimuth
• Driver or application can obtain circumference using the @RRR command, which returns the circumference in whole steps.
• Dead zone still applies. Moves smaller than the dead zone will be ignored. Dead zone is settable using the @DWR command.

This will then require a new version of the ASCOM driver that uses the new command. Optionally, other drivers and plugins would also have to be updated.

Feasibility

Initial investigation suggests that this could be added to the firmware reasonably quickly and with low risk. The firmware would remain backward compatible with all existing drivers and plugins.

Recommendation

I recommend that this feature should be added to the firmware and a subsequent version of the ASCOM driver.

@nexdome Are you happy for me to go ahead and add this feature?

[dolphinzilla]

The experimental firmware version seems to work perfectly - I checked backwards compatibility with ASCOM driver 3.0.1 and ran it through its paces across the 0 point as well (left and right of zero azimuth)

[NameOfTheDragon]

Ok that’s great news, thanks for letting me know. I’ll merge this in to a maintenance release at some point. Rodolphe has also added support into his X2 plugin for TheSky. I suppose I’ll have to update the ASCOM driver now 😉 Best regards, Tim Long From: dolphinzilla <notifications@github.com> Sent: 01 December 2019 20:59 To: nexdome/Firmware <Firmware@noreply.github.com> Cc: Tim Long <Tim@tigranetworks.co.uk>; Assign <assign@noreply.github.com> Subject: Re: [nexdome/Firmware] Telescope aperture vignetting caused by 1 degree dome azimuth command resolution (#20) The experimental firmware version seems to work perfectly - I checked backwards compatibility with ASCOM driver 3.0.1 and ran it through its paces across the 0 point as well (left and right of zero azimuth) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#20?email_source=notifications&email_token=AAJVWCQ7AOWHATPYCKLNYF3QWQQTDA5CNFSM4JTHFPWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFRVNBY#issuecomment-560158343>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJVWCQPK7P6TUIZH5F3GGTQWQQTDANCNFSM4JTHFPWA>.