Problem when using "pc-ble-driver-js", sending a large file to peripheral

RE: Problem when using "pc-ble-driver-js", sending a large file to peripheral

tesc — Thu, 21 Mar 2019 16:28:18 GMT

Hi,

What I meant was that when you get that error, you wait a few ms, then try again. You do not need to wait between each writeCharacteristicValue(), you only have to wait (and then retry) when you get the waiting for BLE_EVT_TX_COMPLETE error.

Regards,
Terje

RE: Problem when using "pc-ble-driver-js", sending a large file to peripheral

Eric YY — Wed, 20 Mar 2019 07:47:42 GMT

Thanks tsec,

Seems you're right, I send the data too quickly, I don't know why but if I add 10ms delay between each writeCharacteristicValue(), the problem gone. But I meet another throughput problem, seems the implementation of the writeCharacteristicValue() is not alright for my application.

RE: Problem when using "pc-ble-driver-js", sending a large file to peripheral

tesc — Tue, 19 Mar 2019 18:18:31 GMT

Hi,

It may be that you are trying to send data too quickly, so that over time for some reason you reach a point where writeCharacteristicValue() times out. You could try to implement a number of retries of the writeCharacteristicValue() call on timeout, with an added delay of a few ms between each try.

The above would not explain why you have to disconnect and connect again to get things going again. Perhaps a sniffer trace, or logs from the peer device, could shed some light on what happens?

Regards,
Terje