NefMoto

I can't find TVUB values for these injectors.

I think its "AMU" engine, but i'm not sure.

If someone knows them or can pull them from stock ECU, i would appreciate that. WinOLS definitions/TunerPro definitions + bin works too.

I had  0280157012 193g/282cc   (blue) installed earlier, stock value for those are (on Porsche ECU) :

6,8,10,12,160
3.2840,1.816,1.1880,0.8240,0.4400

Search ASM based map locator on here. It’s a thread started by PRJ. It’ll find the location of tvub so you can fairly easily find it if you are able to get ahold of the stock file that those injectors came from.


Sent from my iPhone using Tapatalk

What? 5 cylinder 1.8T? what are you talking about man.

Oops, my mistake. Been around my Volvo too much...

I assume you mean "Me7Romtool". I have that, didn't work for my ECU but surely it could work for this case. Thanks for the tip.

No that is a different thing, 360's program works basically on all  me7 ECU's btw. The map locator he's talking about is made by prj, should be stickied in one of the subforums.

Ok thanks, i look into that. 360's me7romtool couldn't find/locate anything at all from my ecu binary. Tried some other rom files too and none of them worked (they were all r32, vw ecus). It did work perfectly on "ferrari 360 challenge" test rom that was available. Not sure why.

I know this is an old thread but I thought I would try it on the latest (yet to be released) version of my tool.  Its now supporting Volvo roms too.

Source file was 'Volvo_S60_T5_Stage1.bin'

I searched for KRKTE and TVUB.. Here's the output for anyone still interested.



-[ TVUB Battery Voltage Correction () ]---------------------------------------------------------

>>> Scanning for TVUB - Fuel Injection time offset in ms (compensates for fuel injector latency)

Found signature @ offset:0x0005684E
TVUB_XNUM       @ File-Offset:0x3f8c (seg=0x0000 [segadr=0x0] val=0x3F8C)
TVUB_XAXIS      @ File-Offset:0x3f8d (seg=0x0000 [segadr=0x0] val=0x3F8D)
TVUB_CELLS      @ File-Offset:0x3f92 (seg=0x0000 [segadr=0x0] val=0x3F92)

TVUB discovered @ File-Offset:0x13F8C

    Long identifier:           Fuel Injection Battery Voltage Correction.
    Display identifier:
    Value:

 No.           |        0        1        2        3        4
            PHY|   8.0256   9.9968  11.9680  14.0096  15.9808
            HEX|     0x72     0x8e     0xaa     0xc7     0xe3
            ADR| 0x13F8D 0x13F8E 0x13F8F 0x13F90 0x13F91
 --------------+---------------------------------------------
            PHY|   2.1888   1.4784   1.0560   0.8064   0.6144
            HEX|    0x2ac    0x1ce    0x14a     0xfc     0xc0
            ADR| 0x13F92 0x13F94 0x13F96 0x13F98 0x13F9A


    Cells:
      Unit:                    ms
      Conversion name:         tinjection_sy
      Conversion formula:      f(phys) = 0.0 + 0.003200 * phys
      Data type:               UWORD
    X-axis:
      Unit:                    V
      Conversion name:         spg_ubatt
      Conversion formula:      f(phys) = 0.0 + 0.070400 * phys
      Data type:               UBYTE


-[ KRKTE Airmass to injector 'on time' conv. based on inj size & fuel pressure]-----------------

        Calculation of constant KRKTE:
        ------------------------------
        rho0Air  = 1.293 [g/dm^3]  (0 Deg C and 1013hPa)
        Vhzyl    =         [dm^3]  Displacement of a cylinder in dm^3

        Lst      = 14.7 AFR        Air/fuel ratio for Lambda = 1.0
        Normmk   = 0.00001667      min/ms Adaptation of units
        Qstat    = g/min           Valve constant with n-Heptane
                                   1.05 Valve correction for petrol/n-Heptane

        Calculation:
        ------------
                                 rho0Air [g/dm^3 ] * Vhzyl[dm^3 ]
              KRKTE [ms/] = --------------------------------------------------
                             100[] * Lst * Normmk[min/ms] *1.05 * Qstat[g/min]

              KRKTE        = 50.2624 * Vh / Qstat

>>> Scanning for KRKTE Lookup code sequence...

found needle at offset=0x5680c
KRKTE           @ File-Offset:0x1981b (seg=0x0006 [segadr=0x18000] val=0x181B)
0x2d (0.0960 ms/%)

All the problem was with the search mask, it was too specific. Relaxing it by masking out registers, etc. makes it work across a much wider span of ecu's. Seems to be working on tonnes of models and firmwares these days, any that I try it on infact.
 

BTW a workalike to ME7Info would be extremely helpful ... finding torque path and timing path RAM variables would be extremely helpful