2018 Nissan LEAF Test Drive

| No Comments

At the National Drive Electric Week event in Seattle, Cathy and I saw the newly-announced but not yet available 2018 Nissan LEAF. At that event, we signed up for a test drive.

ndew-seattle.jpgToday, October 23, 2017, Jose pulled up in front of our house in a beautiful blue Nissan LEAF for our test drive. We spent about an hour going over the vehicle and then out for a drive. Jose was enthusiastic and very knowledgeable about the car. We have a 2011 LEAF, so I'm familiar with that but haven't driven any of the newer LEAFs, so that's my perspective.

blue-2018-leaf.jpgBack Seat

The LEAF claims to be a 5-passenger vehicle, but the middle back seat has no head rest, so no neck protection in a rear-end collision. We often have 5 adults in the car, so that matters to us. I've been especially aware of this since we were rear-ended this summer. Fortunately, it was just the two of us in the car at the time, and neither of us were injured. My head hit the head rest pretty hard, so I'm glad it was there. I can't understand why Nissan doesn't protect the middle seat passenger.

back-seat.jpgCharge Cord

The SV and SL packages include a dual Level 1 (120V)/Level 2 (240V) charge cord. The standard 120V plug comes off to reveal a NEMA 14-50 240V plug.

charge-cord.jpgWith so much public charging available now, there's not much need for Level 2 charging away from home, but the dual mode cord means an owner can upgrade their home charging to 240V by just installing a NEMA 15-40 outlet.

Quiet Ride

When we started the test drive, right away I noticed how quiet it is. I'm told it has the same pedestrian warning sound as the 2011 model, but I couldn't hear it or the inverter whine which are pretty apparent in the 2011. I used to think our LEAF was quiet, but the 2018 is amazingly quiet. There was just the barest hint of a sound at low speeds in the driveway, maybe the pedestrian warning or the electronics, but much quieter. Likewise for road noise at freeway speeds, much quieter than our old LEAF.

One Pedal Driving

One of the best things about the electric driving experience is one pedal driving. It's so natural: push the accelerator pedal to go faster, let up to go slower. With regenerative braking, an EV can be much smoother and natural than a gas car, can slow down on a steep hill without using the brakes, and cruise control can hold you at a steady speed up and down hills. Automakers seem to be afraid of taking full advantage of this feature for fear it will be unfamiliar to gas car drivers, but Nissan has fully embraced it in the new LEAF. In the 2018, I was able to bring the car to a full stop on the steepest part of our driveway. Amazing! At the bottom of our drive, I brought it to a full stop, nudged it forward to look around our mailbox for traffic, then eased onto the road, all using just the accelerator pedal.

Nissan calls this feature ePedal. It can be turned on and off, and can be set to on or off by default. So, gas car drivers can test drive the car without it, then turn it on when they are ready to try driving a car with a superior drivetrain. For most people, once you get used to one-pedal driving, you'll find a gas car feels outdated and you'll never want to go back.

Analog Speedometer

The 2018 LEAF drops the large, easy-to-read digital speedometer for a boring analog speedometer. Jose tells me that Nissan thinks people don't like the digital speedometer, that it doesn't provide feedback on acceleration the way an analog speedometer does. I like the digital speedometer and find that having my back pressed into the seat is all the feedback I need on acceleration.


Nissan did a demo of autoparking at the worldwide announcement, but that feature is only available in Japan, not the United States. Jose gave me the lame company line that US drivers don't use the autoparking feature; maybe we'll get it later. I don't know what the real story is, but that's nonsense.

We got on the freeway and I engaged the ProPilot cruise control feature. As with any cruise control, you get to the speed you want then hit a button. The car will keep you at that speed when it can, but responds to traffic and slows down when there's a slower car in front of you, then speeds back up when the road is clear. It also detects the lane lines on the road and keeps the car centered in the lane. Despite being a nice, sunny afternoon with clearly visible lines on the freeway, the car lost the vision lock a few times and I had to take control. It did slow down when a slower car got in front of us.

It seemed to me like the car was keeping us to the left of center in the lane. Maybe its sensors are better than mine, but I found it a little unnerving when we had a giant semi slowly pass us on the left. I didn't like being so close and took control to put us more center-right in the lane.

When we exited the freeway, I left the ProPilot cruise control on which arguably isn't how it's intended to be used. The exit peels off very gradually for a pretty long, straight stretch. That was working fine, the ProPilot was slowing down to match the car in front of us. As the lane made a gradual curve to the right, the car in front of us was no longer directly ahead, so the LEAF tried to resume full speed. It clearly didn't understand that the lane was curving and that slow car was still in front of us. I disabled the ProPilot at that point.

Maybe it would be cool on a long freeway run, but I found the ProPilot to be too unreliable to really relax and let it drive.

Even when the ProPilot isn't engaged, it watches the road and warns you if you drift in the lane. That happened twice to me, once when I was a little off center and again when the road was curving and I thought I was in the right place.

All-Around Camera

When we got back to the house, I tried out the all-around camera (SL package only). When you pop the LEAF into reverse, the center console screen shows both the backup camera and a simulated overhead view that displays the car's full surroundings. I know the LEAF has had a feature like this available for a few years, but it was super cool to see it in action. It was just like there was a camera over the car looking down to show the car's position in the driveway. It's done with four side camera and math, a very nice effect.

rear-camera.jpgBluetooth Audio

I paired my iPhone 6 up to the car to play some music. That works great, with plenty of volume. The Tesla Model S fails the "enough volume" test when playing Bluetooth from an iPhone. So that was nice.

Premium Bose Sound System

The test drive vehicle was a top-of-the-line SL with all the bells and whistles, including a super-duper Bose sound system which eats up a small slice of the hatch with amplifiers. When I had my iPhone hooked up, I played some Led Zeppelin and found the sound underwhelming. Our Tesla Roadster has a good sound system, with an Alpine headunit we installed. Those Zeppelin tunes sound great there, one of the pleasures of driving the Roadster. Not so much in the LEAF.


Heated Seats

We put in a very early order for our 2011, but then postponed it until they came out with the cold weather package late in the 2011 model year. Heated seats are a big win in an electric vehicle because they are more energy efficient than cabin heating, and the heated steering wheel is a guilty pleasure we love. The 2018 offers heated seats and steering wheel with the all-weather package, but it doesn't heat the rear seats. We use our LEAF in the winter and don't want to leave our rear-seat passengers in the cold. With the bigger battery, using the less efficient cabin heater is less of an issue, but we like offering heated seats to our rear-seat passengers.


