Autonomous Race Cars 137
Octothorp writes: "Though not as complicated as the underwater
vehicles. There is an annual competition sponsored by National Semiconductors to build an autonomous race car. They move along pretty well too, at almost 9 ft/s. More technical information on how they are built is available on a Berkeley page, and there's a video of the winning run for 2002."
Real-life application? (Score:4, Interesting)
Since public transport seems to be out of the question for medium-distance transportation in the States (witness Amtrak's plight - and CoachUSA's financial gymnastics of late) automated private transport might fill the gap - provided price can be brought down.
It is really interesting to see what comes out of this. Certainly more applicable in the near future than football-playing robots - or this terrible series in the UK with robots battling each other, armed with saws, hammers and whatnot contraptions..
Curious,
Re:Real-life application? (Score:2)
Dude, Amtrak's "plight" is that in the USA, trains are expensive, inconvenient, and dangerous. Why would anyone ride on a train, when airplanes are so cheap and safe?
...and that's not all! (Score:1, Troll)
You forgot slow.
To paraphrase horribly:
Take Amtrak... please!
Re:Real-life application? (Score:2, Informative)
On the Boston-New York-DC corridor Amtrak is doing pretty well.
The price and travel time(once you include getting to and from the airport) are about the same.
On the train you have enough time to read a book, do some work or just enjoy the view, no hassle with airport security and you arrive smack in the center of the city.
For the plane you might have to travel a ways to the airport, get your nail clippers confisticated, then fly for like 30 minutes and then get try to get a cab or something into the city in snarling traffic.
Its really a matter of preference, but it certainly seems that trains are viable in more densely populated areas.
Re:Real-life application? (Score:2, Insightful)
Re:Real-life application? (Score:2)
Plane - 1-2 hours (45 minute flight), 99 bux.
Train - 12 hours, 25 bux.
Auto - 4:30 hours, 25-40 bux in gas.
Sometimes its easier to drive, and you dont need to rent a car when you get there. Trains would work, if they where high-speed, and had more runs.
YMMV (haha)
Re:Real-life application? (Score:2)
Auto - 4:30 hours, 25-40 bux in gas.
Trains must have some serious problem in the US. Here's some stats from EU:
short trip (300km), high-speed train:
Train - 1 hour 30 minutes
Car - 3 hours
longer trip (800km), normal train
Train - 7/8 hours
Car - 8 hours (including stops, etc)
Re:Real-life application? (Score:2)
Yes, trains have a huge problem in the US - They're mostly run by Amtrack. Amtrack is a sorta half-governmental entity that runs way in the red, provides crap service and costs too much, surviving mostly off of a series of governmental handouts. They know this, and thus they spend most of their time trying to cater to the various congress critters that bail them out (but only enough to keep the old decripit system running, as opposed to enough to actually implement decent high speed rail) instead of trying to make the system not suck.
Re: Amtrack's "Plight" (Score:1)
Amtrack's plight is...
In the 1930s, with the Great Depression reducing the market for personal automobiles, General Motors Corporation made a push to convert all U.S. transit systems to rubber-tired diesel buses. This effort was supported by Congress, which, in 1935, passed the Public Utility Holding Company Act, requiring most power companies to divest themselves of public transit operations. General Motors purchased transit systems across the nation through its subsidiary, National City Lines. They quickly turned around and bought diesel buses from the parent company and discontinued rail service. The rails were abandoned, often paved over in the city streets, although many ended up being salvaged for their steel once World War II began.
Thieved from here [iatransit.com]. Here's something a bit more cheerful [2600.com] though :)
Ali
Re:Real-life application? (Score:1)
This was more than a few months back, but one of the researchers invovled in the path project was the instructor for the vehicle course at Berkeley.
http://www.path.berkeley.edu/
I did not know that... (Score:1)
Must be nice having that kind of job!
Re:Real-life application? (Score:1)
By murphy's law it had to be in the story portion.
Re:Real-life application? (Score:1)
I think this is great for those idiots that can't pick a lane and/or tailgate. Seein that they don't drive good let computers do it or at least help 'em. Like that Volvo concept car that squaks when you tailgate.
Re:Real-life application? (Score:1)
Re:Real-life application? (Score:2, Interesting)
Congestion (Score:1)
There are 3 basic factors that govern the throughput of a road.
1) number of lanes
2) spacing between cars
3) speed of cars
There are various others such as road condition, length of the cars, weather, etc. but these are the main ones considered when designing a roadway.
If you pick a number for the amount of traffic that is carried on a road, say 10K cars per hour; then divide by the number of lanes, say 2, you get 5K/hour/lane. Obviously, adding lanes will help, but we have not yet completed the formulation.
A car must have a finite length. This is deduced from the limiting case. If a car was infinitely long, the lane could never carry more than 1 car, ever.
The next point is spacing, since we are giving a car a finite length, and we do want the lane to carry more than one car, if there is the minimum of 2, then there must be a space between them. Again, the limits are natural. If we want to have more than one car, the space must be less than infinity and if we want to have maximum density, we could use zero. We can use this "zero option" to our advantage. To make things easier, we will dispense with the spacing and redefine the length of the car to be the distance from the front of one to the front of the next.
To see how speed influences things, we consider the limit of zero. Again it is obvious that our lane will only carry one car, or none, ever. For any speed greater than 0, the traffic capacity of the lane is simply car_length/speed.
Anything that can be done to decrease the length(spacing) or increase the speed will increase the traffic capacity of our lane. Spacing requirements can be reduced by making cars lighter, installing better braking systems and reducing the reaction time of the driver. Speed improvements can be had by making the road smoother, improving suspension design, and aerodynamics.
If you define congestion as any state where the lane is not producing its optimal throughput and reduced spacing is forcing a reduction in speed, then you can see that reducing the spacing(length) while maintaining speed is helpful and so is a speed increase while maintaining spacing.
We have made lighter cars, better brakes, smoother roads, improved aerodynamics and suspensions. Guess what's left?
Re:Congestion (Score:1)
Re:Congestion (Score:2)
> you've got the completely wrong model in your head
I think that you have it backwards. Throughput is exactly what we are talking about. There is a reason that the same terminology is used in data transport design and people transport design. The reason being, that is the same thing that we are measuring or talking about.
Throughput, traffic capacity, latency, all apply, with the same basic concepts to both fields of engineering.
Latency is how long it takes to get from one end to the other.
Throughput is how much can go through in a given time.
Just as with data transport, in people or car transport, throughput is measured in "desired-units" transported per unit of time. We are talking about bits per second, bytes per second, or cars/people per hour. The same principles apply. Make the "desired-unit" shorter and throughput goes up. The spacing of bits at 100MHz is shorter than at 10MHz. A 100MHz data transport has higher throughput than a 10MHz one, all else being equal. In data transport the actual speed is nearly fixed so the only options are to add lanes(make a wider bus) or decrease the spacing of the bits. In the people transport field there is more room to maneuver.
A road that is densely packed with narrow inter-car spacing will have high throughput and long latency. The long latency is produced because the short spacing forces the drivers to slow down due to their limited reaction time and brake performance.
The optimum condition for a roadway is when the cars are operating at the road's maximum possible speed and the minimum spacing allowable at that speed. This condition produces both minimum latency (which is very important in people transport) and the maximum throughput possible while not increasing latency. Add one more car and the spacing will be reduced, forcing the speed to be reduced, causing an increase in latency. This is the "people transport" definition of congestion.
In the data trasnport field congestion also arises when conditions force latency up. The data transport might be operating at peak throughput, but there is more data to move than in can handle. Tha data is forced to wait and therefore latency goes up. This is the data transport definition of congestion. As in the people transport case, operating conditions have forced latency to increase.
All this talk about computer driven cars comes from the need or desire to improve(reduce) reaction times and so reduce the spacing requirements for any particular speed. The alternatives, mass transport or car pooling, operate on the same principle. Notice that while I've been talking about car spacing, I've also been using the term "people transport". Moving people and their stuff is what this is all about. Putting more people, or more stuff in a vehicle also reduces the "people spacing" requirements of a road. As such it also reduces congestion and improves throughput. The same effect is produced in the data transport field by compression.
The same effects produced by compression can be seen in both fields. Compression can improve throughput but can also have a negative effect on latency. Data must wait in a buffer to be compressed and then expanded. People must navigate to and then wait at a bus stop for the bus and then do the reverse at the other end. Depending on the situation in both the data and the people transport scenarios throughput can be improved or reduced as can latency.
In the data transport situation, you rarely start using compression until the latency or throughput limitations become intolerable. The same thing happens in the people transport arena. Given a wide open road, good weather, and a good car, I'm driving. Given instead a traffic jam, I'll take the bus and read the paper on the way...
Re:Congestion (Score:1)
Re:Congestion (Score:2)
In that respect, your comparison of data transport and water plumbing is completely off the wall. If anything, data transport is much more closely related to roadway transport than fluid transport via plumbing.
All I have have done is try to explain the design principles, terminology definitions and the similarities between fields of endeavor. You might think that the principles that govern the design of roads used by a few hundred thousand drivers all doing their own thing doesn't relate at all to data trasnport design, but you will be mistaken. The models all break down when you try to delve into details of individual cars and include accidents and such, but the overall model of the road and how it works does not.
If a crash closes a lane, two things happen. For one, the road can now be modelled as one with one less lane. Two, the approaching drivers within visual range of the wreck can be modeled as having grossly increased reaction times.
The effects are right in line with the principles outlined earlier - increased congestion.
After passing the wreck, the drivers reaction times are reduced back to normal and the road expands by one lane and bingo - free flowing traffic in near optimal conditions.
Re:Real-life application? (Score:1)
Auto Autopilots inevitable (Score:5, Interesting)
I think eventually high-capacity highways will require the use of an autopilot. Doing so would allow the cars to be run with inter-car gaps which would be suicidal with a human behind the wheel. Most stop-n-go situations are due to bad planning on the part of drivers. They speed up too much when traffic clears ahead, zoom up on the cars in front, and then have to slow down to avoid an accident. This type of driving creates waves of congestion which travel backwards down the highway, and is due entirely to poor coordination among drivers. But there is no reason that under computer control rush hour can't cruise along at 60 miles an hour with a car length or less between cars. I bet you could easily triple the maximum capacity of a highway, not to mention getting everybody to their destination faster and with better fuel economy to boot. The R&D will be expensive, but like any electrics the hardware will be practically free once developed. Compared to the cost of expanding existing freeway's, it will make sense finacially too. I figure it's maybe 10 years out.
American's are not likely to give up their cars for any sort of public transportation, no matter how impractical cars become with rising fuel costs, increasing travel times due to congestion, increasing insurance rates, etc. Most Americans have convinced themselves that they enjoy sitting in stop and go traffic, as long as it's in a car and not a bus. But if we could figure out a way to let them keep their cars, reduce pollution, reduce accidents, let them safely talk on their cell phones, and not have to build mile-wide highways I suspect a lot of us might go for it.
Autopilots in maybe 100 years (Score:2)
Americans don't use public transportation, because public transportation here sucks.
Ride a bus in Germany, then ride a bus in NY. There's a world of difference. For me to use public transportation more often, it needs to become less dirty and less dangerous. For me personally, it would also need to be going 24/7.
One might also care to realize that things are laid out differently in America than they are in Europe. Ex: If I want to buy some milk, it would take me 40 minutes to walk to the closest place, and another 40 minutes to walk back. There is no mass transit I could take there even if I wanted to. America is BIG. I can get on the highway, drive for 3 hours and still be in the same state.
I think cars are impractical in certain areas (NYC, Boston, etc). In most places, they are a necessity. Where I live traffic is very efficient. I'm lucky enough to live in an area when most people actually know how to drive, and near a highway big enough to handle their traffic. I love driving on it. Even during rush hour, the average speed is 70.
Re:Auto Autopilots inevitable (Score:2)
Re:Auto Autopilots inevitable (Score:1)
Re:Auto Autopilots inevitable (Score:1)
Actually they're like 3 years ahead of schedule. One of my old girlfriends lived in a house that backed up to 59 at shepherd, it should be opening there very soon. Of course, 59 south is all fucked up because of that dumbass westpark toll road, so I guess it's a moot point.
Re:Auto Autopilots inevitable (Score:1)
Actually, humans are quite brilliant at driving, in spite of the idiocy you see on the road. And computers are particularly bad at things that we are good at.
MJC.
Re:Auto Autopilots inevitable (Score:1, Funny)
Re:Auto Autopilots inevitable (Score:2)
Aircraft are much safer than automobiles, in terms of fatalities and injuries per passenger mile. However, if anything goes wrong on a bus or a plane or a train, people get very upset. If fifteen people die in a given city in automobile accidents over (for example) the Independence Day weekend, and in another city 10 people die in a train derailment, the derailment will get a lot more press than the auto accidents.
The reason for this is that when people are in control, we expect to make the occasional mistake, but when we put our lives in someone else's hands, we expect perfection. So when we go to an automated roadway system, there will be much less tolerance of accidents than when people are controlling their own cars.
I predict that as population density rises in non-public-transit areas, like Dallas or Houston, we'll see a change in peoples housing preferences. Already in Dallas there is a big trend toward lofts and denser population centers as Dallas opens up its light-rail lines. I know of a couple of people who commute to work from the city center to their employment out in the suburbs by public transport, because they didn't like the perpetual traffic jams and construction delays that have sprung up as Dallas has grown. They haven't abandoned cars altogether, but they're cutting back.
I think that's going to be a more likely scenario than automated highways. Peoples unwillingness to put their lives in the hands of a system that could create some spectacular crashes, given the right software glitch, will prevent this coming to pass until there's a dramatic need.
Re:Real-life application? (Score:1)
Re:Real-life application? (Score:2)
So if I am approaching a slower vehicle in front of me, the cruise control will automatically adjust to slow down to maintain distance, but will also automatically accelerate if the space ahead clears, back to the original speed setting.
Re:Real-life application? (Score:1)
Re:Real-life application? (Score:1)
Of course, it also has a V12 and costs $115K, but hey, at least the technology is there.
Mercedes USA S600 website [mbusa.com]
A click on the Features > Feature Spotlight > Distronic will give you a video overview of the functionality.
Re:Real-life application? (Score:2)
A cruise control package on a car is like that range of channels on your cable dial that is dedicated to public access. Useless but there. You might as well drive with your hazard lights, rear window defogger, and seat warmers on full time where you otherwise would use c/c.
Now, if we could get the engineers in Detroit to install sharp gouging implements in hub caps, we could make good time!
Re:Real-life application? (Score:2)
Re:Real-life application? (Score:2)
there cool to watch, espcially the ones with no steering wheel.
May be I can enter the contest too... (Score:1)
Re:May be I can enter the contest too... (Score:1)
At first glance.. (Score:2, Informative)
Just to clarify for those who made the same initial assumption I did.
RC cars? (Score:1)
RC helocopters (Score:1)
Wowzers! (Score:3, Funny)
Wowzers! Methinks flaming shards of this server will be moving - autonomously - at 9 ft/sec very shortly...
[/bad joke]
Re:Wowzers! (Score:1)
Re:Wowzers! (Score:1)
The reason for all the screams at the end was that the zig zags in the course had cause the car to oscillate over the track, and it was able to hold on long enough to make the turn. -- i.e. it was a close call on the last turn.
CMU mobot competition (Score:1)
My tank from the 1998 competition woulda worked fine except for endianess problems between my roommates and I.
Nice, but what about the Army's ALV project? (Score:3, Interesting)
The key to this particular competition seems to be the size and weight limits on the cars. This is a contest for little RC-style cars. The technology exists to go much faster, but not in this form factor.
F1 Hoax (Score:2)
Surprise surprise, the site [man-v-machine.com] is dead now...
Very cool... (Score:2)
It would be interesting to take one those cars (with the electronics still on for weight fairness etc), install some RC gear, and see who's faster.
I suspect that the human would still be the better driver/faster at the moment. Also, a human driver can navigate traffic. These guys look like they might have a hard time in a race with other cars ;)
one at a time (Score:1)
I do think an automated car would have a very hard time in traffic though, and THAT would be a cool competition.
Can I get one in my TC3 RC car? (Score:2)
Speed, Accuracy and Conserving energy (Score:1)
I vote for sponsored demonstrations of these products at Motor Racing events. Normal RC Racing always attracts a very large crowd at any event I have been too! =)
This is going too far. (Score:1)
NASCAR (Score:1)
Re:NASCAR (Score:1)
I'll take a piece of that action. And why wait five years? Bricks and bungee cords are available now.
Re:NASCAR (Score:2)
Re:NASCAR (Score:2)
You can write a program to 'predict' what other cars are going to do just as well as a human can. the trick is to get the right response quick enough to use those 'predictions'.
NASCAR driver do things for very specific reasons.
note: I said easier, not easy.
I would wager, that if there was a "robotic NASCAR" it would only be a few years before the AIs could outperform there human counter parts.
Plus it would be cool to see how the cars start to change when there is no human driver in one.
Every day in Boston... (Score:4, Funny)
None of these machines (except mine, of course) contain any type of human intelligence, but it's interesting to watch the AI at work. At night the roads look like Conway's Game of Life running on a computer with bad RAM.
Expert systems allow some vehicles to negotiate left turns from right lanes and to outbrake school busses when entering a rotary.
Fuzzy logic is essential for speed control, stop lights, parking and many other mission-critical tasks.
Genetic algorithms tend to select the maneuvers which are least expected by other vehicles.
Task scheduling is done according to driver convenience. For example, turn signals are always lower priority than dialing a call on the mobile phone.
Most communications between vehicles is a crude form of "digital" communication.
Unfortunately, most of the vehicles are Windows-based which results in a high rate of crashes. Mack trucks seem to be better than average.
I'd like cars that avoid sidewalls. (Score:1, Insightful)
I was just hoping that these cars were actually using sensors to keep track of the distance to the sidewalls of the track and the next turn.
It would be a good M. Eng. project for somebody to do this, using a half dozen laser distance sensors on the front, so that the car could go fast on straighaways, slow down for turns, and avoid sidewalls.
Does anyone know of a project like this?
With a good onboard computer, the car could build a model of the track as it went around, and calculate the optimal path & speeds to use on all subsequent laps. Using lasers or ultra sonic distance sensors would let the robot know when a turn was going to happen a lot sooner the the few inches of warning it gets in their setup. If you put an accelerometer in the car, you could even have it self-calibrate, discovering it's own acceleration curve, maximum lateral acceleration, and braking. It could then use those values to find the perfect path through the track on the second lap.
Re:I'd like cars that avoid sidewalls. (Score:3, Informative)
Yes, it sounds like a good idea, and in fact that was the original plan for the winning car. But it sounds a lot easier than it is. First of all, time constraint wise - these cars are built from scratch, and tuned to perform well in under fifteen weeks. (Yes, that includes all the sensor circuits, and power supply electronics) Secondly, there is a major problem with wheel slippage - if your wheels slip, you don't know where you are anymore.
A entry from 2001 went slow around the track the first time to memorize it, and then used that information on the second round in order to predict turns and change speed. It used the track crossing location to resync where it thought it was on the track. But if you look at the track layout, there are large section with no track crossing. i.e. wheel slippage - knowing where you actually are - is the main problem to be solved for memorization type approaches.
You can't see it in the video, but the winning 2002 car does detect and speed up (slightly) on straight aways.
Time constraint understood (Score:1)
Did anybody try unsing accelerometers?
An optimal design would have (almost) no wheel slippage.
Maybe something like a feedback circuit, where it never allows itself to pull more than
I think the memorization approach just doesn't work unless you have a ceratin amount of instrumentation.
When I was really young my dad, brought home this robot that had ultrasonic distance sensors and used stepper motors to move itself. It looked a lot like R2D2. It tried to map it's environment, but wheel slippage caused it to suck horribly.
I think any design that would do successful mapping would have to use several sensors for speed data. If someone wanted to go all out (choosing this as their life's quest), they could monitor each tire's rotation individually, use an optcal sensor on the bottom or the vehicle (like an optical mouse), use an accelerometer, and use the data from laser range finders.
Congrats (Score:1)
Re:I'd like cars that avoid sidewalls. (Score:1)
This contest seems pretty cool, and I'm just imagining what it could be like scaled up (in terms of time, people, and resources availible to each team.
I envision a track that has no line in the middle, it's just a normal track with normal walls one each side. This would be harder to drive in, but it would be more impressive and a future generation of these cars could possibly run with more that one car on the track at a time. Only one car can follow a line. Having sidewalls would make it more like actual driving too. If you hit the wall, that run doesn't count.
I'm thinking of this on more of a scale like the whole robocup thing. My school holds a world robocup title, but I'm just not interested in participating. in that project. I'd rather work on something where there was the possibility of doing it better that a human could, and competing alongside one to prove it.
It think it would also be cool, because it would be really computationally expensive. You could use a CPU computing optimal paths through a turn (using perfect Skip Barber style) instead of just an optimal speed, and you could have a ton of different sensors to give you redundant measurements for position tracking and mapping. This would let you handle things like wheels slipping.
Since when is 9ft/s "moving along quite well" (Score:2)
On a more serious note: Is the direction finding logic so intense that a greater speed can't be safely achieved?
Re:Since when is 9ft/s "moving along quite well" (Score:1)
On the other hand, how about porting this project/competition to full size cars? Obviously there is a funding issue, but we could Interest a broader audience who, in turn, may be willing to provide grant money?
Re:Since when is 9ft/s "moving along quite well" (Score:1)
Short answer: It's not the intensity of the logic, it's reaction time.
Long answer: There are several limitation on direction finding -
The CPU board used on the winning car only runs at 40Mhz, so updates to steering can not be done any faster than 40Mhz/loop length.
The servo - a generic RC servo will only take updates every 20ms = 50 Hz. (You can cheat this down to as low as 10ms, but that's still only 100Hz)
In the seen configuration, the sensors only 'see' a couple inches in front of the wheel, so reaction time becomes critical at higher speeds.
With a memorization approach, you could easily increase the speed, but there are other problems with memorization.
Re:Since when is 9ft/s "moving along quite well" (Score:2)
But anyway, 6mph is quite shabby. It's okay for an autonomous robot, but the point was to build and autonomous race car, no? Part of the challenge should be to build the controller for the car so that it can cope with high speeds, while guilding the vehicle around the track and (presumably) avoiding the other cars. For a decent platform, they can head to the local hobby shop and pick up any 1/10th scale gas-powered model car, these will do a lot better than 6mph.
Besides, at 6mph these races will hardly be exiting to watch!
Please think in relative terms (Score:1)
So the litte robot cars going around the track at 6mph would be like real race car going 210mph.
Not so bad for a coupla undergrads, huh?
My roommate did this... (Score:1)
DARPA Grand Challenge 2004 (Score:1)
according to the article, it will be held in 2004, going all the way from LA to Las Vegas. it will be for autonomous robots, no human help allowed.
the winner will get 1 mio $, so get working.
they are quoting US media in the article, so there should be some infos in english somewhere.
Mach 0.008 (Score:1)
Old News... (Score:1)
Why don't they just go their newsagent? (Score:3, Informative)
Not very impressive (Score:3)
The winner was a constant-speed car. At 6MPH. Cars aren't learning the track and then driving it at a good speed; they're just dumb line-followers.
Battlebots are much cooler.
Re:Not very impressive (Score:1)
Oh no, learning. Seriously though, this is a competition aimed at electrical engineering college students, half the point is to learn how things like this really work. Someone has to build those commercial components.
The winner was a constant-speed car. At 6MPH. Cars aren't learning the track and then driving it at a good speed; they're just dumb line-followers.
Not quiet - see this [slashdot.org] post for more info.
A note on R/C speed controllers (Score:2)
You just can't kludge up something like that in a few weeks. Anybody who's done power electronics looks at those numbers in awe. Plus they come with features like total self-protection against dead short, overheating, reverse polarity, etc. And all for about $100. Industrial motor controllers with comparable ratings cost thousands and are huge.
Re:Not very impressive (Score:1, Interesting)
All the Berkeley cars used a microcontroller for timing (Infineon chips, not National Semi), and many of our teams' sensors were simple RLC circuits, not National Semi. Sure we used National Semi for sensor amps and parts of the power circuitry, but even then many of their chips were eschewed in favor of better chips. In my team's case (and for many other teams) we used Linear Technologies and Maxim parts because we found the NatSemi chips insufficient. If NatSemi was trying to push their parts, they didn't succeed too well.
My team attempted a learning algorithm, but given the time frames (15 weeks from chassis to competition, 5 minutes total on competition track with messups included) and various last minute disasters, we couldn't perfect it in time for the competition. I know of at least 2 other teams who also tried to memorize to increase time. Also in the case of teams from other schools, they built completely analog cars (PID controllers in hardware *shudder*), with obviously no memorization possible. Even without memorization, it's more than just dumb line following. You can try to tweak the line following to shave off 10ths of a second here and there, but you still have the challenge to remain stable when the track suddenly changes course. Also, sorting out confusing magnetic fields at track crossings is a challenge all its own.
6MPH, at 1/10 scale, is the equivalent of 60MPH. Try getting a full sized car to follow tracks at that speed on its own, without overshooting more than 15 feet away from the track even on sharp turns. It truely is a challenge.
Re:Not very impressive (Score:2)
At one point in time I tried experimenting by mounting a wireless X-10 cam on the car and tried driving it from my computer. The cars just go too fast to control it that way. But, I see no reason why if you had all the appropriate information available in sensors that you couldn't program the vehicle to outperform even the best human driver.
Re:Not very impressive (Score:2)
2.) Small tracks. yes, I have raced on tracks that looked just as small as the one in the video. Obviously you can't go as fast as on a larger track.
I'm not sure that is was that I couldn't process the video that made it difficult to drive that way. It's a bad perspective to drive fast from. When you race normally you stand up above and can see the whole track. You can make adjustments to your line before you take a turn because you can see the whole track. When you look at it from in-car everything is different. You can't interperet the course as well. Plus, it goes fast as hell from that POV.
9 ft/s ? (Score:2, Funny)
Re:9 ft/s ? (Score:2)
Disappointing (Score:2, Insightful)
What do I get? Hey! I remember thses things from the eighties. You got a little bug with a couple of light sensors underneath, plus a red pen. You also got a thrashing when you covered the most available big flat white surface, which was the kitchen table, with roads (a.k.a. "scribbling").
OK, so they've gotten faster, but it looks like any car you upgrade with this tech will race down the centre marker of any highway you let it loose on
9 ft/s (Score:2)
For the metrically non-challenged:
9ft/s = 2,7432 meter/s
thats = 9,87 km/h or 6,13 miles/h
And for collectors of odd figures and measurements: that speed equals 7769 nautical miles per presidential term.
Re:9 ft/s (Score:1)
9ft/s = 2,7432 meter/s
thats = 9,87 km/h or 6,13 miles/h
Curious (and, possibly, ignorant). Are the commnas typing errors or does your country use commas instead of periods for decimal points? One needs to know these things before furlongs of any sort can be calculated.
MadDad32
What is the opposite of 'defunct'? (QuantSuff?)
Re:9 ft/s (Score:2)
The point is used as a thousand separator, as in 3.500.000 citizens.
You can play at home (Score:2, Interesting)
McLaren F1 Did this in the early 90's? (Score:1)
Mclaren F1? (Score:2)
I was hoping we would see the first car to win a GP without a human. Looks like Schumacher has achieved that now.
I was in this a few years ago (Score:1)
alright you metric police (Score:2)
The site is in imperial measurements.
What is timothy supposed to do, tell them to change there measurement type, then post the story?
last post (Score:1)
underwater is probably easier (Score:1)
Slow down speedy (Score:1)
Re:9 fps? That's like 6 mph! (Score:1)
Re:9 fps? That's like 6 mph! (Score:2)
Re:9 fps? That's like 6 mph! (Score:1)
If you want to be a critic do it constructively.
Re:9 fps? That's like 6 mph! (Score:1)
Re:9 fps? That's like 6 mph! (Score:2)
1. Linked to a video,
2. Was written poorly enough to be nearly incomprehensible, and
3. Called 9 fps "moving along pretty well."
Re:9 fps? That's like 6 mph! (Score:1)
2. Was written poorly enough to be nearly incomprehensible, and
3. Called 9 fps "moving along pretty well."
1. Thus far I have seen little problem with the site hosting the video - the Berkeley network has multiple OC-12's to the outside world. And there was a good reason to link to the video, there are no other links to it, even from the linked webpages.
3. Did you watch the video? You'd have trouble keeping up without running a bit.
Pretty Simple (Score:1)
Re:Pretty Simple (Score:2, Informative)
Actually, that's not the case at all. If I remember correctly, the motor is capable of doing something in the 30 MPH range (though probably not for too long). It turns out that working on the control problem, and the accuracy/reliability of inforation you're working with is much more important.