Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

RE: Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

Liam — Fri, 22 Jun 2018 23:23:08 GMT

This did it. Thank you!

RE: Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

Martin Lesund — Tue, 19 Jun 2018 13:08:58 GMT

Hi Liam,

I have been informed that you will test this on the nRF52DK.

Please let me know your results.

Please check this thread for the solution of your issue.

"The ADC values are not converted to a string before sent over NUS. If you want to display the values as a string, you have to convert it to a string before sending it. You can use sprintf() function or similar for this."

Best Regards,

Martin L.

RE: Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

Liam — Mon, 18 Jun 2018 15:58:54 GMT

Martin, thank you for the reply, and sorry for the delay.

I get the same result when I use the nRF Toolbox app.

The "ble_app_uart_timer_driven_scan_mode" example is unmodified EXCEPT for that I changed the four pins read in default to four different analog pins. (0-3)

I can connect to the device normally when the "ble_app_uart" example is loaded, but I am not sure how monitor the com port -- no port is created by the ST Link programmer, that I can tell.

RE: Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

Martin Lesund — Thu, 14 Jun 2018 08:42:12 GMT

Hi Liam,

First off, I would like you to use the "uart" app inside the nRF Toolbox app. This is the updated version of "nRF Uart v2.0".

From the first look it seems like the baudrate can be off.

Are you running the unmodified "ble_app_uart_timer_driven_scan_mode" example?

Have you tested the standard "ble_app_uart" example as well?