Overall, the 2018 is a huge upgrade from our 2011. Not only the increased range from 84 miles to 150 miles (EPA rated range), but amazing one-pedal driving, nicely improved sound insulation and plenty of cool tech available in the higher package levels. Unfortunately, the lack of a fifth headrest makes us less interested in upgrading to a new LEAF.

OVMS and the Tesla Roadster Charge Time Predictor

| No Comments
Updated April 14, 2014 to add section on charging efficiency.

Charging an electric vehicle is pretty easy: just like my cell phone, I plug it in when I get home and it's fully charged in the morning. It doesn't matter how long it takes because I'm not waiting for it to finish; the car just charges up and waits for me.

That's pretty much the whole story for local driving, but I like driving electric so much I prefer to do longer trips electrically rather than burning gas. On those longer trips, it can be helpful to know how long a charge will take. To help figure out charge times in our Roadster, I did a study in 2010 on how charge rates and energy efficiency vary with available power and published a blog with the results. That blog has a table that shows charge rates for various charge rates from 120V/12A up to 240V/70A.

Charge Rate Ideal Miles
per Hour
Current Tapering Begins At:
Std % Std IM Range % Range IM
120V - 12A 3.3
120V - 16A 5.1
240V - 16A 13 93 179 82 205
240V - 24A 20 94 180 82 205
240V - 32A 28 93 178 82 207
240V - 40A 36 93 178 81 204
240V - 48A 42 91 174 80 201
240V - 70A 61 84 161 75 188

That charge rate table is handy, but it has some limitations:

  • It's a pain to load up the web page and do the math.
  • It covers the full range of charging options from the lowest to highest power rates, but it doesn't cover every possible rate, e.g. lots of sites are on 208V circuits instead of 240V.
  • It's specific to our car and the moderate temperatures in our garage.

The situation also gets more complex as the charge gets near the top and the car starts tapering the charge rate to pamper the battery pack, so calculating the charge time to full is more complicated than just looking at the available power. The graph below from the original study shows how the charge rate tapers down from various power levels.

Finally, since the Roadster has an active thermal management system that cools (or heats) the pack to keep the battery temperature in the best range, and that system uses power, the charge rate also depends on temperature, something my original study didn't address at all.

To build a more complete charge time predictor, I'd need to get charge data across a wide range of power levels and ambient temperatures, develop a charge tapering profile to use for calculating time-to-full, and I'd need to do this for each of the Roadster's three charging modes. This would require capturing a giant amount of charge data, which would need to come from Roadsters in different climates since the temperature in our Pacific Northwest garage doesn't vary much.

Open Vehicle Monitoring System

The Open Vehicle Monitoring System (OVMS) is an open source hardware and software project created by Mark Webb-Johnson, based in part on earlier work done by Scott Swazey who created the Tesla Tattler. OVMS consists of a $130 device that plugs into the car to both collect information and send commands. The device can interact with the driver via SMS messages and/or relay through a web server which communicates with smartphone apps. Since initial deployment on the Roadster, OVMS has been expanded to support other vehicles, all through volunteer support from vehicle owners.

Because the device sends data to a server and that data is stored (for a limited time period), there was a vast amount of charge data accumulated ready to be studied. Mark was kind enough to get me an anonymized capture of that data, 179 MB of data from 126 devices. The data is stripped of all identifying information, so I can't tell anything about the car or owner: no location or even VIN number. I can't tell if a given car is an early Roadster 1.5 in southern California, or a late 2.5 in Norway. What I get is records about every 10 minutes while the car is charging that tells me the time, SOC %, ideal miles, charge mode, charge voltage and amperage, various temperature readings, and the odometer.

Analyzing Charge Rates

I was able to extract data on just over 7,000 usable charging sessions. The graph below shows the available kW vs. temperature for each session. If you don't speak Celsius, 0�C is 32�F and 40�C is 104�F. Temperatures that are much above 40�C are probably due to situations where the Roadster ambient temperature sensor is sitting in direct sunlight on a hot day.

You can see clusters around common charge rates. The two lowest groups are at 1.44 kW (120V/12A) and 1.92 kW (120V/16A), and there are big groups around 7 kW (240V/30A) and 9.6 kW (240V/40A).

I wrote code to march through the data, identify records that correspond to each charge session, calculate the charge rate for the portion of each charge where the car is drawing the maximum allowed current for a steady power level, and note where tapering begins. I then sliced the data to see how temperature affects the charge rate at a given charge level. For example, the graph below shows the steady power charge rate (in ideal miles per kWh) vs. the average ambient temperature sensor reading for all of the charge sessions between 6.8 and 7.2 kW.

The data shows a slight downward trend in charge rate with increasing temperature, which is reflected by the downward slope of the best-fit straight line approximation to the data. There is, however, a lot of variation in the data. Other factors (battery temperature, enclosed or open-air charging, battery pack starting temperature, etc.) have more effect on the charge rate than what can be predicted by knowing the average ambient temperature sensor reading during the charge, so the model can't predict differences in charge times from those external factors.

Using this data slicing, I was able to build a model that predicts the steady-state charging rate for power levels from 1.4 to 16.8 kW. The model incorporates a reasonable data set from a little below freezing to 40� C (104� F). Beyond that temperature range, there's isn't a lot of supporting data, so the model doesn't cover cases where battery heating is required or where battery cooling is extreme.

Modeling Charge Tapering

To figure out tapering curves, I looked at the onset of tapering for each charge mode. Below is the graph of the standard mode data showing the ideal miles at which tapering begins by charge rate.

Once again, you can see that there's a pretty clear trend, reflected by the best-fit straight line, but there's also a lot of variation. Part of the variation is because different cars have different capacities in their battery packs. A nominal new pack will charge up to about 192 ideal miles in Standard mode, but a more well-traveled pack might only charge up to 170 ideal miles. Those two packs will taper the charge rate differently. To build the tapering profile, I had to allow for differences in the capacity of the cars in the data set and adjust accordingly.

The Charge Time Predictor

Doing this fairly giant amount of data analysis, I was able to build a charge time predictor function that is now incorporated in both OVMS and the Tesla Tattler. As you can see from the variation in the vehicle charging data, it's impossible to be perfect for every car, but the charge time predictor generally hits the mark within 30 minutes or 10% of the charge time. It doesn't do as well in temperatures below freezing or much above 100�F, or when the car is charging in a small, enclosed garage, or if the ambient temperature sensor doesn't reflect the actual air temperature, etc., but for common conditions, it seems to be doing a pretty good job.

