Message Router delivery notification message
MRGATE%WOODS.dnet at woods.uml.edu
MRGATE%WOODS.dnet at woods.uml.edu
Sun Jan 29 20:02:16 GMT 1995
RE Message ID: 63754182105991/869073 at WOODS
UA content ID: Message Router delivery notification message
Attempted delivery to:
Route : @AM <--
Userid : VAHEG
Arrival date : 29-JAN-1995 14:57
This delivery failed. Failure reason was "transfer failure".
Diagnostic was "max time expired".
Message-id: 63754182105991/869073 at WOODS
From: MX%"DIY_EFI at coulomb.eng.ohio-state.edu"@MRGATE at WOODS
Subject: Message Router delivery notification message
Precedence: 1
To: VAHEG at AM
Return-Path: <owner-diy_efi at coulomb.eng.ohio-state.edu>
Received: from coulomb.eng.ohio-state.edu by aspen.uml.edu (MX V4.1 VAX) with
SMTP; Sat, 28 Jan 1995 14:57:13 EST
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) for
VAHEG at aspen.uml.edu id AA06498; Sat, 28 Jan 95 19:26:04 GMT
Received: from willow.uml.edu by coulomb.eng.ohio-state.edu via SMTP
(920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper
resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h
coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id
AA06493; Sat, 28 Jan 95 14:26:01 -0500
Received: by woods.uml.edu (MX V4.1 VAX) id 10327; Sat, 28 Jan 1995 14:25:57 EST
Date: Sat, 28 Jan 1995 14:25:57 EST
From: MRGATE%WOODS.dnet at aspen.uml.edu
To: DIY_EFI at coulomb.eng.ohio-state.edu
X-Vmsmail-To: MX%"DIY_EFI at coulomb.eng.ohio-state.edu"
Message-ID: <0098B243.87D29EA0.10327 at woods.uml.edu>
Subject: Message Router delivery notification message
Sender: owner-diy_efi at coulomb.eng.ohio-state.edu
Precedence: bulk
Reply-To: DIY_EFI at coulomb.eng.ohio-state.edu
RE Message ID: 54224172105991/867197 at WOODS
UA content ID: Re: [EFI68k] new release and group survey
Attempted delivery to:
Route : @AM <--
Userid : VAHEG
Arrival date : 28-JAN-1995 14:23
This delivery failed. Failure reason was "transfer failure".
Diagnostic was "max time expired".
Message-id: 54224172105991/867197 at WOODS
From: MX%"DIY_EFI at coulomb.eng.ohio-state.edu"@MRGATE at WOODS
Subject: Re: [EFI68k] new release and group survey
Precedence: 1
To: VAHEG at AM
Return-Path: <owner-diy_efi at coulomb.eng.ohio-state.edu>
Received: from coulomb.eng.ohio-state.edu by aspen.uml.edu (MX V4.1 VAX) with
SMTP; Fri, 27 Jan 1995 14:22:38 EST
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) for
VAHEG at aspen.UML.EDU id AA01097; Fri, 27 Jan 95 18:03:28 GMT
Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via
SMTP (920330.SGI/920502.SGI) for
/usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000
-l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s
-r DIY_EFI diy_efi-outgoing id AA01092; Fri, 27 Jan 95 13:03:25 -0500
Message-ID: <9501271803.AA01092 at coulomb.eng.ohio-state.edu>
To: DIY_EFI at coulomb.eng.ohio-state.edu
Subject: Re: [EFI68k] new release and group survey
In-Reply-To: Your message of "Fri, 27 Jan 95 10:46:20 EST."
<9501271546.AA26327 at ivan.gallium.com>
Date: Fri, 27 Jan 95 13:03:25 -0500
From: John S Gwynne <jsg at coulomb.eng.ohio-state.edu>
Sender: owner-diy_efi at coulomb.eng.ohio-state.edu
Precedence: bulk
Reply-To: DIY_EFI at coulomb.eng.ohio-state.edu
--------
In message <9501271546.AA26327 at ivan.gallium.com> , you write:
| 1) Will the MAX791 and KM681000L allow the contents of the SRAM to be retaine
| d
| over power off? How much current will be drawn to keep the SRAM contents
| alive? (Mine would go in a boat, and drain may be a problem if the boat
| isn't run for week or two.)
yes, it will store RAM and continue to keep time. I believe
I measured less than 100uA at room temp. This should not be a
problem for a car/boat battery but I would like to see a
separate battery. I believe nicad batteries have "problems"
at temperatures below freezing (??? is this true ???) and I
have not tried to find the temperature range of a lithium
battery. I would love to find a battery that would recharge
while the engine was running, have a temperature range
compatible with the car's environment, and be about the size
of a quarter (in the 2-4.5V range). Any ideas?
| 2) Downloading 256KB or code at 9600 baud will take two minutes. Is there any
| way to speed this up? (i.e. much higher baud rate, or parallel interface)
(256*1024)/(9600/10)/60=4.5 minutes (binary transfer) ???
I've been running at 38400 (limited by the host) but am
also transferring s-records. That's about 1920 bytes/sec. I've
heard of 16550's running at over 100k baud. I have not
given parallel port transfer much thought since I don't
believe the parallel port on an SGI Indigo is bidirectional :(.
The C library tends to be about 24k (mostly stdio stuff)
while the C++ library is on the order of 80k. RTEMS is
suppose to be about 16k. The EFI software should be much
less complicated than all of these... maybe 12k (blind
guess) with all the options for a total of 24+16+12=52k.
I hope to use a good portion of RAM as a "data recorder".
John S Gwynne
Gwynne.1 at osu.edu
_______________________________________________________________________________
T h e O h i o - S t a t e U n i v e r s i t y
ElectroScience Laboratory, 1320 Kinnear Road, Columbus, Ohio 43212, USA
Telephone: (614) 292-7981 * Fax: (614) 292-7292
-------------------------------------------------------------------------------
More information about the Diy_efi
mailing list