-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Digitial input on FLIR cameras with AcquisitionTool #13
Comments
I think this would involve checking LineStatus in recordFrame and saving that info to metadata.csv? |
Currently there is no way to read the GPIO Pins of the FLIR cameras. From having a brief look at it it seems like that might be feature that is pretty quick to add, so I will definitely consider adding it. We are currently working on adding support for reading the GPIO pins of the trigger microcontroller and logging that to a file though, this should also make it possible to sync the cameras with external devices. As with many features this is not very well documented at the moment I'm afraid, so you might have to dig into the TriggerFirmware a little bit to make it work for your usecase. I'm gonna refer you to @padok again, since he's the one who implemented all this. Hope this helps, |
[1/2] Current method of synchronizationIf you use our external trigger, a similar functionality is already supported. For synchronization, the microcontroller board logs the first inputs at the time the first pulse was sent. This way you can synchronize the first images of the cameras and their internal clock to the internal clock of the external trigger.
The file contents will look similar to this:
If your setup is working correctly, pulse_id and frame_id should also align within their time intervals. Please note that if you rely on the external trigger or the in-camera clocks, you will need to correct them for longer recordings as they will drift away from each other since they are not real-time clocks. Also, unfortunately, the trigger uptime is currently only a 32-bit unsigned integer, which means it overflows every 71 minutes and 35 seconds. [2/2] Requested method of synchronizationYes, I would absolutely like to add camera input recording. But unfortunately I don't know yet how the Spinnaker SDK exposes this information to us. I need to take a closer look at this first. I have a feeling LineStatusAll might lead somewhere, but it doesn't look quite right yet. |
Thanks! The DIO on the external trigger met my needs, but I'll leave this open. |
Is there any functionality built in to AcquisitionTool to read/save signals from the digital input on FLIR cameras? e.g. for syncing data with other acquisition devices? If so, where is that information saved?
DIO documentation for FLIR cameras here. and here
The text was updated successfully, but these errors were encountered: