any notice of the 94170008?

thanks

 

upgrade to 15

 

why make tephra do more work when you can easily just switch to a new rom version....with no side effects.

 

96530006 is UP

Please treat it as untested - so usual precautions

 

explain your setup? do you have a rear 02 sensor plugged in? if not have you done the rear 02 resistor mod.

it is recommended that you DO NOT to the FAA bit mod for rear 02... That will just screw up the Tephra/MrFred rear 02 simulator...

 

hrmm not yet.. Its hard merging patches together

Maybe next release...

sorry for not replying earlier

 

how can i do that? just write to the ecu the new version and thats all ? or what?
wich version do i need to put

let me know

thanks

 

if you are using 94170008, you can run 94170015 - just copy your x08 maps to the x15 V5.10 ROM, including:

* copy your immobiliser
* copy and tuned maps (ie injector scaling+latencies+fuel+timing+boost maps)

IF you havn't tuned a map (eg Acceleration Enchriment) and it appears different in the new rom - DONT OVERWRITE IT... chances are your definitions are incorrect.

 

thanks tephra

i will do it

 

Tephra, I do not have a rear o2 sensor plugged in. I am currently running my wideband in its place. I have done the rear o2 resisor mod (75 ohm 10W) which was working with V5. I'm not sure why I'm only getting the CEL with the new V5.10 88590015?

 

Hi Tephra,

Just wondering if ID 93660005 is on the cards for release? I'm up and running as you know, but given the choice I would move back to the original ID...

Thanks,

j3llyh34d

 

Jelly - we had problems with 93660005 initially - I might revisit it later

Krazy - did u do the FAA bit on either V5 or V5.10? What is P0037 anyways? I havn't got scantech on me atm

 

For those that haven't managed to do it, I have edited the xml's for 90550001 v5.10fix and uploaded them on the orignal post on page 1 of this thread

 

Typical!, just finished and about to test......

BTW, should the line.... <scaling name="OffsetWGDC" unit...... have an endian of "little"?!

j3lly

 

Not sure, I would guess at yes. It was working fine for me how it was.

But I have now updated all endian to endian=big