Hi Guys - I just posted version 4.13 of TunerPro. http://tunerpro.markmansur.com/ In this episode: - Added 3D chart axis unit labels - Added internal and normalizer-linked table axis label types (Ford/Honda) - Added 16 and 32-bit source data option for checksum calculation - Added "Insert Copy" ability to XDF Item editing (Ctrl + I) - makes for more rapid XDF creation - Added item list "active" highlight option (default: ON) - active parameter being edited is highlighted in item list - Added 3D data visualizer for quickly identifying unknown tables and other data points in a bin (Advanced menu) - Fixed issue where 16 bit MSB first values/tables that output raw hex weren't being saved in the correct endianness - Fixed issue where Y axis of functions were not being saved at all (!) - Fixed issue where X axis of functions were being saved incorrectly (and Y, had it been saved) (!) - Fixed issue where signed tables were not outputting signed data - Fixed issue with Function object editor - X/Y combo box changes do not allow OK/Apply - Fixed issue with Function output when exporting bin data to a text file - Fixed silent crash while sorting the hex output column of the item summary list - Fixed issue with function item description 100 character limit - Fixed issue with XDF header description field - a character was chopped off each time the XDF was saved - Fixed a number of crashing issues Unless a critical fix is required, it will probably be a couple of months before the next major release. For the next release I'm going to focus on completely re-writing the ALDL portion of TunerPro. I plan to have a new ALDL definition format (.ADX) that has many similarities to the XDF format, including more complex equation support (including the ability to "chain" item outputs to make new and interesting items - like fuel economy) and new item types (such as histograms ala Datamaster and WinALDL). I'll also be adding connection and command "macros" that will simplify connection to the more complex ECMs and masks, such as some $58 BCCs, 90-91 Corvette $8D BCCs, LT1, etc. I'll also be adding to the logging features (time stamps, "markable" log sections, etc) that will render logs not compatible with previous version of TunerPro (so prepare for that). And finally I'll be enhancing the ALDL visualization controls (dash, monitors, lists, etc). Enjoy! Mark

It just keeps getting better!
Easily the best complete DIY EFI package out there!
Unreal Mark.
Thank you for your efforts!

Very nice Mark........great work as usual.

Looking forward to the next release with the histograms also.

Gosh........your going to spoil us

Naww....we're already spoiled

Your dedication to continued improvement is appreciated

Thats a MAJOR plus in my book. Looking for WOT section in the .ads replay is a PITA. Once you find it and go to rewind it you end up losing it again.

Great Job man.

Awesome!!!! Best money I EVER spent was on Tuner Pro RT!!!

Alex

Thanks Mark. I'll check this on the Subaru stuff as soon as a I get a chance. Embedded axes rules

Tim

Cool. Did you get my email?

Mark,

I was just helping a buddy down the road from me with his new AutoProm setup. I was able to datalog with tunerpro using an older version than 4.13 on my laptop. The other laptop we used with 4.13 would not datalog. I then upgraded my laptop with 4.13 and had the same problem, no datalogging. Emulation works fine on both laptops. We now have two laptops that can't datalog.

We're both working with build 4.13.0183.00

Wish I could remember what previous version I had on my laptop.

Any suggestions, we both think it's software related.

I made no changes to the ALDL portion of TunerPro, so it would be a little hard to believe that the new version is to blame.

What kind of car?

It's a 34 Willys with a 350 TPI and 1227727 ECM.

This was our order of events:
- Attempted datalogging with laptop A (TunerPro RT 4.13)
- Datalogging failed, but emulation worked
- Attempted datalogging with laptop B (TunerPro RT 4.xx)
- Datalogging worked, emulation worked
- Upgraded laptop B with TunerPro RT 4.13
- Datalogging failed, but emulation worked

We used the same .ads files.

Because we both were working with the same TunerPro RT download, I'll download and install the installation file from your website and try using my laptop with my engine later today or early next week. Maybe something was corrupt with the download?

