NUS only receives the first byte

RE: NUS only receives the first byte

Hung Bui — Fri, 27 Dec 2019 09:16:52 GMT

Yes, it's a very simple app, there is no special driver to send data to NUS. Please have a look at the source code of the nRFToobox here: https://github.com/NordicSemiconductor/Android-nRF-Toolbox

RE: NUS only receives the first byte

Kenan — Tue, 24 Dec 2019 16:25:56 GMT

I'm receiving all bytes when using nRFToolbox.
I'll try capturing the sniffer trace and get back.

From your answer I understand that there's no special drivers needed on the Android side to communicate over NUS. Right? This could be a problem with the debugger app.

RE: NUS only receives the first byte

Hung Bui — Fri, 20 Dec 2019 09:47:17 GMT

Hi,

Could you capture a sniffer trace of the communication when you use the BLE debugger app ?

It would reveal if the app only send one byte or not.

I assume you have no problem when testing with the UART profile inside nRFToolbox ?

RE: NUS only receives the first byte

ox00 — Thu, 19 Dec 2019 03:13:21 GMT

	public void send(final String text) {

		// Are we connected?
		if (mRXCharacteristic == null)
			return;

		if (!TextUtils.isEmpty(text)) {
			final WriteRequest request = writeCharacteristic(mRXCharacteristic, text.getBytes())
					.with((device, data) -> log(LogContract.Log.Level.APPLICATION,
							"\"" + data.getStringValue(0) + "\" senttoMCU"));

			if (!mUseLongWrite) {
				// This will automatically split the long data into MTU-3-byte long packets.
				request.split();
			}
			request.enqueue();
		}
	}

This is the code for sending. Already try using UART toolbox apps and nrfblinky apps . 244 bytes is default transfer packet. Maybe the code in Syntronix's debugger app is the problem.