pgmfi.org

i dissasembled the usdm vx .bin
and began snooping around
i am super.noob

so, basically am i getting this right...? :
it uses different chips which makes the entire language sort of different...?
from say a stock p28 .bin
obviously the .bin was able to be pulled...
so there is some basic ability to communicate with the board
(however that is being achieved...???)

so my plans are surmounting to the old.school brute force tuning methods so i can achieve the high mileage and egr control built in to this board & boost:

basically, 1 or 2 high pressure fuel pumps
super fmu
missing link
msd btm (timing)
techedge wblin/out -> ecu
spoon vtec controller

my limitations using this method become:
6291 revlimit
stressing injectors

my big wish is to merely raise the revlimit and datalogging
however i recognize this perhaps isn't a small wall to scale
i found 1998 in the rom on the p07 page
but i didn't find 1997 and i dont know enough how to add it or find the correct address
i think disabling the revlimit altogether would be dangerous
(not sure if my msd btm unit has rpm pills...or another external limiter..???)
i've read many of the mixed results chipping this ecu
and i think i read of someone successfully raising the revlimit
but they were having trouble with vtec eratic engagement

clearly just opening the .bin in crome changes the code by nature...
even if you dont change a setting and try and close the file...
it requests to save (showing a change has taken place)
so yeah...

i tried finding the revlimit routine in the code...
but obviously my understanding of the 16bit little endien conversion is lacking...
if this ecu even uses this method...?

also is there a generic datalogging script i can add in...?
or is this not going to be feasable with this rom under current development...?

so can someone make this happen fairly easily for some 'beer' money / barter....?
or is this past a few hours of work to achieve a working assembled and modified .bin with the raised revlimit & datalogging...?

thanx for any insight
and sorry for my noobness
and sorry2 if you think this belongs in ROM Help !
=)

Couple things:
1. There are two processors. One processor is thought to run the integrated L1H1 wideband controller, one is thought to run the rest of the "normal" ECU functions.
2. You need a L1H1 wideband. You cannot just feed in a TE wblin output.
3. You probably could use the stock honda datalogging protocol. Using the information posted re: stock protocol and the QD1 protocol, you could probably patch the serial interrupt handler to make Crome/Freelog compatible code.

why just the L1H1...?
i've got the 2A0 w/ L2H2 currently
the wblin output is fully programmable
so i dont see why it wont work
but please dont hesitate to enlighten (bitchslap) me if i'm missing something


and i suspect i have to set the checksum routine to zero's before assembly...???

thanx

You need to read more carefully.

"Integrated wideband controller" i.e. it hooks up to the sensor directly, just like your TE.

If you find the checksum routine, removing it would probably be a good idea.

This really isn't a short, small project. At all. I tried to warn you...

oh 1998 is the speed limiter not the revlimiter..doh
the only rom commented in the wiki for revlimit is the p30
it says 1820

when p07 is opened in crome it knows:
revlimit
maps
target idle
vtec coolant check disabled
speed limit says 114 (but its unchecked so theres an issue there)

so i'm assuming the location of these is pretty standard

it's far from standard... each code base is considerably different.. but someone seems to know those locations.. They might not have the correct script actions in place to disable speed limiter, etc...

well somehow crome knows the values...
so its looking them up in the right place
no...?

maybe. Crome just assumes where things are based on things it finds in the ROM. They may or may not be accurate. Tread cautiously.

well...i guess i could run two o2 sensors...one for the ecu and TEwbo2...
or spend a good part of my life evaluating and modifying the ecu...
the oki chips use 10bit DA converters...the TEwbo2 uses either 10 or 12bit...
so i could theoretically remap the input and skip the internal conversion


i'm beginning to think the 303 rom in the wiki is the cali ecu...
because none of the other vx roms open in crome
and i find it strange that those values mentioned above come up at all
it would take significantly more work and understanding (imo) to yank out the rom from hardware in the 5.wire 48state vx ecu...
correct me if i'm wrong...i'd love to know that one of you guys did this...

so for now...
i'm thinking i will live with a low rpm limiter nondatalogging ecu
what a great way to keep my engine safe...
while i spend the good part of my life learning how each chip functions and communicates with each other

anyone got a list of commands used in asm ???

In WIKI or do a search for OKI, 66k or NX500 core....

is anyone interested in digging thru a known working/altered p07 bin file...?
i have got one

money talks. ITB Tools revisions are #1 on my priority list, seeing as they've already been funded and I'm just holding up the show.