backtop


Print 45 comment(s) - last by Tyler 86.. on Feb 20 at 6:37 PM

A driverless robot car with brains may be road ready by 2030, according to Sebastian Thrun, a great mind in self-driving vehicle development

Speaking at the American Association for the Advancement of Science conference in San Francisco, Sebastian Thrun, a Stanford University computer science and electrical engineering professor, estimated that robot-driven cars will be road ready by 2030

Thrun cited strong advances in the development of artificial intelligence as one of the main reasons that the world could see driverless cars by 2030.  Along with not having a human driver controlling the car, new vehicles should also function properly in a simulated city environment.  
 
Thrun is regarded as one of the world's most successful and innovative manufacturers of self-driving vehicles.  Thrun's team previously won a $2 million prize after "Stanley," a modified Volkswagen Tourage, won a US Defense Advanced Research Projects Agency (DARPA) contest in October of 2005.  Another DARPA challenge in November will feature rule changes that force teams to have their cars obey traffic laws, deal with obstacles and basic road conditions, other vehicles, etc.

It is more likely that robot-driven cars will be seen on battlefields and other hostile environments rather than public roads any time soon, according to Thrun.

Stanford plans to enter "Junior," a converted 2006 Volkswagen Passat that has had its throttle, brakes and steering altered so a computer is able to control them.  The car will be navigated via satellite GPS, with a number of lasers located on Junior's bumpers -- the lasers will be able to look multiple directions and has a range up to 50 yards.


Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: No Thank you.
By Flunk on 2/19/2007 1:37:11 PM , Rating: 2
No it's not. Speeding up the computer's internal clock would just make it operate faster E.G. it would react quicker, read the speedometer more often, etc... Speeding up the clock won't help you at all.

What you would need to do is to hack the speedometer to read lower than the actual speed, either by replacing the actual component or interfereing with the computer reading it correctly (like an intermediate box that would tell the car it was driving 65 when it was actually driving 75). Of course if the cops found you with a hacked car there would be no denying it as it would be really obvious.


RE: No Thank you.
By Oregonian2 on 2/19/2007 3:08:19 PM , Rating: 2
You're assuming that it's a reading a "speedometer" that's not using that same clock. More likely, that same software would be reading a distance-travelled input (rotations of an axel or the like) from which it calculates speed based on the time interval between readings (with a timestamp probably associated with each reading). Speeding up the clock would probably make it think that it's going faster than it really is (went xxx distance in 1-second... where it REALLY happened in 1/2 second) . In other words, overclocking the control mechanism may make it slow down!



RE: No Thank you.
By gdillon on 2/19/2007 3:31:31 PM , Rating: 2
Heh, let's just imagine you could hack it with suck a superficial change as a clockrate increase/decrease. That would mean every time you started from zero, it would FLOOR it. Yipes!


RE: No Thank you.
By masher2 (blog) on 2/19/2007 5:55:25 PM , Rating: 3
You have that logic backwards. If one travels x distance in elapsed time t but, due to a faster clock, measures the time as 2t, the computed speed will be half the actual rate, rather than twice.


RE: No Thank you.
By Tyler 86 on 2/20/2007 6:32:41 PM , Rating: 2
masher's got it.

By increasing the clock counter, you're redefining the second.
There was the infamous "speedhack", which EXACTLY mimics the desired behavior in cars, that changes the system timer resolution - the equivelant effect as increasing the clock rate while reporting the same number of cycles per second (the proposed change) is to decrease the reported number of cycles per second (speedhack).
Go find the Nintendo DS overclocking, or "speedhacker" videos for an effect example.


"Game reviewers fought each other to write the most glowing coverage possible for the powerhouse Sony, MS systems. Reviewers flipped coins to see who would review the Nintendo Wii. The losers got stuck with the job." -- Andy Marken











botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki