nRF8001 C custom advertising data

RE: nRF8001 C custom advertising data

run_ar — Thu, 14 Dec 2017 20:22:09 GMT

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.

RE: nRF8001 C custom advertising data

kvrbek — Thu, 14 Dec 2017 08:40:51 GMT

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.

RE: nRF8001 C custom advertising data

run_ar — Fri, 08 Dec 2017 09:15:00 GMT

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.