An offset of 0 or pi on the poa of DW3000

Wireless Connectivity Ultra-Wideband
1

Hi!
In the paper “Push the Limit of Highly Accurate Ranging on Commercial UWB
Devices”, the authors used an extra post-final message in DS-TWR for CFO cancellation. This method works fine on DW1000.
On DW3000, with CH9 the method works, but with CH5, things are different. It seems that the POA of each message has an offset of either 0 or pi when CH5 is used. It is totally random which offset it has.
What is the cause of this offset? Is there a way to remove this offset by some configurations in the devices?
Thanks!

2

Hi @BC0023 ,

It is a known bug and we’re currently working on this issue.
We’ll keep you informed of the progress.

Kind regards,
Emre

3

Thanks! @Emre_Ozbas_Qorvo
Is there maybe a rough plan for when it will be fixed?

4

Hi @Emre_Ozbas_Qorvo

Is there any update to this issue? I am also working on extracting phase. Is there any temporary workaround for this?

Best,
XX

5

Hello,

1.) is there an update regarding the progress ?

2.) does this issue also exist on the QM33120W ?

6

Hi @FIRSTDRAGON and @xxc ,

Sorry for the delay for the fix of this issue but we haven’t incremented SDK version 1.0.2 yet. I’ll check this with my collegues and get back to you ASAP.

Regarding @FIRSTDRAGON’s Q2, yes this bug should also exist on QM33120W.

There is a temporary workaround this issue if you’re building your own FW based on the source code. If you use the existing FW in the QM33SDK 1.0.2 then you would need to wait for the next release.

Kind regards,
Emre

7

Thanks Emre @Emre_Ozbas_Qorvo ,

I am using DWM3001CDK and only compiles the Drivers code in SDK 1.0.2 for my own application. Could you describe what the temporary workaround is?

Best,
XX

8

Yes I am building my own firmware based on the source code. Could you please kindly share the temporary workaround ?

9

@Emre_Ozbas_Qorvo
Any update regarding this topic ?

10

Hi all,

Thanks for your patience, and sorry for the long overdue reply.

QM33SDK 1.1.0 has been released today. And you can find a new API in DW3XXX_Software_API_Guide_4p12.pdf document, which is dwt_setpllrxprebufen in section 5.2.6. So enabling this API mitigates the phase ambiguity problem that you have. I hope you can resolve this issue by using this solution.

https://www.qorvo.com/products/d/da008582
DW3XXX_Software_API_Guide_4p12.pdf (2.2 MB)

Kind regards,
Emre