FtcRobotController VS ftc_app

Yes, APK from Github, or just connect your phone to the REV Hardware Client.

I think I just stumbled upon where the team got the IMU initialization from. Take a look at the sample code in https://github.com/FIRST-Tech-Challenge/FtcRobotController/blob/master/FtcRobotController/src/main/java/org/firstinspires/ftc/robotcontroller/external/samples/SensorBNO055IMU.java

You can read my testing notes here https://github.com/FIRST-Tech-Challenge/FtcRobotController/issues/317 but there is a way to make it slightly faster

Although written for Blocks, this tutorial can help new Java programmers too: https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Timers-in-FTC-Blocks

are you working from the FtcRobotController project? https://github.com/FIRST-Tech-Challenge/FtcRobotController

Here's a sample program that uses deadlines

https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Writing-an-I2C-Driver This is the core tutorial on i2c devices, although its a little out of date so YMMV. Some things like the constructor may need to be tweaked (I believe there is now a second parameter in the super?). However the core of it is still accurate.

Are you sure? At a minimum Blocks code shows the related Java (not JavaScript) in a side-by-side view, allowing users to upgrade from Blocks to OnBot Java (or Android Studio) fairly easily. See for instance the first image at https://github.com/ftctechnh/ftc_app/wiki/Blocks-Tutorial.

https://github.com/ftctechnh/ftc_app/wiki/Using-an-External-UVC-Camera-and-a-Powered-USB-Hub just look at this, although the hub doesn't need to be a powered one, a normal one will work fine

I coded a simple I2C interface for this sensor, but have not tested it out yet as I haven't received my sensor from Adafruit yet. I'll let you know next week if it works. The code was derived from this helpful tutorial: https://github.com/ftctechnh/ftc_app/wiki/Writing-an-I2C-Driver Note: Adafruit mentions that the I2C implementation is dodgy and it can cause other I2C devices on the bus (looking at the IMU) to crash. I don't know if it matters, but I was going to test it out on its own bus.

Does it seem to tie to ESD events on the robot? If so check https://github.com/ftctechnh/ftc_app/issues/703

I found this link, https://github.com/ftctechnh/ftc_app/wiki/Writing-an-I2C-Driver for writing an i2c driver and got my device to work, but the author says his method is deprecated.

FTC code: https://github.com/ftctechnh/ftc_app/blob/master/FtcRobotController/src/main/java/org/firstinspires/ftc/robotcontroller/external/samples/PushbotAutoDriveByEncoder_Linear.java

You can maybe use this as an example (https://github.com/ftctechnh/ftc_app/blob/master/FtcRobotController/src/main/java/org/firstinspires/ftc/robotcontroller/external/samples/ConceptI2cAddressChange.java) and documentation from the sensor's website / any i2c drivers for it for other devices like Raspberry Pi or Arduino.

Then there is FTC content on github

Apparently, another team was having the same issue but with Tensorflow. Here's the link to that forum: https://github.com/ftctechnh/ftc_app/issues/620 . Once I used the updated software, it worked just fine. Thanks for all the help!

Give this a look if that doesn't get you on your way let me know where you get stuck and I'll try to give some more info where I can