http://pengaru.com/gallery/tuning/e62d.test.4/

coming along nicely, I should have a beta version out within a month. I'm going to be giving away 5-10 beta copies to people with E6K's when it's ready, contact me if you'd like to be one of them. You must have a E6K, and it is preferable that you also have a TechEdge 2a0 as the software also has native support for this wbo2 controller.

And for you E6X guys, don't worry, the backend already has E6X support just needs completion and testing, the design permits multi-model support.

Questions? Comments? Flames? I'm listening.

 

i'd like a beta copy

 

not that i dont think this is a great idea, but why.. the haltech softwear works great.

 

i personally really like the gauge software because the e6k haltech engine data page is straight 1980's

 

The new halwin software is unavailable for the e6k at this time, the DOS haltech software doesnt work that great IMO. I will also have 3d editing which the dos software entirely lacks, and I've already added features that are very useful with street tuning the car that are missing in the DOS software, some of them have been added in the halwin e6x software though (namely follow mode, large wbo2 gauge display while editing maps, simulated analog driving gauges, 3d editing, and more).

The more you tune your E6K the more you realize how much the software limits the E6K from being far better than it is with the provided software package.

Like I stated before, I have native support for the TechEdge 2A0 wideband o2 controller, this adds a wbo2 input, another rpm input (with a much higher sample rate than the E6K's rpm input, approximately double, much better for the simulated analog RPM gauge), 3 extra analog 0-5v inputs, and 3 thermocouple (egt) inputs. My software combines the data coming in from the E6K and the 2A0 seamlessly, and logs all the data together to a uniform datalog format.

If you have ever tried doing something useful with the E6K datalogs, you have probably realized that the values in the datalog are essentially raw. You need to load the ECU data for the datalog to be viewable with properly translated values. Things like MAP sensor type, TPS calibration, are likely to be off until you load the appropriate 6km data either from disk or from the ECU in online mode, it does not store the required calibration values in the datalog file, and does not apply the calibration factors to the data before it is saved to the datalog. My software uses a completely different datalog format, which is viewable with any text editor (it's essentially a CSV file) and all the data stored in the datalog is fully translated already. For example, the TPS data stored in the my datalog is stored as a value from 0 - 100 %, if your TPS was calibrated in the ECU properly when the datalog was taken, the value in the datalog will be correct as-is. This makes the datalogs complete without any ECU or 6KM file, making it easier to send the datalogs to others to look at / post them on forums for review etc. The datalog format is also not E6K-specific at all, since all values are fully translated it's a truely generic format which permits storing data from various devices in a single place complete with timestamp information. This is how I am able to add the 2A0 data seamlessly into the datalog with little extra effort.

For now the E6K and 2A0 are the only things supported (E6X likely in 2nd full version), I plan on adding support for additional useful tuning devices as time permits, I would also like to add support for a GPS devices so coordinates can be stored in the datalog also... imagine viewing your datalog in a overhead geographic view of the track you were driving on (plot all the acquired GPS coordinates on a 2d surface ordered by time), and being able to select a region of the track to view all the acquired data through that area of the track. Way more intuitive than scanning through a graph looking for those misfires in turn # 3 based on timestamps and counting throttle stabs. This would obviously also be useful for street tuning, if you experience problems on the street and have datalogging on, you can easily locate the relevant data by just noting where you were when it happened.

So, do you still have to ask WHY? The reason is innovation, once the basics are implemented and tested to be reliable, flexible, fast, and correct, I can move forward and add support for so many devices we can enter into F1 data acquisition territory for a fraction of the cost. The E6K is a decent ECU platform, the software that comes with it does nothing more than provide the bare minum required to interface with the ECU, it adds no value whatsoever to the package other than supporting ancient laptops that you couldnt read yellow text on blue background in sunlight on anyways.

There is more to the project than just the things I mention here, but I don't want to spoil all of it. It's just if someone has to ask WHY they must really be short-sighted and that required some clearing up.

Cheers.

 

i am totaly interested in your softwear i run a turbo 1990 convertible haltech E6k, and a 1985 with T2 motor, T04-V, 1600 secondarys, 40mm waistgate, e6k... ect but i would love a coppy of your softwear i hate the dos softwear. And actual gauges and converted mesurements would be killer! as well as a proper TPS reading. i have bad problems with that. but when it is done please send me a coppy to rx7pro@aol.com
thank you very much
aaron

 

would this support other wide band units other than that of the TechEdge 2A0? I mean I am seriously interested in the version that supports e6x however If I have to go out and buy a tech edge I would rather stick with the HalwinX which is HUGELY superior to the dos software.

Also could you make a point form list of the options and basic functions that you will be able to go.
Thank You
Jeffrey

 

For now, just the TechEdge 2A0 is supported in addition to the E6K. If you don't have a 2A0 the software just falls back on using the E6K's a/f mv input for the afr gauge... so you still get something, as long as your wbo2 controller is wired into the o2 input on the E6K.

I will make a comprehensive feature list in the near future and post it on my site, I will be working on a page specifically for this project over the next month as I prepare the beta release.

 

wow, That answer my questing, I thought the new halwin softwear supported the E6k

 

Very interested in this.. 1 question though, can you go back and forth between the software without corrupting the maps?


BTW i have a e6K and would be willing to beta the software.. But i have a FJO wideband.. So i could provide support/testing for another wideband. (I know others with other widebands to verify that they are correct)


My email is zyounker@gmk2.com if you want to contact me directly.

 

Good question, and yes, you can switch between the DOS software and my software, my software does not alter the layout of the data stored in the ECU, or require you to change the firmware. It's compatible with the existing firmware, does the same things as the DOS software at the serial communications level. The firmware version that is most supported at this time is series 8 version 14, if you have a different firmware it's likely it will work just as well but simply has not been tested well (this is where the beta testing comes in).

As for the wideband support, perhaps I was not clear enough on this.

The TechEdge 2A0 support does not mean it supports simply having the techedge connected to your haltech (this capability is a given, it comes with the basic E6K suppot), it means it supports having the 2A0 connected to the PC on it's own serial port, in addition to the E6K being connected to a different serial port. This is how the additional inputs are all available from the 2A0, this also avoids the input impedance problems associated with connecting wbo2 controllers to the ECU's O2 input possibly throwing off the readings.

You can connect your FJO to your E6K just like you would have it connected right now if you wanted to have the DOS software display the wbo2 voltage in the engine data page & datalogs. But you won't be able to connect it to a seperate serial port like my software supports with the 2A0 until the software has explicit FJO support added. The difference is, if the FJO has extra features that are available over it's serial port (most wbo2 controllers have additional inputs for logging), they would be available with explicit support. When you simply connect the output wire to the o2 input on the haltech those data streams are unavaiable, just a o2 voltage will be available in the e6k engine data that originates from the FJO.

Make sense?

BTW, another huge benefit of direct wbo2 controller support is a very likely higher sample rate. The E6K has a relatively low sample rate, due to the significant overhead of it's communications protocol. If you connect the wbo2 to the haltech via the o2 input wire, regardless of how fast the serial communications on the wbo2 controller can go, you are now limited by the sample rate of the E6K's serial communications. On the 2A0, using the seperate serial port to communicate with it results in a sample rate almost DOUBLE that of the E6K's in testing, and thats with similar port speeds for both devices. The 2A0 has a much leaner protocol, which results in a higher sample rate, much more efficient use of the bandwidth available on the serial port. This is really useful on a pretty fast responding wbo2 sensor, in my datalogs I have a few wbo2 samples plotted in between every e6k-sourced sample as a result of the higher sample rate, and the in-between values do vary sometimes, these samples would have been missed if the thing was just connected to the e6k o2 input, it makes for very nice wbo2 monitoring.

 

I've taken some more photos of the software, this time previewing the gauges and some videos demonstrating a more general view of the software.

http://pengaru.com/gallery/tuning/e6tuner.1/index.html

I'm always looking for feedback so feel free to comment, looking for a few more beta testers also. PM me your email address and mailing address as I will be mailing the beta out on CD. I think there are only a few more slots open for the free ones. The beta is only available to people who have a E6K, and preferably people with a E6K AND a TechEdge 2A0. I expect feedback from beta testers, no use being a beta tester if you don't even have a ECU to run the software with.

 

This software sounds like what everyone has been waiting for! Looks good!

 

hopefully vito is gonna bring his trusty software with him when we go to pick up my 89 TII this weekend :x

 

jacob, I should have at least something to show you, probably not a beta cd though, still more work to do before that is ready.

I took some quick kinda crappy videos of some parts running in online mode, on my NA FC3S.
http://pengaru.com/gallery/tuning/e6tuner.2/

The text accompanying the videos explains things, but I would like to make clear the laptop is a old compaq armada 1120, very low end pentium (100Mhz I think?) with a very poor/slow graphics chipset, and NO L2 cache, NONE. The screen is 640x480 active matrix garbage. With a slightly newer laptop, with a higher resolution display, things are faster and look alot better.

 

I know the new haltech beta firmware supports multiple maps.. have you thought of supporting that?

I understand about the WB support now. And like i said, i have a FJO so if you wanted to support that with your software i would be willing to help.

Basically i just need to hook it up and watch the serial dumps. figure out the protocol, which i am sure is very simple.


Anyway good luck. and keep us posted.

 

If I can get my hands on the firmware I can add support for it easily. If you're interested in reverse engineering the FJO yourself, do it already If you post what you find and it's accurate myself and anyone else can implement software for interacting with it, if thats what you're interested in doing.

 

what are you looking to charge for it........? It looks great

 

BTW good luck Jake

 

Still undetermined, how much would you pay?

 

dang man I always hate those questions. Just shoot. whad ya think

 

Well, the pricing is yet to be determined... alot of time has gone into the reverse engineering and implementation of the software.

I have taken some videos of the e6tuner_beta_pre2 image running on my friends laptop, on my FC.

http://pengaru.com/gallery/tuning/e6tuner_beta_pre2/

Enjoy the movies, the software captured in these movies is the same as what is announced in my other thread regarding the beta/demo... so you can try it on your car.

 

dear nick, say: "10 dollars"

hopefully i'll have a 'prerelease' of it so you can see it

 

Linky is dead

 

you sure? works for me, it's my server, usually it's really reliable. Try it again?

BTW, I've posted a new beta release with some corrections, the readme.txt has info on the changes.