ftc19743

We are seeing multiple related issues while utilizing 3 Logitech 270s: - Attempts to set up each on their own VisionPortal hang indefinitely during the build process (drove us to...

Thanks as always for the insights! We can see in our log a bit of the call stack you referenced above. ``` getMinExposure(NANOSECONDS)... 2024-11-22 10:40:21.524 1687-1794 Uvc com.qualcomm.ftcrobotcontroller D [jni_devicehandle.cpp:654]...

Thanks, very interesting to see how to get down to the lower levels. This confirmed that the values passed to setExposure are indeed finding their way down to the camera...

The team is now trying to use the captureTimeNanos parameter that is passed to processFrame() to help coordinate their CV with actuator movements. They have not been able to determine...

We got our new PixyCam2 (an I2C device that uses a [request/response style communication](https://docs.pixycam.com/wiki/doku.php?id=wiki:v2:porting_guide#pixy2-serial-protocol-packet-reference) on the bus instead of registers), coded up a basic I2C wrapper for the device following...

> the extra byte is lost inside the Hub firmware and never makes it over the wire to the SDK. Ahhh. :( We'll ping Rev.

> The only command that I see where the length of response is actually variable is getMainFeatures() getBlocks() in the Color Connected Components portion of the interface has a dynamic...

> your best bet is probably to just issue a 100-byte read (the max you can do in a single transaction) for the time being. So this worked for us....

Of possible interest: If we put a powered USB Hub (like the Rev UltraUSB Hub) in between the Control Hub 3.0 port and the webcam, the failure mode shifts to...

Thank you! We are definitely adventurous! However, modifying the SDK at the C++ level and rebuilding the libraries and getting those rebuilt libraries incorporated in our Android Studio build would...