Custom Service Structure

[phipi]

I need to create a service on the nRF52832 that can send large amounts of a few different data types to the central device. For instance

• ADC1 sampling (~256 bytes/s)
• ADC2 sampling (~256 bytes/s)
• IMU orientation (32 bytes/s)

And I also need to be able to receive commands from the central. This would be things like:

• Start/ Stop sampling
• Update device name
• Enter Test Mode
• Device shutdown

Should I create 1 service, and a separate characteristic for each data that I need to send? What's the best way to handle the incoming commands?

[endnode]

Yes, NUS is exactly such multipurpose "tube" example and that's also the reason why it is so popular;) From GATT Server side you have basically 3 options (pull method through Read and push methods Notification and Identification) from which Notify method is the most effective (only simple command no round-trip needed).

[phipi]

And finally, I need to create a separate notify enable flag for each characteristic, correct?

[endnode]

No, once you use SD API call to create Characteristic with Notification or Indication GATT method capability the stack will take care to create CCCD handle automatically for you. All you need to do is store handles' references returned in p_handles structure supplied to sd_ble_gatts_characteristic_add call for future use because there you have both your Characteristic Value handle and CCCD handle (so once there is Write event you can check to which one, look into data and interpret them correctly).