It looks like you're new here. If you want to get involved, click one of these buttons!Sign In
It looks like you're new here. If you want to get involved, click one of these buttons!
Our case is the following problem:
At the moment we use stick v1 with OpenVino.
Our movidius configured to execute predictions at 4fps speed.
When Movidius starts to overheat, predictions slows down depends on the temperature.
Finally, Movidius getting stuck and does not return any predictions.
I succeeded to create the mixed c++ project, using the source of APIv1 for Windows and APIv2 for Linux and now we are able to receive the temperature on Windows. Unfortunately, the Movidius firmware for APIv2, that I am using does not support Stick v2 and is not compatible with OpenVino's firmware. But we can use it now for a while.
However, after the movidius stopped to return predictions, after 45 seconds timeout we reset it and receive its temperature, which is about 73-75 degrees. We don't know exactly, what temperature is at the moment when it stuck, but it's definitely higher. Now, thanks to this function, we are also sure enough, that the problem is in overheating.
We hope there would be some functions in OpenVino to monitor the current Movidius state: temperature, memory consumption and so on. And maybe some internal functions to reinitialize or reset the device during its work.