Miatapower List Archive

This read-only message was archived from a public mail list.
Mail From: Chi Row <(email redacted)>


Thanks Todd for your feedback. I tested on Win98 but it's good to
know that the program works on WinME.

I don't have any of the comm error handling routines in there yet.
With the real program, all the errors will be trapped.

You are right about the many possibilities. I would like some
suggestions on what features you would like to see. I am going to
add a max boost and wg sen% range peak hold with a reset before I go
for dyno. I have been looking for a gauge control but all I can find
is a bar.

I also would like to see how the program will run on a slower system.
Try to watch the "SYNC" vs. "Not Sync" box and see if it ever goes
"Not Sync" while you are running. I think when FM ECU gets busy, it
might loose the sequence from time to time.

Ray, is it possible to increase the baud rate to 4800 or higher?
Once 2 way communication gets going, 2400 might be too slow to keep
the real time datalogging going while configuring the set up.

--- Todd Paciorek <(email redacted)> wrote:
> Great job!
>
> My system - 700mhz PIII running millennium.
>
> Setup - worked, no problems.
> Run program - no problems.
> Press "Start" - no problems
> Start car - Error "6"
>
> Reread you instructions and start car before pressing "start"...
>
> Start car - boost, o2 and rpm all work.... wonderful!!!!!
>
> Now, if you can put some gauges in... mmmmm.... and maybe peak hold
> pointers.... and....
>
> You've opened the box!
>
> Thanks!
> Todd
>
>
>
> -----Original Message-----
> From: (email redacted)
> [mailto:(email redacted)]On Behalf Of Chi Row
> Sent: Wednesday, September 06, 2000 5:56 PM
> To: miata_power
> Subject: Need your help with datalog testing
>
>
>
> Over the weekend, wrote a small program to test the binary logging.
> This is a first step in trying to get to the 2 way communication
> program.
>
> It seems to work ok on my machine but I need few beta testers. The
> program is at people.atl.mediaone.net/csrow/upload/
>
> It's in a zip file called dlg.zip. This zip contains three files.
> Just extract these three files to a temporary directory and run the
> setup program.
>
> Once installed, the program Datalogsc should show up in you start
> menu bar.
>
> The program is hardwired for comm port 1.
>
> Connect the computer to the serial link, start up the engine, start
> the datalogsc program and hit the "start" button.
>
> Please let me know any errors you run into.
>
> Thanks
>
> P.S. The download file is about 1.5M in size. I wish I could make
> it
> smaller but VB just needs a lot of huge support files.
>
> =====
> -------------------------
> Chi Row
> RAGS-110
> JenJen 95 M-Edition
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> mail.yahoo.com/
>


__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
mail.yahoo.com/

This read-only message was archived from a public mail list.
Mail From: "Todd Paciorek" <(email redacted)>


You couldn't find gauge controls? I seem to remember them in the last VB I
worked with, but that was several versions ago... I'm sure they are
available shareware / freeware, I'll look...

Suggestions - If we can find the gauges, that would be fantastic... Also the
peak holding feature would catch some errata. What are your thoughts on the
2-way comm thing? How will the controls be for that?

Wish list - a 3d map of the goings on... I just saw that in the TECII
software and drooled... I'm sure it would take a lot of power to run it, but
I've got plenty right now. : )

I'm available for any help you need... code and I agreed to disagree a long
time ago, but I have a fairly technical background and can help with some
stuff...

Todd

-----Original Message-----
From: Chi Row [mailto:(email redacted)]
Sent: Wednesday, September 06, 2000 8:08 PM
To: Todd Paciorek; miata_power
Subject: RE: Need your help with datalog testing - WORKS!


Thanks Todd for your feedback. I tested on Win98 but it's good to
know that the program works on WinME.

I don't have any of the comm error handling routines in there yet.
With the real program, all the errors will be trapped.

You are right about the many possibilities. I would like some
suggestions on what features you would like to see. I am going to
add a max boost and wg sen% range peak hold with a reset before I go
for dyno. I have been looking for a gauge control but all I can find
is a bar.

I also would like to see how the program will run on a slower system.
Try to watch the "SYNC" vs. "Not Sync" box and see if it ever goes
"Not Sync" while you are running. I think when FM ECU gets busy, it
might loose the sequence from time to time.

Ray, is it possible to increase the baud rate to 4800 or higher?
Once 2 way communication gets going, 2400 might be too slow to keep
the real time datalogging going while configuring the set up.

