team2181 / FRC2016

FRC Team 2181 2016 Robot Deploy Code
0 stars 2 forks source link

Get Gyro to work <TOP PRIORITY> #8

Closed Brekmister closed 8 years ago

Brekmister commented 8 years ago

The Gyro on the RoboRio needs to be programmed so we can start developing the Autonomous System for the robot.

The only issue is that, Our Gyro is not hooked up to any of the Analog Ports, So, we can not use Robot Builder to put the Gyro into the Code since Robot Builder uses AnalogGyro Class which handles Gyros hooked up to the Analog Ports not the Gyro Class that Handles all of the Gyros that was supplied by FRC.

The name for the Gyro in WPILib is ADXRS450

webtekz commented 8 years ago

Alright, looked at the implementation, seems easy enough. We do need to figure out how calibration works, though, don't know what we need to do exactly.

Either way, doesn't look too bad.

Brekmister commented 8 years ago

Yeah I am currently working on it. I just found out how to add new sensors in a robotbuilder export without robotbuilder. Then its just things like GetAngle(), Calibrate() and Reset()

Brekmister commented 8 years ago

C++ has wierd way of doing pointers however

webtekz commented 8 years ago

Alright, sounds good.

And it does. C++ is weird in general.

webtekz commented 8 years ago

Btw, I imagine you are talking about the unique_ptr stuff?

Brekmister commented 8 years ago

That and also shared_ptr On Feb 16, 2016 1:04 PM, "Stevan" notifications@github.com wrote:

Btw, I imagine you are talking about the unique_ptr stuff?

— Reply to this email directly or view it on GitHub https://github.com/team2181/FRC2016/issues/8#issuecomment-184833267.

webtekz commented 8 years ago

Yeah, that's C++11 insanity, you can also just use normal C syntax

Brekmister commented 8 years ago

Oh cool. so things like double* foo On Feb 16, 2016 1:06 PM, "Stevan" notifications@github.com wrote:

Yeah, that's C++11 insanity, you can also just use normal C syntax

— Reply to this email directly or view it on GitHub https://github.com/team2181/FRC2016/issues/8#issuecomment-184833899.

webtekz commented 8 years ago

Yeah, things like double *foo = &bar, so and so. C++ is mostly C-compatible.

Brekmister commented 8 years ago

Nice to know On Feb 16, 2016 1:09 PM, "Stevan" notifications@github.com wrote:

Yeah, things like double *foo = &bar, so and so. C++ is mostly C-compatible.

— Reply to this email directly or view it on GitHub https://github.com/team2181/FRC2016/issues/8#issuecomment-184835119.

webtekz commented 8 years ago

Yep. Only reason I bother with the unique_ptr stuff anyway is because RobotBuilder uses them. If I had to actually make a pointer I'd just use C syntax.

Brekmister commented 8 years ago

Kk On Feb 16, 2016 1:11 PM, "Stevan" notifications@github.com wrote:

Yep. Only reason I bother with the unique_ptr stuff anyway is because RobotBuilder uses them. If I had to actually make a pointer I'd just use C syntax.

— Reply to this email directly or view it on GitHub https://github.com/team2181/FRC2016/issues/8#issuecomment-184835632.

Brekmister commented 8 years ago

Got gyro done. Will push to a new branch. On Feb 16, 2016 1:11 PM, "Samuel Brekke" brekmister@gmail.com wrote:

Kk On Feb 16, 2016 1:11 PM, "Stevan" notifications@github.com wrote:

Yep. Only reason I bother with the unique_ptr stuff anyway is because RobotBuilder uses them. If I had to actually make a pointer I'd just use C syntax.

— Reply to this email directly or view it on GitHub https://github.com/team2181/FRC2016/issues/8#issuecomment-184835632.

Brekmister commented 8 years ago

Pushed to new branch. Issue Closed