nRF51822 bluetooth chip communication to nRF51 Dongle

RE: nRF51822 bluetooth chip communication to nRF51 Dongle

ereichwe — Tue, 10 Mar 2015 19:32:37 GMT

@Annim: I did that and I can see only one number (occasionally I see the whole line). What I see is: 32, when I really want to see $PRY 32, -90 , 175 (or something along those lines, not just the 32). And the log file shows only hex and I cannot understand it. I think your way works but my target device is configured/programmed.

RE: nRF51822 bluetooth chip communication to nRF51 Dongle

Hung Bui — Tue, 10 Mar 2015 14:17:48 GMT

@ereichwe: have you made sure you selected the correct baudrate and configuration in Putty ? You can test it by trying to send some string using simple uart library. The configuration should be 38400 baudrate, 1 stop bit, None parity, Hardware flow control On/Off depends on your configuration in the code.

If you want to try using Master Control panel, you would need to click Service Discovery button after you click connect.

RE: nRF51822 bluetooth chip communication to nRF51 Dongle

Annim — Tue, 10 Mar 2015 07:50:39 GMT

Hi, Right now i do not have device but i have done this from the same window actually by ->select device->and on second window when u connect there will be Rx and Tx showing and corresponding fields named "value", so i u want to send u can select that characteristics from th tree control component and type ur data on the Value field at middle of the window so shown on second window. and if u see what u have received , that u can log to any file or see then and there so updated in the tree control component against field item. this way you can first log the incoming data then see or see immediate real time changes there itself... hope this will help you out.

RE: nRF51822 bluetooth chip communication to nRF51 Dongle

Annim — Sat, 07 Mar 2015 17:44:26 GMT

Try using Master Control panel with dongle and read the incoming data in characteristics window, you will get exact data stream in. Basically it works against service, not against COM Port.