--- Todd Paciorek <(email redacted)> wrote:
> Great job!
>
> My system - 700mhz PIII running millennium.
>
> Setup - worked, no problems.
> Run program - no problems.
> Press "Start" - no problems
> Start car - Error "6"
>
> Reread you instructions and start car before pressing "start"...
>
> Start car - boost, o2 and rpm all work.... wonderful!!!!!
>
> Now, if you can put some gauges in... mmmmm.... and maybe peak hold
> pointers.... and....
>
> You've opened the box!
>
> Thanks!
> Todd
>
>
>
> -----Original Message-----
> From: (email redacted)
> [mailto:(email redacted)]On Behalf Of Chi Row
> Sent: Wednesday, September 06, 2000 5:56 PM
> To: miata_power
> Subject: Need your help with datalog testing
>
>
>
> Over the weekend, wrote a small program to test the binary logging.
> This is a first step in trying to get to the 2 way communication
> program.
>
> It seems to work ok on my machine but I need few beta testers. The
> program is at people.atl.mediaone.net/csrow/upload/
>
> It's in a zip file called dlg.zip. This zip contains three files.
> Just extract these three files to a temporary directory and run the
> setup program.
>
> Once installed, the program Datalogsc should show up in you start
> menu bar.
>
> The program is hardwired for comm port 1.
>
> Connect the computer to the serial link, start up the engine, start
> the datalogsc program and hit the "start" button.
>
> Please let me know any errors you run into.
>
> Thanks
>
> P.S. The download file is about 1.5M in size. I wish I could make
> it
> smaller but VB just needs a lot of huge support files.
>
> =====
> -------------------------
> Chi Row
> RAGS-110
> JenJen 95 M-Edition
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> mail.yahoo.com/
>


__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
mail.yahoo.com/

This read-only message was archived from a public mail list.
Mail From: "Todd Paciorek" <(email redacted)>


>Ray, is it possible to increase the baud rate to 4800 or higher?
>Once 2 way communication gets going, 2400 might be too slow to keep
>the real time datalogging going while configuring the set up.

Will there really be a need to datalog while configuring? I think the
configuring could be an only-at-idle thing where it can take control of the
system, like the keypad does now?

Todd

This read-only message was archived from a public mail list.
Mail From: Chi Row <(email redacted)>


You are probably right about not mixing the control and logging.
Still, I think it will be nice to have virtual gauges operating while
you are adjusting the settings rather than freezing them. From
programming point of view, it will be easier we make the operation
one way only.

At 2400 baud, ECU can send maximum of 240 bytes per second. The
datalog currently sends 195 bytes per second. We'll try it with 2400
baud and if we run into problems then we can go up to higher speed.

Ray brought up the good point about low speed providing better noise
immunity.

Can you tell me about the 3-d feature of TEC? Which three axis does
it map? All it would take is an Active-X 3-d graphics control to
have a real time 3-d display :-) (yea right).

--- Todd Paciorek <(email redacted)> wrote:
> >Ray, is it possible to increase the baud rate to 4800 or higher?
> >Once 2 way communication gets going, 2400 might be too slow to
> keep
> >the real time datalogging going while configuring the set up.
>
> Will there really be a need to datalog while configuring? I think
> the
> configuring could be an only-at-idle thing where it can take
> control of the
> system, like the keypad does now?
>
> Todd
>


=====
-------------------------
Chi Row
RAGS-110
JenJen 95 M-Edition

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
mail.yahoo.com/

This read-only message was archived from a public mail list.
Mail From: Ray Ayala <(email redacted)>


While the chip does support altering zone contents during data logging,
there is no immediate feedback saying that the change was accepted. You
have to wait until the next time the zone in question is spit back out
as a part of the normal datalogging process, and that could be up to 21
seconds later. So I would think that most users would prefer to suspend
datalogging while editing zones. Now about implementing gauges ... why
would users prefer to look at simulated gauges on a laptop on the seat
next to them when they have real gauges right in front of them? Sure
the tach is a bit off, but one gets used to that. Maybe it would be
nice to have an expanded temp display and O2 display though.
Full-screen-wide bargraphs (from 85 to 115 deg for temp, and 70 to 95
for O2) should be readable enough while driving. But the real
motivation for 2-way communication is to be able to implement a much
smarter autotune system in the laptop.

Todd Paciorek wrote:
>
> >Ray, is it possible to increase the baud rate to 4800 or higher?
> >Once 2 way communication gets going, 2400 might be too slow to keep
> >the real time datalogging going while configuring the set up.
>
> Will there really be a need to datalog while configuring? I think the
> configuring could be an only-at-idle thing where it can take control of the
> system, like the keypad does now?
>
> Todd

This read-only message was archived from a public mail list.
Mail From: Ray Ayala <(email redacted)>


When datalogging is active, the ECU accepts commands and processes them
but does not reply to them ... other than the contents of the normal
datalog data stream. Replies would interfere with the datalog frame
sync. It is possible to display gauges while adjusting the fuel and
ignition as you drive with the current baud rate of 2400.

