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
{{ message }}
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.
I've just checked:
write_value calls: gatt_characteristic1_call_write_value_sync
Which seems to be generated code?
Is there a way to call it asynchronously? And is there a way to reduce the connection interval from dbus?
I've just checked:
write_value calls: gatt_characteristic1_call_write_value_sync
Which seems to be generated code?
Is there a way to call it asynchronously? And is there a way to reduce the connection interval from dbus?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've measured the duration of sending one packet of 8 bytes to the peripheral with the code below:
auto tick = boost::posix_time::microsec_clock::local_time();
this->nus_char_tx->write_value(buffer);
auto now = boost::posix_time::microsec_clock::local_time();
boost::posix_time::time_duration diff = now - tick;
auto mili = diff.total_milliseconds();
std::cout << "Time elpased: " << mili << std::endl;
It gives me around 70-90 ms. My peripheral set the connection interval between 7.5-75 ms. So how could it be that long for sending just some data.
Best regards,
The text was updated successfully, but these errors were encountered: