DataReceived Not Firing

RE: DataReceived Not Firing

Jim Hewitt — Thu, 12 Jan 2017 17:26:35 GMT

I was able to get this to work by using the following in PipeSetup:

        BtUuid BtleUuid = new BtUuid("0000F00D1212EFDE1523785FEF13D123");
        masterEmulator.SetupAddService(BtleUuid, PipeStore.Remote);

        BtUuid notifyUuid = new BtUuid("0000BEEF1212EFDE1523785FEF13D123");
        int notifyMaxLength = 20;
        byte[] notifyData = null;
        masterEmulator.SetupAddCharacteristicDefinition(notifyUuid, notifyMaxLength, notifyData);

        pipe1 = masterEmulator.SetupAssignPipe(PipeType.Receive);
        pipe2 = masterEmulator.SetupAssignPipe(PipeType.ReceiveRequest);

OnDataReceived is now firing.

RE: DataReceived Not Firing

Jim Hewitt — Sat, 07 Jan 2017 16:45:08 GMT

@Hung - I'm still working on this. I deleted the question because, truthfully, I haven't done my due diligence on it. I will undelete and update when I get it working. Looking at Proximity and HID demos. They are helpful.

RE: DataReceived Not Firing

Hung Bui — Fri, 06 Jan 2017 09:46:25 GMT

Hi Jim,

Could you confirm you managed to fix the issue ?

Note that the 0xBEEF UUID in the tutorial is 128 bit UUID with the base UUID = BLE_UUID_OUR_BASE_UUID, it's not the 16bit UUID like you are using now. You should check the UUID when you use nRFConnect or Master Control Panel.

RE: DataReceived Not Firing

Jim Hewitt — Thu, 05 Jan 2017 20:09:04 GMT

@Hung - Thanks for your response. I think most of my problems stem from commenting out the "Tasks". I assume this interfered with the callbacks. Also, I looked at the code from the Proximity demo and believe this will help. Note that the "BEEF" UUID comes straight from the tutorial.

RE: DataReceived Not Firing

Hung Bui — Thu, 05 Jan 2017 14:11:16 GMT

Have you called OpenRemotePipe or OpenAllRemotePipes after you get connected ?

The Receive pipe need to be "open" to be able to receive notification. Open here means to toggle CCCD/notification.

Also you have to make sure you have your characerteristic UUID match with "BEEF" UUID you used. It's not a standard Bluetooth SIG 16Bit UUID, but you can use for testing purpose.

I assume when you test your application on the chip with the nRFConnect application it works fine ?

Have you tried to test the Master Emulator example (nRFUART) with the ble_app_uart firmware in the SDK ?