According to Apple’s “Nearby Interaction Accessory Protocol Specification Release R2 Developer Preview” 3.4.2, Nearby-Interaction-Accessory-Protocol-Specification-Release-R2.pdf (413.7 KB), one of the field called UWBConfigData I cannot find any specific information wrt. how to setup the message.
I looked up the DWM3000 API Guide document, there is message struct call dwt_config_t, is this the same as what Apple talks about? I tried to use this structure to compose a message, but the iOS App always rejects this message prompting this is invalid configuration.
Unfortunately these configs (AccessoryConfigurationData/UWBConfigData and AppleShareableConfigurationData/configData) are not documented, but they definitely are not dwt_config_t.
Mostly UWBConfigData seems to be always the same, with only the last two bytes changing according to the device UWB MAC short address.
@Kai17 Did you past the invalid configuration error ? I’m getting the same thing at this moment. @br1 I see there’s only the 35th and 36th byte is changing with some random numbers. The last two bytes are always the same. What do you know about the UWB MAC short address?
The UWB MAC short address is the address of the device used for the UWB transmissions later on. It changes every couple of minutes with the Qorvo demo app.
@br1 The 38 bytes that the config data is sending to the app is like this : {0x01,0x01,0x00,0x00,0x00,0x14,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x15,0x01,0x00,0x01,0x00,0x3f,0xf5,0x03,0x00,0xb8,0x0b,0x00,0x00,0x00,0x00,0x01,0x01,0x01,0x13,0xf8,0x19,0x00}.
Only the 0x13 and 0xf8 bytes is random every x time. Do you have an idea why in the application debug, it’s telling me that the accessory configuration data is invalid ? My config data is mostly like the original config data that the evaluation board is sending to the Qorvo app. Does it means that the MAC short address is not good ?