In addition to the general variation in the data, there's another issue that affects charge times. Occasionally, the Roadster will charge up to the expected charge level (ideal miles) in about the time I expect, but then keeps going. For example, our Roadster generally charges to about 180 ideal miles in Standard mode, but sometimes it will hit 180 and just keep going, perhaps taking another 30 or 40 minutes to finish, showing a charge level that's wildly implausible, like over 190 ideal miles. Ten minutes after the charge, when the car recomputes the actual energy in the battery based on post-charging data, the charge level will drop back to the expected level. So these exceptionally long charge sessions don't seem to actually put any extra energy into the pack, despite the end-of-charge reading. I suspect the car is leveling the individual brick charge levels. When this happens and makes the charge run late, if I need to leave, I just interrupt the charge and go.

Good for the Driver, the Car, and the Utility

Having a charge time predictor enables a whole new charging feature: the ability to set the end time for a charge. This is important for two reasons.

First, when I'm doing a full range mode charge prior to a long drive, I'd really like the charge to finish shortly before I'm ready to leave. When charged to full, the Roadster runs the coolant pump to keep the battery temperature cool and equalized, which drains power. I'd rather be driving on those electrons for both the added range and energy efficiency.

Second, it's nice for the utility. Since we first got the Roadster, we've used the built-in charge timer to delay charging until off-peak hours. Our utility doesn't have time-of-use (TOU) rates, so we don't get any financial benefit, but it's still the right thing to do. Unfortunately, this creates a problem as we get more EVs on the road. If everyone sets their car to charge at some even hour, like midnight, that creates a surge for the utility. In areas where TOU rates are in effect, you can see this effect in the data collected by the EV Project. Using the charge time predictor with the new OVMS "charge by" feature, I can set the charge to end around a specific time, so the start time varies with how much energy I use driving each day. Since the actual charge time varies from the predicted time, even the end time varies, so there won't be a big instant spike or drop at either end of the charge for vehicles that set a charge end timer. That's good for the grid.

Charging Efficiency

Although not directly related to charge time prediction, the data set also allows for examining how charge rate effects efficiency. Using the model developed for the charge time predictor, the graph below shows how charging efficiency varies with charge rate. Charging efficiency is expressed as Wh per ideal mile, so smaller numbers are better.

This shows that in moderate temperatures, charging efficiency increases with charge rate. There's a huge improvement between 120V/15A (1.44 kW) and 240V/24A (7.68 kW), but after that there's a much more gradual improvement with increasing charge rates.


The charge time predictor for the Tesla Roadster is available in the latest firmware versions of OVMS and the Tesla Tattler and also on the Tesla Roadster Charge Time Predictor page.

The Hybrid Garage

| No Comments
Electric vehicles are awesome for local driving. Driving within the single-charge range of an electric vehicle is more fun, more convenient, and cheaper than driving a gas car. Many people are drawn to the idea that they can abandon gas stations, fuel at home, drive 130 miles for the cost of a gallon of gas and all in a car that has a quiet ride and instant, smooth acceleration that can't be matched by a gas car.

However, electric cars are not great for driving long distances beyond their single-charge range. Make no mistake, electric road trips can be done. Plenty of EV owners love driving electric so much they are willing to trade off some convenience for the rewards of driving without combustion, but that's a choice. People who haven't previously owned an EV aren't going to sign up for that when they buy their first.

The Plug In Hybrid

The solution to this that first comes to mind for many people is a plug-in hybrid vehicle. The Chevy Volt is an electric vehicle that has a gas engine that can be used to extend the range of the car, both by augmenting the electric motor and charging the battery. Especially for single car households, the Volt can be an excellent solution: drive electric for your daily commute and burn gas for longer trips. The trade off is that the Volt is more expensive than an all-electric Nissan Leaf, has less than half the electric range, and still needs regular maintenance like oil changes.

No Car Does Everything Well

The issue of a diversity of demands from a single vehicle is not a problem that's unique to electric cars. No car is great for every purpose. You can't carry more than two people or tow a boat with a Miata. A 15 mpg pickup truck is pretty silly as a single-occupant urban commuter vehicle.

Households that own more than one vehicle have the opportunity to own different types of vehicles which excel at different tasks. A household might own a small, economical sedan for daily driving and a more rugged vehicle for excursions into the wilderness.

The Hybrid Garage

Some 60% of Americans have a garage and multiple cars and 78% drive less than 40 miles per day. The tens of millions of American, and many more worldwide, who are in both groups are perfect candidates for what I call the "hybrid garage."

The hybrid garage is replacing one of your gas cars with an all-electric car, keeping a gas car that's good for the things the EV doesn't do well. There are several potential advantages to the hybrid garage over owning a plug-in hybrid car: you get more electric range for the car's purchase price, you don't have to do oil changes on the electric car, and you don't have to worry about gas going bad because it just sits in the tank for months.

Even a single-car household can adopt the hybrid garage approach. Depending on how often a longer-range vehicle is needed, renting a car occasionally may be a lot cheaper than owning a second car. Swapping cars with a friend or relative can take care of the occasional road trip, and allow someone else to see first hand how convenient driving electric is.

Who Gets to Drive the EV?

There is a downside to the hybrid garage: once you have an electric car in the garage and people find out how nice it is to drive electric, everyone will want to drive that car. Fortunately there's an easy solution that Cathy and I developed after we bought our first electric car: whoever is driving farther gets the electric car. This also turns out to be the cure for range anxiety. When you realize how much of your driving can be done with a car that has a "limited range" you'll stop worrying about running out of juice and wonder how it is that we got so used to tolerating the inconvenience of driving on gasoline.

Quiet Vehicles and Pedestrians

| No Comments
I've been driving electric vehicles since 2008, logging over 50,000 miles, and have never had an experience where my vehicle's lack of engine noise created an unsafe situation. However, the issue of quiet vehicles and pedestrians is subtle and complex.

I have had a pedestrian walk backwards through the traffic lane in a parking lot while carrying on a conversation with someone across the lot. She didn't notice my vehicle, but I was watching where I was driving and going slow enough to react to her carelessness. I just stopped and waited about 30 seconds for her to see me. She of course made a rude comment blaming me for the unsafe situation she caused.

I've also had many times when driving through a parking garage where pedestrians are walking up the middle of the traffic lane, totally oblivious to my presence. However I find that happens with about the same frequency it did when I was driving gas cars, which I attribute to the echoing in concrete garages making it hard to hear slow-moving vehicles from behind, even when they are close.

