This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF8001 C custom advertising data

Hi There,

In company we are working with nRF8001 (currently C revision) and we want to send some custom data in an advertising packet. However, when C revision is selected in nRFGoStudio, custom data option is disabled. Is there any way to send custom data with revision C? And another question, how to programmatically determine revision of nRF8001? There is GetDeviceVersion request described in product specification but I cannot find how to interpret response.

Best Regards,
Krunoslav

Parents
  • Custom data isn't supported on revision C.

    You can use the GetDeviceVersion commandt to get the device version, mainly ment for debugging: Configuration ID (2 bytes); nRF8001 configuration identifier (LSB/MSB). This number can be used to trace the nRF8001 HW and FW versions. If you let me know what is returned in the command response event, I can tell you what version it is. Unfortunately i don't have a public list with an overview of the different numbers.

Reply
  • Custom data isn't supported on revision C.

    You can use the GetDeviceVersion commandt to get the device version, mainly ment for debugging: Configuration ID (2 bytes); nRF8001 configuration identifier (LSB/MSB). This number can be used to trace the nRF8001 HW and FW versions. If you let me know what is returned in the command response event, I can tell you what version it is. Unfortunately i don't have a public list with an overview of the different numbers.

Children
  • Thank you very much on response. As you probably know, there is different configuration generated by nRFGoStudio with respect to device version. Configuration for one revision does not work on another, although I read somewhere that config for C should work on D. No, it does not work.
    There are C/D letters on package so we know what revision they are. What we trying to do is to modify current library to have two configurations and programmatically decide what config to apply.
    By last information what we have, new batch ordered is Rev D. so maybe there is no issue anymore.

  • Config for C should run on D, Config for D will not run on C as C is an older version with fewer options. It's probably a good idea to take a look at the PAN document for revision D as well. Just to have the information in the back of your head when devloping.

Related