TunerPro User Forum

The Moates Ostrich 2.0 is an 8 bit emulator (it can emulate 27C256 EPROMs) and it cannot read or program chips.

Try installing the Visual Studio 2017 redistributable manually, see this thread:

http://forum.tunerpro.net/viewtopic.php?f=1&t=5100

The ECU cannot tell the difference between an EPROM and an EEPROM as it is only the method of programming that differs when it comes to using the chip.

Emulation is when you use a device to emulate a ROM and allow real time changes to the calibration. It saves having to burn or reflash a chip every time you want to make a change to the calibration and try it out. Personally I would replace the EPROM with an EEPROM to simplify matters by avoiding ha...

If you are using a 27C256 then you will need a UV eraser too. The datasheet for the chip you are using will give the erase specification you will need to select a suitable eraser. Several different Willem programmers will work, there are also the inevitable Chinese knock offs that are cheaper. A Moa...

Which EPROM are you using? Different programmers and emulators work with different chips.

I am not aware of any plugin that allows you to use TunerPro with a Megasquirt. Are you possibly mixing up TunerPro with TunerStudioMS?

Your formula should be:

317736 * POW(X;-2.292)

Note the semicolon instead of the comma.

The main difference is that if you want to do real time tuning then you will need to use the RT version. Here is a summary of the additional features TunerPro RT has: http://tunerpro.net/features.htm

There are some guides here that will help get you started: http://support.moates.net/category/lear ... g_started/

You need to include what definition and calibration you are using for anyone to be able give meaningful help.

For your first question it depends on how the OS is identified in the binary file as to what the best way of displaying it would be. e.g. what is the size of raw data, length, output type etc. For the second question, use a flag to toggle bit 2. This will allow you to change the value from 6 to 2 an...

A decimal value of 14 equates to bits 1, 2 and 3 in your flag. To set and unset these three bits you need to set the 'Bit Number' option to 'Use mask' and enter '0x0E' for the bit mask pattern value.

'Transmit Data Reply' might be named differently in the definition you are trying to convert.

Right click on the file and select 'Save Link As...', ensure the 'Save as file type' option is set to 'All Files' and add the suffix '.ads' to the file name.

It depends on what EPROM / EEPROM the ECU uses as to what hardware you need to live map this ECU. Maybe something like the Moates Ostrich 2 would would work, or another emulator.

You set this in the XDF header info (Ctrl + F2).

What ECU are you trying to connect to?

Some compatible hardware is available here http://www.moates.net/ford-19862004-c-63.html

The software depends on what strategy the ecu uses and definition availability.

The TunerPro help file (far right drop down menu) covers most things.

Replacing the XXXX with 8414 doesn't work for me either.

There can be issues with the later builds of TunerPro and Windows XP, see http://forum.tunerpro.net/viewtopic.php?f=1&t=3535

I have run build 5.00.8414 on XP.

What operating system are you using?

The 1226865 pinout taken from a post on the thirdgen forum https://i.imgur.com/ZevSw.png

I am not sure why you are having to rename the file, it should be saved to your pc as '5B6.ads'. Are you saving the webpage rather than downloading the .ads?

If the ABS is using the common OBD-I 8192 baud datastream from a SXR chip then you should be able to datalog it. I think robertsaar posted a list (or a link to a list) of ABS .ads files a while back but I cannot remember for sure.

The command(s) need to be included in a macro and one or both of the 'Manually Sendable' check boxes ticked.

The EPROM type is listed on here https://xtronics.com/wiki/GM_ECU_eproms.html but not the manufacturer (I would not have thought that would have made a difference). The EPROM is probably soldered into a Memcal so you will either have to unsolder it or use an adapter such as the Moates HDR1.

I am not familiar with your 16196395 ECU but usually you cannot read the calibration out from the ECU directly using TunerPro. It is more common to put the EPROM or Memcal (with an adapter) into an EPROM/EEPROM programmer (such as the Moates Burn1/2) and then use TunerPro to read the chip's contents...

You need to provide a little more information such as the ECU's BCC, its mask ID and the hardware you are using to interface with the ECU.

Only the calibration (i.e. the bin file) gets written to your ecu / tuning device.

The crashing is most likely a sign of an error message not being handled correctly (I suspect it is probably a failure to report an attempt to import an unsupported format is being attempted). TunerPro will only import .ecu and .csv definition files for conversion to a .xdf file.

Anything in this thread help http://forum.tunerpro.net/viewtopic.php?t=4608 ?

I think the T23B.xdf is for TunerPro v4 which may be the problem. It's been a long while since anything was done with that xdf so I cannot remember for definite.

The TunerPro help file gives the basics of getting started.

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

TunerPro can handle 16 bit little endian and big endian data, use the 'LSB first' tick box as appropriate.

The W4H0 ecu is for an automatic gearbox vehicle but it can be used on a manual gearbox vehicle if you change a few parameters such as TSTRAT and TRLOAD.

Beware of putting in 0xFF or 0xFD as both seem to cause a bit of a fuss in the processor. One is the code for reset and the other is the code for NOP, they shouldnt be interpreted as code due to their location but both seem to be a problem in some tables. Any issues with using 0xFF or 0xFD in data ...

Are you installing it as an 'administrator'? If not, you will probably need to do so.

Look in the folder where you saved your .bin file.

You need to open the folder that has the binary file in it in order to see the file you want.

The api-ms-win-crt_stdio-l1-1-0.dll appears to be part of the Visual C++ Redistributable for Visual Studio 2015. See here for the update:

https://support.microsoft.com/en-us/hel ... in-windows

MSVCP140.dll appears to be part of the Visual C++ Redistributable for Visual Studio 2015 which is downloadable from here: https://www.microsoft.com/en-us/downloa ... x?id=48145

TunerPro works with versions of Windows newer than XP, the system requirements are at the bottom of this page http://www.tunerpro.net/features.htm

It sounds like you installed TunerPro rather than TunerPro RT.

The emulation option is greyed out because that is for use with a ROM emulator (e.g. Moates Ostrich). You need to use the 'Acquisition' drop down menu item to load the datalogging .adx definition file and the 'Acquire Data (Connect/Disconnect)' button (blue arrows pointing in different directions) t...

Using Firefox, right clicking and "Save Link As" works OK for me. Can you try a different browser?

Which adx / ads are you trying to save?

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

TunerPro User Forum

Search found 614 matches

Re: Best reader/programmer for EPROM chip tuning?

Re: Can't start program

Re: Best reader/programmer for EPROM chip tuning?

Re: Best reader/programmer for EPROM chip tuning?

Re: Best reader/programmer for EPROM chip tuning?

Re: Best reader/programmer for EPROM chip tuning?

Re: cant get anywhere in tunerpro RT help!!!

Re: XDF POW function

Re: New member- Tunerpro versions?

Re: 1993 Camaro Z28 LT1

Re: spark WOT table negative numbers

Re: New to tuner pro, maybe I'm missing these things, but??

Re: ้็How to create xdf in function flags

Re: ADS to ADX conversion problem

Re: .adx definition file download issue

Re: MS42 Live Mapping

Re: How can I put a password on my XDF?

Re: connection to ecu

Re: 1999 f150 read &write

Re: DOWNLOADING BIN FILES

Re: help with initial installation!

Re: help with initial installation!

Re: help with initial installation!

Re: 1985 K10 ALDL