[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ET) Ooops, timer died

Subject: (ET) Ooops, timer died
From: Christopher Zach <cz alembic crystel com>
Date: Tue, 23 Apr 2013 14:38:39 -0400
List-archive: <http://cosmos.phy.tufts.edu/mhonarc/elec-trak>
List-help: <mailto:elec-trak-request@cosmos.phy.tufts.edu?subject=help>
List-id: Electric tractor discussion list <elec-trak.cosmos.phy.tufts.edu>
List-post: <mailto:elec-trak@cosmos.phy.tufts.edu>
List-subscribe: <https://cosmos.phy.tufts.edu/mailman/listinfo.cgi/elec-trak>, <mailto:elec-trak-request@cosmos.phy.tufts.edu?subject=subscribe>
List-unsubscribe: <https://cosmos.phy.tufts.edu/mailman/options.cgi/elec-trak>, <mailto:elec-trak-request@cosmos.phy.tufts.edu?subject=unsubscribe>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

Checked my tractor this morning and it was still charging, for 20 hoursor so. In other words the timer motor died.

Drat! Serious overcharge. Fortunately I am using NiCD cells, they canhandle this fairly well. But I should put in a redundant timer in theevent one fails.

Follow-Ups:
- Re: (ET) Ooops, timer died
  - From: Charlie
- Re: (ET) Ooops, timer died
  - From: David Roden

Prev by Date: Re: (ET) Elec-trak Digest, Vol 11, Issue 77
Next by Date: Re: (ET) Ooops, timer died
Previous by thread: Re: (ET) Elec-trak Digest, Vol 11, Issue 77
Next by thread: Re: (ET) Ooops, timer died
Index(es):
- Date
- Thread