Nice Jack

 

Nah, motivation does weird things to me.. LOL

 

You Know I read this but I am really being on ECU flashing, what exactly did you do jack?

 

nope..

the author of evoscan decided to take a different direction. ECUFlash is still supposed to be an open source project, but I haven't seen anywhere to download the source.

 

Why don't a bunch of you guys work on the project together? It has worked with great success in the honda ecu community.

 

Out of curiosity...what are you writing it in Jack?

 

I sucessfully initiated a MUT protocol transfer, and sucessfully read logger data at a very high speed.. This was the biggest step needed to be made in order to produce a working logger that can function faster than an OBD-II logger.. Everything from now on is feature, data and GUI.. This was the hardest part since I had to work from very incomplete data on the MUT protocol..

There is a possibility I can add all sorts of interesting features, not just logging, but features mirroring the capabilities of the MUT-II and III diagnostic tool, if I had one I could get alot more data.

 

ECUFlash is indeed open source, he is working on some licensing issues with regard to the development tools he used in producing portable code..

EvoScan however started as open source, and he later withdrew his opensource intentions and made the software both closed source and no longer freeware.

This logger tool is intended to offer a freeware alternative to EvoScan... The software will be free in my current development.. I may fork off the code into a commercial product in the future, but the logging tools that you will always be free...

This probably will not become open source since its too hard to offer sourcecontrol with VB.NET projects using things like freshmeat and whatnot, there are only a few files and everyone would be fighting to make modifications to it, its just not realistic to work that way.

I may make the source code for the initialization and reading of a single data item available so you guys can create your own logger tools, but considering the modular nature of how I"m writing the new logger, you guys might want to contribute addons to enhance the software.

I'm still undecided on releasing source code, however the program to do the logging and other cool stuff will be free...

 

Sounds great Jack. Can't wait to have another (probably better ) alternative to EVOScan Keep us updated!

 

is there any possibility to clear SRS errors?

 

Anyone catch this post from Evo4Mad yet? It sounds like he's addressing a lot of our complaints with the 0.9 release:


Update v0.96

- Calculated data value feature added - calculated values can be based on other log items using their current value.
- Load added to the logs as a calculated data value.
- Gear added as a calculated data value - used for the dashboard view.
- Miles per gallon added as a calculated data value.
- KMs per Litre added as a calculated data value.
- GaugeFactor field added to data.xml - used for e.g. on the Rev counter gauge to display x1000rev/min
- State Indicators feature added to gauge windows
- Digital Gauges feature added to gauge windows
- Log Run Editor - specify the log file and start/end times for each run. first stage to being able to compare and view log runs in the new graphing being developed.
- Alarm Editor - allows criteria to be applied per data item logged, and a specific wav sound file to be played, any wav file from the \SoundFiles\ directory.
- Wideband serial port logging - used for debugging
-Innovate LC1 wideband logging support

 

Its nice that he's finally doing that, but this isn't the thread for it..

Its entirely possible that knowing there is another codebase that works out there has motivated him to get the useful stuff out there.

Those features are good news because it removes the need for the old log analyzer tool.. Since the gear thing is something I had planned from the start, I'm glad he implemented it. I'm especially happy he took the suggestion about creating a calculation based on any data captured.. It is easy enough to implement if the data is there..

This doesn't change how I feel about paying for something that promised source code and then no longer made it available. Hence why I developed my own code.

I did add standard OBD-II communication routines to my code so I can get the standard OBD-II powertrain codes and other snapshot data.. I had been stumped how to do it until I came across the freediag project and found some communication stream data for each of the exchanges.. OBD-II conversations are different then MUT, its a little more complex and quite a bit slower.. But that will allow me to read and reset OBD Trouble codes and snapshots..

Let me be clear, the tool I am developing is not going to have pretty gages, its purely functional to generate usable logs and integrate different devices together..

Not only wideband, but NMEA GPS Location data, alternate serial data streams from other data aquisition.. All of this is done through linked plugins where you can then utilize VBScript to compile the different useful data streams into a log or GUI.. The GUI can even be a video capture tool (I already have working code for that) so you can overlay useful information onto a camera view from inside the car..

The master controller (server) and the GUI and Logger are all seperate components that will run together, and can communicate over a fast internet connection too.. (This is an expansion of the old UTEC Digital Dashboard project)

This is only a small portion of desired features that I personally need to implement for my own purposes.. Adequate logging is about data correlation, and that is what all of these components are intended to do.. Correlate data.. The playback of video will correlate with the playback of the logs, etc..

Modules can be supplied by anyone for devices I never thought to support...

 

Will you ever have a trace or something that tells me what cell I am in when I am doing a dyno pull tuning?

 

Yes.. Initially you would have to manually add your axis information and timing cells..

Eventually I'll have it so it can read it from a rom..

The plan is to map trace the data, but also to build "optimum" cells by writing the values into the cells if you tell it to.. This will then give you a resulting map after the knock correction that you can use as a rough start..

I have done this sucessfully in a another VB app that went through my load calculated logs and placed the timing values in the cells.. If two cells were already filled, it would take the lower of the two values..

 

Sweet stuff MJ!

Some DataLogLab style log viewing would be helpful too