I've also had the experience of being in a shopping center parking lot, hearing a car drive up behind me, and before turning around knowing it was my wife, Cathy, because I recognized the distinctive sound of a Tesla Roadster. On the flip side, Cathy has noticed not being able to hear a nearby gas car in a parking lot because of the noise made by a much louder gas car an aisle or two over.

As a responsible driver, I don't depend on pedestrians hearing the roar of my engine so they can scramble out of my way before I mow them over. But the situation is more complex than just my personal experience.

In May of 2011, I participated in a meeting of the United Nations working group that is developing a proposal for an international standard for quiet vehicles. There I learned a great deal about the subject and was able to share my insights as an experienced electric vehicle driver.

The predominant sound made by cars moving above 15 to 20 miles per hour is tire noise. At slower speeds, it's engine idling, fans, and so forth. It's those lower speeds that are of concern.

Hybrid and electric vehicles aren't the only quiet vehicles on the road. Many modern sedans are also virtually silent at low speeds where tire noise is not significant. Therefore, the UN is taking a broader approach to this problem than the US Pedestrian Safety Enhancement Act of 2010, which only considers minimum noise levels for electric and hybrid vehicles.

The sound made by gas cars is actually quite poor for alerting pedestrians to nearby vehicle traffic. Most of the sound made by internal combustion vehicles is low-frequency, which humans have difficulty locating, and carries for long distances, adding to ambient noise levels that can mask out nearby vehicles.

For an artificial car sound to be effective, it has to be localizable and distinguishable as coming from a vehicle. So having an EV rumble like a muscle car or chirp like a bird is a terrible idea. Studies presented at the UN workgroup meeting show that the best sounds are broad spectrum sounds without low frequency content.

The issue is even more complex for blind pedestrians who develop skills in using their senses in ways that are completely outside the experience of the sighted public. The idling sounds made by stationary vehicles are useful not only for detecting the presence of nearby cars, but also for using them as positional markers. Consider walking across a wide, busy street and trying to stay in the crosswalk with your eyes closed. The sound of the idling cars nearest the crosswalk act as navigational beacons, keeping blind pedestrians from drifting out of the crosswalk and into traffic. For this reason, it's important to be able to hear a car in the street even if it is not moving.

It's also important to be able to judge the size of vehicles by their sound. Drivers behind a large, stopped vehicle can get impatient at the hold-up and decide to blast around the unwanted obstruction, only to find that there was a good reason for the large vehicle to be stopped: pedestrians in a crosswalk. For this reason, blind pedestrians may choose to avoid this risk by choosing not to cross when they hear a large vehicle at the head of the line.

As an EV driver, I appreciate the quiet ride of electric cars. The last thing I want is some obnoxious artificial sound added to my car. From what I learned at the working group meeting, a properly designed sound doesn't have to be overly loud, it can be effective even at a sound level that is below the ambient noise level. I believe we can add sound to quiet cars to increase pedestrian safety without compromising the advantage of electric cars in improved driving experience and reduced noise pollution, but doing so demands careful thought and consideration of many complex issues.

Quick Chargers: Ignore The Charge Percent!

| No Comments
Electric vehicle drivers are excited to see the first DC Quick Charge stations coming online. Oregon and Washington have done their part to power up the West Coast Electric Highway allowing electric vehicle drivers to travel I-5 from the Canadian border to the Oregon-California border and take advantage of stations that can charge a Nissan LEAF or Mitsubishi iMiEV from empty to 80% in about half an hour. This greatly increases the usable range of electric vehicles for longer trips and also provides a safety net for rare situations when drivers unexpectedly need more than their normal overnight charge.

Unfortunately, there's a problem that is causing a lot of confusion that can result in a driver getting less charge than needed. Even though the stations are working properly, drivers may think something went wrong because of a user interface issue.

AV-DCQC-Screen.pngThe above is the screen from an AeroVironment DC Quick Charge station in Tumwater, WA, as shown while charging our Nissan LEAF in June. The screen shows the driver two pieces of information: the amount of energy delivered to the car and a charge percent.

The problem is the displayed charge percent: it is not the car's state of charge (SOC) and should not be treated as such by a driver to decide when to end the charge.

It's pretty well known that it's difficult to determine the exact SOC of a car's battery. Even the best estimate of the battery's SOC may be off by a few percent. That's not what's going on here. The SOC value reported to the station is completely artificial and differs significantly from the car's estimate of the true SOC.

In addition to showing the invalid SOC value to the driver, Blink quick charge stations also require the user to choose a station-controlled charge limit. This has two big problems. First, the LEAF wants to control the charge and will stop the charge at either 80% or near 100% based on the battery state at the start of the charge, so even if you choose 100% on the station the LEAF will terminate the charge at 80% if the car was at 50% or less when the charge started. Second, the Blink station doesn't know the real state of charge and therefore cannot know when to stop charging at the point it says it will.

Here's an example. I recently used the Blink quick charge station at Harvard Market in Seattle, WA. I arrived with just over a half charge remaining, which means the LEAF will allow me to do a full quick charge up to near full capacity. After plugging in the car, the screen on the Blink station gave me a choice of charge levels, defaulting to 80%, which was the highest level shown. I had to press a "more options" button to be able to choose a 100% charge. The graph below shows data collected from the resulting 52-minute charge, comparing the car's actual SOC with the SOC shown on the station's screen.

Blink_50_to_100_Graph.pngAs you can see, not only is the reported SOC higher than the actual SOC, the reported SOC rises more quickly, increasing the gap as the charge progresses. Throughout the entire charge, the SOC shown on the station consistently overstates the actual charge level and the problem gets worse later in the charge period. As the car gets to about 80% actual SOC, the reported SOC jumps up to plateau near 100% and just sits there for the remainder of the charge, even though the car is far from fully charged.

Had I left the default 80% setting, the charge would have stopped when the reported SOC hit 80%, but the car was really only at 73% at that time. A requested 90% charge would have stopped around 80% actual.

Any driver who sees this behavior and doesn't know that the charge percent value on the station is not the SOC would see it jump up to 97%, perhaps watch it sit there for a few minutes, and likely decide that it would be a waste of time to spend any longer waiting for that last 3%. If the driver ends the charge at that point, the car will be missing perhaps 10% of the potential charge. If that last 10% is needed to finish the journey, this could result in a very unhappy EV driver.

