I have nothing to offer to your search and am hoping to vulture information. I'm sorry.There, somebody is actually sharing their chip data:
And that mx6-mod2.bin works fine, just needs 0x52B1 changed to FF for boost cut.
Today when I asked to buy .bin instead of physical chip someone said "We do not provide bin files to the public ". I am not your fu**** public.
Another seller wants a price for the chip the same as an equipment needed to create it I better buy an Ostrich 2.0 instead LOL.
And the saddest thing is, none of the sellers are the actual creators of the tune. Just reselling copies.
If things gona stay that way. I will get that chips anyway, and release the bin's to the public.
You not only need an eeprom programer, but an emulator also if you want to not just edit a rom on software but to also be able to tune in real time, and to try to figure out which hex address does what.I looked into buying an EEPROM reader/writer but the cost was high and I have no idea how to interpret programming...
Well maybe... I am not certain for this model of ECU, but for If I remember correctly, 4AGE ECUS, people just overclocked them. I think by changing the quarz crystal (not shure it's name in english. oscilator maybe). And for the ecu the engine apieared to work slower. An effect was that max RPM limit raised, but with a bit of side effects. Maybe you can just move ignition and fuel map values per one cell to the lower rpm ranges then to compensate. Just wondering.I would kill for some 88-89 Aspec chips with boost cut removed, closed loop o2 sensor control raised from 3000 to 3250 rpm and red line raised to 6500.
But there is probably no programing for closed loop o2 reading above 3000rpm and there are probably no fuel or timing maps programmed above 6250 rpm.
Is there any way of making the ECU read 250rpm = 0 rpm, 251rpm = 1 rpm... without it screwing up ignition timing
Does anyone found out more parameters than the two maps and the boost cut? I read everything what could find in this forum, but all the links are dead, no more pictures, or the old users that used to tune this ECU. Nothing.I use an Ostrich 2.0 to emulate and cell trace with TunerPro RT. As there is no ADX definition you can't do logging, but the tunerpro cell trace is useful.
Some of your scaling and table start locations are off, but you've made a good start. I've been working through the maps on and off for about the last 8 years, but I haven't had access to my car for the last 5 years due to moving interstate and the car is in storage, so progress has been slow.Besides the obvious two big maps, in a stock rom I also found 4 small maps, but don't know what they do.
View attachment 14093
17x7 starts at 765A
View attachment 14094
17x9 starts at 7769
View attachment 14095
9x7 starts at 7400
View attachment 14096
8x4 starts at 70BA
can anyone test these? or maybe already know something? I dont yet have an emulator.