TunerPro User Forum

if the vette uses $6E, then yes. $6E code is $6E code, regardless of the application (in other words, there are no variations of the $6E code itself, only the parameters within the bin - which is what TunerPro, TunerCat, etc, are used to modify!). So yes, the $6E def can be used to edit any $6E bin,...

i'll look into this and report what i find. thanks!

nope. just copy it to your windows (or windows/system in win98 windows/system32 in win2k/winxp) and you're good to go. you can also just put it in the directory with the tunerpro.exe.

The best way to confirm is to look at the hack file itself (the "source code" of the bin).

the 6E hack (nor the 6E ECU file) won't help you create $0D ECU. You need the $0D hack, which is out there. Google it. $6E is out there, but a little harder to find.

be sure you're looking at the same address in both programs. your ECU file may be incorrect. or you may just be looking at two different items.

Either way, this isn't a bug in TunerPro.

the ecu format doesn't allow for "scaling one item based on another". This isn't a tunerpro limitation, but a limitation of the file format it uses (public domain = I didnt write it).

You don't typically need to deal with the scalars.

the start and end addresses are "adjusted" automatically when you adjust the chip size, start address and end address of the source and dest. buffers.

play with the addressing and you'll see what I mean.

Very odd indeed. I didn't put a lot of effort into the hex editor (sorry about the load times... its becuase of the fact that I'm using a control thats not really meant to show that much data). I'll be putting more work into the hex editor over time. I just wanted to get something "useable"...

Sounds like a bug. I'll look into it and get it fixed. You'll probably find a lot of this stuff around chip burning (its not an easy problem to solve). The verify is known issue, as it doesn't currently make use of the start address. I will be fixing this for the next release. THe chip does burn cor...

depends on the application. TunerPro is "dumb" in that it doesn't know/care what car you have. Its only made "smart" by the ECU file you're using.

So the question is, does your ECM (and therefore ECU) contain this?

No problem. Let me know if you can get solid repro cases. Even vague repros can be helpful.

I'll play around in win98 and see if I can get anything bad to happen.

m

Its hard to say without repro cases. I'd love to help track these down if you can help me out with that.

No. It will be included in the next release (this coming week).

Load a .ADS file before switching tabs until then...

David -

I found and fixed the page fault. Thanks for reporting it!

Mark

Yeah, I figured there'd be bugs in the aldl editor. Not sure whats crashing the aldl com tool when selecting other tabs. Only thing I can think of is that you have a corrupt version of riched20.dll in your windows/system (or windows system32) directory. Can you download the dll from the tunerpro sit...

Yes, I will be adding the ability to copy a table to the clipboard (tab delimited) such that you can import it into excel/winaldl. I'll also be adding the ability to "print to file".

this is a negative side effect of the ECU file format being in "public domain". That is, anyone can create one, mistakes and all.

The best thing to do is find a well commented hack for your code mask (what code mask are you using, anyway?) and verify things for yourself.

Mark

not yet. this is planned, but i haven't gotten around to it yet. i'll be working on that next. i think every datastream with a MAT needs this. =(

ps - look for a release this weekend with the datastream editor.

All depends on the ECU file you're using. The 6E ECU included, you disabled the checkbox entitle VATS. OPen the item comments toolbox (F10) to see if there are comments associated with the flags. If not, you'll hae to consult the hack to see what the other flags are for.

Thanks! Do you know what ALDL Datastream ID the $58 code uses? I could write up a definition for your really quick.

If you do end up buying an AutoProm, be sure to let me or craig know that you already have a registration key. This will take $30 off the price of the AutoProm.

Hi Dig -

Thanks for the suggestions. Your first suggestion is "on the list" already. Your second - this is a big one, but t is planned. I need to move away from the ECU file format first.

oh. sorry.

click the email button below.

please do.

Hi guys. Its been a while since the last release (6 weeks!). Craig and I have been working hard on the AutoProm, but I've been working hard on other features of TunerPro as well. Lots of new stuff in this release. Lots more coming in the next release. Download version 3.03 at [url]http://tunerpro.ma...

Makes sense. That'll teach me to keep my nose out of area's of which I have little understanding.

Hopefully someones else knows the answer to your question. If not, the thirdgen.org boards are a *great* place to get this answered.

Mark

injector flow rate for $58 codemask is at offset $328.

For gallon/hr, multiply the value by 0.032614. You should be able to figure out lb/hr from there.

nope, not in there yet. been suggested a few times. this is on the long "features to be added" list. =)

