Is it possible to "reinit" OPU after incorrect close operation

Once I’ve messed ctrl+c with ctrl+z shortcuts and suspended the python process instead of killing it. Then I’ve resumed the process and saw something like this

[2021-06-16 14:14:58,589] ERROR siso.fglib.lib: Failed to get last pic number: Timeout [board-index=0, board-serial=754114f9, board-type=7541, dma-index=0, error=-2120, handle=(P11Fg_Struct_s)0x56047a3d3528, next-frame=187, thread-id=139825756251904, timeout=5]
^C[2021-06-16 14:15:03,709] ERROR siso.fglib.lib: Failed to get last pic number: Timeout [board-index=0, board-serial=754114f9, board-type=7541, dma-index=0, error=-2120, handle=(P11Fg_Struct_s)0x56047a3d3528, next-frame=1, thread-id=139825756251904, timeout=5]
Traceback (most recent call last):
  File "/opt/anaconda3/envs/opu-base/lib/python3.8/site-packages/lightonml/internal/utils.py", line 23, in try_or_giveup
    return func(*args, **kwargs), count
RuntimeError: Input device is stalled, remaining items is 513

After killing the process I found, that OPU refuses to work:

/opt/anaconda3/envs/opu-base/lib/python3.8/site-packages/lightonml/internal/device.py in open(self)
    138         # noinspection PyPep8
    139         try:
--> 140             self.__opu.open(self._frametime_us_off, self._exposure_us_off,
    141                             self._sequence_nb_prelim, self.verbose)
    142 

RuntimeError: Starting input device system: Unknown error -1

How to deal with such situations?

Hi Bogdan,

In some rare case the OPU device can get stuck, and needs intervention from us to be reset. It should now be working again for you.

Best,

Charles