https://devzone.nordicsemi.com/f/nordic-q-a/77211/wrong-iq-value-typeHi, I&#39;m designing my own algorithm for direction finding and for that i need IQ value as input. In NCS v1.6.0, in the locator exemple for aoa, the IQ value are store in a int8_t type in struct bt_df_per_adv_sync_iq_samples_report -&gt; bt_hci_le_iq_sampleen-USTelligent Community 13Thu, 08 Jul 2021 13:04:11 GMThttps://devzone.nordicsemi.com/thread/319194?ContentTypeID=1Thu, 08 Jul 2021 13:04:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e17dcc9a-411c-445e-850c-8068fdfc35b7PaKa<p>You will always have the chance of getting I/Q values with 0 value so your SW must support that value as well.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/319184?ContentTypeID=1Thu, 08 Jul 2021 12:48:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d6317d04-91de-474a-ba80-d856723b954fNathan_INOSI<p>Thanks, that make sense to me. The problem with 8bit format is&nbsp;that i often get a &quot;0&quot; value either at I or Q and i get a divide by 0 in my calculation.&nbsp;</p> <p>With my modifications, i get values that seem correct.&nbsp;&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/319164?ContentTypeID=1Thu, 08 Jul 2021 12:21:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b6418fb7-6d02-42fd-a0bc-b6b3a32e3daePaKa<p>The example in the nRF Connect SDK is built to be Bluetooth 5.1 compliant and then the data format for IQ data is 8 bits. The HW runs with 12 bit that is then truncated to 8-bit. To utilize the 12 bit mode you would need to use vendor specific HCI commands and that has not been implemented.</p><div style="clear:both;"></div>