From the product description, this is very hard to use in FTC. In order to use this Ultrasonic sensor, you need the capability of sending a pulse to the "Trigger" pin with a pulse width of at least 10 usec. Then you need to monitor the "Echo" pin for a pulse and time the pulse width. This is easy for micro-controllers such as Arduino or Raspberry Pi because that have interrupt pins that you can start a timer to time a pulse. FTC SDK is running on Android which is not a real-time OS. So, it is difficult to do hardware timing precisely. For example, let's say you have a tight loop monitoring a digital input pin on the REV control hub that's connected to the "Echo" pin. Once you saw the "reflected pulse", you note the current timestamp and keep a tight loop monitoring the trailing end of the pulse. But if Android OS is preempting your thread in this tight loop to do something else, you could come back much later when the pulse trailing end is long gone. Therefore, the accuracy of timing a pulse is not guaranteed. In addition, there is no direct way of monitoring a digital input pin in FTC SDK. If your robot program is running on an Android phone, your call to read the state of a digital pin goes to the FTC SDK which will send a USB request to the REV expansion hub. FTC SDK is also doing some "optimization" with caching (i.e. USB bulk read) etc. It means the digital input read is not performed in real time. Therefore, it is impossible to time a pulse accurately. You should get an ultrasonic sensor that have hardware/firmware to time the pulse for you and send you the distance data in some other form such as I2C, or even an analog voltage. Products such as MaxBotix Ultrasonic sensor which is popular with FRC robots (https://www.amazon.com/MaxBotix-Ultrasonic-Sensor-MB1242-000-I2CXL-MaxSonar-EZ4/dp/B07F1V6GQ1/ref=sr_1_12?crid=27ZG563C32YR7&keywords=ultrasonic+sensor&qid=1640473524&sprefix=ultrasonic+sensor%2Caps%2C364&sr=8-12) But of course these are much more expensive than a few bucks because they have built-in circuitry to do the timing, I2C and analog output interfaces. You also need to check the "custom circuits" rule in FTC because they are more restrictive than FRC. Not to mention that you have to do a lot more programming work to write driver code for this ultrasonic sensor if you are using its I2C interface. I am sure FTC SDK does not have support for it. Having said that, I would recommend using the Maxbotix in analog output mode, so you just connect the analog output pin to an analog input pin on the REV expansion hub. Then you just read the analog voltage and calculate the distance.