[virtuald]

Originally Posted by CloakAndDagger

We updated the code not to have the calibrate or reset functions, no feedback from the gyro.

Next, we copied the sampleRobot code from the wpilib website, and implemented only the gyro code, no feedback.

We then deployed C++ onto the same robot, and got feedback from the gyro, so we know it's not a hardware problem. You can see the current code we are using in the Initial-Code-Copy branch.

I'd hate to ask for a code snippet but we are on day 4 of trying to get this thing working at this point

https://github.com/Team74/FRC_2017_P...-Copy/robot.py
^Current Robot Code

https://github.com/Team74/FRC_2017_P...ging/Robot.cpp
^C++ code for comparison

https://github.com/Team74/FRC_2017_P...gging/Robot.py
^SampleRobot tests

Currently running pyfrc version 2017.0.4

Oh interesting, you have something in the constructor. Maybe that's it? Here's how I tested it:

• ssh into the robot
• frcKillRobot.sh -t
• python3

>>> import wpilib
>>> a = wpilib.ADXRS450_Gyro()
>>> print(a.getAngle())

Move the roborio

>>> print(a.getAngle())

So.. that's it. Nothing else getting in the way. I won't be home for a few hours, I'll try your code when I get there.

One difference that I thought of is that I'm using a slightly newer version RobotPy that I'm working on adding some things to, but I don't think there have been any changes that would impact it. I'll try installing 2017.0.4 also to make sure that works also.