The main protocol changes to increase the range are:
Change the data rate to 850kb/s
Increase the preamble length and the preamble acquisition size (the manual gives typical values for PAC based on preamble length).
Change the SFD symbol type to 2 (non standard 16 symbol)
The data rate is probably the biggest single win. All of these will increase packet transmission times, you may need to increase various timeouts in your code to allow for that.
You can also look at physical changes to do with antenna placement, mostly putting them higher, angeling them slightly and keeping other things away from them.
If you need to be compatible with something else then there isn’t much you can do. You’re stuck using the settings they have. You can maybe increase the preamble lengths as long as you don’t hit any timeout issues but that’s about it.
Failing that you ignore the iphone system and create your own mobile reader that then talks to a phone app over bluetooth. Which for infrastructure may be a good idea anyway, you need something that can be supported long term. Who knows what features will and won’t be in phones in 5 years time.
This is just a site demo. It is to provide evaluation of iPhone only. The deployment will talk to not just FIRA devices but other UWB protocols. We will follow with NXP, Samsung, Google phones, car locks and custom devices for government and government licensed vehicles (ie. taxis, delivery vans, etc.).
We are adding camera assist as this is supposed to increase the field of view of the UWB sensor for some reason. For our demo we need to double the number of DWM3001CDK anchors. Sample code to do this would be nice. I search the Qorvo Apple Main example app folder but did get a hit on camera assist. Been searching the internet for hours and only found isCameraAssist function. Which I assume if inquiring if camera assist is enabled.