TunerPro User Forum

I've e-mailed you what I have got, it's not got a great deal defined but it's a starter.

The Y axis (row) of the 'Fuel Startup Table' (aka FN1306) table is seconds (since start).

If you have the 'Table Editor' window open (press F9) whilst viewing a table it shows the axis labels.

Version dated 10/01/07 now available.

Version dated 10/01/07 now available.

Version dated 09/30/07 now available.

Version dated 09/30/07 now available.

Version dated 09/30/07 now available.

Version dated 09/30/07 now available.

Version dated 09/30/07 now available.

Version dated 09/30/07 now available.

A couple of related threads that might help;

http://tunerpro.net/forum/viewtopic.php?p=2308
http://forum.tunerpro.net/viewtopic.php?t=524

Is this with 4.14.0365.00?

Is this with 4.14.0365.00?

There's a xdf for the 1993 LT1 on the definitions download page so I would guess yes (but it is only a guess

)

I suspect that the Burn1 cannot produce the 25 Vpp and 21 Vpp the 2732 and the 2732A need for programming respectively. The chips the Burn1 can handle all need lesser programming voltages. Maybe it can handle a 2732B or 27C32 as I think they only need 12.5 Vpp. This is definitely a question for Crai...

Version dated 08/28/07 now available.

Version dated 08/28/07 now available.

I don't any experience with them other than I know there can be multiple checksums using different calculations. Bit of an old link but it may be of use http://www.andywhittaker.com/ECU/BoschM ... fault.aspx

Which ecu type?

Gunnar wrote:Ah, so a 256kb bin file is 40000 and a 512 is 80000 then ?

Yes, 256kb = 266752 bytes in decimal = 40000 bytes in hexadecimal.

You need to specify the bin size in the xdf header. Press 'cntrl +F2' to access the XDF header editor and enter '40000' in the 'Bin Size (hex)' box.

It's good to see someone trying another ecu type

From your other post I see this is sorted

No worries, we all make mistakes when learning something new

Possibly, I couldn't say for sure though.

Any use for the VN? http://www.techedge.com.au/vehicle/aldl160/vn_aldl.htm

I'm presuming you are using the T23B xdf and you have a 8UA, LA3 or LB3 ecu here; I expect your bin size isn't correct for the xdf. See http://forum.tunerpro.net/viewtopic.php?t=530 for more about this.

Is the 'address tracing' functionality of the new Ostrich 2.0 on the cards for TunerPro?

'Paint' is bundled with Windows and usually found via the Start>Programs>Accessories menu.

Anytime

If you have any questions, just ask.

Email sent

That's a CCAQE strategy and I'm afraid I don't know of an xdf for it. I do have a spreadsheet with some 100 odd parameters defined, you could use that to make yourself an xdf if you wished.

Hardware wise see www.moates.net

What's the ecu's 'catch code'?

Version dated 07/03/07 now available.

Version dated 07/03/07 now available.

I don't know if this applies to your set up but I just recently read something I didn't know about A9L / A9P loom issues; http://www.corral.net/forums/showthread.php?t=540841 Also, the board can suffer failure between the VSS and BAP sensor traces shorting. This is meant to be obvious from looking a...

Awful lot of sensor/actuator related errors there, are your voltages OK?

Craig Smith wrote: the start address in the Hex. I have it set at 03000

Is this a typo? The start address for the F2 and F3 adapters is 0x30000 for the eec-iv when using a 64k bin.

No need to feel stupid, we all have to learn about the way the eec works (and it's quirks :) ). These things aren't always obvious but the strategy document helps immensely. AFAIK there isn't really anything else that has the same kind of detail and the forums are often the best place to get more he...

The result from this table lookup is multiplied with the result of the 'EGR Altitude Table' (aka FN908B) table lookup. The resultant value is then added to the result of the 'Sea Level Multiplier vs BP' (aka FN212A) table lookup multiplied by the result of the 'EGR Sea Level Table' (aka FN908A) tabl...

Something new learned

I didn't know the bin stacker tool could do that.

It's another 89-93 5.0l Mustang ecu that uses the GUFB strategy.

There's an A3M1 and an A9L on Ebay at the moment, it might be worth messaging the vendors to see if they'll end the auction early.

I've got no idea why it would have changed, have you used another binary editor or a Tweecer?

I use HDD Software's Hex Editor v2.0 to 'pad' the first 8k of a bin with null data. Open the bin with the editor and under the 'Edit' drop down menu there is a 'Insert' option that allows you to insert zero's at the current cursor position.

Reply sent, it looks like a lack of 'padding' in the binary.

Email me your binary and I'll see if I can spot anything.

I'm not sure what's gone wrong so I've emailed you the last xdf to see if this will work. Keep me posted please.

Nothing major has been changed, the GUF* updates usually consist of the following; The odd new item found (often something that no one is ever going to use but added for completeness :) ) Maybe a parameter name change to more accurately reflect what the item does A description added or updated (it's...

Yes, DOI3 is the catch code. ODAL1 is the strategy, not one I myself recognise.

I suspect you might be out of luck for a xdf but what's the catch code on the ecu just in case someone has one?

Version dated 05/28/07 now available.

Version dated 05/28/07 now available.

Version dated 05/28/07 now available.

Version dated 05/28/07 now available.

Version dated 05/28/07 now available.

Version dated 05/28/07 now available.

Whilst the high bit of a signed byte is used to signify whether the number is positive or negative it's not simply a case of toggling it to change the value from positive to negative and vice versa. To convert a number to negative perform NOT and add 1 To convert a number to positive subtract 1 and ...

Read this http://forum.tunerpro.net/viewtopic.php?t=530

Hopefully this will sort you out

It's the air mass flow through the throttle body when the butterfly is closed against the idle stop screw and the ISC dutycycle is 0%. This value is used by the eec to determine the ISC dutycycle required to meet the calculated desired idle air flow.

I'm not at home at the moment so this is from memory, I think it's under the 'hardware' category. If you use TunerPro's search function you'll be able to find it straight away.

TunerPro User Forum

Search found 615 matches

Ostrich 2.0 address tracing question