OFT v2.06 Non-Beta

[akyp]

Originally Posted by steve99

Shiv,s 2x tunes are much better knock wise and i pulled a bit of timing in problem areas for 98 ron fuels so the amount of fbkc or flkc will b verry little hopefully

I am getting a fair bit of flkc during aggressive driving: http://www.datazap.me/u/akyp/20140904
It happens mostly when lifting off before a corner, or modulating the throttle for the corner exit. No flkc at all when going wot on a straight road or normal urban driving. Did some reading and seems this is not severe enough to bother, it is probably too hot for the ECU to be 100% happy anyway.

My LTFT is also a bit over the place compared to a log I made in April. Could also be the weather but I notice v2.0 has a new MAF scaling. I may just have a crack at scaling the MAF myself when it's not so hot out there.

[steve99]

Originally Posted by akyp

I am getting a fair bit of flkc during aggressive driving: http://www.datazap.me/u/akyp/20140904
It happens mostly when lifting off before a corner, or modulating the throttle for the corner exit. No flkc at all when going wot on a straight road or normal urban driving. Did some reading and seems this is not severe enough to bother, it is probably too hot for the ECU to be 100% happy anyway.

My LTFT is also a bit over the place compared to a log I made in April. Could also be the weather but I notice v2.0 has a new MAF scaling. I may just have a crack at scaling the MAF myself when it's not so hot out there.

to me it looks like you on the throttle and load increasing when you get the knock

It looks like it was hot as the oil temp is running to almost 250F , you have not logged IAT but I suspect it may be 90+F

You might want to try making the IAT vs ignition retard tables a bit more aggressive if your already on the 98RON MAP I did. The knock its not that bad but its pretty consistent.

This is what I am using I did not put the temp compensation changes in the maps I posted

[Shiv@Openflash]

Hi guys,
Looks like the proposed map released date also coincided with a new firmware release (v1.29) and a new OF Manager software version (v1.10.4) that should be available for download later tonight. So to keep to many updates from happening all at once, I'm going to be pushing back the release date of the v2.06 maps until tomorrow

This also means that ll new OFT orders that came in over the weekend should ship tomorrow with the v2.06 maps preloaded in them.

Cheers,
shiv

[benlaz88]

Originally Posted by Shiv@Openflash

Hi guys,
Looks like the proposed map released date also coincided with a new firmware release (v1.29) and a new OF Manager software version (v1.10.4) that should be available for download later tonight. So to keep to many updates from happening all at once, I'm going to be pushing back the release date of the v2.06 maps until tomorrow

This also means that ll new OFT orders that came in over the weekend should ship tomorrow with the v2.06 maps preloaded in them.

Cheers,
shiv

@Shiv@Openflash Awesome, can't wait when its receive!!

[cookiesowns]

Originally Posted by akyp

Probably just my unit then.

On another note, I've been able to log IAM and FLKC with my 700G ROM for some time, still no FBKC though.

Same issues here, but on D00C :/ Unable to log IAM, FLKC, and FBKC.

[Shiv@Openflash]

Originally Posted by cookiesowns

Same issues here, but on D00C :/ Unable to log IAM, FLKC, and FBKC.

Has your OFT updated to the new firmware (v1.29)? If not, connect it to OF Manager and let it update. Then connect OFT to ECU and go to Configure channels and then press the right arrow. This step is important as it updates the new changes to the datalogging protocol. Then see if you can log those channels successfully. I know we have made changes to enable logging for FLKC and IAM. If those work as they should, we can enable FBKC next.

[solidONE]

Originally Posted by Shiv@Openflash

Hi guys,
On Monday we plan to release the first non-beta version of our v2.0x maps. With this release we will add support for all the other Cal IDs that are currently not support with our v2.0x beta maps. We will also disable the U0155 code (as we have always done before in our non-beta map releases). This code/CEL is triggered the OFT is disconnected from the OBD2 plug in the middle of communication (datalogging, data displays, etc,.) It's harmless but annoying nonetheless.

In additional to releasing the new maps in non-beta format, we will be preloading all OFTs with v2.0 maps prior to shipping. So now there will be no need to manually upload the v2.0 maps using your laptop. For those who already have OFTs, we will also be releasing the database file (.dev) that will auto generate all compatible v2.0 maps for you. But by now you've probably already loaded the v2.0 maps you needed anyway

If there is any other suggestions you have with regards to beta->non beta changes, let me know and I can look into implementing them.

Cheers,
Shiv

PS. The sales team is also running a sale: http://www.ft86club.com/forums/showp...0&postcount=21

Where do we go to disable U0155 if we are running an modified v2.0 beta? I cannot seem to find it in the Rom Raider Defs. It's not under 'Diagnostics Trouble Codes' folder.

[solidONE]

Also, would disabling this U0155 code prevent the car from going into limp mode if the connection between OFT and the ECU at the OBD port goes bad for whatever reason (usually because of my right knee hitting the cable, I think)

I've had my car go into limp mode may times while in a middle of logging and triggering a CEL, so I've been afraid of logging with the OFT on track. Typically it's between the U0115 code and some other code I cannot remember off the top of my head.

[lucid215]

Originally Posted by solidONE

Also, would disabling this U0155 code prevent the car from going into limp mode if the connection between OFT and the ECU at the OBD port goes bad for whatever reason (usually because of my right knee hitting the cable, I think)

I've had my car go into limp mode may times while in a middle of logging and triggering a CEL, so I've been afraid of logging with the OFT on track. Typically it's between the U0115 code and some other code I cannot remember off the top of my head.

Mine has been doing the same thing but when I hit a decent bump

[JB86'd]

The other day I lost and gained connection a few times in quick succession, and my car threw a U0xxx code, and my tachometer was stuck around 6000 rpms, with the car off, started the car and it stayed there..so I turned the car off and cleared the code with my Scangauge, since the OFT said no codes. I then disconnected my battery and reset my ECU and all went back to normal. Just about shat myself though. Found out my OBD2 port was bad, got a 30cm extension cable and all is good.
Anyways, to disable this from happening again I'd need to modify the map in romraider and reflash?

[solidONE]

Originally Posted by JB86'd

The other day I lost and gained connection a few times in quick succession, and my car threw a U0xxx code, and my tachometer was stuck around 6000 rpms, with the car off, started the car and it stayed there..so I turned the car off and cleared the code with my Scangauge, since the OFT said no codes. I then disconnected my battery and reset my ECU and all went back to normal. Just about shat myself though. Found out my OBD2 port was bad, got a 30cm extension cable and all is good.
Anyways, to disable this from happening again I'd need to modify the map in romraider and reflash?

Yup had that happen many times as well. CEL on and OFT detects no code.

[JB86'd]

Originally Posted by solidONE

Yup had that happen many times as well. CEL on and OFT detects no code.

It only detects engine related codes so that doesn't surprise me. Just don't want this to happen again.

[steve99]

Originally Posted by JB86'd

It only detects engine related codes so that doesn't surprise me. Just don't want this to happen again.

disable code U0155 in romraider and reflash its comms fail to instrument panel , can cause limp home mode as well

[solidONE]

Originally Posted by steve99

disable code U0155 in romraider and reflash its comms fail to instrument panel , can cause limp home mode as well

Where is U0155 located in the defs? I could not locate it under 'diagnostic trouble codes' folder.