4 replies to this topic

[archiebald]

My Poseidon-C runs under NINA and Sharpcap either using the native driver or the ASCOM driver, however the ASCOM driver version lacks many of the useful controls.  For example, in NINA, fan speed, sensor window heating, and cooling power is not available under ASCOM, whereas all the bells and whistles are available under the native driver.  No a problem, I just use the native driver.

 

However, I recently purchased the newly released Uranus-M Pro (IMX585) and found that under the native Player One driver, the camera is not available at all in NINA or Sharpcap. The ASCOM driver "works" but with missing features.

 

After a bit of research I came across another user with a similar problem on a different forum.

 

So here is the fix.

1.  Download the recent Camera SDK file "PlayerOne_Camera_SDK_Windows_V3.8.1.zip" or later from https://player-one-a...rvice/software/

2.  Unzip the contents and navigate into PlayerOne_Camera_SDK_Windows_V3.8.1\lib\x64.

3.  In there you'll find a file named PlayerOneCamera.dll

4.  Copy this then navigate to either Sharpcap or NINA at one of the following locations

• NINA - C:\Program Files\N.I.N.A. - Nighttime Imaging 'N' Astronomy\External\x64\PlayerOne
• Sharpcap - C:\Program Files\SharpCap 4.1 (64 bit)

5.  In these folders there is an older outdated DLL file that you simply overwrite with the new one from the SDK.

6.  Restart NINA / Sharpcap and you have the camera available under the native driver with all the native features - no need for the ASCOM driver, although it does no harm to have them both installed and might be useful in some cases.

 

PHD2 is only a 32 bit program, you can do the same thing, however, you must be sure to copy the dll file from the SDK kit from the 32-bit folder "PlayerOne_Camera_SDK_Windows_V3.8.1\lib\x86".  Having said that, there isn't really any benefit to doing this with a guide camera.

 

Hopefully this will be automatically updated in later versions of NINA and Sharpcap and PHD2, but for now this works.

 

BTW, I'm running under;

Windows 11 64bit,

NINA 3.1HF2

Sharpcap 4.1.12660.0

PHD2 2.6.13dev7

 

Edited by archiebald, 10 May 2025 - 01:25 AM.

[Bob Denny]

 

Hopefully this will be automatically updated in later versions of NINA and Sharpcap and PHD2, but for now this works.

This is a result of Player One not making those extra features available in their ASCOM driver. If they would implement those adjustments in their settings window (Chooser Properties... or NINA's Settings (triple-gear icon)), then NINA, SharpCap, PHD2 and all of the other apps like SGP, ACP, etc. would not need to code special PlayerOne settings user interfaces, and people wouldn't need to copy native DLLs around. One ASCOM driver serves all.  

 

Maybe you could ask PlayerOne to put their settings into the ASCOM SetupDialog window so ALL apps can immediately access them without each of them having to add new code in each app. We can't badger device makers for this stuff because we just seem self-serving. But a paying customer... maybe they'll pay attention to. 

 

You don't need to change fan speed, sensor window heating, and/or cooling power/temperature from one sequence to another right? Or does NINA let you change those things for each image??? Do you change them during your sequences (I'm no NINA wizard)? If so, then I am wrong here.

Edited by Bob Denny, 12 May 2025 - 04:25 PM.

[archiebald]

This is a result of Player One not making those extra features available in their ASCOM driver. If they would implement those adjustments in their settings window (Chooser Properties... or NINA's Settings (triple-gear icon)), then NINA, SharpCap, PHD2 and all of the other apps like SGP, ACP, etc. would not need to code special PlayerOne settings user interfaces, and people wouldn't need to copy native DLLs around. One ASCOM driver serves all.  

 

Maybe you could ask PlayerOne to put their settings into the ASCOM SetupDialog window so ALL apps can immediately access them without each of them having to add new code in each app. We can't badger device makers for this stuff because we just seem self-serving. But a paying customer... maybe they'll pay attention to. 

 

You don't need to change fan speed, sensor window heating, and/or cooling power/temperature from one sequence to another right? Or does NINA let you change those things for each image??? Do you change them during your sequences (I'm no NINA wizard)? If so, then I am wrong here.

Ah, you again.  I posted here under the title "PSA" to help anyone that might be having a similar issue, not to apportion blame.

 

I think I've seen mentioned elsewhere that not only Player One, but with other equipment too, ASCOM dialog box in NINA DOES allow access to all those settings.  The problem is that NINA only allows access to the full ASCOM setting dialog box while the device is not connected.  Once connected, you are locked into seeing only what NINA allows you to see.  Whether this is a NINA problem or a Player One problem is irrelevant.

 

I'm not a programmer, but isn't that exactly why Player One and others publish their SDK's, to allow developers to simply include updated and supported features?  For example, the Player One SDK version is at 3.8.1, the current full release of Sharpcap only supports up to version 3.7, it appears NINA is the same.

 

The solution I found was due to a conversation between a Sharpcap user and Robin Glover, the developer of Sharpcap.  Robin agreed that to solve the problem, that particular version of Sharpcap would require an update to support the updated SDK.  Take a look at this page's changelog of Sharpcap, apart from bug fixes etc, it is chock full of updates based on hardware maker's SDK's.

https://www.sharpcap...rpcap/downloads

 

As for your final point, yes it is sometimes necessary, or at the very least very useful, to be able to adjust those settings during a sequence in NINA.  Here's my personal experience of why.....  

https://www.cloudyni...n#entry13550586

 

Having access to that setting during the sequence allowed me to modify the dew heater power without having to interrupt my sequence.
 

Edited by archiebald, 12 May 2025 - 05:51 PM.

[fetoma]

Is there a Player One representative on Cloudy Nights?

[Bob Denny]

Ah, you again.  I posted here under the title "PSA" to help anyone that might be having a similar issue, not to apportion blame.

My purpose was not to "apportion blame". It should be clear to readers that every app developer needs to add logic for every camera when going the "native" route. I'm an ASCOM evangelist.

 

I understand why you'd like to change the heater during a sequence.

Edited by Bob Denny, 13 May 2025 - 08:27 PM.