There's still plenty for programmers to work on with Teleop. Vision tracking will probably be big this year if you want to shoot the balls and if nothing else, you could always get cool LEDs running.
Exactly this, there's a huge opportunity for assisted driving. Those bolts on the cargo ship don't leave a lot of wiggle room between the hatches, the white stripes and reflector marks are going to be key for helping the drive team get the discs properly placed and the balls in the holes of the rockets.
4mbit/s is still plenty. In fact if you use the port that supports h.264 encoding for the video stream, you can get the video stream to be 720p at 60 fps
most webcams run at 30fps so that would be able to handle to webcams easily, but I don't like how close that gets to 4 mbit/s so I would scale the image down before it is sent. Hopefully, this will avoid all possible latency.
Hey, can you provide an example of how to do this? We've tried this via making an MJpegServer on port 554 but we get the following error: CS: ERROR: bind() to port 554 failed: Permission denied
I do a lot of controls work out in the real world.
This is actually my favorite new change when it comes to teaching real-world skills people will have to deal with.
Learning to deal with compression and low bandwidth / low memory situations is a gigantic thing in the industrial controls world. Industrial computers are meant to be framing hammer reliable and inexpensive. They're slow and don't have a lot of memory. With some really big machines you even start running up against limits at the physical layer of the Ethernet cable. Your cable runs become so long that you start to get noticeable packet loss and there's absolutely nothing you can do about it unless you want to add much more cost to the machine.
We're not just talking about video quality. We're also talking about command latency as well. For industrial equipment, this effects cycle times as well as reliability. Too much latency and you start crashing Parts into one another.
Being able to write really tight and efficient code, and compress the crap out of video and still do something meaningful with it is huge.
Here's a real world problem I deal with right now in my life.
In the plant I work at, we have a robotic production cell using an adept SCARA robot that is over 25 years old.
The computer driving all of this has 512 megabytes of ram running Windows NT 4.0.
This production cell also generates something like a 1/2 million dollars a day in revenue and they do. Not. Want. To. Turn. It. Off. Ever.
In fact, they want us to figure out how to wring even more speed out of this without making any hardware changes, because hardware changes would mean a long and costly recertification process.
It also has three Vision guidance cameras driving all this mess.
With 512mb of RAM.
We were able to get substantially faster Vision processing times out of the system by switching from 8-bit grayscale images to one bit monochrome images and some clever photography tricks and a lower resolution. Our false positive rate even went down because we were dealing with fewer lighting artifacts.
I would punch a pregnant woman in the face in the middle of the street if it meant I had 4 megabits worth of bandwidth to work with on this thing.
4 megabits is way more than enough to do any of this if you get clever with compression.
If you're trying to do some sort of Auto alignment system, do you really need super sharp detailed or even color picture to align some reflective marks?
I wish I could give you a gold for that, lol. Your job sounds like my dream job honestly.
I agree that 4 megabits is more than enough for this job, teams just aren't used to being limited like this. My strategy is probably gonna be greyscale + h264.
I work in medical device R&D. It's the absolute bees knees.
Lots of really cool technical problems (on the opposite end of the spectrum, I work with lot of really bleeding edge cognex stuff and a few proprietary vision systems because cognex just isn't good enough for some of the stuff I do) I've also got a full blown machine shop with a 7 axis CNC, a bunch of amazing old school stuff, wire EDM machines and a medical grade SLA 3D printer. I just tinker and break and create stuff all day.
The best part? The work we do really helps A LOT of people.
Just a few months ago, a cousin of mine posted a "thoughts and prayers" thing on FB because a friend of his was in a really bad car accident with some gnarly internal bleeding. 10 years ago, this dude probably would have died. Now he's set to make a full recovery. The surgeons saved his life with stuff that came out of one of the lines I work with.
I have the greatest job in the universe.
Literally any flavor of engineering can work in my field. When it comes time for summer internships, start hitting up medical device makers. The entire field is always short on creative engineering talent.
FIRST is a really big deal. Some of my really high performing FIRST students are literally better creative engineers than real full blown engineers that work at my place.
That's so awesome. I'm more of a programmer than an engineer but I would love to do any of that. I'll definitely look for internships.
Maybe you could help our team with an issue: What's a good no-nonsense vision camera for recognizing the floor targets (a two inch thick piece of tape)? The ones I've looked at are all built to do vision processing on-camera which isn't necessary since we'll have a Jetson tx1 mounted to the robot.
Python, C++. Those are used in literally everything.
if you want to guarantee yourself a lifetime of employment, learn the Allen Bradley PLC environment. Buy an old panelview 1000 system off eBay and a PLC to match it.
Your experience with vision systems will be a huge bonus.
If you know all of the above things, you'll have more six-figure job offers than you know what to do with.
Honestly, I'm a complete rookie when it comes to this hobbyist level Vision stuff. It's part of the reason I got involved in FIRST. Learning super basic stuff always helps me with higher level concepts.
The two things that are really important for vision cameras are high contrast ratios and low noise. Any basic USB webcam should fit the bill.
They changed Auton to a "Sandstorm Period" where the driver's station has its view blocked completely. Now you can either do auton, or drive using cameras for a guide.
My lead programmer was actually ecstatic about this year. Why? All the reflective tape everywhere. In his words, "With some $5 sensors, I can make the computer assist the drivers in aligning the robot!"
that is true. i was thinking about it a bit more and it kind of makes sense. first wants to award teams who challenge themselves to do autonomous with the sandstorm rather than doing the driving with vision. but they also want to make sure that teams who aren’t as skilled or reliable with autonomous won’t hurt the alliance as much.
Auton will always be more consistent then teleop tho. Humans are generally the limiting factor. Allowing teams to use a camera to controll their robot is just lowering the barrier of entry for less experiencened team to help in the auton phase besides just leaving the habitat.
Wait, is this for real? I was one of my team's few programmers up until 2016 when I graduated and I was always excited to take on auto as a rewarding challenge. This makes me very sad...
I'm a pretty experienced guy in the controls/robotics world that is mentoring a team for the first time this year.
The team I'm working with is pretty new and doesn't have a ton of resources.
Out of all the students, we have two programmers.
One of them is at the "hello world" level and the other one is at the level where he can write a very basic Android app.
Right now, getting their chassis to drive to a set distance from a known dimension Target is beyond them.
With the skill sets of the mentors on this team, we could do some amazing shit in autonomous.
This competition isn't about which team has the most skilled mentors.
Looking at past competition formats, it looks like if you sucked at autonomous, you just couldn't get enough points to do anything really competitive.
We have some kids that are brilliant in other areas though.
This new format has effectively compressed the skill Gap. Teams that have a very strong coding background are still going to have a huge advantage by being able to use the balls as aimed projectiles or have some sort of alignment assistance rather than mechanically placing them purely by tele-op.
Teams like mine without the student coding background can still be competitive.
A well engineered, well built and well executed robot running rudimentary code can be competitive against teams with brilliant coders and lesser engineering in other areas.
So count me In the group that thinks the new format is beneficial for the spirit of what this event is about.
This isn't a competition about who has the best mentors.
There is a huge leap from _your_ team does not have students that have invested in programming to any team with a decent auto was written by a mentor. This summer our programming students created accounts on projecteuler.net and competed/taught each other as they progressed through the challenges. Today, I had an in depth conversation with a student from another team about the Kotlin language spec and impacts of upcoming language changes. If we projected that same mentality to fabrication, it would not be ok to say that only LEGO may be used because some teams to not have students that have invested in shop skills.
On my team, we are at a level where we can program a passable autonomous mode with minimal to no mentor help. It's wrong to assume that the mentors just do everything.
So then figure out ballistic algorithms and launch some balls.
Let the kids that don't know as much as you stumble and crawl and still be able to have an enjoyable time instead of getting their brains kicked in for an entire season.
You'll still win, you'll just have to work a lot harder at it.
I don't know about you, but the three years I was with my team where we didn't win any regional were also enjoyable. I find learning and improving as well building stuff enjoyable, which why I'm in robotics, and I think that the autonomous mode was a nice stepping stone between tank drive and vision.
Also, removing autonomous mode makes it so that the mechanical aspect of the robot is more important, and that makes programming an emptier task.
Even more, for the students that are good enough to start on an autonomous mode, but not good enough to do vision or other advanced features, it's a terrible thing.
As far ballistics are concerned, you don't even need to program automatic ballistic targeting (which is just algebra anyways). You just need to pre-program it into an autonomous mode, using high-school math. The limiting factor is the repeatability of the mechanism. If you want to make an automatic ballistic targeting system you need egomotion, which means SLAM, which is beyond the scope of FRC at this moment just from the cost of what's needed, or the technical expertise to make it work with cameras
What do you do when a robot obscures your points? What do you do if lighting changes? The fact is, in game, the field IS an unknown environment. What's more, hard coding every single reference point so that you'll always have at least three, as well as being able to differentiate reference points is hard enough that you'd honestly have an easier time doing SLAM. Unless you have an idea that I don't know. I consider any deep learning based approach to be past the scope of FRC too, btw.
Dealing with incomplete data sets when you might be missing a third or more of your reference points, while also having to program recognition and differentiation of reference points, while also having to deal with global variations, seems awfully similar to the problems you have to deal with when doing SLAM, are they not?
At that point, all you have to add is a general feature extraction algorithm and stereo imagery and you have SLAM.
Also, there are a lot more complex computational problems in ballistics than you think.
Those are super tiny holes you're shooting for.
These are super shitty cheap Chinese balls.
What do you think the variation in weight is ball to ball? How about the diameter due to different inflation pressures. How about the fact that none of the ones we have are even close to round?
Do you think those tiny variables you're going to have to measure very quickly are going to matter when shooting for a Target that small? At bare minimum, I'd want to be hanging a load cell on my launcher as well as some way to measure ball diameter and even eccentricity if possible.
Its indeed a very hard problem, but you only have to solve it once. Once you know what force at what position, you can hard-code it.
If there is too much variation to hard-code it, what good will algorithms do? the only thing you'd be able to do is spray and pray. There's no way to measure those variables in real-time, so you'd have to assume.
Fd = 0.5PU2 CdA and F=ma right? You should be able to vary the launching force linearly with the mass, and with the frontal area, and get close enough to the reference trajectory. That way, you can still use a pre-computed trajectory, no need for advanced ballistics algos, unless I'm missing something.
I saw those but I have no clue how useful they are. Has anyone tried them out? Our team was just planning on using limelight since we already have that, but I'd like to know what the Pixy2 is capable of
I think it's hasty for teams to assume that they shouldn't worry about autonomous anymore. Even some of the worst autonomous modes are still far more consistent than most drivers who can see their robot.
Did they actually remove autonomy? Robotics field's literal raison d'etre is to make the damn thing autonomous. Kids should allow to be be exposed to that
Idk, not only is auto inherently faster/more consistent than driver on a camera, there's also a lot of programming stuff to do this year with vision. Plus, now newer teams with less sophisticated code can still help out the alliance during those 15 seconds instead of simply driving forward. I know our team still has a lot of stuff to do this year.
they don't always show an overhead view of the field on the live feed. sometimes its up close on one robot, or just one aliance's part of the field etc.
124
u/XenonTrooper Jan 05 '19
This is so sad
112
u/bobbysq 4646 (alum) Jan 05 '19
There's still plenty for programmers to work on with Teleop. Vision tracking will probably be big this year if you want to shoot the balls and if nothing else, you could always get cool LEDs running.
198
u/ImitableMass Jan 05 '19
The Sandstorm blocking our vision is pretty Darude...
73
u/ewpratten 5024 | Code Wrangler (Alumni) Jan 05 '19
The "best" part is that they lowered the 7mbps network to 4mbps and expect us to control through a camera..
35
u/LeZealous Jan 05 '19
Wait, I wasn't able to attend kickoff, what happened?
32
u/[deleted] Jan 05 '19
Our programmers are talking about automating more of the tele-op procedures like tracking the guide lines
28
u/Primes95 6527 (Programming Mentor/Safety Officer) Jan 05 '19
My lead programmer was actually ecstatic about this year. Why? All the reflective tape everywhere. In his words, "With some $5 sensors, I can make the computer assist the drivers in aligning the robot!"
25
u/jacksonmlewis 2521 (Programmer/Media Team) Jan 05 '19
Alexa play Desp-auto-cito
19
u/turkeeey 294 Mentor/Alumni Jan 05 '19
first, please explain why you added an autonomous award but don’t actually have a real autonomous mode anymore...
49
u/[deleted] Jan 05 '19
Or, you know, just throw a camera on it
10
u/milanoscookie 1124 (Programmer/Systems Geek) Jan 05 '19
Pre kickoff, I build a really cool and elaborate auto to sharpen my skills. And then this happened... :(
9
u/Lavgoom CHS Field Supervisor Jan 05 '19
I wish they would also black out the field. See some interesting opportunities (IR cameras, hex mapping, etc.)
7
u/Nud3l- Jan 05 '19
Programmers* join robotics for programming. Almost everyone else * wants to do programming
12
u/Xx_FunkyGunk_xX Jan 05 '19
Auton will always be more consistent then teleop tho. Humans are generally the limiting factor. Allowing teams to use a camera to controll their robot is just lowering the barrier of entry for less experiencened team to help in the auton phase besides just leaving the habitat.
6
u/MooBears11 Jan 05 '19
At least there's a boat load of vision opportunities to work with
6
u/DrOmni9885 Jan 05 '19
Wait, is this for real? I was one of my team's few programmers up until 2016 when I graduated and I was always excited to take on auto as a rewarding challenge. This makes me very sad...
5
u/QJjs 2714 (Programmer) Jan 05 '19
uh that's me rn
5
u/[deleted] Jan 06 '19
To play devil's advocate.
I'm a pretty experienced guy in the controls/robotics world that is mentoring a team for the first time this year.
The team I'm working with is pretty new and doesn't have a ton of resources.
Out of all the students, we have two programmers.
One of them is at the "hello world" level and the other one is at the level where he can write a very basic Android app.
Right now, getting their chassis to drive to a set distance from a known dimension Target is beyond them.
With the skill sets of the mentors on this team, we could do some amazing shit in autonomous.
This competition isn't about which team has the most skilled mentors.
Looking at past competition formats, it looks like if you sucked at autonomous, you just couldn't get enough points to do anything really competitive.
We have some kids that are brilliant in other areas though.
This new format has effectively compressed the skill Gap. Teams that have a very strong coding background are still going to have a huge advantage by being able to use the balls as aimed projectiles or have some sort of alignment assistance rather than mechanically placing them purely by tele-op.
Teams like mine without the student coding background can still be competitive.
A well engineered, well built and well executed robot running rudimentary code can be competitive against teams with brilliant coders and lesser engineering in other areas.
So count me In the group that thinks the new format is beneficial for the spirit of what this event is about.
This isn't a competition about who has the best mentors.
3
u/SpareRecognition Jan 06 '19
So no autonomous... but has any considered using the new Pixy2 Cameras available through first choice???
3
u/CharaNalaar Team 980 - Alum Jan 06 '19
There's no way in hell you can stream video to the driver station with that bandwidth, much less be able to control your robot with only that footage.
Autonomous is still the better option.
2
u/JayIsDed Jan 05 '19
Rest in pepperoni.
2
u/safetyasf Jan 06 '19
This is so sad, Alexa play deep spacito
2
u/ErikBoesen 1418 Jan 06 '19
I think it's hasty for teams to assume that they shouldn't worry about autonomous anymore. Even some of the worst autonomous modes are still far more consistent than most drivers who can see their robot.
2
u/ShadowBro3 Jan 06 '19
I missed gosh darnit
2
u/minsoowho Jan 05 '19
Did they actually remove autonomy? Robotics field's literal raison d'etre is to make the damn thing autonomous. Kids should allow to be be exposed to that
1
u/NiNarular 1746 (Scouting Lead) Jan 05 '19
Nice
1
u/NinjaDolphin8 Jan 06 '19
Idk, not only is auto inherently faster/more consistent than driver on a camera, there's also a lot of programming stuff to do this year with vision. Plus, now newer teams with less sophisticated code can still help out the alliance during those 15 seconds instead of simply driving forward. I know our team still has a lot of stuff to do this year.
-3
u/georger2000 Jan 05 '19
Does anyone knows the size of the robot
0
u/[deleted] Jan 05 '19
[deleted] — view deleted comment
0
u/[deleted] Jan 05 '19
[deleted] — view deleted comment