There were a few big fixes:

- Improved performance of the logger.
- Fixed Zeitronix logger so it shouldn't crash when RPM signal is present.
- Wideband data is no longer incomplete on occasion, no longer drops data.
- If you had more than 99 Logger items total, program would crash, increased this limit to 300 This should allow all the requestID's you could ever want, plus custom requests.
- If you shut down app with [x] instead of Exit, settings will now be saved properly
- Removed [x] button from Wideband logger windows to prevent users from inadvertantly closing them.

New Features:

- Added support for the AEM Wideband, Thanks www.nolimitmotorsport.com for providing the AEM Wideband.
- I added a rudimentary dashboard that will start evolving into something a bit more elaborate as time permits.
- Logger window and dashboard stay in foreground when logger is running.
- One-Button logging, hitting enter will start and stop logging.


There's a few more bug fixes and feature refinement that I'm hoping to get done, but the major feature I wanted to add was the AEM Wideband as its a very popular unit. Also keep an eye open for a how-to on creating the wideband logger cable as the AEM documentation is enough to confuse ANYONE wanting to do this.

I'm hoping to release this some time this upcoming week.

 

 

I wanted to point out that the dashboard you see, is just the "Test mode" that I'm using to break up the different items, the actual dashboard you guys will get will have 7-8 items on it, RPM, AFR, Fuel Trims, Octane Number, Calculated and ECU Load, if those items are logged..

After I started doing some dyno tuning, I realized that having some of this data easily visible is useful, however I definitely wanted to take a the KISS approach (Keep it Simple Stupid) as I don't want to have people distracted while their driving, but I did need to see the data easily on the dyno, especially load and fuel trims.

 

You're just a big tease. Can't wait for the new version MJ.

 

One of the features I'm considering adding is a "Client" database..

Basically its a dropdown where settings are saved for different clients, things like Injector scale, baud rate, wideband settings (since different users may have different widebands), file path, etc..

This will require me to re-think a few things, I'm also going to try to get the voltage interpolation for the Injector Voltage Latency value working, which means there will be a 12v and 14v value you copy from the maps.. This should render the Load calculations more accurate.

 

cool, dashboard would be nice, I often have my brother riding along with me holding the laptop and it's hard to read the tiny font while the car is bouncing around the track

also I like the one button logging...a colored indicator would be nice. Maybe turn the button red and flash when it's recording.

 

Woooot!

You know what I would pay dearly for?

A simple 2-3 button USB wired remote that will stop and start logging. I'm sure I could program one of my music remotes to do this but something with only a couple buttons would be sweetness!

Keep up the good work man!

Andy

 

Thanks for the idea. I have a wireless usb remote that I used to use for Powerpoint presentations.

 

I never understood the indicator thing..I would figure the "Stop logger" text and the changing numbers would be a dead giveaway...

 

Not a bad idea, but I'm pretty sure you can already buy something to do that.

 

http://www.ukeland.com/pages/article...cts/controller here's a how-to..

Its really not that tough to modify a tiny joypad/joystick to do this and then use software to handle connecting the button presses..

There are even several keyboard emulator boards that let you wire switches to it to control input.. Among dozens of other things.

 

if it's in your face sure, but often my laptop is in my passenger seat and it's kind of dangerous to take my eyes off the road for more than a second to make sure it's logging

 

I guess I do things differently.. I start the logger, verify it started, then just leave it there until I'm done. I don't check it unless I come to a stop. No need to check it as it rarely stops for no reason.

 

yeah I don't like sifting through miles of data so I start the logger just before going WOT and stop it when I'm done. I make multiple logs like that and compare them to each other to make a decision, tweak the tune, rinse and repeat as necessary.

 

That still doesn't really stop me. I do the same thing, I stop for a moment, get the car set up for a log, start the logger, make a pull, then stop and stop the logger..