Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Technical Discussion (http://www.chiefdelphi.com/forums/forumdisplay.php?f=22)
-   -   Which sensors should be used throughout the robot? (http://www.chiefdelphi.com/forums/showthread.php?t=137836)

jajabinx124 30-07-2015 11:20

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by carpedav000 (Post 1491784)
I'm not a programmer, but I would say a gyro would be very useful if you want to drive field-oriented.

^

A gryo can be a huge help in autonomous. Our team used a gryo in autonomous and it was very simple to make 90 degree or 180 degree turns, making it simple to implement turns/movements.

So to make life easier for autonomous, definitely consider using gyros. You won't have to rely on random numbers that you think will make it turn or move the way you want it to, instead you can rely on a sensor.

Ari423 30-07-2015 11:57

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by Gdeaver (Post 1491697)
For 2016 we are looking for a better IMU. We recently purchased a Arduino Shield with a Bosch BMO055 orientation sensor. It has a 3 axis accelerometer, gyro and magnetometer. Plus a Arm cortex M0 core running fusion code. Easy set up. Initialize the I2C port, write to a few registers and its running. We bought the Arduino shield for testing. Will use the Adafruit board on the robot if we go with it. Only have 1 hour of testing. Gyro, accelerometer fusion looks rock solid. Add in the mag and it is not good. Interesting is the linear acceleration output. It's a little noisy but with a little clean up could give direction of motion. Not suitable for distance. Better than the Invensense outputs. Looks good but you never know until it's on the robot.

We were possibly looking to use the Bosch BNO055, but we were unsure of how to connect it to the RoboRIO (via Arduino or otherwise). Can you please explain how you did it and how difficult it was to do.

marshall 30-07-2015 12:32

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by Ari423 (Post 1491791)
We were possibly looking to use the Bosch BNO055, but we were unsure of how to connect it to the RoboRIO (via Arduino or otherwise). Can you please explain how you did it and how difficult it was to do.

Looks like it is an I2C device so you could break out the pins to the RoboRIO. I'd probably avoid the arduino and go straight for a breakout like this one: http://www.adafruit.com/products/247...VwFxoCpIzw_wcB

If you want/need to do some formatting of the stream first then I suppose you could go the RIOduino and shield route:

http://www.andymark.com/product-p/am...tm&Click=35018
+
http://www.robotshop.com/en/arduino-...icIRoCJTXw_wcB

Henrique Schmit 30-07-2015 14:10

Re: Which sensors should be used throughout the robot?
 
From what we've done in previous years you can use limit switches to do a lot in a very simple way, so when you have boolean aplications, like an arm that only has two positions switches can do the job very well. This year we've used them to set a zero point on our elevator, this way every time it went back down the zero on our encoder would reset to avoid problems with it getting lost. Our team really likes to use this kind of limit switch http://www.amazon.com/ME-8108-Adjust...s=limit+switch they are very robust, adjustable and cheap, so we can keep it simple and still do a lot with them.

feverittm 30-07-2015 14:33

Re: Which sensors should be used throughout the robot?
 
I agree with a number of posters on this thread that limit switches are very good and extremely valuable in FRC robots.

However, I want to emphasize one item. Do NOT overlook the mechanical design of the switch actuation. I have seem too many (including our own robot in 2014) switches that were designed to be impacted by a mechanism, versus acting in a bypass fashion.

Thanks

AdamHeard 30-07-2015 14:47

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by feverittm (Post 1491830)
I agree with a number of posters on this thread that limit switches are very good and extremely valuable in FRC robots.

However, I want to emphasize one item. Do NOT overlook the mechanical design of the switch actuation. I have seem too many (including our own robot in 2014) switches that were designed to be impacted by a mechanism, versus acting in a bypass fashion.

Thanks

This is why hall effect, beam break, and inductive sensors are great! Non-contacting is the way to go.

thatprogrammer 30-07-2015 14:52

Re: Which sensors should be used throughout the robot?
 
Just to clarify, you use a beam break by using a piece of tape to reflect its own laser back to it, and if that laser is not reflected, it returns a false value?

AdamHeard 30-07-2015 14:57

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by thatprogrammer (Post 1491836)
Just to clarify, you use a beam break by using a piece of tape to reflect its own laser back to it, and if that laser is not reflected, it returns a false value?

It depends on the specific switch, and how it's wired.

Generally you decide based on what you want the failure mode to be. Do you want a disconnected/broken switch to read the same as seeing an object? Or do you want a broken/disconnected switch to read the same as never seeing an object.

AustinSchuh 31-07-2015 00:13

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by Necroterra (Post 1491691)
So if I understand this DMA thing, the FGPA reads off the sensor values on an event happening, and the relatively slow accessing of the memory can be done later? Wouldn't that still give you inaccurate data unless you added on the expected change since it was read?

Also, by upstreamed, do you mean it will be part of default WPILIB?

Yes, part of WPILib. I sent out patches in December ish, but there were too many other issues for the patches to get much attention.

With DMA, you get to read the captured data when you want. But, that capture can include both the signal that changed, all digital inputs, the timestamp of the event, all encoder values, all analog inputs, etc. If you are trying to correlate a digital input change to an encoder value, that delay is fine. If you are trying to correlate an analog input with an encoder at an edge, the delay is also fine. And by delay here, I mean up to 5 ms for our system, since we run our control loops at 200 hz and only pull out of the DMA buffer at that frequency.

thatprogrammer 31-07-2015 11:36

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by AdamHeard (Post 1491837)
It depends on the specific switch, and how it's wired.

Generally you decide based on what you want the failure mode to be. Do you want a disconnected/broken switch to read the same as seeing an object? Or do you want a broken/disconnected switch to read the same as never seeing an object.

Say you planned to use a beam break to detect if a tote was in the robot or not. When the beam broke, you'd know it saw the tote. In that case, would you use the tape to reflect back to it?
Thanks!

EDesbiens 01-08-2015 22:49

Re: Which sensors should be used throughout the robot?
 
What would you guys use to know the position of the robot on the field at all time? And do you know any not drifting gyro?

jajabinx124 01-08-2015 23:00

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by EDesbiens (Post 1492081)
What would you guys use to know the position of the robot on the field at all time? And do you know any not drifting gyro?

The gyros we've used tend to drift as well, but the drift isn't significant enough to mess up movements. (At least in autonomous) Our team only uses gyros in autonomous, and when autonomous initiates we reset the gyro in the code (so it resets the drift right when auto starts, so we don't have to worry about drift). Since auto usually is 10-15 seconds, the drift isn't significant enough to mess things up for us.

I don't know any gyros that don't drift.

EDesbiens 01-08-2015 23:12

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by jajabinx124 (Post 1492084)
I don't know any gyros that don't drift.

So it would be pretty hard to get a good measure during an entire match... Could we use something else to balance?

Thad House 01-08-2015 23:17

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by EDesbiens (Post 1492081)
What would you guys use to know the position of the robot on the field at all time? And do you know any not drifting gyro?

This is something that's actually very difficult to do.

Pretty much any gyro within FRC budget is going to drift, at least a little bit. Things like the NavX, or 2 gyros stacked on top of each other upside down can help, but since a gyro is a rate sensor, getting angle requires integration, and any integral error just adds up and compounds, which is actually what creates the drift. A compass could work if the motors didn't create so much interference, but with FRC robots compass's are not reliable enough.

Position is difficult as well. Things like encoders on drive wheels can give a start to position, but since you need a gyro to detect angle, you still get error, plus if your wheel's slip everything goes bad fast. You could use a non driven wheel to measure, but those can slip too, and you still have the gyro error.

The only good options that would be within FRC price ranges would be something like a FIRST provided HD camera above the field, that teams could use to track their robots. But with current items, getting 100% accurate position and angle of the robot throughout an entire match is not easy, and I would say its not possible within the current budget and DS rule limits.

EDesbiens 01-08-2015 23:21

Re: Which sensors should be used throughout the robot?
 
Quote:

Originally Posted by Thad House (Post 1492091)
The only good options that would be within FRC price ranges would be something like a FIRST provided HD camera above the field, that teams could use to track their robots. But with current items, getting 100% accurate position and angle of the robot throughout an entire match is not easy, and I would say its not possible within the current budget and DS rule limits.

That is a neat idea... Hard to realise but pretty cool :)

My goal is to create a semi-autonomous robot (or autonomous if possible)...


All times are GMT -5. The time now is 05:59.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi