Monodax

[EagleMark]

I've never participated much there so maybe someone who has can post a link?

Here's is the TIS Cal lookup:
http://tis2web.service.gm.com/tis2web

[1project2many]

I renewed an old thread on PP about my 302. Maybe it's time to update it.

I found a copy of MXScan on moates.net but it won't connect to my old TC cable. Well, it will in the test area but nowhere else. Disappointing. I switched to the freeware UVScan and after changing comm speed and setting the COM port in the INI file it worked just fine. Maybe I'll try TP / Scanner Pro as well. With John Prevost working on it also, two heads might make a fair amount of progress together.

Now as far as OBDII tuning / programming with TP, what's the deal? Is it mainly the read / program part that's an issue? I know there can be multiple checksums in an OBDII cal but is TP able to work with that?

[RobertISaar]

why TP can't support it natively? yeah, i'd say the read/write process would be it, since it can be different for each OS. and there are a LOT out there to support. it probably wouldn't be too bad to get a single program to work for nearly all applications, but not a lot of people want to tempt fate and erase the OS section.... they avoid doing anything but writing to the calibration section, since if the flash goes bad, they won't have a bricked unit.

as for the checksums, if you can write C++, you can make a checksum plugin to deal with it, otherwise the stock checksum module won't handle most of it. the 97-~03ish 3100/3400/3800 V6 stuff? only has a single 32-bit checksum, but it's located in an area where the processor adds up every byte before it and every byte after it, then compared it to the stored checksum. TP doesn't natively support what is essentially skipping over an address. that's actually the same reason i haven't attempted to pound out a full 93-95 northstar XDF, it does the same thing. i tried to make a plug-in, but looking at C++ makes me feel like a child doing brain surgery.

[EagleMark]

Writing file through OBDII is the issue, need a converter box like AVT 852 which are available for sale.

I tested an ADX file made for AVT cable today that dimented247 is writing and he said it would not work on his truck but it worked fine on mine.

Look at sticky in TunerPro OBDII section for link to dimentred247 XDF files for TunerPro. They work great with a RoadRunner...

There are already several LS1 ADX files done either Elm or AVT...

[brianko]

I have an AVT852 as part of a tuning package I have...there are drivers available? Some links would be great...

[EagleMark]

Not drivers but ADX files for Data Logging to TunerPro RT.
http://www.gearhead-efi.com/Fuel-Inj...TunerCat-OBDII

[1project2many]

TC OBDII handles read / write the same way as the LT1 using a separate program to handle data transfer. I think that's a reasonable approach when using the TP "user supported" model. Imagine the complaints if a malformed definition file got out there and a bunch of pcm's got bricked. Who's at fault? Who pays? Ultimately TP could become known as "Junk" because of a user error. No, it's better for newbies and hacks not to be mucking about in the flash program.

I've written some C and C++ code but most of what I know is not Windows programming. So writing a "plugin" is something I'll have to research. As far as coding in C, don't be intimidated. In most cases it's far easier than hand coding in assembly. Like any language, it's all about knowing the rules and how to manipulate within them to do what you want. C and C++ tend to be very open ended IMO and very, very flexible. Visual Basic, OTOH, not so much fun. :(

Mark, I'll look at those files and I'll probably see what JP is up to as well. I love doing this stuff... I just don't ever have time any more.