Enhancement request: a machine camera interface for PHD2

[Roy]

All,

I decided to turn this into an enhancement request.  I think that there should be a choice to select either DirectShow, USB3Vision or GenICam machine vision cameras (like Point Grey, Basler, IDS, Imaging Source) that are populating the equipment shelves of astrophotographers.  In my case I have a Point Grey Grasshopper3 that I thought might do double duty as an OAG guide camera but there is no way to connect to PHD2.  About the above I would guess that the order of preference would be USB3Vision, then DirectShow and finally GenICam (but Point Grey has no GenTL producer which I thought would have been the camera manufacturer's responsibility).

Here is my last communicaton with Point Grey:

(me)

If the developers of PHD2 were to create something we could call "Generic GenICam camera" would they then be able to access the wide range of machine vision cameras including Point Grey but perhaps also others (Basler, IDS, Imaging Source) that are finding wide acceptance in astrophotography?  Is this something that would be possible for someone with only an expert's level of knowledge of drivers, digital cameras, etc. but abundant spare time?

So:  generic, fit for purpose, wide applicability, feasible?

(response)

Yes, if the developers could include support for USB3Vision or GigEVision cameras, then it would support any camera manufacturer who implements those standards like Point Grey.

We do not know much about open source code for USB3Vision, but Aravis is open source code for GigEVision, so even implementing something like the Aravis API may help and reduce the need for extra driver/standards development.

As an alternative, support for our cameras could be added by using our API in the software, but that would limit it to supporting Point Grey only.  Using a standard would help add multiple machine camera manufacturers to the list of supported cameras.

Point Grey does not offer a GenTL producer though, a new or existing driver stack would need to be used in any GenIcam based software that would work with our cameras.

At this point I am well past my pay grade.  Please pass this enhancement request up to "the committee" for consideration.  I don't know if I am asking for something that can be done in a long weekend by the appropriate party or if we would have to go the crowdfunding route and hire someone.

Thank-you for your consideration.

Roy

[Marcin Szczurowski]

Hi,

It looks like I missed that topic yesterday. Digging it out from 8 years ago o_O.

I'm on the same train here.

I have a Daheng MER-130-30UM-L, which is GenICam compliant industrial USB camera with monochromatic Onsemi MT9M001 sensor. Some IDS units use that sensor as well.

And it just fails to run properly as WDM webcam (although it works in MetaGuide in 1024x768 resolution with DirectShow driver).

PHD2 could use vast majority of acquisition hardware having just those general options implemented:

- USB video device class (UVC)

- DirectShow

- GenICam / GenTL

- USB3 Vision

- GigE Vision

Leaving Matrox and other legacy standards out, as this would probably be overkill.

I'm not that sure about order of that list / popularity.

Anyway, that would pretty much rule out further implementation efforts, as virtually all cameras follow at least one of those standards.

Best regards,

Marcin