Chi Row wrote:
>
> You are probably right about not mixing the control and logging.
> Still, I think it will be nice to have virtual gauges operating while
> you are adjusting the settings rather than freezing them. From
> programming point of view, it will be easier we make the operation
> one way only.
>
> At 2400 baud, ECU can send maximum of 240 bytes per second. The
> datalog currently sends 195 bytes per second. We'll try it with 2400
> baud and if we run into problems then we can go up to higher speed.

This read-only message was archived from a public mail list.
Mail From: "Murray, Rick" <(email redacted)>


Does the current auto tune adjust more than one zone "cell" at a time, i.e.,
IADV for knock events?
You are right, offloading tuning logic to a laptop would allow things like
restoring some timing advance back a few seconds after the ECU pulls some
timing for a knock event. Or, even more complex adjustments of more
parameters than the ECU can manage now.

-----Original Message-----
From: Ray Ayala [mailto:(email redacted)]
Sent: Wednesday, September 06, 2000 21:58
Cc: miata_power
Subject: Re: Need your help with datalog testing -
WORKS!


While the chip does support altering zone contents during
data logging,
there is no immediate feedback saying that the change was
accepted. You
have to wait until the next time the zone in question is
spit back out
as a part of the normal datalogging process, and that could
be up to 21
seconds later. So I would think that most users would
prefer to suspend
datalogging while editing zones. Now about implementing
gauges ... why
would users prefer to look at simulated gauges on a laptop
on the seat
next to them when they have real gauges right in front of
them? Sure
the tach is a bit off, but one gets used to that. Maybe it
would be
nice to have an expanded temp display and O2 display though.

Full-screen-wide bargraphs (from 85 to 115 deg for temp, and
70 to 95
for O2) should be readable enough while driving. But the
real
motivation for 2-way communication is to be able to
implement a much
smarter autotune system in the laptop.

Todd Paciorek wrote:
>
> >Ray, is it possible to increase the baud rate to 4800 or
higher?
> >Once 2 way communication gets going, 2400 might be too
slow to keep
> >the real time datalogging going while configuring the set
up.
>
> Will there really be a need to datalog while configuring?
I think the
> configuring could be an only-at-idle thing where it can
take control of the
> system, like the keypad does now?
>
> Todd

This read-only message was archived from a public mail list.
Mail From: "Ray Ayala" <(email redacted)>


No. That's why the fine tuning mode only operates when the engine is
quite close to a zone center.


Qwest Long Distance -- 5¢ a minute with no monthly fee!
Visit qwesteferral.com/r.jsp?a=ek2yzT11N1JfVU541Lz2HA$$&x
----- Original Message -----
From: "Murray, Rick" <(email redacted)>
To: "'Ray Ayala'" <(email redacted)>
Cc: "miata_power" <(email redacted)>
Sent: Friday, September 08, 2000 6:10 AM
Subject: RE: Need your help with datalog testing - WORKS!


>
> Does the current auto tune adjust more than one zone "cell" at a time,
i.e.,
> IADV for knock events?
> You are right, offloading tuning logic to a laptop would allow things
like
> restoring some timing advance back a few seconds after the ECU pulls
some
> timing for a knock event. Or, even more complex adjustments of more
> parameters than the ECU can manage now.
>
> -----Original Message-----
> From: Ray Ayala [mailto:(email redacted)]
> Sent: Wednesday, September 06, 2000 21:58
> Cc: miata_power
> Subject: Re: Need your help with datalog testing -
> WORKS!
>
>
> While the chip does support altering zone contents during
> data logging,
> there is no immediate feedback saying that the change was
> accepted. You
> have to wait until the next time the zone in question is
> spit back out
> as a part of the normal datalogging process, and that could
> be up to 21
> seconds later. So I would think that most users would
> prefer to suspend
> datalogging while editing zones. Now about implementing
> gauges ... why
> would users prefer to look at simulated gauges on a laptop
> on the seat
> next to them when they have real gauges right in front of
> them? Sure
> the tach is a bit off, but one gets used to that. Maybe it
> would be
> nice to have an expanded temp display and O2 display though.
>
> Full-screen-wide bargraphs (from 85 to 115 deg for temp, and
> 70 to 95
> for O2) should be readable enough while driving. But the
> real
> motivation for 2-way communication is to be able to
> implement a much
> smarter autotune system in the laptop.
>
> Todd Paciorek wrote:
> >
> > >Ray, is it possible to increase the baud rate to 4800 or
> higher?
> > >Once 2 way communication gets going, 2400 might be too
> slow to keep
> > >the real time datalogging going while configuring the set
> up.
> >
> > Will there really be a need to datalog while configuring?
> I think the
> > configuring could be an only-at-idle thing where it can
> take control of the
> > system, like the keypad does now?
> >
> > Todd
>