Is the e4t encoder compatible with the rio and Java

[ozrien]

Hey Tparbotmail,
I just responded to your PM, but basically the roboRIO languages supports sensors connected to the roboRIO, and supports the Talon features when the sensors are connected to the Talon SRX (CAN Bus). This is because of the combined efforts of (NI + FRC + WPILIB + CTRE).

So yep that includes quadrature encoders like the E4T.

Hardware wise there are many breakouts that allow connecting sensors to the Talon (several on our site but there are many developed by FRC teams too).
Hardware wise the roboRIO has digital and analog inputs for sensors.

Software-wise you can run closed-loops / motion-profiles in the roboRIO when sensors are connected to the RIO.

Software-wise you can run closed-loops / motion-profiles in the roboRIO when sensors are connected to the Talon.

Software-wise you can just tell the Talon what you want and leverage it's internal firmware features to do closed-loops / motion-profiles without much roboRIO involvement. These are the closed-loop features that make Talon SRX on CAN bus unique.

Talon SRX Software Reference Manual (and Motion Profile Reference Manual) explains the software API in the roboRIO for when sensors are connected to Talon SRX.
WPILIB/FRC-screensteps documentation covers sensors connected to the RIO (C++/java)
NI/FRC-screensteps documentation covers sensors connected to RIO (LabVIEW).