It's not clear where this value comes from, but displaying this invalid SOC on the quick charge stations has created user interface problem with unfortunate consequences for LEAF owners, and perhaps iMiEV owners as well.

So to any EV driver using a CHAdeMO quick charge station that shows an SOC percentage:

1. Ignore what the station shows. Put a sticky over it if you have to. Only look at the car's representation of the SOC.

2. If the station offers you different charge levels, choose 100% charge so that you get the car's best available charge level. If you want to stop the charge early for some reason, do it based on the SOC shown by the car.

I'll contact the quick charge station manufacturers to make sure they are aware of this problem. In the meantime, please help spread the word so EV drivers can get the maximum benefit from these highly valued stations.

For charts of two AeroVironment quick charge sessions, see Cathy Saxton's report. More tips for using quick charge stations are available on our Avoiding Quick Charging Pitfalls page.

US 2 DCQC Inaugural EV Rally

| No Comments

On Saturday, June 16, 2012, a dozen electric vehicles made the inaugural drive along US Highway 2 over the 4,061-foot summit at Stevens Pass utilizing the newly-installed quick charge stations. Most of these vehicles recorded data for driving and charging; this blog is a summary and analysis of that data.

Cars charging at the DCQC and Level 2 stations in Skykomish, WA.


We have analyzed this data as well as measurements from other driving and have created pages with information on planning an EV road trip, including guidelines for predicting energy use based on drive conditions and tips for avoiding quick charging pitfalls.

Thanks to Ron Johnston-Rodriguez for all his work getting electric vehicle charging stations installed along US 2 and organizing this event.


This event marked the official opening of DC quick charge (DCQC) stations in Sultan, Skykomish, Leavenworth, and Wenatchee, WA. It was also a test of the spacing between stations. Tom had helped with the US 2 electrification process by collecting data for driving this route in our Tesla Roadster in December, 2010, so we had good information on the energy use required for each segment.

With a carefully-orchestrated schedule from Ron, each vehicle was assigned a charging period at each station. This added a unique constraint, as vehicles would not necessarily have sufficient time for a full charge at the DCQC stations. We provided suggestions for a target charge level when departing each location and the expected energy required to comfortably reach the next station. The most demanding segment was the one over Stevens Pass; our guidance included a recommended state-of-charge level at the summit so drivers would know whether they should stop for Level 2 charging at Stevens Pass ski resort.

We got nifty SWAG from Leavenworth and Wenatchee!



We have data from 8 Nissan LEAFs, 1 Mitsubishi iMiEV, and 1 Tesla Roadster.

The DCQC spacing worked great for the LEAFs.

The iMiEV was able to make the drive with additional charging for the segment over the pass (charging Level 2 at Stevens Pass in both directions and Level 1 at Nason Creek for the westbound trip).

The Roadster can't use DCQC stations, but with its longer range didn't need much extra energy use. Tom was able to "opportunity charge" at Level 2 while we charged our LEAF and participated in the ribbon-cutting ceremonies.


For those interested in all the gory details, the data and analysis are in this spreadsheet (XLS, 214k).

Drivers recorded information on time, distance, energy, temperature, and driving conditions. The details are in the individual EV# sheets. There are summary sheets for driving and charging that compare the data for multiple vehicles.

The iMiEV (EV1 in the spreadsheet) used an amount of energy similar to the LEAFs.

There were three LEAFs with after-market state-of-charge (SOC) meters that enable more precise monitoring of battery state than the factory instrumentation. These meters show the SOC as a percentage, and also in a unit called a "gid," which represents 80 Wh of energy in the battery. The gid values fell nicely in the range of values based on the LEAF's more coarse SOC bars.

We drove our LEAF (EV4) and Roadster (EV4b) together so that we could compare energy use for the same driving conditions. They turned out to be very similar; there is a summary sheet showing the data for both cars together.

Thanks to everyone who collected and shared data: Patrick, Phil, Lee, Jeff & Mary Lynne, Matt & Laura, Bruce, George, and Mike & Kimm.

EV drivers at the US2 DCQC inaugural ceremony in Wenatchee, WA.


Photo by Jessie Lin, WSDOT. Used by permission.

Quick Charging

DCQC stations made it practical to make this trip (and the return) in a single day. We learned several things about the stations with all the data collected by drivers during this event.

One of the most enlightening was confirmation of an observation during our prior DCQC experience: the station-reported SOC is not a useful indication of the car's charge.

When using a DCQC from under 50% to get to 80%, the LEAF's charge rate averaged 400-500 Wh/minute. When charging from over 50% to "full," the charge rate averaged about 200 Wh/minute.

