Skip to content

Um reporting incorrectly #330

Description

Describe the bug
When connecting the Altair Astro 115M Mono Camera using either the ASCOM or Altair Driver it reports the pixel size as 4.63um and should be 2.31. The resolution it reports when connected in the Camera section is 8176x5616 which should be bin 1 with the pixel size of 2.31um. When selecting bin 2 the um goes from 4.63 to 9.2 but the resolution is correct at 4088x2808.

The fits header also records the wrong um and causes plate solving to fail.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Camera'
  2. Click on 'Connect'
  3. Screen shows 4.63um instead of 2.31um
  4. See screen shot

Expected behavior
The pixel size to be 2.31um would correct the FITs header.

Screenshots
If applicable, add screenshots to help explain your problem.

Image

Desktop (please complete the following information):

  • OS: [Windows 10 Pro]
  • Version [10.0.19045 build 19045]

Relevant logfiles and attachments

<Logfiles are stored in "%LOCALAPPDATA%\NINA\Logs">

20260726-140100-3.2.0.9001.6092-202607.log

Additional context
If I go to options then equipment change the 4.63 to 2.31 the fits header rights the correct um of 4.63 and a resolution of 4088x2808. However when I disconnect the camera and reconnect it the default of 4.63 is put back.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions