Skip to main content

The Karma Revero's solar roof is a gimmick

You may have seen a few stories about the Karma Revero's solar roof. For those that follow cars, the Revero is the re-born Fisker Karma, a hybrid gas and electric vehicle.

By Fisker at speed in the fog.jpg: Fisker Auto derivative work: Mariordo (Mario Roberto Durán Ortiz) [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

Fisker went bankrupt and was bought by a Chinese automotive components company. Fisker was renamed to Karma and the car was renamed from the Karma to the Revero.

Karma's website has this text on their website about the solar roof:

"Our solar roof will create enough energy to power the car. No other vehicle sold in the U.S. has ever offered this capability. Our owners consider our solar roof an important element in our brand identity, and we listened."



Lots of sites have written stories about the solar roof idea, copying the information from Karma without doing any kind of analysis.

Solar panels can be helpful when used on cars. Toyota offered, and may still offer, a solar panel option for the Prius that would use solar power to run a fan to vent the car when the interior was hot. This would reduce the inside temperature and help reduce the need for air conditioning.

Karma is claiming their solar roof can go beyond just powering a fan, and instead power the car. It may be factually true that the solar roof can power the car but it is misleading to suggest that they can do so in a way that you would notice on a daily basis.

Wikipedia lists the Karma (and presumably the Revero's) energy consumption at 65 kWh / 100 miles, or 650 Wh/mile. For comparison I get between 250-310 Wh/mile in my Model S on the highway in the summer with AC, depending on speed and elevation change.

Wikipedia reports that the Karma's solar roof can generate approximately 500 Wh per day.

Let's assume that the Revero has had some improvements and has increased its solar output by 50% to 750 Wh per day and the efficiency of the electric drivetrain has improved and its consumption was reduced to 400 Wh/mile. Together this means you can travel about two miles on the energy from a full day's solar roof generation.

750 Wh / 400 Wh/mile = 1.875 miles

This is an optimistic number and its very likely that actual generated range will be lower than this.

Two miles isn't a lot of driving range and it isn't surprising that other car manufacturers, even those with electric drivetrains, haven't been putting solar panels on their cars. In the summer it might save more energy to park in the shade.

The Revero's solar roof as it's currently presented is a gimmick that Karma is using to attract interest. Looking at the contribution of the solar roof over the life of the car might yield a different result. Even a small amount of energy per day could add up to a substantial amount over the life of the car, although that isn't the only factor. Will it generate enough energy to offset the extra energy used to haul around the solar roof and its electronics? Will it generate enough energy to offset the cost of the panels and electronics? I'd like to see Karma make their case by providing more information and clarify the real-world utility of their solar roof.



Update: Jalopnik writes The Claim That The Karma Revero's Solar Roof Will 'Power The Car' Is Such Bullshit. I agree.

Comments

Popular posts from this blog

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was

Memory efficient queuing of variable length elements

In embedded environments memory can be a critical driver of the design of data structures and containers. Computing resources have been expanding steadily each year but there are still a wide range of systems with far less than a megabyte of memory. On systems with tens of kilobytes of memory, structures are often designed to be compact to maximize data density. Rather than splurging on memory aligned elements that would be faster for the processor to access, a developer will typically use types with minimal sizes based on the known range of values that the element is intending to hold. Fixed sized buffers At my day job a fixed size pool of messages was implemented to hold message data. While this achieved one design goal of using statically allocated buffers, avoiding dynamic allocations that might fail at runtime, it isn't efficient if there is a wide range of message sizes. It isn't efficient because each message uses a message buffer. With small message sizes the buff