The charging overhead (energy from the station that didn't make it into the battery) was 10-18%.

More details on DCQC are on our page with tips for avoiding quick charging pitfalls.


For each drive segment, these are the minimum and maximum kWh (and corresponding gids and bars) used between the DCQC stations. The energy use will vary based on speed and weather conditions.

Trip miles kWh gids bars
Sultan to Skykomish 26.4 7.20 - 8.24 90 - 103 4.5 - 5.2
Skykomish to Leavenworth 51.0 12.24 - 14.88 153 - 186 7.7 - 9.3
Leavenworth to Wenatchee 20.5 2.40 - 2.48 30 - 31 1.5 - 1.6
Wenatchee to Leavenworth 22.3 5.60 - 5.84 70 - 73 3.5 - 3.7
Leavenworth to Skykomish 51.0 12.48 - 13.60 156 - 170 7.8 - 8.5
Skykomish to Sultan 26.5 4.80 - 7.04 60 - 88 3.0 - 4.4


The spacing of the DCQC stations along US 2 over Stevens Pass works well for LEAF drivers. Level 2 charging at the pass is either helpful or mandatory for iMiEV drivers, depending on the driving conditions.

We believe that an SOC meter is a valuable tool when making a trip like this, especially when pushing the range limits of the car. Because we'd projected our energy use for each segment and had a meter providing a higher resolution SOC reading, we were able to minimize the amount of time that we spent charging — including successfully skipping one station — and return home with a comfortable buffer.

1,823-Mile Oregon Coast Tesla Road Trip

| No Comments

roadtrip-route-thin.jpgCathy and I took an 1,823-mile electric vehicle road trip to attend the Plug In America board meeting in Berkeley, CA, on June 23rd, 2012. Ever since we took delivery of our Tesla Roadster in June of 2009, I've wanted to take it on a long road trip just to have the experience. Over the past three years, the challenge of making the drive from Seattle to California has been greatly reduced. When Rich Kaethler took delivery of his Roadster in San Carlos, CA, and drove it back to Seattle in August of 2009, and Chad Schwitters made his long trek from Seattle to San Diego and back in April of 2010, these were pioneering efforts. Now we have full speed (240V/70A) Tesla charging along I-5 from British Columbia to southern California, which makes it possible to do the Seattle-to-San Francisco drive electrically in just a couple of days.

However, Cathy and I wanted to take a more leisurely approach and add some new territory to the EV road trip experience, so we made our way down the Oregon and California coast on highway 101, eschewing the more convenient charging established on I-5. Here's what we did, what we learned, and a few adventures we had along the way.

Our Tesla Roadster has a range of about 240 miles at 55 to 60 mph on level freeway in moderate weather. In practical terms, that means we can generally drive 180 to 200 miles without any need to charge in the middle. About four hours of driving per day is our threshold for convenient travel and leaves plenty of time to enjoy a leisurely drive and see the sights, which works well with the Roadster's single charge range.

The coastal drive is a bit of a challenge because there is almost no installed public charging infrastructure. Fortunately, all we need is a power source, and one of the best sources for power is the 240V/50A service commonly available at RV parks. Finding charging is actually pretty easy; the challenge is finding a place to charge and a place to sleep nearby. Cathy did careful planning in advance, finding hotels and motels that either provided charging or were adjacent to EV-friendly RV parks.

Day 1 Because we had a four-hour delay from our intended start time, we cheated and took the easy route south down I-5 toward Portland, taking advantage of 70A charging while eating lunch at Burgerville in Centralia. That gave us enough juice to remove any chance of range concern for our 237-mile drive.

For our first night, Cathy found what turned out to be a wonderful location, the Harborview Inn and RV Park in Garibaldi, OR. The Inn is a modest little motel, but it and the RV park are right on the harbor, which was hard to appreciate when we arrived shortly after sunset, but treated us to a beautiful view as fog was lifting from the harbor when we woke up in the morning.

The restaurant options in Garibaldi were pretty limited, so we got dinner in Seaside on the way, then ate breakfast in a dodgy little place in Bay City.

Day 2 We made a couple of stops in Lincoln City where there are two locations with two ChargePoint charging stations each. We didn't find much to do near either location, and we didn't really need to charge, so we took off after a quick bit of exploring. 

Cathy found some information online about the many wonderful historic bridges along the Oregon coast, so we made that our theme for the drive. One of our favorites was Cape Creek Bridge.

That night we charged at Charleston Marina RV Park in Charleston, OR. It cost us $23 to use an RV spot to charge overnight, but the folks were very nice and the manager expressed interest in installing EV charging stations. It was fortunate that we had a suite with a full kitchen at Charleston Harbor Inn, because there was very little in the way of restaurants open at the late hour of 5 pm on a Tuesday night. We bought some food at the local convenience store and made dinner.

Day 3 We took in the last of the Oregon coast historic bridges then crossed over into California with a quick stop at the Redwood National Park visitor information center in Crescent City. We stopped for a walk in the forest and a drive up to an overlook of the mouth of the Klamath River to watch gray whales feeding. Late that afternoon, we rolled into the Chinook RV Resort in Klamath, CA. They had all brand new 50A service in nice pretty enclosures that have a bar running right below the outlet, which prevented us from plugging in. The very helpful handyman was able to "modify" the enclosure on spot #2 so that we could plug in.

Restaurant options in Klamath are very limited. One place had a big sign out front that said "Now Open" which, as we found out, isn't the same as "Open Now"; they seem to only be open from 11:00 am to 2:00 pm for "breakfast." Another place had people loitering out front and a sign that said "armed guard on duty." That didn't sound very inviting! Again, we had a suite with a kitchen at the RV park, but we didn't have groceries and the only store open in town is a gas station convenience store. We ate at Steelhead Lodge, which is not even a little bit vegetarian friendly. Cathy asked for a baked potato with cheese and was told "we don't have cheese." Definitely, another good place to make dinner in the suite; be sure to do your shopping in Crescent City.

Day 4 Was our most fun driving day, taking the Avenue of the Giants, a portion of the old Highway 101 running parallel to 101, to drive through the Redwoods. Driving a quiet electric car on a road surrounded by the forest canopy was one of my top 2 all time Roadster drives. We also had probably our best meal of the trip, lunch at the wonderful vegetarian Wildflower Cafe and Bakery in Arcata, CA.

We spent the night at the historic Benbow Inn in Garberville, CA. They feature biscuits and tea in the afternoon, an elegant dining room serving a seasonal menu, a rich event calendar (an outdoor jazz concert the night we were there), and free EV charging via a 50A outlet. There's also an associated RV park, which we planned to use until we learned about the hotel charging option. It was the priciest hotel we stayed at, but we just couldn't resist trying out a previously unknown EV-friendly hotel.

Day 5 We needed to drive 213 miles. Just to be safe, we stopped at what turned out to be two SemaCharge stations at Coddingtown Mall in Santa Rosa, CA. Although we'd heard reports that SemaCharge stations don't work with 2010 and later (v2.x) Tesla Roadsters, we were quite pleasantly surprised to find the one we tried worked flawlessly with our 2008 (v1.5) Roadster.

For our hotel in the Bay area, we chose the Four Points Sheraton in Emeryville because it was the closest EV-charging hotel to the Plug In America board meeting in Berkeley. (How can Berkeley not have a ton of public charging? What's up with that?)

Unfortunately, we weren't the only ones to figure out that this is the only charging station near Berkeley as we were unable to use the level 2 ChargePoint station until over 12 hours after our arrival. When we arrived, there was a Volt charging. While we were out for dinner, a Leaf pulled in and started charging from near empty. I happened to wake up way too early and could see the Leaf had finished, so I dashed down to start charging at 5:25 am. I didn't want to leave our very expensive adapter cable out all day, so I took a chance and unplugged when I left to take the bus to the board meeting. Fortunately, I was able to plug back in that evening, finish the charge that night, and top off again in the morning. When we left, a plug-in Prius was using the Level 1 station. When we got home, I checked the data from my Plug In America charging infrastructure study and found that station is one of the most-used ChargePoint stations in the country, averaging 11 hours of use per day.

Neither the Leaf nor the Volt were driven by hotel guests, and the hotel staff was completely unconcerned that a guest was blocked from charging for over 12 hours. "Those stations are there for the public to use." That's all good, but we chose the hotel because of the charging station. Because of the high use rate, and no preference given to guests, I can't recommend this hotel for a single night stay where charging an EV is required.

Day 6 I attended the board meeting. Cathy visited the California Academy of Sciences at Golden Gate Park and had a quite an adventure with the bay area bus systems, but that could be a blog all on its own.

Day 7 There are a series of Tesla charging stations along I-5 making it possible to drive from the Bay Area to Seattle in two days. We wanted a more leisurely experience, so didn't need use any of them until we were almost home. Our first overnight was in Red Bluff, CA. We stayed at a Super 8 motel and charged across the street at the Rivers Edge RV Resort where we had another adventure. They claimed to have three 50A outlets, but we had to scrounge through the park to find them. We tried five that didn't have power until we finally found success with the sixth. The manager and the park handyman were very supportive and helpful. We ate a tasty late lunch at the New Thai House; the Yelp reviews weren't kidding that the food is spicy. We also took in a movie at the local cinema.

Day 8 In Red Bluff, the Tremont Cafe and Creamery is a decent place for breakfast, although we enjoyed the historical notes on the menu more than the missing-in-action service.

Although we only needed to drive 176 miles to Ashland, OR, we had to climb over the Siskiyous Mountains which means climbing to 4,000 feet, dropping back down to 2,000 then up again to 4,000. We could have done it on a single charge, but decided to try out a charging site in Redding, CA, while taking a walk through the adjacent Lema Ranch Trails.

The Blink charging station was only delivering 187V (normally it's around either 208V or 240V), so we were only charging at about 75% of the rate we expected. This was fine for what we needed, but not so good if you're counting on a more typical Level 2 charging rate.

Historical note: while crossing the Siskiyous, we saw Tony Williams' Nissan Leaf speed by southbound, making the return trip from his BC2BC tour.

We arrived at the Chanticleer Inn in Ashland, OR, with plenty of charge remaining (25%) despite the serious elevation climbs along the way. Although there is a Level 2 station in Ashland, we arranged with Ellen at the B&B to charge from a 120V outlet. Since we were going to be there for 2 days, that was enough to get us charged (28.5 hours).

Day 9 We were in town to watch three shows at the Oregon Shakespeare Festival, so we spent a second night in Ashland and had a great time. Ellen was very accommodating, both of our charging needs and our vegetarian diet. She even invited a friend over to see the Roadster which turned into an impromptu car show for our breakfast mates from the inn. It was a much more pleasant stay than at the hotel with the oversubscribed Level 2 charging station.

Day 10 We had a full charge and only a 60-mile drive, so we got to enjoy full-blast air conditioning on a hot day, driving up and down a couple of mountain passes in the left lane not sparing the accelerator pedal at all. I tried to show some restraint, but I have to admit it was more fun for me behind the wheel than for Cathy in the passenger seat.

We charged at the Level 2 AeroVironment station next to the DC Fast Charger while spending the night at the historic Wolf Creek Inn.

Day 11 Nearing the home stretch, we detoured to Corvallis, OR, to visit a friend from the EV community who generously allowed us to charge in his garage while we went out for lunch and had a wide ranging chat about EVs, wacky diets, and lots more.

In Portland, we met up with John Wayland and had dinner with John and his daughter Marissa at our favorite neighborhood Thai place in Portland, Thanh Thao. Sadly, the wonderful Jaciva's chocolate shop and dessert bakery had closed too early for us to visit.

We had another adventure in charging at the Downtown Crowne Plaza. They have two Blink stations, which we've used before without issue. That night, we started a charge at 10:27 pm and hit the sack. At 11:58, my cell phone woke us up with an alert that the charge session had ended abnormally. Concerned that someone might be messing with the car or the adapter cable, I dashed out to check. Nothing was disturbed, but something had terminated the charge session. I can't say for sure whether the Blink station burped, or someone messed with the locking switch on the Tesla connector (and put it back), but I was very pleased that I had an OVMS box (similar to the Tesla Tattler) installed and set to text me if a charge is interrupted. Without that notice, we would have found a partially charged car in the morning and then had to wait five hours before we could depart.

Day 12 We made our usual 30-minute stop at Burgerville in Centralia, WA, for a quick bit of charge and a meal. We totally dig Burgerville for their healthy fare, including vegetarian options, environmental consciousness, and especially for the Tesla charging station they have provided since 2010. From there, it was an easy drive home.

Planning a Road Trip Using DC Quick Charging

| No Comments

Hi, this is Cathy; I'm guest-blogging on Tom's page, and he's playing editor this time!

We recently needed to drive approximately 80 miles (one way) to get to clearer skies for viewing the Venus transit. That provided a great opportunity to try out DC quick charging (DCQC) with our LEAF.

We charged up to full in Bellevue using Level 2 charging, drove to the Tumwater DCQC station, charged back to full while we watched the transit, and returned home to Sammamish.

Data Collection

We have one of Gary Gidding's SOC Meters. It shows a state-of-charge (SOC) percent, which it calculates from a raw energy unit reported on the car's CAN bus. The meter can be set to show the raw energy unit, which the LEAF community has dubbed a "gid." It is reasonably well established that a gid represents 80 watt-hours (Wh). Gids are divided by 281 to approximate an SOC %.

Note that the pack kWh is not something that can be directly measured. The car determines this value through sophisticated measurements and calculations, which result in periodic adjustments that are seen as "jumps" in the gids.


We arrived in Tumwater with 2 bars, or more precisely 61 gids, which translates to 4.88 kWh, or 21.7%.

Since we were under 50%, our (first) DC quick charge brought us to 80%. The car charged for approximately 26:40 minutes, at which point it was showing 226 gids (18.08 kWh, 80.4%). The station reported having provided 14.36 kWh, and the car showed a net gain of 13.20 kWh.

The graph below shows the status each minute during charging. The lower blue bar shows the energy in the car's pack at the beginning of the time interval. The upper red bar shows how much energy was supplied by the station during the time interval. You can see that the total energy (existing + added) closely matches the pack kWh at the beginning of the next time period. (We only logged the station-reported kWh for some of this charge session.)

The SOC % axis is scaled to correspond to kWh values (both graphs).


It is interesting to note that the SOC % reported by the station (gold dots) does not match the SOC % of the car. We are not sure what causes this discrepancy, but we've seen this consistently in subsequent DCQC sessions.

We expected to need more than 80% charge to make it home, and we wanted to see how to handle getting a full charge after arriving at a station under 50%. So, after the first charging session stopped at the expected 80%, we unplugged and returned the connector to the station. Then we initiated another charging session.

Our second DCQC charge took 36:35 minutes, increasing the car's charge to 266 gids (21.28 kWh, 94.7%). The station supplied 3.609 kWh and the car's charge increased by 3.2 kWh.


At the end of the second charge, the battery temperature was registering 6 bars. Ambient temperature was 61° F.



We have monitored gids and miles driven over several recent drives. For freeway and combined freeway / surface-street driving we see typical energy use in the range of 250 to 280 Wh/mi, with extreme readings as low as 230 or as high as 290.

The image on the left is after we had driven 74 miles from Tumwater to Issaquah. Stopping for dinner won out over completing the drive home and growing more trees.

Data from our drives to and from Tumwater:

milesWh / miNotes
65.9 251 Bellevue - Tumwater
79.1 235 Tumwater - Sammamish, slow freeway traffic for several miles

Details on a few legs of the trip from Bellevue to Tumwater.

milesWh / miNotes
23.6 247 Freeway, uneven speeds (traffic, merges, etc), partially rainy
15.7 255 Cruise at 60
7.1 259 Cruise at 60

Gids in Relation to Bars


The bars are based on an approximation of the percentage of the maximum available energy. This maximum varies with temperature as well as with battery age as capacity is reduced.

Therefore, there is not a static gid-to-bar mapping; it will vary based on current conditions. The image on the right shows gid readings that we observed as bars dropped during driving. It also shows a simple approximation of the gid values at the bar transition points. Since the gid values tend to vary a little anyway, those values should be an easy way to get a pretty close approximation to the actual kWh (gids × 0.08) remaining in the pack. (The gid range will be between approximately 20 × bars + 20 and 20 × bars + 40.)

Don't forget that there is some amount at the bottom (2%?) that is unavailable; the car will shut down before letting you deplete the battery that far.

When we got to approximately 50 gids, the LEAF warned us of low charge with the following:

  • Warning message ("Battery level is low") on the dot matrix liquid crystal display just above the steering wheel.
  • Illumination of the low battery charge warning light (the icon showing a pump with a plug).
  • Flashing driving range (affectionately known in the LEAF community as the Guess-O-Meter).

We arrived home with 35 gids remaining and did not see the turtle.

News Flash: Electric Cars Like to Be Plugged In

| No Comments
Today's big news flash is that if you leave a Tesla Roadster sitting for a long time without being plugged in, it can ruin the battery.

In other news, if you never change the oil in a Ferrari and drive it until the engine seizes, you're out of luck on warranty and insurance coverage.

To put this issue in context...

In January of 2010, we were away from home and left our Roadster sitting for 26 days. Before we left, I put the Roadster in Storage Mode and plugged it in. Storage mode tells the car to charge only when needed to keep the battery at the ideal, safe charge level to best preserve battery longevity, something like 20% of capacity.

While we were gone, the temperatures dropped down into the 20's. (We were glad to be in Hawaii.) I'm sure our garage stayed above freezing due to waste heat from the furnace keeping the house at minimum temp.

The Roadster battery pack was at 68% when we left and at 55% when we returned. That's a nice even 0.5% loss per day. The logs showed that the car never charged. This was confirmed by our wall meter not moving (less than 0.1 kWh). Since it never charged, I could have left it unplugged and it would have made no difference.

This means I could drive the Roadster 100 miles to the airport, running the charge down to 50%, and leave it sitting for nearly 80 days and still be above 10%. Obviously, if I wanted to leave the car parked at the airport for over two months, I'd park it in a pay lot that would let me plug it into power, even a normal 120V outlet, to keep it charged while I was away. But even if they messed up, the car would be fine in this case (assuming moderate weather).

In a hot environment, where the car might need to actively cool the battery pack, being plugged in is more of a concern.

In normal situations, this is a total non-issue. Even in extreme weather, or if the car is driven to a low state of charge, or left in storage for months, the owner just needs to follow the directions and plug it in. Pro tip: before leaving, make sure the car can charge to verify the cord, the outlet and the car are all happy with the situation.

It's not difficult to plug in an electric car. The photo above shows us charging from a 120V outlet at a yurt 40 miles from the nearest gas station. If we can find out an outlet there, you'll be able to find an outlet if you ever need to leave your electric parked for several weeks.

Gas cars have similar vulnerabilities, they are just more familiar. Never change your oil: kill your engine. Fill your radiator with water: break your engine block when it freezes. Drive over a rock, puncture your oil pan: kill your engine. Pay someone to change your oil and not tighten the plug: kill your engine. Have a neighborhood prankster dump something in your gas tank: kill your engine. Never service your transmission: buy a new transmission.

Electric cars have a lot less that can go wrong, it's just not the same things that will kill a gas car.

Leaf SOC-Meter Build Party

| No Comments
Nissan did a great job with the Leaf, but I do have one gripe: the lack of a state-of-charge meter with enough precision that you can understand how much energy you use and how driving conditions affect efficiency. Having a good SOC meter allows drivers to comfortably use more of the car's range.

Fortunately, there's a strong Leaf community with a lot of smart owners. Generous owners have spent probably thousands of hours decoding the messages available through the Leaf's on board diagnostics (ODB) port, creating software to interpret those messages, and designing hardware to view and log this information conveniently.

About a month ago, I realized my efforts to build a gizmo and contribute to the community effort were stalled while I worked on other projects, so I suggested we buy one of GaryGid's SOC-Meter kits. As long as we were doing it, I thought it would be fun to invite other owners in the area to do a group order.

Cathy liked the idea and organized the purchase and a build party. We got enough interest to order 10 kits, which arrived in time for Cathy to build our meter in advance so she understood the assembly and could help everyone with the build. In addition, she updated the build manual and added photos.

We arranged to meet at a local Maker space, StudentRND, in Bellevue. It's a great shop, with lots of room to work and cool tools like a laser cutter. If you're in the area, we recommend checking them out.

We met on Saturday. Despite the inclement weather (we had to shovel two inches of mostly ice from our steep 500-foot drive to get our Leaf on the road), we had a good turnout. Here's a photo Cathy took early in the process:

A little later, there was more going on as people made progress on their kits. I'm in the back of the photo, working on my iPhone program for logging EV data.

The only barrier to getting the assembly done in a couple of hours is letting the silicone adhesive cure for an hour in the middle of the process. Still, we had a couple of folks finish and test their meters during the meeting. Cathy is putting the finishing touches on an update to the assembly manual with some insights she learned from the party.

The final product is pictured below, including labels that Cathy added to the kits for our build group.

We now have our meter fully installed in the car. It's awesome.