Skip to content

ASCOM camera driver support#9

Open
rkinnett wants to merge 109 commits into
esa:masterfrom
rkinnett:master
Open

ASCOM camera driver support#9
rkinnett wants to merge 109 commits into
esa:masterfrom
rkinnett:master

Conversation

@rkinnett

Copy link
Copy Markdown

Main changes:

  1. segregated camera/mount/receiver hardware libraries
  2. added 'ascom' model to camera hardware library

The ASCOM implementation is still pretty rough, but it works with several ASCOM-enabled astronomy cameras. Tested with asi120mc, asi174mm, qhy5Lii-m, and ASCOM camera simulator. Needs review for style consistency and error handling.

@rkinnett rkinnett changed the title Added ASCOM driver support ASCOM camera driver support Aug 23, 2021
@rkinnett rkinnett mentioned this pull request Aug 23, 2021

@gustavmpettersson gustavmpettersson left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See some specific code comments.

Remove all use of hasattr, instead set all self._ascom variables necessary to None in the constructor.

Several try-except blocks are catch-all, must be fixed.

For properties that can not be set, raise AttributeError instead of returning False.

Finally the big-ticket item, there is here a thread constantly triggering and reading out the ascom camera. Is there no image event support in ascom? The present implementation is going to be very slow.

Please work on these and make a new pull request onto hw_ascom branch.

Comment thread pypogs/hardware_cameras.py Outdated
if name is not None:
self.name = name
if auto_init and not None in (model, identity):
if auto_init and model is not None:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check if model is ptgrey, if true must check identity is not None before auto init.

Comment thread pypogs/hardware_cameras.py Outdated
Comment on lines +270 to +272
- For model *ascom*, a driver name may be specified if known, (i.e. DSLR, ASICamera1, ASICamera2,
QHYCCD, QHYCCD_GUIDER, QHYCCD_CAM2, AtikCameras, AtikCameras2, etc), otherwise the ASCOM driver
selector will open.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does ascom have any way of identifying individual hardware resources? E.g. what happens if I have two cameras connected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants