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
With long writes from a device to the 101: I noticed that valueLength is always returning 64. It is necessary to get the correct length of data to keep from reading garbage at the end. I haven't seen any crashing though. I will attach the peripheral sketch used. I was using nRF connect to send text "0123456789". Ellisys shows "0123456789" in the traces.
This is the output from the serial terminal of the peripheral sketch that is reading the 10 characters sent from the phone.
value length: 64
value: 0123456789K?õßm÷çõðë·�–Pñß�ÿüÿ�ŸˆhÓ�
The text was updated successfully, but these errors were encountered:
BLE.begin();
BLE.setLocalName("Test101");
BLE.setAdvertisedServiceUuid(CloudPrimaryService.uuid());
BLE.setDeviceName("Atmosphere Test");
// add service and characteristics
With long writes from a device to the 101: I noticed that valueLength is always returning 64. It is necessary to get the correct length of data to keep from reading garbage at the end. I haven't seen any crashing though. I will attach the peripheral sketch used. I was using nRF connect to send text "0123456789". Ellisys shows "0123456789" in the traces.
This is the output from the serial terminal of the peripheral sketch that is reading the 10 characters sent from the phone.
value length: 64
value: 0123456789K?õßm÷çõðë·�–Pñß�ÿüÿ�ŸˆhÓ�
The text was updated successfully, but these errors were encountered: