See below for a screenshot of the MAX30102ACCEVKIT# software GUI's error prompt with the text "USB HID report timeout; no interrupt? Board power? I2C connection?"
/msdyn_blobfile/$value)
This error is typically due to incorrect connection of the flexible cable between the microcontroller board and the sensor. Here are two photographs showing proper orientation:
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
The customer should carefully reconnect the two boards with the flexible ribbon cable, keeping in mind two things:
1) A little more force than originally expected may be required to get the cable into the connectors to where they make good electrical connection.
2) The cabling is small, and thus it is very easy to connect to the boards incorrectly -- such as attaching the cable at an angle, upside down, or not all the way in, etc. These conditions generate the above USB HID errors specifically when the GUI has found the microcontroller but is unable to communicate with the sensor.
This error is typically due to incorrect connection of the flexible cable between the microcontroller board and the sensor. Here are two photographs showing proper orientation:
The customer should carefully reconnect the two boards with the flexible ribbon cable, keeping in mind two things:
1) A little more force than originally expected may be required to get the cable into the connectors to where they make good electrical connection.
2) The cabling is small, and thus it is very easy to connect to the boards incorrectly -- such as attaching the cable at an angle, upside down, or not all the way in, etc. These conditions generate the above USB HID errors specifically when the GUI has found the microcontroller but is unable to communicate with the sensor.