Skip to main content

Big ride to the causeway

Yesterday I finally got a chance to do a "proper" bike trip on my e-bike.  And I finally got to establish a good, new baseline for my battery pack.

Name: causeway trip
Trip time: 02:05:50
TripDistance: 34.1 mi
Average speed: 16.3 mi/h
Maximum speed: 35 mi/h
Climbed altitude: 1432 ft

The trip started out with a familiar jaunt through the network of South Burlington rec. trails.  From there I rode up to the UVM campus, out to Main St. and hit downtown.  For fun and people watching, I walked my bike up Church St.  Although I probably looked a little odd (perhaps like a Burlington bike cop) I am constantly amazed at the ability to bring something like an e-bike right into the middle of a pedestrian mall, walk through it, hop on on the other side, and continue on. Try to do that with a car, motorcycle, scooter or even a moped!   

Rode down to the waterfront to get a quick look at the water level.  Definitely getting up there.  Breakwaters  (restaurant/bar) is flooded, and there are extra ramps around the boat loading areas at the boathouse.  I remembered that they had done a big overhaul on the Colchester Causeway (which had been beaten to a pulp during Irene after being brutalized by flooding of spring 2011).  I decided I wanted to get a look at it before it was wrecked again (ha).  I took the bike path up.  It was kind of fun, but a little annoying as I felt like I was in a bit of a hurry.  I am always very respectful of pedestrians and regular ped-power bikes (don't want to ruin it for everybody) so there was a lot of braking and excusing.  

The work they did on the causeway is phenomenal.  Not only is it perfectly smooth and flat (not a single pothole along the whole thing), but they also managed to widen it quite a bit.  No more almost wiping out oncoming traffic or when passing people.  There were many places where I was able to hold it almost wide open (25-30 mph) for great distances.  Of course as soon as I saw anyone I would slow it way down.  The last thing we need is someone getting hurt or even nervous, as that will be the end of "the Wild West" for e-bikes around here.  I'm sure it's only a matter of time anyway (as e-bike prices come down, more idiots will own them).

I was keeping an eye on my battery pack min. voltage (essentially estimating when the battery would die by observing how much voltage sag vs. throttle/load there was).   The pack seemed very strong all the way there. After I rode as far as I dared (which might have been a little too far), I turned around and started the long haul back to Shelburne.  I was easily 14-15 miles away.   This time I took main roads all the way home.  North Avenue was a real treat as there was very little traffic, and I was able to roll full speed (while being as gentle as I could on the battery), and not have to stop for traffic lights or turning cars.  In about 20 minutes, I had made it all the way back to Shelburne Rd, when, without any warning, the pack cut out.  Just "plink" (no sound effect), no power, followed by the foreboding thought of having to pedal 80 lbs of bike 4 miles home. It really wasn't so bad though.  I needed the work out anyway (whoever thought that owning an electric bike meant you get no exercise is sorely mistaken).  I got home in about 20 minutes, taking it slow.

So in retrospect, the battery almost certainly cutout due to cell (#1) under voltage.  The pack voltage minimum was 46 volts, which is fairly high, so it's doubtful that the entire pack was dead when cut out happened.  Of course I should have expected this, as #1 is the damaged cell.  In all, I am pretty content knowing my battery pack can still take me 34+ miles after all it's been through.  

AH: 16.06
WH: 800.8
Vmin: 46.93
Vquiescent: 51.17



Comments

Popular posts from this blog

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* favori

An Alternative Take on AI Doom and Gloom

 I've purposely held my tongue until now on commenting about "AI" (or, more specifically as has come to be known, GAN or Generative Adversarial Networks).  It seems like it is very in-style to complain about how it has made a real mess of things, it is displacing jobs, the product it creates lacks soul, it's going to get smart and kill us all, etc. etc.  But I'm not here to do any of that. Rather I am going to remind everyone of how amazing a phenomenon it is to watch a disruptive technology becoming democratized From the time of its (seeming) introduction to the public at large, around November of 2022, to late 2023, the growth and adoption rate has been nothing short of explosive. It features the fastest adoption rate of any new technology ever, by a broad margin.  To give a reference, the adoption rate for AI image and text generation, real-world uses, in just 12 months is comparable to all of that of the another disruptive technology, the World Wide Web, takin

RANT TIME: Why do replies to a message I sent go to my spam folder?

Despite what one would think/hope, sending a message to a given address does not inherently give Google a high confidence that a reply from this address is expected (and, for example, that it should bypass spam checks). I have confirmed with Google's tech support that there is no way to automatically have this happen. The user can do the following: 1. Add the address to your contacts list in Gmail. 2. Check spam folder for replies, and mark it as "not spam" if something ends up there, which should influence the fate of future replies received. I can also approve an address at the domain level, i.e. if it is a big vendor or similar. I've had to do this with several of our Chinese vendors. I regularly ask engineering and purchasing to give me a list of the supplies we deal with, so I can approve them as a preventative measure. For what it's worth, all of the false positive instances of reply -> spam we have experienced have involved the sender's email server