Just for the he!! of it did you check the box to disable checksum when you put in the new software? under tools, prefrences?

No, but I'll try that.

Yeah, it should work with the 7727. Let me know how it goes.

We do alot of DFI and Motec systems at our shop. We also use LS1 edit on the OBD cars. Is this Tunerpro the most comprehensive setup for the earlier prom cars?? We do alot of Syclones, Grand Nationals, and other PROM OBDI vehicles and we need a comprehensive sofware/hardware setup that will allow us to tune 85-94 vehicles. Does anyone know if this setup/system has data screen similar to DFI and if a prom burner setup is available with it.

Thanks for your help.

John

Hi John -

To be honest, if you want comprehensive, go with Tunercat (http://www.tunercat.com). He, by far, has the most "complete" definitions and stands by them (because he specifically created them). Tunercat does not datalog, however. The other advantage to Tunercat that it has the built-in abality to flash LT1 PCMs (94 & 95). TunerPro does not. I've been trying to find information on how to do this so that I can integrate it into TunerPro, but to no avail (anyone?). The main disadvantage to Tunercat, in my opinion, is the price. The main program is $80-$100, and additional definitions are $20. However, being a professional shop, the price might not mean so much (cost vs. benefit). It's a GREAT product and has been around a long time.

If you want versatile, go with TunerPro. Almost every definition for GM OBDI vehicles is availble (almost). You can easily add and remove data items if you have the appropriate information. TunerPro datalogs and uses an open, configurable ALDL definition format that will allow you to create definitions for any OBDI vehicle (if you can't find one that already exists). TunerPro definitions are, for the most part, created by the user-base (and not by me, the author). It is a little harder, therefore, to "verify" each and every definition, and there are likely to be mistakes here and there (though I've never really run into anything major). Of course, even the Tunercat definitions have known to have some minor mistakes here and there.

In the end, though, I'd say Tunercat is much more plug and play, and Tunerpro is much more directed towards the DIY-er who has time to spend (or invest) in searching for more information on the technical side beyond just the tuning. TunerPro is very inexpensive (free, actually), and the definitions don't cost you more money over and above the software.

The choice, obviously, is completel yours. Give both a try (please!). Let us know what you think of both (or either), and why you might prefer one over the other.

Let me know if you need any further detail, guidance, or have any general (or specific) questions.

[quote][To be honest, if you want comprehensive, go with Tunercat (http://www.tunercat.com). He, by far, has the most "complete" definitions and stands by them (because he specifically created them). Tunercat does not datalog, however. The other advantage to Tunercat that it has the built-in abality to flash LT1 PCMs (94 & 95). TunerPro does not. I've been trying to find information on how to do this so that I can integrate it into TunerPro, but to no avail (anyone?). The main disadvantage to Tunercat, in my opinion, is the price. The main program is $80-$100, and additional definitions are $20. However, being a professional shop, the price might not mean so much (cost vs. benefit). It's a GREAT product and has been around a long time.

If you want versatile, go with TunerPro. Almost every definition for GM OBDI vehicles is availble (almost). You can easily add and remove data items if you have the appropriate information. TunerPro datalogs and uses an open, configurable ALDL definition format that will allow you to create definitions for any OBDI vehicle (if you can't find one that already exists). TunerPro definitions are, for the most part, created by the user-base (and not by me, the author). It is a little harder, therefore, to "verify" each and every definition, and there are likely to be mistakes here and there (though I've never really run into anything major). Of course, even the Tunercat definitions have known to have some minor mistakes here and there.

In the end, though, I'd say Tunercat is much more plug and play, and Tunerpro is much more directed towards the DIY-er who has time to spend (or invest) in searching for more information on the technical side beyond just the tuning. TunerPro is very inexpensive (free, actually), and the definitions don't cost you more money over and above the software.

The choice, obviously, is completel yours. Give both a try (please!). Let us know what you think of both (or either), and why you might prefer one over the other.

Let me know if you need any further detail, guidance, or have any general (or specific) questions./QUOTE]




Could not have been explained any better.