This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Question about the VoxelSDK, registers MOD_N1 and MOD_N2 in the OPT9221

Other Parts Discussed in Thread: OPT9221

Hello TI,

When programming the OPT9221 registers MOD_N1 (and/or MOD_N2), using the VoxelSDK depthCamera->set("mod_n1", mod_n1)) method, I have noticed something strange:
it seems that (of the possible values 0,1,2,3) only values 1 and 2 are functioning as expected. Looking at the SDK code and comparing it with the OPT9221 specification I get the feeling that there is a bug in the SDK: register MOD_N1 (register 0x580f[ 1: 0]) is interpreted (by the SDK code) as a frequency division factor, while the OPT9221 specification says that this division factor is actually "2^(MOD_N1-1)". (Same remark for MOD_N2). Maybe this has gone unnoticed since for values 1 and 2 accidentally we have MOD_N1 == 2^(MOD_N1-1), so the bug would not reveal itself. No big issue for me (I can live with a value of 2) but please comment.

Kind regards,

Age