Trying to get in touch with Enerdel; UPDATE: Disappointing Success

Here is the response from Enerdel:

From: Battery Support <support@enerdel.com>
Date: Fri, Jun 17, 2016 at 7:22 AM
Subject: Inquiring on Think City Car
To: “john.mayer@greendropgarage.com” <john.mayer@greendropgarage.com>

Thank you for Inquiry.

We are sorry for your inconvenience, however, we no longer provide
replacement parts for the Think City Car.

Continue reading Trying to get in touch with Enerdel; UPDATE: Disappointing Success

Programming RLEC ID’s

I have Enerdel’s ProgTool (specifically Programming Tool V4.16), which when configured properly I simply need to transmit a single message to the RLEC to set a new slave index/ID:

(For a description of the hardware required to connect to the RLEC, go to this post. You’ll need the PCAN adapter and the modified 4-wire RLEC wire harness.)

Enter message:
7E0 04 15 0X 00 00 00 00 00
Where X is the RLEC location ID ( 0-15 )
represented in hex ( 0-F )

But the ProgTool actually sends and receives a few messages (some kind of unlock procedure) before transmitting that message. Here’s a screen shot:
IMG_20160511_095050

In the first sentence I glossed over the details of configuring the settings. Here’s what you need to do before you type in the transmission message:

  • Check the box for “Use CAN.”
  • In the Transmission section, select the radio button for “Manual mode.”
  • Check the box for “SEC 13.” (This option will only show up in the Transmission section after you have selected “Manual mode.”)

Now replace the text in the “Enter message: ” text box with the message described above and click “Send.”

Now, when you install it into the pack make sure you put it in the correct position. Even Enerdel’s CommTool has inconsistent ways of referring to RLECs. Is the data that you’re looking at referring to the RLECs position in that pack by natural numbering (e.g. the first RLEC is number 1), or is it referring to the RLEC by its ID which is numbered in the way that is more conventional to computer programming (e.g. the first number is zero (aka 0, aka 0x0). It’s almost like they’re trying to trick you, so stay on your toes. Also it helps to know how they’re laid out in the pack.

Good luck!

That Pesky Rear Liftgate Latch…

I’m not surprised anymore when a Think arrives at the shop and the rear liftgate is released. Often the latch position switch (that should turn on the “Door Ajar” light on the center console) is not adjusted correctly. And I’ve seen plenty of liftgate latches slowly get further and further out of adjustment until you really have to slam it to get it to shut. So here’s what you can do about it: Continue reading That Pesky Rear Liftgate Latch…

+STEAM project brainstorm

Solar car
Soap box derby car
+STEAM outreach to high school (earlier?) students
Short TED talks at the beginning of meetings
Robo-kites
Deployable wind generators
Ship propulsion
Glider launches
Distributed suction cups
Configurable pulleys
Gravity and air flow cleaner
Vacuum crawler

+STEAM for TH!INK

I’m working on a Think today, so there are a lot of ideas floating around my head about things I could make to slightly improve these cars:

A shroud for the master cylinder to keep water from dripping on/standing on the brake fluid reservoir causing moisture contamination.
Maybe the same sort of shroud should be over the transaxle vent to prevent water intrusion…
A new cowl design that isn’t so crappy.
A silencer/muffler for the vacuum pump.
Headliner arch supports.
Rear fender liner stiffeners to prevent tire rubbing.
Rear hatch headliner baton.
Scan tool– Raspberry Pi + CAN adapter?