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.

OPT8241-CDK-EVM: Unable to Update Register for Parameter "comp_vref"

Part Number: OPT8241-CDK-EVM


Hello Everyone,

We've been using the OPT8241-CDK-EVM successfully with the VoxelSDK over the past half-year or so. Just recently we've encountered a rather strange issue preventing us from actually streaming data.

Upon trying to connect to the TintinCDK camera, we receive the following chain of log messages:

ERROR: USBIO: Control transfer issue: Status 0
ERROR: VoxelUSBProgrammer: Could not read register for address 0x540
ERROR: VoxelProgrammerBase: Could not read register for address 0x5400
ERROR: DepthCamera: Failed to update value for parameter 'comp_vref'
ERROR: USBIO: Control transfer issue: Status 0
ERROR: VoxelUSBProgrammer: Could not read register for address 0x540
ERROR: VoxelProgrammerBase: Could not read register for address 0x5400
ERROR: DepthCamera: Failed to update value for parameter 'comp_vref'
ERROR: CameraSystem: Could not refresh parameters for TintinCDKCamera(0::0451:9105::916050915799).
ERROR: USBIO: Control transfer issue: Status 0
ERROR: VoxelUSBProgrammer: Could not read register for address 0x540
ERROR: VoxelProgrammerBase: Could not read register for address 0x5400
ERROR: DepthCamera: Failed to update value for parameter 'comp_vref'

The "comp_vref" parameter is the "reference voltage used for comparing the laser voltage in the illumination delay compensation loop." It is defined by TintinCDKIllumVrefParameter in TintinCDKCamera.cpp.

For your reference the chain of calls in the VoxelSDK generating these messages: CameraSystem::connect() > DepthCamera::refreshParams()

We've tried multiple host machines and have concluded that something must have failed on the sensor hardware itself. I'm hard-pressed to believe it's a firmware issue especially considering that our software can detect the sensor's existence and that the sensor seems to successfully boot up (the master LED is green and the chipset status LED is blue). Even the sample applications (such as "people_tracking") are experiencing the same issue. I should also note that the VoxelViewer application has no such issues connecting to and streaming from the camera. 

Any suggestions or speculation as to what the problem could be is very much welcome.

Thank you for your help,

Abdul


  • Hi Abdul,

    If VoxelViewer works without this issue, I'm not sure what causes the failure when using your own application to call into the SDK. VoxelViewer also uses the SDK internally. A few things to try to help narrow down the problem:

    1) Run VoxelViewer once to start streaming and then close VoxelViewer and connect to the board from your program.

    2) Also, try to read back "comp_vref" from the "Parameters" table in VoxelViewer. (Right click and refresh to read it back).

    3) Also, could you check if VoxelCLI (distributed as part of the SDK) throws the same error at startup)?

    4) Could you confirm the exact version of VoxelSDK that you are using?

    - Anand