Last week, new studies came back on the California High Speed Rail project. They have raised the estimated cost to $99 billion, and dropped the ridership estimate to 36.8 million and $5.5 billion in annual revenue. Note that only around 20 million people currently fly the SF to LA corridor -- they expect to not just capture most of those but large numbers of central valley trips.
Congestion on the roads has a variety of sources. These include accidents of course, reductions in road capacity, irrational human driving behaviours and others, but most of all you get congestion when more cars are trying to use a road than it has capacity for.
That's why the two main success stories in congestion today are metering lights and downtown congestion charging. Metering lights limit how fast cars can enter the highway, so that you don't overload it and traffic flows smoothly. By waiting a bit at the metering light you get a fast ride once on the highway. Sometimes though, especially when the other factors like accidents come into play, things still gum up.
Now that more and more cars are connected (by virtue just of the smartphone the driver carries if nothing else) the potential will open up for something else in congestion -- finding ways to encourage drivers to leave a congested road.
I'm just back from the "ITS World Congress" an annual meeting of people working on "Intelligent Transportation Systems" which means all sorts of applications of computers and networking to transportation, particularly cars. A whole bunch of stuff gets covered there, including traffic monitoring and management, toll collection, transit operations etc. but what's of interest to robocar enthusiasts is what goes into cars and streets. People started networking cars with systems like OnStar, now known in the generic sense as "telematics" but things have grown since then.
The big effort involves putting digital radios into cars. The radio system, known by names like 802.11p, WAVE and DSRC involves an 802.11 derived protocol in a new dedicated band at 5.9ghz. The goal is a protocol suitable for safety applications, with super-fast connections and reliable data. Once the radios in the car, the car will be able to use it to talk to other cars (known as V2V) or to infrastructure facilities such as traffic lights (known as V2I.) The initial planned figured that the V2I services would give you internet in your car, but the reality is that 4G cellular networks have taken over that part of the value chain.
Coming up with value for V2V is a tricky proposition. Since you can only talk to cars very close to you, it's not a reliable way to talk with any particular car. Relaying through the wide area network is best for that unless you need lots of bandwidth or really low latency. There's not much that needs lots of bandwidth, but safety applications do demand both low latency and a robust system that doesn't depend on infrastructure.
The current approach to safety applications is to have equipped cars transmit status information. Formerly called a "here I am" this is a broadcast of location, direction, speed and signals like brake lights, turn signals etc. If somebody else's car is transmitting that, your car can detect their presence, even if you can't see them. This lets your car detect and warn about things like:
- The car 2 or 3 in front of you, hidden by the truck in front of you, that has hit the brakes or stalled
- People in your blind spot, or who are coming up on you really fast when your're about to change lanes
- Hidden cars coming up when you want to turn left, or want to pass on a rural highway
- Cars about to run red lights or blow stop signs at an intersection you're about to go through
- Privacy is a big issue. The boxes change their ID every minute so you can't track a car over a long distance unless you can follow it over every segment, but is that enough? They say a law is needed so the police don't use the speed broadcast to ticket you, but will it stay that way?
It turns out that intersection collisions are a large fraction of crashes, so there's a big win there, if you can do it. The problem is one of critical mass. Installed in just a few cars, such a system is extremely unlikely to provide aid. For things like blindspot detection, existing systems that use cameras or radars are far better because they see all cars, not just those with radios. Even with 10% penetration, there's only a 1% chance any given collision could be prevented with the system, though it's a 10% chance for the people who seek out the system. (Sadly, those who seek out fancy safety systems are probably less likely to be the ones blowing through red lights, and indeed another feature of the system -- getting data from traffic lights -- already can do a lot to stop an equipped car from going through a red light by mistake.)
The latest JD Power survey on car satisfaction has a very new complaint that has now the second most annoying item to new car owners namely problems with the voice recognition system in their hands-free interface. This is not too surprising, since voice recognition, especially in cars, is often dreadful. It also reveals that most new tech has lots of UI problems -- not every product is the iPod, lauded from the start for its UI.
It's very common to use mobile phones for driving activities today. Many people even put in cell phone holders in their cars when they want to use the phones as navigation systems as well as make calls over a bluetooth. There's even evidence that dashboard mounting reduces the distracted driving phenomenon associated with phones in cars.
Last year I wrote about an interesting but simple pedal powered monorail/PRT system called Shweeb which had won a prize/investment from Google. Recent announcements show they are not alone in this concept. Scott Olson, the original developer of the Rollerblade, has founded a company called Skyride Technologies to build their own version of a pedal powered suspended monorail.
Every day I get into my car and drive somewhere. My mobile phone has a lot of useful apps for travel, including maps with traffic and a lot more. And I am usually calling them up.
I believe that my phone should notice when I am driving off from somewhere, or about to, and automatically do some things for me. Of course, it could notice this if it ran the GPS all the time, but that's expensive from a power standpoint, so there are other ways to identify this:
You're driving down the road. You see another car on the road with you that has a problem. The lights are off and it's dusk. There is something loose that may break off. There's something left on the roof or the trunk is not closed -- any number of things. How do you tell the driver that they need to stop and check? I've tried sometimes and they mostly think you are some sort of crazy, driving to close to them, waving at them, honking or shouting. Perhaps after a few people do it they figure it out.
There was a bit of a stir when Google last week announced that one of the winners of their 10^100 contest would be Shweeb, a pedal-powered monorail from New Zealand that has elements of PRT. Google will invest $1M in Shweeb to help them build a small system, and if it makes any money on the investment, that will go into transportation related charities.
While I had a preference that Google fund a virtual world for developing and racing robocars I have come to love a number of elements about Shweeb, though it's not robocars and the PRT community seems to not think it's PRT. I think it is PRT, in that it's personal, public and, according to the company, relatively rapid through the use of offline stations and non-stop point to point trips. PRT is an idea from the sixties that makes sense but has tried for almost 50 years to get transit planners to believe in it and build it. A micro-PRT has opened as a Heathrow parking shuttle, but in general transit administrators simply aren't early adopters. They don't innovate.
What impresses me about Shweeb is its tremendous simplicity. While it's unlikely to replace our cars or transit systems, it is simple enough that it can actually be built. Once built, it can serve as a testbed for many of PRT's concepts, and go through incremental improvements.
Looking at new electric cars like the Nissan Leaf, we see that to keep costs down, cars with a range of 100 miles are on offer. For certain city cars, particularly in 2-car families, this should be just fine. In my particular situation, being just under 50 miles from San Francisco, this won't work. It's much too close to the edge, and trips there would require a full charge, and visits to other stops during the trip or finding parking with charging. Other people are resisting the electrics for lesser reasons, since if you ever do exceed the range it's probably an 8 hour wait.
An alternative is a serial hybrid like the Chevy Volt. This has 40 miles range but a gasoline generator to provide the rest of the range and no "range anxiety." Good, but more expensive and harder to maintain because electric cars are much simpler than gasoline cars.
Here's an alternative: The electric car vendor should cut a deal with car rental services like ZipCar and Hertz. If you're ever on a round trip where there is range anxiety, tell the car. It will use its computer and internal data connection to locate a suitable rental location that is along your route and has a car for you. It will make all appropriate reservations. Upon arrival, your electric car would transmit a signal to the rental car so that it flashes its lights to guide you and unlocks its doors for you. (The hourly car rental companies all have systems already where a transmitter unlocks the car for you.)
In many cases you would then pause, pull the rental out of its spot and put your electric in that spot. With more advanced robocar technologies, the rental would actually pull out of its spot for you. Zipcar has reserved spots for its vehicles and normally it makes no sense for the renter to have just pulled up in a car and need the spot, but it should work just fine. At Hertz or similar companies another open spot may be available.
Then off you go in your gasoline car. To make things as easy as possible, the negotiated contract should include refill of gasoline at a fair market price rather than the insane inflated price that car rental houses charge. Later come back and swap again.
I've been predicting a great deal of innovation in cars with the arrival of robocars and other automatic driving technologies. But there's a lot of other computerization and new electronics that will be making its way into cars, and to make that happen, we need to make the car into a platform for innovation, rather than something bought as a walled garden from the car vendor.
In the old days, it was fairly common to get a car without a radio, and to buy the radio of your choice. This happened even in higher end cars. However, the advantages in sound quality and dash integration from a factory-installed radio started to win out, especially with horizontal market Japanese companies who were both good at cars and good at radios.
For real innovation, you want a platform, where aftermarket companies come in and compete. And you want early adopters to be able to replace what they buy whenever they get the whim. We replace our computers and phones far more frequently than our cars and the radios inside them.
To facilitate this, I think the car's radio and "occupant computer" should be merged, but split into three parts:
- The speakers and power amplifier, which will probably last the life of the car, and be driven with some standard interface such as 7.1 digital audio over optical fiber.
- The "guts" which probably live in the trunk or somewhere else not space constrained, and connect to the other parts
- The "interface" which consists of the dashboard panel and screen, with controls, and any other controls and screens, all wired with a network to the guts.
Ideally the hookup between the interface and the guts is a standardized protocol. I think USB 3.0 can handle it and has the bandwidth to display screens on the dashboard, and on the back of the headrests for rear passenger video. Though if you want to imagine an HDTV for the passengers, its possible that we would add a video protocol (like HDMI) to the USB. But otherwise USB is general enough for everything else that will connect to the guts. USB's main flaw is its master-slave approach, which means the guts needs to be both a master, for control of various things in the car, and a slave, for when you want to plug your laptop into the car and control elements in the car -- and the radio itself.
Of course there should be USB jacks scattered around the car to plug in devices like phones and memory sticks and music players, as well as to power devices up on the dash, down in the armrests, in the trunk, under the hood, at the mirror and right behind the grille.
Finally there need to be some antenna wires. That's harder to standardize but you can be we need antennas for AM/FM/TV, satellite radio, GPS, cellular bands, and various 802.11 protocols including the new 802.11p. In some cases, however, the right solution is just to run USB 3.0 to places an antenna might go, and then have a receiver or tranceiver with integrated antenna which mounts there. A more general solution is best.
This architecture lets us replace things with the newest and latest stuff, and lets us support new radio protocols which appear. It lets us replace the guts if we have to, and replace the interface panels, or customize them readily to particular cars.
Back in 2008 I wrote a controversial article about whether green transit was a myth in the USA. Today I updated the main chart in that article based on new releases of the Department of Energy Transportation Energy Fact Book 2009 edition. The car and SUV numbers have stayed roughly the same (at about 3500 BTUs/passenger-mile for the average car under average passenger load.)
I just landed on a flight from Toronto to San Francisco. If you were inside the USA you may not have heard about the various crazy rules applied to travel to the USA, or at least not experienced them. While we were away the rules changed every day, and perhaps every hour.
It was over 5 years ago that I blogged about a robot that would travel in front of a train to spot cars stuck on the tracks in time to stop.
I recently read a local story about an RV that was demolished while stuck on the tracks here. The couple had time to talk to 911, who told them to get out, and it's not clear from the story but it seems like a moderate amount of time may have passed (a couple of minutes) before their RV was smashed.
I struck a nerve several years ago when I blogged about the horrible beep-beep noise made by heavy equipment when it backs up. Eventually a British company came up with a solution: a pulsed burst of white noise which is very evident when you are near the backing up vehicle but which disperses quickly so it doesn't travel and annoy people a mile away as the beeps do.
After every RV trip (I'm back from Burning Man) I think of more I want RVs to do. This year, as we have for many years, we built a power distribution system with a master generator rather than having each RV run its own noisy, smelly and inefficient generator. However, this is expensive and a lot of work for a small group, it is cheap and a lot of work for a larger group.
There's been a revolution in small generator design of late thanks to the declining cost of inverters and other power conversion. A modern quality generator feeds the output of its windings to circuits to step up and step down the voltage to produce the required power. The output power is cleaner and more stable, and the generator is spun at different RPMs based on the power load, making it quieter and more efficient. With many models, you can also combine the internal output of two generators to produce a higher power generator.
RVs have come with expensive old-style generators that are quieter than cheap ones, and which produce better power, but today they are moving to inverter generators. With an inverter generator, it's also possible to draw on the RV batteries for power surges (such as starting an AC or microwave) beyond what the generator can do.
I'm interested in the potential for smarter power, so what I would like to see is a way for a group of RVs with new generation power systems to plug together. In this way, they could all make use of the power in the other vehicles, and in most cases only a fraction of the generators would need to be running to provide power to all. (For example, at night, only one generator could power a whole cluster. In the day, with ACs running, several would need to run, but it would be very unlikely to have to run all, or even 75% of them.)
RVs all have a fresh water tank. When you rent one, they will often tell you not to drink that water. That's because the tanks are being filled up in all sorts of random places, out of the control of the rental company, and while it's probably safe, they don't want to promise it, nor disinfect the tank every rental.
I recently got a small "pen" which you put in a cup of water and it shines a UV light for 30 seconds to kill any nasties in the water. While I have not tried to test it on infected water, I presume that it works.
Recently, some prosecutors, in efforts to crack down on drunk driving, are pushing for murder convictions. This is happening in the case of really blatant disregard on the part of the drunk drivers -- people with multiple DUIs getting smashed, going out, and killing.
I've written a few times about the "Selfish Merge" problem. Recently, reading the new book Traffic: Why We Drive the Way We Do by Tom Vanderbilt, I came upon some new research that has changed and refined my thinking.
The selfish merge problem occurs when two lanes reduce to one. Typically, most people try to be "good" and merge early, and that leaves the right lane, which is ending, mostly vacant. So some people zoom ahead of everybody in the right lane, and then merge at the very end. This is selfish in the sense that butting into any line is selfish. Even if overall traffic flow is not reduced (and even if it is increased) the person butting in moves everybody back one slot so they can get ahead by many slots. This angers people and generates more counter-productive behaviour, including road rage, and attempts to straddle the lanes so that the selfish mergers can't move up to the merge point.
In Traffic, Vanderbilt writes of surprising research that changed his mind, which showed that, in simulations, some merging forms provided up to 15% more traffic throughput than proper attempts at a zipper merge. In particular, a non-selfish merge fully using the vanishing lane worked better than the typical butt-in situation described at the top.
In this merge, which I'll call the "slow and fair merge," drivers are told to use both lanes up to the merge-point, and then to fairly "take their turn" at the merge point entering the continuing lane. Nobody is selfish here, in that nobody butts ahead of anybody else, but both lanes are fully utilized up to the merge point.
This problem is complex, I believe, because there is a switch-over point, which I call the "collapse" point. This is the point at which the merge flow becomes high enough that traffic collapses to "stop and go" mode, before and at the merge-point. Before that point, in lighter traffic, there is little doubt (for reasons you will see below) that the "cooperating fast zipper" merge results in the best traffic flow. In particular, there are traffic volumes where you could either have cooperating zipper or "slow and fair" but cooperating zipper would do a fair bit better. There are also traffic volumes where cooperating zipper just isn't possible any more, and we will either have "slow and fair" (which has the best volume) or "selfish merge" which has a worse volume.
Real world experiments show different results from the theoretical. In particular, many drivers, used to the anarchic selfish-merge approach, don't understand fair and slow, even when signs are explicit about it, and so they resist using both lanes and try to merge early. They also try to straddle, devolving to selfish merge. An experiment with digital signs which changed from advising drivers to zipper-merge in light traffic to advising "use both lanes" and "merge here, take your turn" in heavier traffic was disobeyed in fair and slow mode by too many drivers. The experiment ended before people could learn the system.