Nonbattery Energy Storage: Ultracapacitors and Flywheels

Ultracapacitors

Ultracapacitors are devices that can directly store electrical charges—unlike batteries, which store electricity as chemical energy. A variety of ultracapacitor materials and designs are being investigated, but all share some basic characteristics-very high specific power, greater than 1 kW/kg, coupled with low specific energy. The U.S.

Department of Energy mid-term goal is only 10 Wh/kg (compared to the U.S. Advanced Battery Consortium midterm battery goal of 100 Wh/kg). Other likely ultracapacitor characteristics are high storage efficiency and long life. Ultracapacitors’ energy and power characteristics define their role. In electric vehicles, their high specific power can be used to absorb the strong power surges of regenerative braking, to provide high power for brief spurts of acceleration, and to smooth out any rapid changes in power demand from the battery in order to prolong its life. In hybrids, they theoretically could be used as the energy storage mechanism; however, their low specific energy limits their ability to provide a prolonged or repeatable power boost. Increasing ultracapacitors’ specific energy is a critical research goal.

Flywheels

A flywheel stores energy as the mechanical energy of a rapidly spinning mass, which rotates on virtually

frictionless bearings in a near-vacuum environment to minimize losses. The flywheel itself can serve as the rotor of an electrical motor/generator, so it can turn its mechanical energy into electricity or vice versa, as needed. Like ultracapacitors, flywheels have very high specific power ratings and relatively low specific energy, though their energy storage capacity is likely to be higher than ultracapacitors. Consequently, they may be more practical than ultracapacitors for service as the energy storage mechanism in a hybrid. In fact, the manufacturer of the flywheel designed for Chrysler’s Patriot race car, admittedly a very expensive design, claims a specific energy of 73 Wh/kg, which would make the flywheel a very attractive hybrid storage device. Mass-market applications for flywheels depend on solving critical rotor manufacturing issues, and, even if these issues were successfully addressed, it is unclear whether mass-produced flywheels could approach the Patriot flywheel’s specific energy level.

READ MORE.......

Advanced Automotive Technology: Visions

of a Super-Efficient Family Car

OTA-ETI-638

GPO stock #052-003-01440-8

for more details and updates about automotive-technology-guide please visit.........

www.automotive-technology-guide.com

---or---

www.automotive-technology-guide.com

Read More

What’s next for the connected car?

It’s been almost three years since QNX Software Systems launched its connected car concept, and I thought it would be an interesting exercise to look at what has been accomplished in the automotive industry around the connected car and how some of the concepts are evolving. When the QNX CAR Application Platform was introduced, we provided a simple way to look at a connected car, using four “dimensions” of connectivity:

• Connected to portable consumer devices for brought-in media and handsfree communications
• Connected to the cloud for obvious reasons
• Connected within the car for sharing information and media between front and rear seats, between the center stack and the cluster, and for other similar functions
• Connected around the car for providing feedback to the driver about the environment surrounding the car, be it pedestrians, other cars, or vehicle to infrastructure communications

We’ve seen significant advances and evolutionary thinking on all fronts. Although QNX is not (and cannot be) at the forefront of all of these, our primary emphasis has been on cloud and consumer device connectivity. Nonetheless, it is interesting to look at each area.

Connected to consumer devices, connected to the cloud
Why lump these two together? There is not exactly a clear line between the two since consumer devices are often just extensions of the cloud. If my car connects to a smartphone which, in turn, draws information from the cloud, is there much point in creating a distinction between consumer device and cloud connections? Although it made sense to differentiate between cloud and consumer device connections when phones provided only handsfree calling and simple music playback, today the situation is quite different.

Device integration into the car has been a beehive of activity over the last few years. Smartphones, superphones, and tablets are providing entertainment, social networking, news, and access to a myriad of other content and applications to consumers anywhere, anytime. Automakers want to take advantage of many of these capabilities in a responsible, non-distracting way.

The primary issue here is how to marry the fast-paced consumer electronics world to the lifecycle of the car. At present, there are solutions at the opposite end of the spectrum: standardized Bluetooth interfaces that allow the car to control the smartphone; and screen replication technologies (iPod Out, VNC/Terminal Mode/Mirror Link) where the smartphone takes control and uses the car as a dumb display.

Neither of these scenarios takes full advantage of the combined processing power and resources of the car and the brought-in device. This, to me, is the next phase of car and cloud connectivity. How can the power of the cloud, brought-in devices, and the in-car systems be combined into a cooperative, distributed system that provides a better driver and passenger experience? (If the notion of a distributed system seems a bit of a stretch, consider the comments made by Audi Chairman Rupert Stadler at CES 2011.)

When looking for technologies that can bring the cloud, devices, and car together, you do not need to look any further than the web itself. The software technologies (HTML5, Javascript, AJAX, peer-to-peer protocols, tooling, etc.) that drive the web provide a common ground for building the future in car experience. These technologies are open, low cost, widely known and widely accessible. What are we waiting for?

Connected within the car
The integrated cockpit has emerged as a prevalent automotive design concept. It is now commonplace in higher-end vehicles to see seamless integration between center stack functions and the instrument cluster and driver information displays. For example, turn-by-turn directions, radio tuning, and song now playing are all available to the driver on the cluster, reducing the need to constantly glance over to the main display. One such example is the Audi cluster:

Connected around the car

Three years ago, systems in this category were already emerging, so there really wasn’t much of a crystal ball required here. Adaptive cruise control has become one of the most common features that illustrate how a car can connect to its surroundings. Adaptive cruise control detects the car’s surroundings (cars in front of you) and adjusts your speed accordingly. Other examples include pedestrian detection (offered in Volvo S60 and other models)automatic parking, lane departure warning, and blind spot detection/warning systems.

These Advanced Driver Assist Systems (ADAS) will become more common as cost reductions take place and the technology is provided in lower-end vehicles.

In contrast, vehicle-to-infrastructure communication that requires industry-wide collaboration is proceeding at a pace that you’d expect from an internationally standardized solution.

Read More