Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

Vikram Kopuri
Hi ,

I've been using Point Grey's CM3-U3-31S4M-CS with MicroManager with Flycap version 2.10.3.169.

I  was able to put the camera in TTL trigger mode by settings the Device Property "Trigger Mode-OnOff" to ON. and it worked fine.

Yesterday I got the latest Nightly build of MicroManager and then updated my FlayCap to version 2.10.3.266. I did copy FlyCapture2_v100.dll and libiomp5md.dll to micromanager directory.

I see that the Trigger property was changed to "TriggerMode" and it accepts properties "Software","Internal" and "External". Setting this property to "external" doesn't seem to work, it still trigger from internal/software.

Could someone please look into it. Or correct me if i'm doing something wrong. Thanks.


With Regards

Vikram Kopuri
Electronic Engineer | Applied Scientific Instrumentation , Eugene OR, USA | +1 541-461-8181 x119


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

MarshallC
Vikram Kopuri wrote
I've been using Point Grey's CM3-U3-31S4M-CS with MicroManager with Flycap version 2.10.3.169.

I  was able to put the camera in TTL trigger mode by settings the Device Property "Trigger Mode-OnOff" to ON. and it worked fine.

Yesterday I got the latest Nightly build of MicroManager and then updated my FlayCap to version 2.10.3.266. I did copy FlyCapture2_v100.dll and libiomp5md.dll to micromanager directory.

I see that the Trigger property was changed to "TriggerMode" and it accepts properties "Software","Internal" and "External". Setting this property to "external" doesn't seem to work, it still trigger from internal/software.
I use a CM3-U3-50S5M and found the same bug.  I had to roll back to a previous version of the device adapter to get the external trigger functionality back.  I haven't had time to see if this problem exists for other models, but at least on the Chameleon3 it seems to be an issue.

I'm currently working on an update to the device adapter that adds camera specific trigger mode and source selection, as well as clearing up this and another issue with micromanager freezing when trying to connect to a camera that has it's internal registers configured for external triggering.  I haven't got to troubleshooting the external trigger issue yet, but it's fairly urgent for my own application so I hope to have it done in a day or two, and will let you know when I've got a working adapter.
Reply | Threaded
Open this post in threaded view
|

Re: Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

Vikram Kopuri
Hi MarshallC,

Thank you for taking a look at this :) , much appreciated.

Let me know if you need additional details such as logs from me to help with the debug. I'll be happy to test your improved device adapter when your done.

In the meantime , I moved to a PCO pixelfly. I wanted my plugin to support multiple cameras anyway , this is a good excuse for it.

With Regards

Vikram Kopuri
Electronic Engineer | Applied Scientific Instrumentation , Eugene OR, USA | +1 541-461-8181 x119
Reply | Threaded
Open this post in threaded view
|

Re: Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

MarshallC
Hi Vikram,

I've been very busy with other projects, but finally got back to this.  I see that in the meantime Nico fixed the external trigger issue in sequence acquisitions.  I've got a working version of my updated adapter now, and will figure out how to commit it for review this afternoon (I only use git, so any help with sending stuff upstream via svn would be appreciated).

I included a fix similar to Nico's, but have added detection of all available sources as well as modes for any FlyCapture2 compatible camera.  There are also some additional properties such as trigger parameter (used in some of the more advanced trigger modes), brought back the on/off parameter, and brought out the trigger polarity parameter for use with external hardware triggers.

In the meantime I'd appreciate anyone that's willing to test it out.  I can send the .dll or source or both via email or dropbox.  I've only been able to test it with a cm3-u3-50s5m-cs chameleon3 camera, and would like some feedback from other models.

Marshall
Reply | Threaded
Open this post in threaded view
|

Re: Possible Bug with PointGrey Device Adapter when setting Camera to TTL trigger

MarshallC
Quick update:

I issued a pull request through GitHub, so hopefully it'll propagate through to the nightly build soon.  I was also able to test it on a Grasshopper3 GigE camera (GS3-PGE-23S6M-C) this evening and the adapter is working as intended, and finds the more limited list of modes available with this camera.  Internal, software, and external triggers worked fine.

If anyone else is willing to give it a try please let me know.