I am looking at parallel processing both the logger and autotuner. The logger is 1/3 of the size of the Autotuner and will be easier to interface. I am working on the structure of the calibration table for each wideband to make a standard structure so that adding a new wb will be as easy as writing a 20 line text based table and the software will do the rest. It has the name of the wideband, comms speeds and settings, data lenght, decode structure, request code if any, code to determine when O2 is ready. You may see a logger being released in about 6 weeks. I am in the process of buying 2 series 2 RX7 so I may have some of my time taken up with that.
Cheers
Michael Smith

 

Michael,

How's the progress on this project?

 

OK I ve been slack. I have been working on some money making software in my spare time. I need a income before I can dump the crappy job that my job has turned into. It used to be great but now it has changed from a good semi indoor job to a almost completely outdoors and at 35-45 degree C it is NO FUN this time of year it sucks. I need to get a job with balance again..

I will have a little crack at it tonight.
Cheers
Michael Smith

 

No rush, don't want you to forget

 

I just had a play around with the tewblog for the techedge units (i dont have one but was thinking about getting one). Anyway this software makes a .txt file similar to the logger program. What i was thinking is it wouldn't be that difficult to arrange the .txt file so you can load the logged values into the tewblog program. You can then view all the logged data on nice graphs and use the matrix analysis mode.

One question with the logger your designing will any oxygen sensor work? Like a proper wideband 0-5v one (LSU4 etc) ? I understand the wolf handcontroller wouldn't display the correct voltage but if the logger logs it ok that doesn't matter so long as it doesnt blow something up on the wolf.

 

Thats a great Idea! I will look into that.

The Wolf handset displays the correct voltage but the wrong AFR. I would guess that any wideband would work. The AFR calibration tables inside the Wolf indicate that it reads fro 0 to 5 Volts. If you look in the Wolf logger directory you will find something like Cal_maker.exe this makes linier custom cal tables which you can use under the Custom O2 option.

Cheers
Michael Smith

 

ok great. One other thing i tried to use your wolf logger program (i have used it before) and i'm getting a error when i try load it.

"component 'comdlg32.ocs' or one of its dependencies is incorrectly registered"

I'm thinking it might be a windows problem but not sure.

 

Don't worry i think i know the cause. I dont have office installed on this machine and its something to do with that.

 

download the VB6 runtime files from microsoft and install them> I have a copy on the Wolf logger website too!

Cheers
Michael Smith

 

With the help of nyt and raddavey we may have a converter to convert Wolf logger files to run on tewblog Using a wideband setup for 0 volts= afr20= and 5 volts = AFR10 using the Wolf wideband input or EVEN a auxillary input we may be able to get a realtime graph using tewblog after doing a conversion on the Wolf logfile. The idea from Raddavey was to use the first user input for timing.

Thanks Guys

Cheers
Michael Smith

 

Hey it was only an idea from me but you are the one doing all the hard work.
Micheal I would pay for this software!!.

It would be all the datalogging we really need, and we could log timing aswell. And hopefully like you said we could use a cheaper and better true wideband sensor.

 

Software written, debugging indicates 2 possible bugs should be finished this week

 

It's like Christmas again!!

 

so how close to the whole thing being finished?

kevin.

 

yea to be able to use it with my innovate lm-1 would be nice....

kevin.

 

i made a slight change myself - multithreaded the app for logging and tuning;

 

Hmm can you explain that further? Do you have an update? Or maybe forward the changes to Michael and he can make the changes.

 

Well my changes aren't much (yet), besides, Michael is very much able to make the same changes... Rum or no Rum

I do have another idea though - I've been hooking Wolfs App menus and junk...

i've bound my exe with the wolf exe and hooked their system menu, inserting my own into the wolf ecu app - so it looks as if the autotuner is part of the Wolf3D application. this is the direction i'm taking from here on out (mostly because i need the wolf ecu app with me when i start making changes).

I'm just tinkering around with ideas... Michael has something great up his sleve.. you'll see ;]

 

forgot to attach a screen shot of what i'm talking about

 

Did you ever get to complete this project Michael ?