NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/f/nordic-q-a/3416/nrf51822-uart-print-stops[Update 8/15] Here&#39;s the file for the main part of my code: sensors.c . The sensors_start() function at the bottom is where the while loop and the print statements are located. If there are any questions about the code, please let me know. Helloen-USTelligent Community 13Fri, 30 Oct 2015 12:09:31 GMTRE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12411?ContentTypeID=1Fri, 30 Oct 2015 12:09:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cc6d3708-8b94-4c25-96e9-9d871fa2b555ahmet<p>I&#39;m currently using the nrf51822 and I&#39;m trying to constantly send the accelerometer data to the nRF UART v2.0 Android Application.But I cant.Can you give me this project code? ahmet.serefoglu46@gmail.com</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12407?ContentTypeID=1Fri, 10 Oct 2014 14:12:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b794e464-fa89-429b-a53c-1fbc4cee67f8Anders<p>I&#39;ve successfully run the UART example using ble_nus_send_string() (only string literals, though) in a while (1) loop. I agree with scytulip: run in debug mode and set a breakpoint in the app_error_handler() function of your application. The breakpoint will trigger if the SoftDevice stack returns an error code other than NRF_SUCCESS. Then you can read out what the error code, the line number and the source file where the error occurred. If the breakpoint never triggers, you could manually halt execution when the chip stops sending data to your phone.</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12410?ContentTypeID=1Fri, 15 Aug 2014 20:59:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bbcbb5b2-f06a-425d-bab9-2d9567848874Kenneth<p>Sorry for the response, classes have been keeping me busy. The post has been updated with the sensors.c code attached. Also the sample code and screenshot have been updated to the most recent changes I&#39;ve made to the code.</p> <p>scytulip, I believe debugging does not work with the bluetooth enabled. I&#39;ll try using the error handler though.</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12409?ContentTypeID=1Mon, 11 Aug 2014 13:10:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7c60bc8f-09b1-4664-879d-afa496335117John<p>What code returned that error? Perhaps post the code snippet or module to give more context.</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12408?ContentTypeID=1Sun, 10 Aug 2014 07:53:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:58123ca6-e73e-4ae2-87fc-21e9f3b7bc2aFlow Sky<p>I met the same problem. I found that the value of return error is NRF_ERROR_INVALID_STATE, but I did&#39;t known why.</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12406?ContentTypeID=1Fri, 08 Aug 2014 15:14:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3dbd60ec-c0ab-4e10-aa86-90da1381d4ffscytulip<p>Use debug to find out whether your code run into error handle, and locate the line No. which triggered the error. Are you using scheduler? Sometimes the event queue overflow due to too many BLE events in a short time.</p><div style="clear:both;"></div>RE: NRF51822 Uart Print Stopshttps://devzone.nordicsemi.com/thread/12405?ContentTypeID=1Fri, 08 Aug 2014 11:40:04 GMT137ad170-7792-4731-bb38-c0d22fbe4515:967bd9b9-c63f-4aac-ae99-e3107ba1bad4Anders<p>Could you please attach the complete code?</p><div style="clear:both;"></div>