| Dale McPeters |
01-28-2009 07:14 AM |
Quater Horse update
A quote from Craig on our yahoo list....
Quote:
Ok folks,
Everyone is asking, and I've been sorely remiss in keeping quiet. We've had our
heads down taking care of all the standard 'life' stuff and getting this new
product polished up and ready.
New project name: QuarterHorse
(someone else wanted to use all of the mythological creatures / Dungeons and
Dragons monsters, so I let them have the 'Pegasus' name for an unrelated
offering to avoid confusion)
Status updates:
- In summary: 110% Success!
- Form factor adjusted to fit nicely in all the EEC-IV and V packages.
- Datalogging on the A9L/A9P advanced significantly. Both bench testing and
in-vehicle completed.
- Most data can be picked up WITHOUT CODE PATCHES, and the rest can be harvested
with some minor register shuffling.
- Several custom code patches were implemented successfully during testing to
move values around, pull ADC directly, render internal timers/counters, etc.
- Thanks to Paul Booth for helping me get my head around the 8061 stuff. Thanks
to others too, but Paul's the man!
- Performed live datalogging at 500+ frames per second, ALL data in external RAM
is shadowed accurately. Internal registers can be (and have been) remapped as
visible with patches if necessary.
- Simplified protocols for high throughput and easy legacy compatibility
updates.
- Details to follow for you software architects out there, but look forward to
an instruction set that has been streamlined.
- 100% nondisruptive realtime updates, you can upload entire binaries back and
forth / over and over without disturbing vehicle operation at all.
- We're digging into the BMD0 strategy (Marauder test vehicle) to flesh out the
EEC-V datalogging at similar data rates if not faster.
- We're actually polling the EEC_IV stuff faster than it updates internally (see
spreadsheet). Maybe the EEC-V will keep up with us? Nah.
Future 'nice to have' Features not available for introductory release but
(possibly) to be added later (will likely incur additional cost and require
bench update by sending it in):
- Multiple binary loading for EEC-IV, possibly EEC-V also.
- Remote breakout box accessory device for black-box logging capabilities, data
display, remote switching, ADC channels, Bluetooth, etc.
- EEC-read capabilities to read 'stock' ECU contents like the F2E or
EECSucka-type devices.
Production and distribution status:
- Rare species! Three units in existence: one has been in the field with Jody at
DP-Tuner for months doing emulation on the Powerstrokes, one is in my hands, and
one is on its way to Paul Booth for delivery on Wednesday.
- 10 new boards are in hand, to be completed for further field testing and
development this week: There's a short list of folks who have helped and have
one of these coming to them. You know who you are, so no need to ask. You'll be
getting your units within 2-3 weeks from now, software guys obviously get
priority.
- First 50-100 full production units are to be completed and available by
February. I'm serious this time, no more schedule stretching!
- Pricing will be $249 initially, not to exceed $295 later on. Available from
http://www.moates.net
Here's your data preview:
http://www.moates.net/zips/testa9l.zip (watch out, it's 8 megabytes unzipped!)
It's just under a minute's worth of data, but there are almost 150,000
datapoints (5 parameters HEGO1/HEGO2/RPM/MAF/TPS at around 500 frames/sec).
There's loads of optimization still available, theoretical limits are much
faster. But again, we're hitting the parameters faster than the EEC can keep us
posted, so we're well into the overkill zone on much of this. And that's where I
want to be.
What will you possibly do with all of this data? That's up to you, it's your
vehicle!
Hope this helps,
Craig
|
:D |
