I am testing the anchor location setup function on the android app.
For anchors, the position contains 13 bytes, as x, y, z for 4 bytes each, and 1 byte for qf.
However, when I try to set some bytes to the x/y/z fields, and read them again, the bytes I got are not the ones I initially put into.
Initially I put 0x002519ee007e1a880007000000 as the byte stream into DWM1001-Dev through the android app. When I decode it, I got 0x012519ee807d1a880007000000.
Everytime the erroneous bytes aren’t giving me consistent values.
It seems to me that some indices within this byte stream have problems. They happen to be the LSB or Less-SB of the integers used by X, Y, Z in millimeters. After the rounding activities they are not quite obvious or won’t even render an error.
What is going on here and can anybody tell me what is the cause of this problem?
Thanks a lot