[quote="Bill usn-1"]Bummer,
I really want to start using you program. I like the idea of using 1 program for logging and RT tuning.[/quote]

yup. sorry. so many combinations out there to support, so much time in a day.

yes, eventually. changing the exntension won't work. in a few weeks I'll be releasing a version of TunerPro with an editor to create your own data stream definition. You'll use the files you found to create a definition for tunerpro. however, 160 baud won't be supported for at least another 2 months...

ah, so the vortec code bases use multiple checksums? i see now. thats a different problem altogether. TunerPro does not support this kind of thing yet, but is planned a number of months down the road.

You only checksum the block that contains the chips binary information. you don't checksum the entire chip. so if your car uses a 16k chip, you only calculate the checksum for the 16k that the car uses ( $0008 through $3FFF ), even if the binary information lives in the highest memory block of a 29F...

Chris - So your checksum should be calculated from 0x08 through 0x7FFF. I'm not sure what you mean when you say that you compare several files and one of them gets corrected in $8000. in the case of GM, a single checksum should be used for the entire block of memory from just beyond the checksum its...

the next version will have unlimited bin size.

your english makes it a little hard to figure out exactly what you're saying, so if you prefer to write in spanish, feel free.

I'm unsure what exactly you're trying to do, but GM checksums are usually the LSW (least significant word) of the sum of the bytes from just beyond the checksum itself to the end of the bin. if your checksum lives at offsets 6 and 7, for instance, then checksum is calculated from offset 8 through th...

=) nah, I'm not a hitter.

I'm going to add a separate dialog box for the rom to file feature. it will be more intuitive and less technical. Basically, you'll select the bin size and the device type (romulator/autoprom) and it will auto-export.

m

The "dump from emulator to file" feature is a little more advanced. You're doing something a little different than what TC or GMPCM do. Thanks for understanding. Also, if you're emulating, whatever you have loaded into TunerPro should be identical to what is in the emulation buffer (unless...

none, unfortunately. i've been working on aldl data logging (to/from file) for the next release. i intend to have the datastream editor in place for the release after that. (2-3 weeks away if everything goes well). i know you need it in order to make use of ALDL data logging/monitoring for your appl...

I'm confused. So, you loaded your bin into tuerpro, opened the emulation toolbox, uploaded the bin to the emulator, made changes, and then wanted to dump the emulator ram to a file. so you inputted the addresses in the emulation toolbox and hit Exceute (Rom to file). questions: did you input the cor...

I'll fix this for the next release.

next release. i've got it working nicely so far. =)

If you're talking about the ECU, yes, its as simple as modifying the ECU Item in question with the correct factor/offset to convert the voltage to BAR (or whatever). If you're talkinga bout the ALDL 730 datastream definition, yeah, I'll take care of this for you. You're the second person to ask for ...

Does this contain Jon's fixes?

yes, please.

a ways down the road, yeah, i plan to do "auto-tuning" stuff. have a number of fundamentals to get into place before that can even happen though. regarding the autoupdate, currently you need to click the update button in order for the emulator to be updated. adding full-on autoupdate would...

also, in the ECU, bitmask generally allows you to specify how many bits you want in the item. It only applies to flag and should *always* be set to 80.

I believe their exponential scaling factor is the equivelant of mult,div, bit in the ECU. when their exp. sc. factor is set to -1, that means divide (x^-1 = 1/x), which the same as setting mult, div, bit to "1" in the ECU (0 = multiply, 1 = divide, 2 = bitwise). so, I can (almost) guarante...

freudian clit? i mean, slip? isn't that when you say one thing but you mean your mother? i mean, another?

=)

thanks! I'll fix that.

see your other post about the ALDL def.

see here:
http://www.supportfitness.com/tunerprof ... c.php?t=52

TunerPro User Forum

Search found 1925 matches

TunerPro Free & RT v3.03 now available!