Submitted by brad on Sun, 2013-09-15 15:22.
Over the years, particularly after Burning Man, I’ve written posts about how RVs can be improved. This year I did not use an regular RV but rather a pop-up camping trailer. However, I thought it was a good time to summarize a variety of the features I think should be in every RV of the future.
We keep talking about smart power and smart grids but power is expensive and complex when camping, and RVs are a great place for new technologies to develop.
To begin with, an RV power system should integrate the deep cycle house batteries, a special generator/inverter system, smart appliances and even the main truck engine where possible.
Today the best small generators are inverter based. Rather than generating AC directly from an 1800rpm motor and alternator, they have a variable speed engine and produce the AC via an inverter. These are smaller, more efficient, lighter and quieter than older generators, and produce cleaner power. Today they are more expensive, but not more expensive than most RV generators. RV generators are usually sized at 3,600 to 4,000 watts in ordinary RVs — that size dictated by the spike of starting up the air conditioner compressor when something else, like the microwave is running.
An inverter based generator combined with the RV’s battery bank doesn’t have to be that large. It can draw power for the surge of starting a motor from the battery. The ability to sustain 2,000 watts is probably enough, with a few other tricks. Indeed, it can provide a lot of power even with the generator off, though the generator should auto-start if the AC is to be used, or the microwave will be used for a long time.
By adding a data network, one can be much more efficient with power. For example, the microwave could just turn off briefly when the thermostat wants to start the AC’s compressor, or even the fans. The microwave could also know if it’s been told to cook for 30 seconds (no need to run generator) or 10 minutes (might want to start it.) It could also start the generator in advance of cooling need.
If the master computer has access to weather data, it could even decide what future power needs for heating fans and air conditioning will be, and run the generator appropriately. With a GPS database, it could even know the quiet times of the campsite it’s in and respect them.
A modern RV should have all-LED lighting. Power use is so low on those that the lights become a blip in power planning. Only the microwave, AC and furnace fan would make a difference. Likewise today’s TVs, laptops and media players which all draw very few watts.
A smart power system could even help plugging into shore power, particularly a standard 15a circuit. Such circuits are not enough to start many ACs, or to run the AC with anything else. With surge backup from the battery, an RV could plug into an ordinary plug and act almost like it had a high power connection.
To go further, for group camping, RVs should have the ability to form an ad-hoc power grid. This same ability is already desired in the off-grid world, so it need not be developed just for RVs. RVs able to take all sorts of input power could also eventually get smart power from RV campsites. After negotiation, a campsite might offer 500v DC at 12 amps instead of 115v AC, allowing the largest dual-AC RVs to plug into small wires. read more »
Submitted by brad on Tue, 2013-07-02 10:42.
BART, one of the SF Bay Area’s transit systems, is on strike today, and people are scrambling for alternatives. The various new car-based transportation companies like Uber, Lyft and Sidecar are all trying to bump their service to help with the demand, but in the future I think there will be a much bigger opportunity for these companies.
The average car has 1.47 people in it, and the number is less on urban commutes. Since most cars hold 4-5 people, the packed roads have a huge amount of excess capacity in empty seats. While Lyft and Sidecar call themselves ridesharing companies, they are really clever hacks at providing taxi service. Lyft’s original product, Zimride, is more ridesharing but aimed at the long-distance market. Many companies have tried to coordinate true ridesharing for commuters and people in a city, but with only limited success.
A transit strike offers an interesting opportunity. Without commenting on the merits of the sides in the strike, the reality is that we can do much better with the empty seat resource than we do, and a transit strike can prompt that.
Of course, the strike is already naturally increasing carpooling, and casual carpooling (also known as slugging) also gets a large boost. In the Bay Area, things are complicated because BART is the main alternative to the Bay Bridge, and that bridge is going to get very heavily loaded. Ferry service is increasing but it’s still a 25 minute trip every 45 minutes from the various Ferry docks. The bridge and highways are increasing incentives for HOV-3+ carpools.
Casual carpooling tends to only get you to a rough area near your destination. In this case that may be OK, as other transit is still running, only BART is out. At the semi-official casual carpool stations, there are signed waiting places that get long lines for all the general destinations. You take what you can get, and it’s also efficient in moving cars in and out.
Computer assisted carpooling could schedule people together who are both starting and ending their trip fairly close together, for maximum convenience and efficiency. If the trip starts at people’s houses, or some common point, you don’t have the casual carpool concentration issue. If you start from stops of the transit lines which are running, you still have a problem.
Because of the load on the bridge, the ferry seems attractive, though there you have a chokepoint, particularly in picking up people from the boat. To do that, you would need a parking lot with numbered spaces. People allocated to a car because of a common destination would be given a spot number, and walk to the car there as they get off the ferry. A simple curb (which suffices for casual carpools) would not be enough.
Companies like Lyft and Sidecar make use of people who want to become part-time taxi drivers. While they pretend (for legal reasons) that they are people who were “already going that way” who take along others for a donation, that fiction could become reality in a transit strike. Most carpoolers would probably take along extras for no money, or gas money, especially when they gain a special carpool lane or toll saving as they do on the Bay Bridge. There would also be value in Jitney service, where a “professional” driver (who is just driving for the money, officially or not) takes 3-4 passengers along the common route, and they all pay a reasonable share.
Within a city, that share could be competitive, even with the subsidized cost of transit, which tends to be close to $2/ride. Taxi fares are $2.50/mile plus a flag drop, which means a trip of 3-4 miles could be competitive if split among 4 people, and not that bad (considering the higher level of service) even on trips that are twice as long. (The Bay Bridge is 10 miles long so taxi fares will have a hard time competing with even the higher BART fare.)
Jitney service (shared door to door or on-demand fixed route) is quite popular outside the USA, and indeed there are many cities with active private transit systems and jitney systems. But most Americans are not interest in the inconvenience of going slightly out of their way to deal with the needs of other passengers, and so attempts at such rideshare here don’t rule the world. It’s probably too late for this strike, but the next transit strike might end up demonstrating there are other systems aside from transit that are efficient and cost-effective.
The interface would not be too different from existing systems, except people would specify how much inconvenience they would tolerate from having others in the vehicle and going out of their way, in exchange for savings.
When it comes to robocars, this might happen as well, and it could even happen with vans to provide a very effective shared system that still offers door-to-door. Robocars also offer the potential for mixed-mode vanpool trips. In such a trip, a single person robocar takes you to a parking lot, where 12 other people all arrive within the same minute and you call get into a van. The van does the bulk of the trip, and stops near your set of destinations in a parking lot where a set of small single-person robocars sit waiting to take people the last mile. This highly efficient mode should be able to beat any existing transit because of its flexibility and door-to-door service. The vans offer the ability to be luxury vans, with business class seats with privacy screens, so that upscale transit is also possible.
Submitted by brad on Mon, 2013-05-20 13:12.
There are a growing number of apps designed to help people find parking, and even reserve and pay for parking in advance. Some know the state of lots. These apps are good for the user but also can produce a public good by reducing the number of people circling looking for parking. Studies suggest in certain circumstances a large fraction of the cars on the road are doing that.
This weekend, I attended the Maker Faire. I’ve been to almost every Make Faire, including the first, and now it’s grown to be far too successful — you can hardly walk down the aisles at the busy times. They need more space and a way to put more of it outside so thin out the crowds. Still, it is one of those places that makes you feel very clearly you are in the 21st century.
Early on Maker Faire realized it had a parking problem. The lot at the fairgrounds fills up now even before the event opens, and they manage various satellite lots and run shuttle buses to them.
This year they tried something interesting, a twitter feed with parking updates. They tweeted when lots filled up or re-opened, and suggested where to go. They took some limited feedback about lack of shuttles. I think that it by and large worked and reduced traffic around the event.
However, my judgment is that they were not entirely honest in their tweets. This year, and in prior years, they strongly encouraged people to go to one of the most remote lots, regularly telling people it was the fastest route to the event. This was not true. I don’t want to ascribe any particular malice here, but there is a suspicion that there is a temptation to make reports in the interest of the event rather than the user. This does have positives, in that cars diverted from near the event reduce traffic which makes the shuttle buses run much faster, but if you give wrong information (deliberately or by accident) this means people stop trusting it and you get the traffic back as more people ignore it.
For example, we stopped at a remote lot, and saw a very long shuttle line. We drove on to a closer lot (also reported as having spaces, but not reported as clearly a better choice) to find lots of spaces, no shuttle line, frequent shuttles and also a walk that was only slightly longer than the shuttle trip. read more »
Submitted by brad on Thu, 2013-03-21 22:37.
Earlier in part one I examined why it’s hard to make a networked technology based on random encounters. In part two I explored how V2V might be better achieved by doing things phone-to-phone.
For this third part of the series on connected cars and V2V I want to look at the potential for broadcast data and other wide area networking.
Today, the main thing that “connected car” means in reality is cell phone connectivity. That began with “telematics” — systems such as OnStar but has grown to using data networks to provide apps in cars. The ITS community hoped that DSRC would provide data service to cars, and this would be one reason for people to deploy it, but the cellular networks took that over very quickly. Unlike DSRC which is, as the name says, short range, the longer range of cellular data means you are connected most of the time, and all of the time in some places, and people will accept nothing less.
I believe there is a potential niche for broadcast data to mobile devices and cars. This would be a high-power shared channel. One obvious way to implement it would be to use a spare TV channel, and use the new ATSC-M/H mobile standard. ATSC provides about 19 megabits. Because TV channels can be broadcast with very high power transmitters, they reach almost everywhere in a large region around the transmitter. For broadcast data, that’s good.
Today we use the broadcast spectrum for radio and TV. Turns out that this makes sense for very popular items, but it’s a waste for homes, and largely a waste for music — people are quite satisfied instead with getting music and podcasts that are pre-downloaded when their device is connected to wifi or cellular. The amount of data we need live is pretty small — generally news, traffic and sports. (Call in talk shows need to be live but their audiences are not super large.)
A nice broadcast channel could transmit a lot of interest to cars.
- Timing and phase information on all traffic signals in the broadcast zone.
- Traffic data, highly detailed
- Alerts about problems, stalled vehicles and other anomalies.
- News and other special alerts — you could fit quite a few voice-quality station streams into one 19 megabit channel.
- Differential GPS correction data, and even supplemental GPS signals.
The latency of the broadcast would be very low of course, but what about the latency of uploaded signals? This turns out to not be a problem for traffic lights because they don’t change suddenly on a few milliseconds notice, even if an emergency vehicle is sending them a command to change. If you know the signal is going to change 2 seconds in advance, you can transmit the time of the change over a long latency channel. If need be, a surprise change can even be delayed until the ACK is seen on the broadcast channel, to within certain limits. Most emergency changes have many seconds before the light needs to change.
Stalled car warnings also don’t need low latency. If a car finds itself getting stalled on the road, it can send a report of this over the cellular modem that’s already inside so many cars (or over the driver’s phone.) This may take a few seconds to get into the broadcast stream, but then it will be instantly received. A stalled car is a problem that lasts minutes, you don’t need to learn about it in the first few milliseconds.
Indeed, this approach can even be more effective. Because of the higher power of the radios involved, information can travel between vehicles in places where line of sight communications would not work, or would actually only work later than the server-relayed signal. This is even possible in the “classic” DSRC example of a car running a red light. While a line of sight communication of this is the fastest way to send it, the main time we want this is on blind corners, where LoS may have problems. This is a perfect time for those longer range, higher power communications on the longer waves.
Most phones don’t have ATSC-M/H and neither do cars. But receiver chips for this are cheap and getting cheaper, and it’s a consumer technology that would not be hard to deploy. However, this sort of broadcast standard could also be done in the cellular bands, at some cost in bandwidth for them.
19 megabits is actually a lot, and since traffic incidents and light changes are few, a fair bit of bandwidth would be left over. It could be sold to companies who want a cheaper way to update phones and cars with more proprietary data, including map changes, their own private traffic and so on. Anybody with a lot of customers might fight this more efficient. Very popular videos and audio streams for mobile devices could also use the extra bandwidth. If only a few people want something, point to point is the answer, but once something is wanted by many, broadcast can be the way to go.
What else might make sense to broadcast to cars and mobile phones in a city? While I’m not keen to take away some of the nice whitespaces, there are many places with lots of spare channels if designed correctly.
Submitted by brad on Mon, 2013-03-18 16:28.
Last week, I began in part 1 by examining the difficulty of creating a new network system in cars when you can only network with people you randomly encounter on the road. I contend that nobody has had success in making a new networked technology when faced with this hurdle.
This has been compounded by the fact that the radio spectrum at 5.9ghz which was intended for use in short range communications (DSRC) from cars is going to be instead released as unlicenced spectrum, like the WiFi bands. I think this is a very good thing for the world, since unlicenced spectrum has generated an unprecedented radio revolution and been hugely beneficial for everybody.
But surprisingly it might be something good for car communications too. The people in the ITS community certainly don’t think so. They’re shocked, and see this as a massive setback. They’ve invested huge amounts of efforts and careers into the DSRC and V2V concepts, and see it all as being taken away or seriously impeded. But here’s why it might be the best thing to ever happen to V2V.
The innovation in mobile devices and wireless protocols of the last 1-2 decades is a shining example to all technology. Compare today’s mobile handsets with 10 years ago, when the Treo was just starting to make people think about smartphones. (Go back a couple more years and there weren’t any smartphones at all.) Every year there are huge strides in hardware and software, and as a result, people are happily throwing away perfectly working phones every 2 years (or less) to get the latest, even without subsidies. Compare that to the electronics in cars. There is little in your car that wasn’t planned many years ago, and usually nothing changes over the 15-20 year life of the car. Car vendors are just now toying with the idea of field upgrades and over-the-air upgrades.
Car vendors love to sell you fancy electronics for your central column. They can get thousands of dollars for the packages — packages that often don’t do as much as a $300 phone and get obsolete quickly. But customers have had enough, and are now forcing the vendors to give up on owning that online experience in the car and ceding it to the phone. They’re even getting ready to cede their “telematics” (things like OnStar) to customer phones.
I propose this: Move all the connected car (V2V, V2I etc.) goals into the personal mobile device. Forget about the mandate in cars.
The car mandate would have started getting deployed late in this decade. And it would have been another decade before deployment got seriously useful, and another decade until deployment was over 90%. In that period, new developments would have made all the decisions of the 2010s wrong and obsolete. In that same period, personal mobile devices would have gone through a dozen complete generations of new technology. Can there be any debate about which approach would win? read more »
Submitted by brad on Mon, 2013-02-18 14:13.
You’ve probably seen the battle going on between Elon Musk of Tesla and the New York Times over the strongly negative review the NYT made of a long road trip in a Model S. The reviewer ran out of charge and had a very rough trip with lots of range anxiety. The data logs published by Tesla show he made a number of mistakes, didn’t follow some instructions on speed and heat and could have pulled off the road trip if he had done it right.
Both sides are right, though. Tesla has made it possible to do the road trip in the Model S, but they haven’t made it easy. It’s possible to screw it up, and instructions to go slow and keep the heater low are not ones people want to take. 40 minute supercharges are still pretty long, they are not good for the battery and it’s hard to believe that they scale since they take so long. While Better Place’s battery swap provides a tolerable 5 minute swap, it also presents scaling issues —
you don’t want to show up at a station that does 5 minute swaps and be 6th in line.
The Tesla Model S is an amazing car, hugely fun to drive and zippy, cool on the inside and high tech. Driving around a large metro area can be done without range anxiety, which is great. I would love to have one — I just love $85K more. But a long road trip, particularly on a cold day? There are better choices. (And in the Robocar world when you can get cars delivered, you will get the right car for your trip delivered.)
Electric cars have a number of worthwhile advantages, and as battery technologies improve they will come into their own. But let’s consider the economics of a long range electric. The Tesla Model S comes in 3 levels, and there is a $20,000 difference between the 40khw 160 mile version and the 85kwh 300 mile version. It’s a $35K difference if you want the performance package.
The unspoken secret of electric cars is that while you can get the electricity for the model S for just 3 cents/mile at national grid average prices (compared to 12 cents/mile for gasoline in a 30mpg car and 7 cents/mile in a 50mpg hybrid) this is not the full story. You also pay, as you can see, a lot for the battery. There are conflicting reports on how long a battery pack will last you (and that in turn varies on how you use and abuse it.) If we take the battery lifetime at 150,000 miles — which is more than most give it — you can see that the extra 45kwh add-on in the Tesla for $20K is costing about 13 cents/mile. The whole battery pack in the 85kwh Telsa, at $42K estimated, is costing a whopping 28 cents/mile for depreciation.
Here’s a yikes. At a 5% interest rate, you’re paying $2,100 a year in interest on the $42,000 Tesla S 85kwh battery pack. If you go the national average 12,000 miles/year that’s 17.5 cents/mile just for interest on the battery. Not counting vehicle or battery life. Add interest, depreciation and electricity and it’s just under 40 cents/mile — similar to a 10mpg Hummer H2. (I bet most Tesla Model S owners do more than that average 12K miles/year, which improves this.)
In other words, the cost of the battery dwarfs the cost of the electricity, and sadly it also dwarfs the cost of gasoline in most cars. With an electric car, you are effectively paying most of your fuel costs up front. You may also be adding home charging station costs. This helps us learn how much cheaper we must make the battery.
It’s a bit easier in the Nissan LEAF, whose 24kwh battery pack is estimated to cost about $15,000. Here if it lasts 150K miles we have 10 cents/mile plus the electricity, for a total cost of 13 cents/mile which competes with gasoline cars, though adding interest it’s 19 cents/mile — which does not compete. As a plus, the electric car is simpler and should need less maintenance. (Of course with as much as $10,000 in tax credits, that battery pack can be a reasonable purchase, at taxpayer expense.) A typical gasoline car spends about 5 cents/mile on non-tire maintenance.
This math changes a lot with the actual battery life, and many people are estimating that battery lives will be worse than 150K miles and others are estimating more. The larger your battery pack and the less often you fully use it, the longer it lasts. The average car doesn’t last a lot more than 150k miles, at least outside of California.
The problem with range anxiety becomes more clear. The 85kwh Tesla lets you do your daily driving around your city with no range anxiety. That’s great. But to get that you buy a huge battery pack. But you only use that extra range rarely, though you spend a lot to get it. Most trips can actually be handled by the 70 mile range Leaf, though with some anxiety. You only need all that extra battery for those occasional longer trips. You spend a lot of extra money just to use the range from time to time. read more »
Submitted by brad on Tue, 2012-11-27 10:39.
(Of late I have been writing a few articles for some other online sites. The following is an article that appeared on Forbes.com It was also commented on positively and negatively with angry threads.)
There’s been much debate in the USA about High Speed Rail (HSR) and most notably the giant project aimed at moving 20 to 24 million passengers a year through the California central valley, and in particular from downtown LA to downtown San Francisco in 2 hours 40 minutes.
There’s been big debate about the projected cost ($68B to $99B) and the inability of projected revenues to cover interest on the capital let alone operating costs. The project is beginning with a 130 mile segment in the central valley to make use of federal funds. This could be a “rail to nowhere” connecting no big towns and with no trains on it. By 2028 they plan to finally connect SF and LA.
The debate about the merits of this train is extensive and interesting, but its biggest flaw is that it is rooted in the technology of the past and present day. Indeed, HSR itself is around 50 years old, and the 350 kph top speed of the planned line was attained by the French TGV over 30 years ago.
The reality of the world, however, is that technology is changing very fast, and in some fields like computing at an exponential rate. Transportation has not been used to such rapid rates of change, but that protection is about to end. HSR planners are comparing their systems to other 20th century systems and not planning for what 2030 will actually hold.
At Singularity University, our mission is to study and teach about the effects of these rapidly changing technologies. Here are a few areas where new technology will disrupt the plans of long-term HSR planners:
Cars that can drive and deliver themselves left the pages of science fiction and entered reality in the 2000s thanks to many efforts, including the one at Google. (Disclaimer: I am a consultant to, but not a spokesman for that team.)
Readers of my own blog will know it is one of my key areas of interest.
By 2030 such vehicles are likely to be common, and in fact it’s quite probable they will be able to travel safely on highways at faster speeds than we trust humans to drive. They could also platoon to become more efficient.
Their ability to deliver themselves is both boon and bane to rail transit. They can offer an excellent “last/first mile” solution to take people from their driveways to the train stations — for it is door to door travel time that people care about, not airport-to-airport or downtown-to-downtown. The HSR focus on a competitive downtown-to-downtime time ignores the fact that only a tiny fraction of passengers will want that precise trip.
Self-delivering cars could offer the option of mobility on demand in a hired vehicle that is the right vehicle for the trip — often a light, efficient single passenger vehicle that nobody would buy as their only car today. These cars will offer a more convenient and faster door-to-door travel time on all the modest length trips (100 miles or less) in the central valley. Because the passenger count estimates for the train exceed current air-travel counts in the state, they are counting heavily on winning over those who currently drive cars in the central valley, but they might not win many of them at all.
The cars won’t beat the train on the long haul downtown SF to downtown LA. But they might well be superior or competitive (if they can go 100mph on I-5 or I-99) on the far more common suburb-to-suburb door to door trips. But this will be a private vehicle without a schedule to worry about, a nice desk and screen and all the usual advantages of a private vehicle.
Improved Air Travel
The air travel industry is not going to sit still. The airlines aren’t going to just let their huge business on the California air corridor disappear to the trains the way the HSR authority hopes. These are private companies, and they will cut prices, and innovate, to compete. They will find better solutions to the security nightmare that has taken away their edge, and they’ll produce innovative products we have yet to see. The reality is that good security is possible without requiring people arrive at airports an hour before departure, if we are driven to make it happen. And the trains may not remain immune from the same security needs forever.
On the green front, we already see Boeing’s new generation of carbon fiber planes operating with less fuel. New turboprops are quiet and much more efficient, and there is more to come.
The fast trains and self-driving cars will help the airports. Instead of HSR from downtown SF to downtown LA, why not take that same HSR just to the airport, and clear security while on the train to be dropped off close to the gate. Or imagine a self-driving car that picks you up on the tarmac as you walk off the plane and whisks you directly to your destination. Driven by competition, the airlines will find a way to take advantage of their huge speed advantage in the core part of the journey.
Self-driving cars that whisk people to small airstrips and pick them up at other small airstrips also offer the potential for good door-to-door times on all sorts of routes away from major airports. The flying car may never come, but the seamless transition from car to plane is on the way.
We may also see more radical improvements here. Biofuels may make air travel greener, and lighter weight battery technologies, if they arrive thanks to research for cars, will make the electric airplane possible. Electric aircraft are not just greener — it becomes more practical to have smaller aircraft and do vertical take-off and landing, allowing air travel between any two points, not just airports.
These are just things we can see today. What will the R&D labs of aviation firms come up with when necesessity forces them towards invention?
Rail technology will improve, and in fact already is improving. Even with right-of-way purchased, adaptation of traditional HSR to other rail forms may be difficult. Expensive, maglev trains have only seen some limited deployment, and while also expensive and theoretical, many, including the famous Elon Musk, have proposed enclosed tube trains (evacuated or pneumatic) which could do the trip faster than planes. How modern will the 1980s-era CHSR technology look to 2030s engineers?
Decades after its early false start, video conferencing is going HD and starting to take off. High end video meeting systems are already causing people to skip business trips, and this trend will increase. At high-tech companies like Google and Cisco, people routinely use video conferencing to avoid walking to buildings 10 minutes away.
Telepresence robots, which let a remote person wander around a building, go up to people and act more like they are really there are taking off and make more and more people decide even a 3 hour one-way train trip or plane trip is too much. This isn’t a certainty, but it would also be wrong to bet that many trips that take place today just won’t happen in the future.
Like it or not, in many areas, sprawl is increasing. You can’t legislate it away. While there are arguments on both sides as to how urban densities will change, it is again foolish to bet that sprawl won’t increase in many areas. More sprawl means even less value in downtown-to-downtown rail service, or even in big airports. Urban planners are now realizing that the “polycentric” city which has many “downtowns” is the probable future in California and many other areas.
That Technology Nobody Saw Coming
While it may seem facile to say it, it’s almost assured that some new technology we aren’t even considering today will arise by 2030 which has some big impact on medium distance transportation. How do you plan for the unexpected? The best way is to keep your platform as simple as possible, and delay decisions and implementations where you can. Do as much work with the knowledge of 2030 as you can, and do as little of your planning with the knowledge of 2012 as you can.
That’s the lesson of the internet and the principle known as the “stupid network.” The internet itself is extremely simple and has survived mostly unchanged from the 1980s while it has supported one of history’s greatest whirlwinds of innovation. That’s because of the simple design, which allowed innovation to take place at the edges, by small innovators. Simpler base technologies may seem inferior but are actually superior because they allow decisions and implementations to be delayed to a time when everything can be done faster and smarter. Big projects that don’t plan this way are doomed to failure.
None of these future technologies outlined here are certain to pan out as predicted — but it’s a very bad bet to assume none of them will. California planners and the CHSR authority need to do an analysis of the HSR operating in a world of 2030s technology and sprawl, not today’s.
Submitted by brad on Mon, 2012-05-21 12:22.
There’s a lot of excitement about the potential of autonomous drones, be they nimble quadcopters or longer-range fixed wing or hybrid aircraft. A group of students from Singularity University, for example, has a project called MatterNet working to provide transportation infrastructure for light cargo in regions of Africa where roads wash out for half the year.
Closer to home, these drones are not yet legal for commercial use, while government agencies are using them secretly.
Here’s one useful idea: A small set of medical drones scattered around the city. Upon emergency call, they can fly, via a combination of autonomous navigation and remote-human-operated flying at the end, to any destination in the city within a couple of minutes. Call 911 and as soon as you say it’s a medical emergency the drone is on the way. When it gets there, the human operator lands it or even sends it in a balcony on tall buildings with balconies. Somebody has to carry it to the patient if they are far from the outside.
When it gets to the patient it has a camera and conferencing ability to a remote doctor can examine the patient and talk to people around the patient to ask them questions or give them instructions. It also could contain one of those “foolproof defibrillator” modules able to deal with many kinds of heart attacks. They are already in many buildings but this way they could be anywhere. It’s more useful than a taco.
The remote doctor could advise any medical staff who come, or give advice to the ambulance that’s on the way but not getting there for a few minutes. If a medicine that can be administered by a layperson is needed, there might be some in the drone but a second drone could be loaded and dispatched within a few minutes as well — that might take longer to fly but less time than an ambulance. You might not put any valuable medicines in the first drone to prevent people from summoning them just to steal them, though this might just happen for the valuable drone unless steps are taken to make that non-productive.
This should be combined with something I have felt is long overdue in the world of our mobile phones. People who are able to be on-call EMTs and doctors should have their phones updating their locations with a medical service while they are on call for such action. Then anybody with an emergency should be able to summon or get to the closest professional very quickly. (Of course there is no need to record this data after it changes, to avoid making a life-log of the doctor.) Nobody should ever have to ask “is there a doctor in the house?” 911 should be able to say, “There is a doctor 3 doors down, she’s been notified.” But the drone can always come, and bring a remote specialist if need be.
The other barrier to this is network dead zones. A map would need to be made of network dead zones and the drone would not fly into them, though it could fly through them. It would land just outside the dead zone and warn people not to carry it into one if the remote doctor’s services are needed.
Someday, the drone could contain a winner of the X-prize “Medical Tricorder” contest with sensors to diagnose all sorts of conditions, and it might even eventually be a robot able to administer emergency drugs — but the actual delivery and video feed is something we can do today.
Submitted by brad on Thu, 2011-12-22 15:49.
This time of year I do a lot of online shopping, and my bell rings with many deliveries. But today and tomorrow, not Saturday. The post office comes Saturday but has announced it wants to stop doing that to save money. They do need to save money, but this is the wrong approach. I think the time has come for Saturday and Sunday delivery to be the norm for UPS, Fedex and the rest.
When I was young almost all retailers closed on Sunday and even had limited hours on Saturday. Banks never opened on the weekend either. But people soon realized that because the working public had the weekend off, the weekend was the right time for consumer services to be operating. The weekend days are the busiest days at most stores.
The shipping companies like Fedex and UPS started up for business to business, but online shopping has changed that. They now do a lot of delivery to residences, and not just at Christmas. But Thursday and Friday are these odd days in that business. An overnight package on Friday gets there 3 days later, not 1. (If you use the post office courier, you get Saturday delivery as part of the package, and the approximately 2 day Priority mail service is a huge win for things sent Thursday.) In many areas, the companies have offered Saturday and even Sunday delivery, but only as a high priced premium service. Strangely, the weekend also produces a gap in ground shipping times — the truck driving cross-country presumably pauses for 2 days.
We online shoppers shop 7 days a week and we want out stuff as soon as we can get it. I understand the desire to take the weekend off, but usually there are people ready to take these extra shifts. This will cost the delivery companies more as they will have to hire more workers to operate on the weekend. And they can’t just do it for ground (otherwise a 3 day package sent Friday arrives the same time as an overnight package.)
Update: I will point out that while online shipping is the David to the Goliath of brick & mortar, changing shipping to 7 days a week will mean a bunch more stuff gets bought online, and shipped, and will bring new revenue to the shipping companies. It’s just just a cost of hiring more people. It also makes use of infrastructure that sits idle 2 days a week.
This is particularly good for those who are always not hope to sign for packages that come during the work week. The trend is already starting. OnTrak, which has taken over a lot of the delivery from Amazon’s Nevada warehouse to Californians, does Saturday delivery, and it’s made me much more pleased with Amazon’s service. When Deliverbots arrive, this will be a no brainer.
Submitted by brad on Fri, 2011-11-11 19:20.
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.
Even at the earlier estimates the project was an obvious mistake, and there’s no way to financially justify spending $99 billion to pull in $5.3 billion/year even subbing zero in for the large operating cost. But for various political reasons involving getting federal money, some are still pushing for this project, and we may well build a short train to nowhere in the central valley just to get the federal bucks.
They’re planning there because the various cities in the populated areas have been fighting legal battles to block the train there, not wanting its disruption. Because the train can only stop if a very few places at the speed it wants to go, a lot of towns would end up having construction and noise and street blockage and not get a lot of use from the train.
The local opposition is a tough barrier, because the train ends up really only being useful where the people are. While I have doubts about how many people would ride the long haul, since few want to go from downtown SF to downtown LA, lots of people would ride a fast train in the urban areas. In particular, what nobody talks about is running the HSR primarily to the airport, and streamlining both security clearance and the connection with new technology. The only reason HSR is pushed as possibly competing with flights is because of the nightmare we have made of flying, where people have to get to airports 45 minutes ahead of even short-haul flights and take a fair bit of time to get out of airports on the other end and make it through traffic to their destinations. A fast train from a downtown to the airport where you clear security (and check bags) right on the train, and the train drops you right at the central gate areas post security would create an unbeatable trip from downtown anywhere to downtown anywhere.
For fast trains, the San Francisco to San Jose route is so short that a 250mph HSR could do the 48 mile trip between the towns in 12 minutes without stopping, call it 15 with the start and stop at each end. This opens up an interesting cost saving — you could build a single track, and have a train zip back and forth on it, and still provide service every 30 minutes. You could put a double-track section in the middle and have service every 15 minutes, with lots of safety interlocks of course. A single track requires less land, less of everything and could probably be built along easier routes, even highway medians in some cases. You could avoid turnaround time by having double track at the endpoints, so one train is leaving for opposite route the moment the other train arrives, giving each train quite a long turnaround — with double rolling stock.
Of course, having no stops is not that valuable because only a few people want to go from SJ to SF. People would want a stop at the airport as I have indicated, and at least one in Mountain View or Palo Alto. Each stop costs a bunch of time, and eventually the trip gets long enough that the single-track trick becomes less useful. For a while I’ve wondered if you could make trains that could dock, so that the main train runs non-stop and is able to shed cars which stop at local stops (not that hard) and to dock with cars coming from local stops (harder.) I proposed this 7 years ago near the start of this blog, and there are serious rail designers thinking along the same lines — see the video in that link.
In the Priestman Goode proposal, they have trains docking side to side. That seems much more challenging though it offers fast transfer. If you combine the two ideas, you would have two tracks — one for the nonstop trains and one for the docking shuttles which serve all the local stops. Indeed, if you could do this you could get rid of the old regular speed rail service running on existing track pairs because this would be superior in all ways except cost. My own proposals attempted to dock on a single track, which seems easier to me.
Robocars play a role in all this too. Even the HSR authority realizes they have a big problem, in that once people get quickly to an HSR station, they still have to get to their real destination. Using local transit may mean spending more time on a local bus than on the HSR. The mobility on demand of robocars is a great answer, and I’m pretty sure that with a 2030 forecast completion date (if they’re lucky) we’ll have robocars long before then. And the one thing cars can’t readily do is go very fast efficiently between cities.
The docking approach, should it work, has another advantage. The main train can take the best route (cheapest or shortest) without too much regard for where the stations are. People like stations in urban centers, but bringing the high speed train right through such areas (like Palo Alto) is hard and has caused the lawsuits. If the train goes through the industrial space along the Bay, and a spur goes into downtown for the shuttle that docks with it, you get a win all around.
Another approach that doesn’t require dock/undock works when you have a solid terminus like SF. You have 3 trains leave SF at the same time. The first one goes express to San Jose. The second goes express to Palo Alto and Mountain View and then switches to low speed tracks to go to Sunnyvale and Santa Clara. The third goes to SFO airport. Because SFO airport is also an origination point, it sends a train to SJ just before or after the one from SF, and another train to Mountain View right after that one. Mountain View to SJ service might be able to fit in or have to be local service. These sub-trains are just a few cars. This is not as energy efficient, though it can be if the trains are able to get close to one another and draft, sort of a virtual coupling without physical contact. You need perfect sync, and special long-spring collision bumpers in case the sync fails and they bump. The risk of higher-speed bumping must be prevented by failsafes that don’t even let the trains get on the same track until speed is matched close enough. This requires more than just a single track of course.
Submitted by brad on Tue, 2011-11-08 14:57.
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. read more »
Submitted by brad on Thu, 2011-10-27 11:28.
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.) read more »
Submitted by brad on Tue, 2011-06-28 20:45.
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.
But one interesting realization in the study is that users have become frustrated at having too many devices with too many UIs. Their car (which now has a touchpad and lots of computer features) uses a different UI from their phone and computer and tablet and whatever. Even if the car has a superb UI, the problem is that it is different, something new to learn and remember.
One might fix this by having the same platform, be it iOS or Android on several of the devices, but that’s a tall order. Car vendors do not want to make a phone one one platform and tick off people used to the other platform.
The answer lies in something the car makers don’t like: Don’t put much of their own smarts in the car at all, and expect the user to slot their own mobile phone or tablet into the car. This might be done with something like Nokia’s “Terminal Mode” where the car’s screen and buttons can be taken over by the phone, or by not having a screen in the car at all, just a standard mounting place.
Some time ago I wrote that cars should stop coming with included radios as they used to 30 years ago, and let the slot in the dashboard where the radio and electronics go become a center for innovation. In particular innovation at the speed of consumer and mobile devices, not innovation at the speed of car companies. But there are too many pressures to stop this from happening. Car companies get to charge a lot for fancy radio and electronics systems in the cars, and they like this. And they like the control over the whole experience. But as they get more complaints they may realize that it’s not the right thing for them to be building. Especially not when the car (and the in-dash system) last for 10 to 15 years, while most consumer electronic devices are obsolete in 1-2 years.
There aren’t that many makes of cars, nor so many mobile platforms, so making custom apps for the car and the mobile platform isn’t that hard. In fact, I would expect you would see lots of competing aftermarket ones if they opened up the market to it. And open source ones too, built by fans of the particular cars.
Submitted by brad on Sun, 2011-05-01 19:27.
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.
Nokia and others are pushing one alternative for the cars that have dashboard screens. This is called “Terminal Mode” and is a protocol so the phone can make use of the display, buttons and touchscreens in the car. Putting the smarts in the phone and making the dash be the dumb peripheral is the right idea, since people upgrade phones frequently and cars not nearly so much. The terminal mode interface can be wireless so the phone does not have to be plugged in, though of course most people like to recharge phones while driving.
Terminal mode will be great if it comes, but it would be good to also push for a standard port on dashboards for mounting mobile phones. Today, most mobile phone holders either stick to the windshield with a suction cup, or clamp onto the vents of the air conditioner. A small port or perhaps flip out lever arm would be handy if standardized on dashboards. The lever arm would offer a standard interface for connecting a specific holder for the specific device. In addition, the port would offer USB wiring so that the holder could offer it to the phone. This would offer power at the very least but could also do data for terminal mode and some interfacing with other elements of the car, including the stereo system, or the onboard-diagnostics bus. Access to other screens in the back (for playing video) and to superior antennas might make sense. While many phones use their USB port to be a peripheral to a PC, some have “USB to go” which allows a device to be either master or peripheral, allowing more interesting functions.
Even with terminal mode, there could be value in having two screens, and more buttons, though of course apps would have to be developed to understand that. However, one simple thing is that a phone could run two apps at once on two screens (or even two apps at once on the larger screen of the car) which would actually be pretty handy.
Submitted by brad on Sat, 2011-01-29 17:05.
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.
You will find much that is similar between the two concepts, though they were developed independently. I will have to give Skyride the nod of picking names, though. Skyride offers both pedaling and a rowing-machine style interface, the latter aimed both at the disabled and those seeking a different kind of workout.
At present, the Skyride car is also open to the air, which has both advantages and disadvantages when it comes to cooling, drag, and exposure to the elements. Skyride does not also seem to offer the “bumper” system in the wheel cartridge which Shweeb claims will allow vehicles to safely hit one another and then push one another in trains.
Both are confined to prototype tracks for now, though the Schweeb one is an amusement ride that is open to the public. Both have plans to solve the most important problem in turning this into a real transportation system for campuses or urban areas, namely a switch that lets the vehicle smoothly and safely change tracks. Switching has always been an issue in monorails — not that it can’t be solved, but it’s just a little harder than changing lanes in a car. Rail systems sometimes put the switching in the track (that’s what regular heavy rail does) but that’s not very practical if you are going to have very frequent small vehicles. You want in-vehicle switching but with no risk of derailing.
While this concept is interesting, and even more fun if they can prove it works and then add some automation, I am not sure it will ever become a really big space. Still, having 2 companies will not doubt spur a bit more innovation.
Submitted by brad on Fri, 2011-01-14 20:58.
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:
- If the car has bluetooth, the phone usually associates with the car. That’s a dead giveaway, and can at least be a clue to start looking at the GPS.
- Most of my haunts have wireless, and the phone associates with the wireless at my house and all the places I work. So it can notice when it disassociates and again start checking the GPS. To get smart, it might even notice the MAC addresses of wireless networks it can’t see inside the house, but which it does see outside or along my usual routes.
- Of course moving out to the car involves jostling and walking in certain directions (it has a compass.)
Once it thinks it might be in the car, it should go to a mode where my “in the car” apps are easy to get to, in particular the live map of the location with the traffic displayed, or the screen for the nav system. Android has a “car mode” that tries to make it easy to access these apps, and it should enter that mode.
It should also now track me for a while to figure out which way I am going. Depending on which way I head and the time of day, it can probably guess which of my common routes I am going to take. For regular commuters, this should be a no-brainer. This is where I want it to be really smart: Instead of me having to call up the traffic, it should see that I am heading towards a given highway, and then check to see if there are traffic jams along my regular routes. If it sees one, Then it should beep to signal that, and if I turn it on, I should see that traffic jam. This way if I don’t hear it beep, I can feel comfortable that there is light traffic along the route I am taking. (Or that if there is traffic, it’s not traffic I can avoid with alternate routes.)
This is the way I want location based apps to work. I don’t want to have to transmit my location constantly to the cloud, and have the cloud figure out what to do at any given location. That’s privacy invading and uses up power and bandwidth. Instead the phone should have a daemon that detects location “events” that have been programmed into it, and then triggers programs when those events occur. Events include entering and leaving my house or places I work, driving certain roads and so on.
And yes, for tools like shopkick, they can even be entering stores I have registered. And as I blogged at the very beginning of this blog many years ago, we can even have an event for when we enter a store with a bad reputation. The phone can download a database of places and wireless and Bluetooth MACs that should trigger events, and as such the network doesn’t need to know my exact location to make things happen. But most importantly, I don’t want to have to know to ask if there is something important near me, I want the right important things to tell me when I get near them.
Submitted by brad on Sat, 2010-11-20 13:58.
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.
We have a few signals. Oncoming cars flash lights on and off to warn you your lights are off. (Sometimes they are also warning of a speed trap.) High beams means, “I want to pass and you’re impeding the lane” and while many think that’s rude it’s better than tailgating.
We need a signal for “There is a problem with your car, you should check it out.” This signal should be taught in driving schools, and even be on the driving test. A publicity campaign should educate existing drivers.
One proposal that might make sense is the SCUBA signal for “I have a problem.” This is holding your hand flat, palm down, and wiggling it side to side (ie. rotating your wrist.) Then you point to the source of the problem, like your regulator or whatever. (There are specific SCUBA signals for well known problems, like being low on air, nitrogen narcosis etc.)
For this signal you would waggle the hand and then point at the place on the other person’s car. To those untrained, the signal often mean’s “dicey” or uncertain. Shaking of the head could also strengthen the signal.
Anybody have a better signal to propose?
Submitted by brad on Sun, 2010-10-03 00:53.
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. read more »
Submitted by brad on Wed, 2010-08-04 15:35.
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. read more »
Submitted by brad on Sat, 2010-04-17 19:32.
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. read more »