We have ble tags and these ble tags give us x, y, z acceleration. While receiving this acceleration, a default value is returned with certain periods. The hardware company confirmed that the reason for this default value is software related. During the calculation (x,y,z), some values in x,y,z overlap with deviceInfo, that is, the hex form of the device.name value in the library. To be more precise, the 13,16th digits of the returned row value give us information about the device name, while 16,17 gives us a value about the x period and causes a confusion. Can you support us to solve this situation?
We have ble tags and these ble tags give us x, y, z acceleration. While receiving this acceleration, a default value is returned with certain periods. The hardware company confirmed that the reason for this default value is software related. During the calculation (x,y,z), some values in x,y,z overlap with deviceInfo, that is, the hex form of the device.name value in the library. To be more precise, the 13,16th digits of the returned row value give us information about the device name, while 16,17 gives us a value about the x period and causes a confusion. Can you support us to solve this situation?