Creation of some data processors times out
I'm currently trying to somehow squeeze out a
no_motion signal using the currently available c++ api (as it's not available) through the python bindings, but I have noticed that some data processors work fine (e.g.
highpass) whereas some of them time out upon creation and the callback is never called (e.g.
counter). I assume each data processor supports certain types of
MblMwDataSignals on the chip? If so could you please point me somewhere to read about those? I couldn't find anything about them in the docs.
Example case of a callback that is never called:
def processor_created(context, pointer): print("created") self.processor = pointer self.context = context e.set() fn_wrapper = cbindings.FnVoid_VoidP_VoidP(processor_created) libmetawear.mbl_mw_dataprocessor_counter_create(acc_signal, None, fn_wrapper) e.wait() # This is never reached libmetawear.mbl_mw_datasignal_subscribe(self.processor, self.context, self.callback)
Changing the counter to a highpass will make things work as expected:
libmetawear.mbl_mw_dataprocessor_highpass_create(acc_signal, 16, None, fn_wrapper)