You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the writing and notification exchange during initialization I get a status 16 response and initialization breaks. When changing the value to >250, then everything works fine and initialization is completed successfully.
Is it possible to make TIME_PER_COMMAND into parameter to set instead of a constant? Or at least bump it to >250?
The text was updated successfully, but these errors were encountered:
Increasing the constant to 250ms is fine. I don't want it set too high or else the initialization timeout will end up being 15+ seconds which is over kill.
I understand and agree. Currently I replace 150 with 300 before compiling MetaWear-CppAPI, so there is no immediate need to bump it to a higher value just to get something to work.
In src/metawear/core/cpp/constant.h the value is hard coded to 150. This value is used in
mbl_mw_metawearboard_initialize
and makes the initialization fail when I use the library.During the writing and notification exchange during initialization I get a status 16 response and initialization breaks. When changing the value to >250, then everything works fine and initialization is completed successfully.
Is it possible to make
TIME_PER_COMMAND
into parameter to set instead of a constant? Or at least bump it to >250?The text was updated successfully, but these errors were encountered: