---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id AE113167003C; Thu, 29 Jan 2004 20:31:13 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <6.00CC4055@cherry.ease.lsoft.com>; Thu, 29 Jan 2004 23:30:57 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 9384 for PICLIST@MITVMA.MIT.EDU; Thu, 29 Jan 2004 23:30:48 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 4869; Thu, 29 Jan 2004 23:30:35 -0500 Received: from *unknown [63.65.120.68] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Thu, 29 Jan 2004 23:30:34 EST X-Warning: mitvma.mit.edu: Could not confirm that host [63.65.120.68] is smtp.covadmail.net Received: (covad.net 17479 invoked from network); 30 Jan 2004 04:25:18 -0000 Received: from unknown (HELO ezbake) (bobblick@68.164.174.56) by sun-qmail16 with SMTP; 30 Jan 2004 04:25:18 -0000 MIME-Version: 1.0 Priority: normal X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-ID: <40196E1A.19721.8828D6@localhost> Date: Thu, 29 Jan 2004 20:33:30 -0800 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Bob Blick Subject: Re: [EE]: High current PCB To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <20040129215352.735cee92.sunkist@iastate.edu> Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856430 On 29 Jan 2004 at 21:53, Eric Christensen wrote: > A friend of mine is building a dual battery system for his custom off-road > truck. His truck has a somewhat hard-starting chevy 350 engine and a > failure-prone electrical system. He wants to have a second battery that is not > normally connected to the system so that it won't be run dead in an electrical > failure. He then wants to be able to connect either battery to the engine > individually or both in parallel. > He has worked out the circuit using several high power MOSFETs in parallel, but > does not know how to connect them. Normally this is done with a couple of continuous-duty solenoids, available at most auto-or-truck parts stores. I don't mean to discourage the MOSFET approach, but it may prove to be a fussy design, and prone to exciting failure especially if the gate drive gets to oscillatin' Cheerful regards, Bob -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details. . Return-Path: <> Received: from mitvma.mit.edu ([18.92.0.3]) by tomts17-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040128010106.QBWY17233.tomts17-srv.bellnexxia.net@mitvma.mit.edu> for ; Tue, 27 Jan 2004 20:01:06 -0500 Received: by mitvma.mit.edu (IBM VM SMTP Level 430) via spool with SMTP id 6115 ; Tue, 27 Jan 2004 20:01:03 EST Received: from MITVMA.MIT.EDU (NJE origin LISTSERV@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 2220; Tue, 27 Jan 2004 20:01:03 -0500 Date: Tue, 27 Jan 2004 20:01:03 -0500 From: "L-Soft list server at MITVMA.MIT.EDU (1.8e)" Subject: PICLIST: error report from YAHOO.COM To: listsjosh@3MTMP.COM, piclist_errors@SYMPATICO.CA Message-ID: X-LSV-ListID: None The enclosed message has been identified as a delivery error for the PICLIST list because it was sent to 'owner-piclist@MITVMA.MIT.EDU'. ------------------------------ Message in error ------------------------------- Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 2218; Tue, 27 Jan 2004 20:01:03 -0500 Received: from mta133.mail.sc5.yahoo.com [66.163.174.161] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Tue, 27 Jan 2004 20:01:02 EST X-Comment: mitvma.mit.edu: Mail was sent by mta133.mail.sc5.yahoo.com From: MAILER-DAEMON@yahoo.com To: owner-piclist@mitvma.mit.edu X-Loop: MAILER-DAEMON@yahoo.com Subject: Delivery failure Message from yahoo.com. Unable to deliver message to the following address(es). : Sorry, your message to hbarregrd@yahoo.com cannot be delivered. This account is over quota. --- Original message follows. Return-Path: Received: from 209.119.0.109 (EHLO cherry.ease.lsoft.com) (209.119.0.109) by mta133.mail.sc5.yahoo.com with SMTP; Tue, 27 Jan 2004 15:19:56 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <0.00CBF1D9@cherry.ease.lsoft.com>; Tue, 27 Jan 2004 9:19:15 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 3739 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 09:19:09 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 1100; Tue, 27 Jan 2004 09:18:42 -0500 Received: from sprucegrove.com [12.151.22.244] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Tue, 27 Jan 2004 09:18:41 EST X-Comment: mitvma.mit.edu: Mail was sent by sprucegrove.com Received: (from jay@localhost) by sprucegrove.com (8.11.0/8.11.0) id i0REFag32211 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 09:15:36 -0500 X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <200401271415.i0REFag32211@sprucegrove.com> Date: Tue, 27 Jan 2004 09:15:36 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: "D. Jay Newman" Subject: Re: [OT:] SCO lobbying Congress about Linux To: PICLIST@MITVMA.MIT.EDU In-Reply-To: from "Bill Couture" at Jan 27, 2004 06:50:35 AM Precedence: list > > What if you are not trying to flame :-) I was deliberately avoiding > > specifics and the whole thrust of the line of thought was simply an > > observation about the biological similarities of (some) OpenSource > > licenses and virus's.. > > However, unlike biological viruses, it's YOUR decision if you want to > catch this virus. > > If you don't like the license terms of the code, just don't use it. > > Bill Unfortunately there are enough similarities between the GPL and a virus that this analogy keeps coming up. Example: One problem is that large commercial programs are made by large teams of programmers. Some of these programmers may not understand the problems they may cause by including GPL'ed code. The companies legal department probably doesn't look through the source code. Now this company has released a commercial program that *should* have been GPL'ed. What should happen if they are "caught"? I would say that if the original GPL'ed code is a small part, that the company should just rewrite it. There are other opinions on this. I'm a moderate. The GPL was written by somebedy much less moderate (great piece of work, however). -- D. Jay Newman ! jay@sprucegrove.com ! Xander: Giles, don't make cave-slayer unhappy. http://enerd.ws/robots/ ! -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads *** MESSAGE TRUNCATED *** .. .