InferenceFrameID set to 0 when restarting acquisition
Answered
Product: FFY-U3-16S2M-S-DL
Using ChunkData::GetInferenceID you can get an inference id.
To my understanding, this id can be used to check for updates of the inference data.
However, I observed that it seems like restarting the acquisition (CameraBase::EndAcquisition(), CameraBase::BeginAcquisition()) will set the inference id in the chunkdata buffer to value '0'.
This messes with the ability to check for inference updates.
I need to stop acquisition temporarily in between frames in order to reconfigure image ROI (region of interest).
-
Hello Philipp,
Thanks for the question. You are correct, the InferenceFrameID can be used to relate which FrameID corresponds to the latest Inference results, since the framerate could be higher than the inference time.
I tested this on my side in SpinView, and stopping/starting the camera did not reset the FrameID or the InferenceFrameID chunk data. I also disconnected and reconnected the camera in the SpinView GUI, and tried changing ROI size and position between stopping/starting, and the IDs did not reset. I believe they should only reset if the camera power is unplugged.
Could you please try to test this via SpinView to see if the IDs change? If you see what I see, can you please provide some code so I can test your steps on our side?
Thank you,
Demos0 -
If you can also please provide the firmware version you are using on your FFY-U3-16S2M-S-DL, I can ensure we are testing the same firmware. I am using 1905.4.0.0.
Thank you,
Demos
0 -
By the way, are there other methods (than InferenceFrameID) of testing whether the inference result has updated?
0 -
Hello Philipp.
If your framerate is different than your inference rate, the InferenceFrameID is the best way to sync them up. Can you confirm my testing, since I do not see the frameIDs resetting to 0, I believe this solution should work for you.
If you only want frames when there is new inference data available, you can actually put the camera into software trigger mode, and have inference output trigger the camera. That way, every image you get will have new inference data, the framerate will just be slower.
Details on framerates, and how to set the trigger mode can be found in the second section of our App Note at Neural Networks Supported by the Firefly-DL | Teledyne FLIR.
I'd be happy to troubleshoot the resetting to 0 issue if you decide to keep going down that path and not software triggering, I just need a way to see what you are seeing.
Thank you,
Demos
0 -
Hello Demos,
thank you, I think syncing the FPS and the inference rate is a sufficient workaround for me.
Regarding the (presumed) bug I need to clarify:
The observation was that the InferenceFrameID was set to 0, but then the counting would resume at the old value, eg:
401, 405, 408, 0, 411, 415, ...
I believe this is difficult to observe with SpinView, do you agree?
Since I will be using the above workaround, I will likely be too lazy to provide some minimal code for reproducing / detecting this behavior.
0 -
Maybe you can reproduce this by setting
TriggerSource -> InferenceReady
AcquisitionMode -> SingleFrame
And restarting acquisition a few times. The InferenceFrameID should always be '0'.
0 -
Hello Philipp,
I am unable to replicate this issue as well. Do you have a sample code that demonstrate this? Could you double check that Trigger Mode is 'ON' while using TriggerSource as InferenceReady?
I am not sure which firmware version you are referring to. Do you mean 1905.4.49.0?
Hereunder is the link to the firmware I tested:
1905.4.89.0 --> https://flir.box.com/s/e1v9hetq49ynhpbld5ekg61nd4dgp18n
Thank you,
Ifeanyi
0 -
Thanks for your help.
Yes, I am using firmware v 1905.4.49.0
Are there any known bugs with this version?
Perhaps you can try this
AcquisitionMode -> Continuous
TriggerMode -> Off
Width -> 320
Height -> 320
Inference -> On
InferenceType -> Classification
AcquisitionFrameRateEnable -> Off
For me, the camera stream freezes approximately within a minute.
Could this be the fault of the NN I am using?
0 -
Hello Philipp,
I presume that the issue you reported with '0' chunk InferenceFrameID has been resolved, right?
Yes, we had a known issue where inference sync trigger mode may freeze the acquisition.
Could you confirm if the beta firmware release from below link fix this issue?
https://flir.box.com/s/p11qcafusnhplrr5hhjrxk9ke5etps9p
Thanks,
Best regards,
Ifeanyi
0 -
Hi Philipp,
This is just a follow up message from the previous. Which neural network model version is uploaded to this camera?
To ensure that this may not be related to this model, I have attached from below link an example classification network to test with this camera:
https://flir.box.com/s/6go3f5wx1blyibzegxjporp0kb8dqjyc
I would power cycle the camera before making this test to ensure camera is not in a bad state.
Please let us know if the provided info helps to resolve this.
Regards,
Ifeanyi
0 -
Hi Ifeanyi,
Thanks!
No, the original issue is not resolved yet.
I would like to try updating the firmware.
I read this should be done using SpinView (see http://softwareservices.flir.com/FFY-U3-16S2-DL/latest/40-Installation/Firmware.htm).
However, for me the option "update device firmware" does not show up when I right-click the camera entry in the device list.
Am I doing something wrong?
Best regards
Philipp
0 -
Hello Philipp,
It seems you may be right-clicking at the interface instead of device section.
Here is an example screenshot on how to update firmware on the camera using spinView.
If the issue still persist, we may have to look at this together through remote session.
For the remote session, please open a support ticket via https://flir.custhelp.com/app/ask
Kind regards,
Ifeanyi
0 -
Hello Ifeanyi,
It seems to me like the functionality of updating firmware is only available for the windows version of SpinView, not on linux. I was not aware of that.
Is there an overview / list of know bugs for different firmware versions?
Kind regards
Philipp
0 -
Hello Philipp,
For Window OS, it is possible to flash a new firmware to this camera using either spinView or SpinUpdateConsole from command line.
Unfortunately, there is no option to update the firmware using SpinView in Ubuntu OS. We provide SpinUpdateConsole from /opt/spinnaker/bin directory to perform this operation in Ubuntu:
$sudo SpinUpdateConsole_v140.exe -R{serial number} {firmware file}
For more info about this application, enter from comand line:
$sudo SpinUpdateConsole_v140.exe --help
I am afraid we do not have such documentation available publicly for different firmware release.
As I mentioned in my previous message, we could do a remote session to work through this issue together.
Please do not hesitate to open a support ticket, and we would get back to you shortly with remote session link.
Best regards,
Ifeanyi
0 -
Hello Ifeanyi,
thank you for the offer of remote session! I will think about it.
Installing the firmware worked fine, though.
I would very much value if you would test this for me though:
Using SpinView Windows
Firmware v. 1905.4.89.0 (as you suggested)
AcquisitionMode -> Continuous
TriggerMode -> Off
AcquisitionFrameRateEnable -> On
AcquisitionFrameRate -> max
Size -> 256 x 512
Offset -> 0 x 0
Inference -> On
InferenceType -> Classification
Network -> as you suggested:
https://flir.box.com/s/6go3f5wx1blyibzegxjporp0kb8dqjyc
Please let it run for 10 minutes and report back, whether the video freezes
Also please let me know which SpinView version you are using.
Best regards
Philipp
0 -
Hello Philipp,
I have made the test for more than an hour with SpinView version 3.0.0.118, and the camera did not stop streaming.
However, customer reported in the past where camera freezes after streaming frame for a long time. But this bug has been fixed in firmware version 1905.0004.103.000.
Here is the link to download the package:
https://flir.boxcn.net/s/3e7ekmgqqjq0yv6kfl5yxf6237ad9kuh
Fortunately, the package also contain the release note including the bug fixes, changes and known bugs.
Please let us know if the provided information resolve this issue.
Best regards,
Ifeanyi
0 -
Hello Philipp
I just wanted to check the status of this camera based on what we discussed thus far.
Is the camera working fine now, or is there still some issues you could share with us?Best regards,
Ifeanyi
0
Please sign in to leave a comment.
Comments
17 comments