Sending PDF files through BLE_APP_UART

RE: Sending PDF files through BLE_APP_UART

haakonsh — Wed, 16 May 2018 08:57:53 GMT

Use our macro for setting the minimum and maximum connection interval. As of now you are assigning the value 7.5 to an uint16_t which makes no sense.

You should set:
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(20, UNIT_1_25_MS)

#define MAX_CONN_INTERVAL MSEC_TO_UNITS(75, UNIT_1_25_MS)

Use these settings before you start to optimize you latency.

I will also recommend using UARTE with flow control. Then you'll get an event when the UART transmission is complete, instead of checking every receive byte for a newline.

RE: Sending PDF files through BLE_APP_UART

Mani — Mon, 14 May 2018 16:04:11 GMT

Find the code in the attached file

.devzone.nordicsemi.com/.../44716.main.c

RE: Sending PDF files through BLE_APP_UART

haakonsh — Mon, 14 May 2018 08:46:07 GMT

Hey Manigandan,

I need some detail on your implementation and more importantly some debugging information(source code, logs, error info, sniffer logs, etc).

I think the two symptoms, disconnections and data corruptions, might be unrelated.

The BLE_APP_UART example is sends ASCII strings over BLE and it is completely agnostic to it's string content with one exception. From Handling data received over UART:

"The implementation of the example requires the newline character to be '\n'. Some terminals use different characters to trigger a newline, for example '\r'. Therefore, you might need to configure your terminal to interpret only '\n' as a newline."

The reason why the doc and txt files have less corruption might be because they use less special characters or '\r' as newlines, or something in that direction.

Cheers,

Håkon.