TunerPro User Forum

Not all ALDL modes are supported in some ECM's. The $74 mask I'm currently looking at only supports Mode 0, 1, 2, 3, 4, 7 and 10 requests. In this ecu responding to the F97 ALDL polling message is sufficient to stop the "normal mode" broadcast messages. The "normal mode" broadcas...

The FAZ3 bin file cannot be run on a CDAN4 strategy ecu as it requires twice the memory the CDAN4 hardware has.

You can use the HYY1 bin on the JPA1 ecu.

It may be worth listing the vehicle(s) the Bosch 0 261 200 011 is used on and which Motronic version it runs. Someone may recognise those rather than the part number.

Is that ecu OBD-II? If so, you would need the OBD-II plugin and an OBD-II .adx.

There are quite a few .adx files on the TunerPro definition download page.

Tunerpro V5 uses .adx definition files for the datastream. You need to select "Import Definition" rather than "Load Definition File" when trying to open a .ads definition file.

It's better to create these types of items as a "Flag/Switch" when inserting them as a new XDF parameter rather than as a scalar.

Have you opened the bin file in a hex editor program to check whether it is a valid read?

.xdf and .bin files http://www.tunerpro.net/downloadBinDefs.htm#GM

You can use the ROUND function to round a number to a specified decimal place.

Is the 6411 value in hexadecimal? If so, when you divide by 4096 (in decimal) the quotient will be equal to the upper nibble (i.e. the leftmost character). Depending on how the PK2 code treats the remainder you will probably need to round this up or down to zero decimal places.

Does the chip you are programming have more memory than the ecu's stock chip? If so, are you offsetting the bin file when programming the chip?

Sorry, no, I already have too many other things that occupy my time.

There's no way of doing it that I'm aware of. If you think SARCHG is a hassle wait until you find others like NUMEGO with 40 plus locations.

You need to create a scalar for each memory address.

The PROM code usually has four letters too.

Are you sure the part number is 16128261? I ask because it's coming up as an ESC module in search results rather than an ecu.

Listing your PROM code and engine size may help someone identify your ecu.

If you have a comprehensive definition (i.e. one that is well developed with regard to the number of parameters exposed) then you can easily tune for modifications such as turbocharging. Creating a definition involves more than finding the address of a parameter, you also need to define its characte...

The attitude of some of the users and moderators on FEOA has killed off any interest I have in further working on the Escort ecu's so I am not able to help.

Hi Aaron, you've already emailed me directly about this

Regarding copying parameters from one tune to another, if they use the same xdf then you can use the compare feature to have both bins open at the same time.

If your binary file is 32k and the'7427 uses a 64k rom then that's your problem. Either the chip you have is only mapping half of the rom to the ecu and using the OE rom for the other half or you are only reading half of it.

You may need to offset the binary file when writing to the chip, for more detail see http://support.moates.net/programming-c ... g-offsets/

From the drop down menu select "XDF" and then "View/Edit XDF Header Info". On the checksum tab you can create checksum calculations. Use “Save” or “Save As…” before pressing the “Upload” button so that the checksum gets updated along with any changes.

Are you using an xdf that has a checksum calculation in it? This could be changing the first two bytes in your bin file.

Some eeproms (for example the 27C32) require the use of the Moates SocketBooster for emulation to work.

The date and start time of the datalog is included in the export of the datalog so if your datastream has the engine run time included in it you could create a timestamp for each entry using a formula in Excel.

Whilst a J2534 pass through cable is easy to obtain you need the software too. Also, the dealership software might use a proprietary file format for reflashing.

Even with a definition unless the J3 issue can be figured out you may have difficulty re-flashing the ecu if the protocol if different to the Ford one and there's no tuning s/w that supports it.

Seems odd to have a J3 connector and it not be functioning. That said, they've also etched a lot of the chips to hide their markings

This is the usual way: http://web.archive.org/web/200703240357 ... clinks.jpg

How is it disabled? Some eec-v ecu's needed a couple of solder pads joining together to use the J3 connector.

If you want to do real time tuning you'll need the Quarterhorse otherwise if you are content with just burning chips for the tune changes then the Burn2 combo is fine. To develop a definition you'll need to disassemble the code to try to figure out what's what. I doubt you'll make meaningful headway...

I would be surprised if the Moates gear doesn't work with your Mazda eec-v ecu. Maybe the problem is obtaining a definition suitable for the strategy the ecu uses.

Congratulations on figuring out your problem. A word of warning though about that xdf you provided the link for; it will not work correctly for some scalars. The CDAN4 strategy is one of those fun strategies that hard code certain scalars within the code and you need to change the value multiple add...

Is the J3 port clean? They usually have protective grease over a conformal coating both of which need removing.

That was my only suggestion. Hopefully someone with more knowledge will be able to help.

You need to convert the .ads into .adx format; see http://support.moates.net/tprtv5-ads-to-adx/

You do not need a .xdf if you are only reading the live data.

As asked above you need to say which xdf you are using (there's a lot out there). Your ecu 'catch' code would be useful to know too.

Earlier eec-iv EFI/SFI prefixed hardware tends to support different strategies. The later SMD/E/O prefixed hardware gets used differently. I'd guess this is because manufacturing techniques changed allowing easier tweaks to the board design resulting in far more numerous hardware variations througho...

The W2E1 uses EFI-MA35G hardware, hence my doubt about it using the same strategy as the LAG0 ecu.

W2E1 is not a strategy, it's the catch code of an earlier eec (naming like this is sometimes done to recognise common ecu's when the strategy name is not known). I doubt your LAG0 ecu is the same strategy as the W2E1 as I have it listed as being the same as the ANY1 ecu which uses the later EFI-MA46...

Hmm, yesterday I downloaded 8414 but today the link is for 8383....

The RT version downloads 8414 (I have not tried the base version).

http://www.tunerpro.net/downloadBinDefs.htm

OK, the rpm header is fixed now. The deg C issue remains though.

The definition is correct AFAIK.

I cannot copy the error report contents (Windows will not let me) so I have sent you a copy of the log that gets sent with the Windows error report.

The Visual C++ Redistributable Package for Visual Studio 2013 is already installed on this particular pc. Following XP SP3 installation I get a different error now; "error signature". Deleting the TunerPro setting .dat files did not appear to affect anything. I know what you are saying abo...

In the same boat here, I get a similar error message stating "The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link library KERNEL32.DLL." Uninstalling and reinstalling the previously working version (8200) gets me back to a working version. Runn...

Search found 614 matches