DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
This represents something like 8 months of work (and sometimes not-work, hence the 8 months), but I've finally decided to kick TunerPro 4.0 out the door and make it available to everyone. I believe it's ready for prime time. I want to go back to the old days of releasing incremental builds to the public as I fix and change things anyhow, so here you go!
There's tons of new and improved features, so I'm not going to list them here. A few of the new stuff is evident in the following screenshot. Please download it and find them all for yourself!
Yes, there are probably still some issues and kinks that haven't yet been found or worked out. I am fully aware of a couple. What I'm aware of isn't serious enough to sit on this thing any longer, however. If you come across any issues, please contact me via email with detailed information and supporting files.
Please note that I actually fell short of my targeted list of new and improved features. I decided to go ahead and cut a bunch of stuff for the initial 4.00 release. Please be aware that the features are not cut altogether and will be added as 4.00 evolves. I've got a long (and quickly growing) list of ideas and things to add to the software. Make sure you use that "Check Internet for Updates" feature to keep afloat!
In any case, please enjoy the software and let me know what you find. Contact me via email with any issues or suggestions.
I can handle that. For now I will bask in the ability to see an ALDL history and know if I am connected and and ...
Can I ask what you use to develop this software? Like what language and what IDE etc? I am a MecE with some desire to learn to program for some strange reason.
This TunerPro thing is great, I mean it looks so much like the MTS ADAPT fully flexible engine management stuff I get to use at school..
Yes, record button is fixed in the latest build on the site (2608).
EDIT:
Shoot, something's wrong with the build on the server. Its an earlier build (pre-release). I have no idea how that happened, but I won't be able to fix it until I'm home from work.
Oddly enough, it was working great (building a '302 ecu ADS to send you) when it crashed out, and Win2k Pro says 'TunerPro.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created'
I can't find the error log though... nothing in Event Viewer. Any ideas?
Originally posted by Doward Oddly enough, it was working great (building a '302 ecu ADS to send you) when it crashed out, and Win2k Pro says 'TunerPro.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created'
I can't find the error log though... nothing in Event Viewer. Any ideas?
Send crashes and things to me offline (email or via the TunerPro forum).
The best thing to do is try to get it to happen again and send me the exact steps and any related files to reproduce it.
Very happy to see the new release.
I was able to download last night, which took a while on dial up here in Sicily.......but it loaded right up and I was able to emulate and monitor ALDL with the same program, running the 7747!!!
I use the romulator on a USB adapter cable from IO gear and the ALDL on the serial port.
Sent a PM but thought I would post here as well. The changes are terrific. One issue I have found involves creating multiple XDF items with the same address. Previous versions of TP alerted you to that fact as you were attempting to create it. 4.0, in my usage does not. Were you aware of this?
I was able to communicate/log thru the ALDL as well as emulate with the Romulator.
Couple questions, possible issues because I am unfamiliar with the software.
The ALDL monitor and ALDL dash. When i first clicked them up the dash was all 0.0 and the monitor had 4 graphs with nothing displayed.
I was unable to find a way to set them up or make them read?(again I am unfamiliar, but had no luck trying various methods)
I went back to the dash and monitor later and founf the dash was grey screened where the 0.0 were prior and on the monitor it was just a black screen period with nothing in it....
Was it something I did or wasnt able to do? Or is there another issue lurking?
Use the "right" mouse button to bring up the listing of available items. That selects the display.
I found on my slow laptop that when emulating and logging I needed to move the mouse up/down to make the video refresh cause it seemed like the list would not display. Not a big deal, it justy took me a couple times to figure out what was happening.
Jp
Originally posted by 3.8TransAM
I was unable to find a way to set them up or make them read?(again I am unfamiliar, but had no luck trying various methods)
Was it something I did or wasnt able to do? Or is there another issue lurking?
Right-click on each gauge or monitor in which you'd like to display data. ;-)
Originally posted by JP86SS Use the "right" mouse button to bring up the listing of available items. That selects the display.
I found on my slow laptop that when emulating and logging I needed to move the mouse up/down to make the video refresh cause it seemed like the list would not display. Not a big deal, it justy took me a couple times to figure out what was happening.
Jp
Interesting. Can you send me more specifics on this issue?
Got it all up and running and driving, like the dash display for taking a quick peek while your going down the road, as you can make it quite a large display.
The one issue I had was the Inj Pulse Width, when diplayed on dash was off and seemed to be reading backwards.
The value was reading roughly 1/2 what Datamaster was and would decrease as throttle increased to accelerate.
Just a heads up. I was out solo so I did what changes I could in a parking lot. I don't know if it does the same thing on the graphing portion or not.
Another bug I have encountered causes TP 4.0 to crash.
It involves having a Flag open and then switching to another bin for the Compare. That crashes the app. It doesn't do that for Constants and Tables.
Anyone know what is the most current known good ecu for a 730 $8D?
And do I save the modified bins as xdf's? Appears so? The whole bin vs. xdf has me slighltly off kilter as this is my first wholescale TunerPro venture.
Originally posted by 3.8TransAM And do I save the modified bins as xdf's? Appears so? The whole bin vs. xdf has me slighltly off kilter as this is my first wholescale TunerPro venture.
TunerPro as related to TunerCat for Jeremy:
XDF = TDF
BIN = BIN
ADS = ??? =)
Save your bins as bins. If you modify the XDF, save it as an XDF. The XDF is the definition. The bin is the car's data. The ADS file is like an XDF, but it's for the datastream. It tells TunerPro what byte in the datastream corresponds to what "real world" engineering value. Much like the XDF does for the bin.
XDF is a new format for 4.0. You can use your old ECUs by importing them.
XDF serves the same basic purpose as ECU, only it is far more powerful and can be used for a much larger set of applications (and soon to grow even more).
Originally posted by kidcamarosc I tried to run the setup file but it gave me this error. "The setup files are corrupted. Please optain a new copy of the program."
Sounds like your download is corrupt. Download it again.
<-- would think having XDF + ADS as one file would make things easier. That way you don't have all these file open, close save blah blah confusion. Or better yet, have the basic ecm's ADS files built into the program where you just have to select which ecm you're running. Kind of like how WinAldl does it. Just shooting out idea's to make Mark's head hurt... I just recently got to working with the prominator, romulator, and autoprom (spring's here with warmer weather) and so now I've found a bunch of bugs. Still it's a LOT better than the older version so a big .
Originally posted by JPrevost <-- would think having XDF + ADS as one file would make things easier. That way you don't have all these file open, close save blah blah confusion. Or better yet, have the basic ecm's ADS files built into the program where you just have to select which ecm you're running. Kind of like how WinAldl does it. Just shooting out idea's to make Mark's head hurt... I just recently got to working with the prominator, romulator, and autoprom (spring's here with warmer weather) and so now I've found a bunch of bugs. Still it's a LOT better than the older version so a big .
Takes a lot more than that to make my head hurt. Here's a few reasons why I don't do that:
1) I hate hard coding anything into an application. I am completely against hard coding an ALDL definition into TunerPro. Not to mention the fact that there are many, many different ones.
2) What happens if you like one XDF and another ADS? If they're combined, what do you do about it? Modifying the XDF means the ADS has to go along. Modifying the ADS means the XDF has to go along. How do you track so much information in terms of versioning? Possible, but a pain and just that much more confusing for the end user (many of whom aren't so computer savvy).
3) XDFs and ADSs do not always match up in pairs. There are a number of different streams associated with the 7747, for instance.
4) Free version of TunerPro does not need the extra overhead of the ADS information in the definition.
5) Download size. Hard-coding the definitions into the application would make the application HUGE.
6) Download size. Combining the ADS and XDF would make definitions quite large.
7) What happens when someone wants to edit an ADS or XDF when its hard coded? That means I need to release another TunerPro version. That's not something I want to maintain.
Okay, so here's a feature I KNOW you can implement that would make life easier... link an open xdf with an ads file. This would be an option for the xdf, and if it doesn't find the ads file then prompt for it, then prompt if location would be linked with that xdf . That would make life a litte easier for us traveling (without a mouse) tuners .
edit: Also, Mark, your xdf file is a tad... well... boring and missing some things. It looks like you just imported the ecu file. For example, the table #6 scalor is missing but more importantly you didn't link the MAF tables to the scalors. I did that and have e-mailed you the xdf file that incorperates the scalors into the tables... thank you xdf format
Originally posted by JPrevost edit: Also, Mark, your xdf file is a tad... well... boring and missing some things. It looks like you just imported the ecu file. For example, the table #6 scalor is missing but more importantly you didn't link the MAF tables to the scalors. I did that and have e-mailed you the xdf file that incorperates the scalors into the tables... thank you xdf format
Sweet. Thanks for the, uh, kind words, and thanks for the updated XDF. To be clear, Jon's wonderful and astute observation is referring to the $6E XDF file. Not the XDF format in general (I hope).
No, I didn't just import the ECU. I added a number of things and added the table offsets to the appropriate tables (that I know of).
Nothing's ever perfect. :-D
Post Script: I didn't know the adjective "boring" could be tied to an XDF file. The English language is an interesting one, isn't it!
I downloaded the latest TP4 and like it very much...I have only started my learning curve into DIY Proms so please excuse what may seem like silly questions.
My current setup is with a 1227165-(ACXS) $32B, logging with DataMaster, edit with CATS. TP4 is very close to doing everything better so I'm keen to use it if I can.
I get the impression (hex data errors) that to use TP4 I must be very sure that the xdf file matches the chip bin file hex data. My stock chip was a ACXS and it would appear that macthing this to the correct xdf or ecu file to use with TP4 may not be easy or desireable.
I'm hoping...based on what I think that I've learned on this site that changing to say a 6E bin, or other more flexiable bin would be best....or could this cause a problem? My car is a 1988 IROC LB9 305 TPI (MAF) 700R4 (no air/egr/cat).
__________________ Siggy from Oz
1988 IROCZ Convert.
LB9 700R4 Sniper Catback
Don't you have an .ecu or .xdf for the $32? Seems to me that's the only one you can use. You can't use a $6E to edit $42 bin for instance. Heck, there's mistakes in some of the $42 .ecu files floating around.
Originally posted by Siggy I get the impression (hex data errors) that to use TP4 I must be very sure that the xdf file matches the chip bin file hex data. ... yadda yadda ...
Thanks for the help....
I can appreciate the need to match the bin with the correct mask, for now I will be using my AXCS bin with 32Bv001.xdf and so far it does look good.
However while looking at different combinations...specifically the 6E and ARAP bins combinations... I can't help but wish the 32B mask reflected similiar flags and constants.
My 88 IROC 305 TPI does not carry the cold start injector and other then a slight change in the injector the 89 F-body 305 TPI (6E match ?)must be near identical...?
Given that the correct sensors exist the mechanicals match and the ECM 165 are all identical except for the Eprom what would limit me from using ARAP or 6E match Eprom...?
Or do I have crossed wires being very low on the smarts curve?
Originally posted by Siggy Thanks for the help....
I can appreciate the need to match the bin with the correct mask, for now I will be using my AXCS bin with 32Bv001.xdf and so far it does look good.
However while looking at different combinations...specifically the 6E and ARAP bins combinations... I can't help but wish the 32B mask reflected similiar flags and constants.
My 88 IROC 305 TPI does not carry the cold start injector and other then a slight change in the injector the 89 F-body 305 TPI (6E match ?)must be near identical...?
Given that the correct sensors exist the mechanicals match and the ECM 165 are all identical except for the Eprom what would limit me from using ARAP or 6E match Eprom...?
Or do I have crossed wires being very low on the smarts curve?
You're hijacking the thread, my friend. Search. In the interest of being a good Internet neighbor, I'll save you from it:
To run 6E in your vehicle disable VATS in the bin if your car doesn't have it, and you should be good to go. Search for more information. Burn a 6E bin to a chip, put it in your adapter, and fire it up.
...
