Re: ALDL stream recycle time

["Dave Zug" <dzug@delanet.com>]

You mean that the stream is not simply 'completely' populated and THEN spat
out, that it reads each location just before spitting it?

I see. so theres hope. all that other stuff the 730 spits out decreases the
number of samples per second compared to the good ol '165.

Putting the good stuff in the first 10 bytes and shortening the quantity
transmitted to 10 would do it if I could have my way.. but the 63 thing
works if like you say it changes a few times during the 63 byte transmission
time.

Thanks John!  Food for thought.



----- Original Message -----
From: John S. Gwynne <jsg@jsgpc.mrcday.com>
To: <gmecm@diy-efi.org>
Sent: Tuesday, October 17, 2000 7:46 AM
Subject: Re: ALDL stream recycle time


>
>
> | Rephrased: Does the ALDL stream ('165 and or '730) simply repeat nose to
> | tail or is it's transmission restarted at a set interval of time?
>
> it definitely can be made to repeat nose-to-tail with smaller frames
> and do a faster update rate as you ask.
>
> quick and dirty....
>
> You could replace each entry in the MODE1 address table with that for
> MAP (for example). Then each MODE1 frame would give 63 readings of
> MAP. You probably would need to time stamp each byte as received to
> make sense out of the stream; each sample would not necessarily have a
> fixed sample period.
>
> Similarly, you could divide the 63 data bytes into 3 or 4 sub-frames for a
> faster update rate.
>
> john gwynne
>
> --------------------------------------------------------------------------
--
> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> in the body of a message (not the subject) to majordomo@lists.diy-efi.org
>
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo@lists.diy-efi.org