camera support for player one astronomy camera

[Dave Smith]

Who do i contact to get support for player on astronomy cameras

[bw_msgboard]

In order to support the native driver and SDK, we would need to have the camera in-hand and someone with the time and interest in working with it.  But it looks like Player One has an ASCOM driver as well, and that should work with PHD2 without any changes on our side of things.  Why don’t you install the ASCOM platform and the ASCOM driver for the camera and give it a try.

 

Bruce

 

---

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/b223b807-d3ba-4ba9-82d7-610daef3cc59n%40googlegroups.com.

[mj.w...@gmail.com]

Google is your friend.

https://player-one-astronomy.com/service/software/

[Brian Valente]

Hi Nikko

>>>I'm currently using ASCOM to connect the camera, but would like to have native driver support to have better control over the camera in PHD2, and be able to use the darks library.

Is there something in the ASCOM driver that is preventing you from using the dark library function in PHD with your camera?

 

On Mon, Jan 24, 2022 at 10:12 AM Nikkolai Davenport <wcoas...@gmail.com> wrote:

Hi Bruce,

I've been wondering this as well. I'm currently using ASCOM to connect the camera, but would like to have native driver support to have better control over the camera in PHD2, and be able to use the darks library.

I have two Player One cameras: Mars-M (IMX290) and Neptune-C II (IMX464). Please let me know if you'd like me to test. I have a background in QA and software development, and am more than happy to help.

Kind regards,

Nikko

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/7064390e-1393-48a0-9b22-de1ec3259270n%40googlegroups.com.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[bw_msgboard]

Can't you access these camera properties from the ASCOM properties dialog?  From the Help content:

 

 

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Nikkolai Davenport
Sent: Monday, January 24, 2022 11:57 AM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] camera support for player one astronomy camera

Hi Brian,

No, I think I was mistaken. The "Darks > Dark Library..." menu option is disabled while the camera is looping. I was able to select the menu item, and generate the darks library after pressing "Stop".

The only thing that seems to be unavailable is camera settings while the camera is connected. Current workflow is to disconnect the camera, adjust camera settings (bit depth, gain, offset, bandwidth), and then reconnect to the camera via ASCOM drivers.

Would camera settings for Player One cameras be available if native driver support were implemented in PHD2?

Thanks in advance,

Nikko

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/4b850316-bc00-4d5c-be48-8ab9721ff784n%40googlegroups.com.

[Brian Valente]

Hi Nikko

we're talking about the guide camera, so i'm not sure how much evaluation you would need to do? pretty much set it up once and forget it. Or is there something unique about what you are doing?

I've imaged going on 12+ years and never had to tweak my guide camera settings, been through a handful of guide cameras and mfgs as well. I do not have the Player One camera though

On Mon, Jan 24, 2022 at 4:02 PM Nikkolai Davenport <wcoas...@gmail.com> wrote:

Yes, but again, those camera settings (bit depth, gain, offset, bandwidth) are only accessible when the camera is not connected.

Current workflow involves:

1) Observe and evaluate image quality
2) Disconnect camera

3) Open camera settings to adjust camera settings (bit depth, gain, offset, bandwidth)

4) Reconnect camera

5) Repeat

Having to disconnect/reconnect between changes seems unnecessarily inconvenient from the perspective of the user. An easier approach would be to just determine these camera settings using another application such as SharpCap, then apply them once in PHD2 and be done with it. Which is my current approach, but I was hoping for better simply from a quality of life standpoint.

I'm happy to offer my services as a tester, but I understand this issue is not urgent and may not be significant enough to warrant attention at this time.

Either way, I appreciate the consideration.

Kind regards,

Nikko

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/ed83020b-96b2-41cc-bf1d-72b9e34976een%40googlegroups.com.

[bw_msgboard]

Hi Nikko.  Just to wrap this up, there's really no way for us to implement a native driver interface without having a camera and the time required for the development and testing.  Right now, we have neither. Obviously, if a particular camera has gained a large market share and many people are requesting it, the priority for us would go up and we might be able to acquire a camera from the vendor.  That said, I think you're possibly making things harder for yourself than they need to be.  None of the camera properties you mentioned below should be affected in a meaningful way by differences from one night to another.  I've never heard of anyone who fiddles with these things for every session.  The ASCOM driver should retain whatever values you have chosen, so I really think you can just connect to the gear and start imaging.

 

Regards,

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Nikkolai Davenport

Sent: Monday, January 24, 2022 4:02 PM
To: Open PHD Guiding

Subject: Re: [open-phd-guiding] camera support for player one astronomy camera

Yes, but again, those camera settings (bit depth, gain, offset, bandwidth) are only accessible when the camera is not connected.

Current workflow involves:

1) Observe and evaluate image quality
2) Disconnect camera

3) Open camera settings to adjust camera settings (bit depth, gain, offset, bandwidth)

4) Reconnect camera

5) Repeat

Having to disconnect/reconnect between changes seems unnecessarily inconvenient from the perspective of the user. An easier approach would be to just determine these camera settings using another application such as SharpCap, then apply them once in PHD2 and be done with it. Which is my current approach, but I was hoping for better simply from a quality of life standpoint.

I'm happy to offer my services as a tester, but I understand this issue is not urgent and may not be significant enough to warrant attention at this time.

Either way, I appreciate the consideration.

Kind regards,

Nikko

On Monday, January 24, 2022 at 2:58:42 PM UTC-8 bw_m...@earthlink.net wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/ed83020b-96b2-41cc-bf1d-72b9e34976een%40googlegroups.com.