It seems that Point Grey expects the video imaging app to access their software with DirectShow or use their specific SDK. Perhaps some folks out there with video programming experience knows what that means.
As a user I would have thought that any camera that plugs into the USB port of a Windows PC would be recognized as an imaging device to any imaging app and could be controlled with a set of common commands, enough for PHD2 to do its work. Either DirectShow is the modern incarnation of what WDM used to do or perhaps Point Grey is going in its own direction.
Here are excepts of my conversation with the Point Grey support team:
We downloaded the software [PHD2], and cannot find a way for our cameras to work with it.
We do not have an ASCOM driver, or a WDM driver, which is what this software seems to require.
There is an option in the software for an OpenCV
webcam. Looking at code examples, this is just capturing through
opencv from a webcam, so this is still blocked by the lack of a webcam
(WDM) driver. For openCV applications, we always
suggest grabbing with our SDK and then processing with openCV, since
openCV does not support Vision standards like GigEVision, USB3Vision,
etc.
So from what we can tell, our cameras will not work on this software.
We do have a DirectShow interface in fc2, and many 'webcam' applications may support DirectShow.
The primary purpose for this camera (a Grasshopper3 with the Sony Pregius CMOS sensor) is Sun, Moon and planets so not being able to use this camera as a guidecam is only a minor frustration. This sensor is 10x the size of the DSI, so it is a "nice to have".
Time to take another look at the Starlight Xpress Lodestar. Are those ten years old yet?
Roy