For the ultrasonic distance sensor (device ID 0x3E), there are 9 modes (numbered 0 - 8). After sending the serial command select 8, the BH does not return any data.
Although, it is possible to indirectly get the data for mode 8 by configuring a combi, e.g. combi 0 8 0 8 1 8 2 8 3; select 0, it seems that there is a bug in the implementation of the BH fw for reading the data of modes numbered >= 8.
I have no direct evidence, but would suggest that developers check to see if any leading CMD_EXT_MODE message is ignored before reading the MESSAGE_DATA message.
EDIT:
I realized a little later that combi doesn't work the way I thought it would, so I crossed out the sentence above.
However, the main problem described in this issue still stands. As another example, the SPIKE color sensor (ID 0x3D) has 10 modes, and the select 8 or select 9 commands do not get any output.
For the ultrasonic distance sensor (device ID 0x3E), there are 9 modes (numbered 0 - 8). After sending the serial command
select 8, the BH does not return any data.Although, it is possible to indirectly get the data for mode 8 by configuring a combi, e.g., it seems that there is a bug in the implementation of the BH fw for reading the data of modes numbered >= 8.combi 0 8 0 8 1 8 2 8 3; select 0I have no direct evidence, but would suggest that developers check to see if any leading CMD_EXT_MODE message is ignored before reading the MESSAGE_DATA message.
EDIT:
I realized a little later that
combidoesn't work the way I thought it would, so I crossed out the sentence above.However, the main problem described in this issue still stands. As another example, the SPIKE color sensor (ID 0x3D) has 10 modes, and the
select 8orselect 9commands do not get any output.