[TurboSid]

Go simple and easy. get a cobb v2/v3 and enjoy.

Thats the route i'm taking.

[mump]

Originally Posted by TurboSid

Go simple and easy. get a cobb v2/v3 and enjoy.

Thats the route i'm taking.

This....

will keep you happy for a bit. I have ran the Cobb with my DCIs for a year now and was happy. Now I am back in the urge. Just ordered a FMIC and as soon as it gets here, slap that bad boy in and I will be contacting PTF to get my Cobb tuned.

Getting ready for spring and back up to Nurburgring...

[09BMW335i]

Originally Posted by LMB335IS

JB4 has worked perfect for me. I need to find a cheap Cobb to get the backend BMS flash though, but it's a beast on E40 as it sits.

you can use the BT spend 175 and get a BMS flash from the website depending on yout needs

[LMB335IS]

Originally Posted by 09BMW335i

you can use the BT spend 175 and get a BMS flash from the website depending on yout needs

Now you can. Terry is releasing the files after you send your bin in. The factory DME in the 335is is different than a standard 335i. I guess the available flashes didn't work well in the 'is'. Time to order up that BT cable now though!

[OpenFlash]

OFT sample ROMs for the 335is (IKBOS, ILAOS, IKMOS, IKCOS) for our stage 1 tune are now posted up on our website

[TurboSid]

Originally Posted by shiv@vishnu

OFT sample ROMs for the 335is (IKBOS, ILAOS, IKMOS, IKCOS) for our stage 1 tune are now posted up on our website

I like your wording... what exactly is a "sample ROM"? A sample of what a real rom might look like that actually worked?

Why are u responding to new business posts but not supporting any of your existing customers who have issues? I can't believe I've been supporting your company all these years.

Here's where the community is with your maps...

[Kid Eh]

I'm using COBB v2 tuned by PTF. Car runs smooth as silk.

[OpenFlash]

Originally Posted by TurboSid

I like your wording... what exactly is a "sample ROM"? A sample of what a real rom might look like that actually worked?

Why are u responding to new business posts but not supporting any of your existing customers who have issues? I can't believe I've been supporting your company all these years.

Here's where the community is with your maps...

Iirc, BuraQ eventually realized that he was using the incorrect XDF file as he mistook what software version he had. One of the requirements of using an XDF is using the correct one. Or else, it all looks messed up.

And a sample rom is a tuned rom. One you use with Tuner Pro's difference tool to patch in all the tuning changes to your original rom. We have a tutorial video on how to use the difference tool on out website

[TurboSid]

Originally Posted by shiv@vishnu

Iirc, BuraQ eventually realized that he was using the incorrect XDF file as he mistook what software version he had. One of the requirements of using an XDF is using the correct one. Or else, it all looks messed up.

And a sample run is a tuned rom. One you use with Tuner Pro's difference tool to patch in all the tuning changes. We have a tutorial video on how to use the difference tool on out website

No he and desertdude realized they were using the wrong ROM because i accidentally confused IKBOS and IKCOS. Once that was corrected both of them were still having issues with the files in your 1.04 release.

you wouldn't need to "remember correctly" if you would just chime in on the forums or respond to my/others' emails.

[TurboSid]

Following the tutorial on your site, i still don't see a "Stage 0/1 OTS" setting at the bottom of the parameter tree to make a tuned rom... where can I find that?

[OpenFlash]

Originally Posted by TurboSid

Following the tutorial on your site, i still don't see a "Stage 0/1 OTS" setting at the bottom of the parameter tree to make a tuned rom... where can I find that?

It may help if you took the time to understand what I said above. There is no patch feature in the new XDFs. That is where the Difference Tool comes into play. This is explained in the Read Me file as well.

Also, the emails you sent to the sales account asked for E85 maps for the 335is which we don't have. Never did. And based upon our E85 testing with a 7DCT, we never will due to clutch pack limitations. I'm sorry.

I don't know of any error in the XDF file. If there is, let me know what it is and I'll fix it.

Cheers
shiv

[Allen@MOTIV]

If anyone is interested we offer ethanol blend mapping for 335is cars and have tuned many DCT equipped cars running the fuel.

[TurboSid]

Shiv you originally stated that any DME software versions not available on your site should be emailed to you for a custom rom within 2-3 business days. So no matter what I needed to email you my IS original rom to get the OFT working (at that time). In my email i requested if possible for an e85 map, but I still needed something.

So don't BS on here that I asked for e85 only.

October 26th -

Hey Shiv

Here is my original rom from my OFT which i just purchased used. it is IKBOS

Is it possible to get an e-85 map for it? something like your e40 maps?

Thanks,

I still to this day have no response for that email, next u will say its because i told you to go fuck yourself, which was after waiting until November 17th.

Nowhere did you state above that the only way to patch is the difference tool, u just suggested I use it and nowhere on your getting started section on the website does it say that for certain XDF's you MUST use different tool rather than the method that's clearly outlined.

So don't tell me to "take the time to understand" your vague responses and unfinished work on your website.

[OpenFlash]

Originally Posted by TurboSid

Shiv you originally stated that any DME software versions not available on your site should be emailed to you for a custom rom within 2-3 business days. So no matter what I needed to email you my IS original rom to get the OFT working (at that time). In my email i requested if possible for an e85 map, but I still needed something.

So don't BS on here that I asked for e85 only.

October 26th -


I still to this day have no response for that email, next u will say its because i told you to go fuck yourself, which was after waiting until November 17th.

Nowhere did you state above that the only way to patch is the difference tool, u just suggested I use it and nowhere on your getting started section on the website does it say that for certain XDF's you MUST use different tool rather than the method that's clearly outlined.

So don't tell me to "take the time to understand" your vague responses and unfinished work on your website.

Sorry mate. I apologize for not getting back to you earlier as I was away at SEMA all week and had a pile of email to catch up on. But for this reason, it is clearly stated in the Read Me file that a difference tool is necessary to build a map for these ROMS, at this time. Soon this will not be the case as the next firmware OFT update will allow to preload the device will 25 tuned ROM files. But for now, it is all that we offer for the 335is/1M.

Regards
Shiv

[DesertDude]

Originally Posted by shiv@vishnu

And based upon our E85 testing with a 7DCT, we never will due to clutch pack limitations. I'm sorry.

Hmm. I'm running a 50/50 E85/91Oct blend on an IS with 7DCT, and as long as I don't defeat ignition torque reduction and keep max torque below 2000 RPMs to a reasonable amount (throws transmission torque limit codes), I haven't had any issues with it.

I'm currently running 18+PSI in the mid range and up to 15 degrees of advance. Tuned with just OFT. Clutch packs hook up great.

[BQTuning]

Originally Posted by shiv@vishnu

Iirc, BuraQ eventually realized that he was using the incorrect XDF file as he mistook what software version he had. One of the requirements of using an XDF is using the correct one. Or else, it all looks messed up.

Nope this was after the fact. @DesertDude himself realized that even the correct XDF file was "bleeped" up. He tried to help by correcting the "bleeped" up axis', emailed it to me, I went through every table one by one and it was soo bad I had to give up, it was pointless

Here is thread well documented of the trouble http://www.e90post.com/forums/showth...860720&page=59

Originally Posted by shiv@vishnu

..... But for this reason, it is clearly stated in the Read Me file that a difference tool is necessary to build a map for these ROMS, at this time. ....

This is a copout for not being able to provide a legitimate XDF for his ROM version

Originally Posted by shiv@vishnu

..... Also, the emails you sent to the sales account asked for E85 maps for the 335is which we don't have. Never did. And based upon our E85 testing with a 7DCT, we never will due to clutch pack limitations. I'm sorry.

I don't know of any error in the XDF file. If there is, let me know what it is and I'll fix it.

Cheers
shiv

Shiv, this talk about the clutch pack limitation is obsolete. This is an inherent problem with piggybacks, with the exception, Terry was able, eventually, to find a way around it and you haven't. The OFT should not have a problem since it is 100% flash based tuning and there is no middle man management.

I have done over 400+ launches on my DCT running E30-E60, and was running PTF's E50 map and at no time my DCT failed me, and at no time has ANY PTF 335is E50 map caused a fail on any stock DCT

The only spec of evidence, provided by flash tuning only, is the DCT can handle up to 550 wtq

Here is one example of our stock DCT at work and this was no upgraded clutch pack:

I posted one error of the XDF for example and quoted you, @DesertDude provided us with assistance, not you, and he himself found it was "bleeped" up

http://www.e90post.com/forums/showpo...postcount=1285

http://www.e90post.com/forums/showpo...postcount=1290

Originally Posted by Allen@PTF

If anyone is interested we offer ethanol blend mapping for 335is cars and have tuned many DCT equipped cars running the fuel.

Trust me, we are trying our best and I am know he will be very happy with it. He has seen and witnessed first hand how the PTF E50 map runs on my car.

[DesertDude]

Originally Posted by TurboSid

No he and desertdude realized they were using the wrong ROM because i accidentally confused IKBOS and IKCOS. Once that was corrected both of them were still having issues with the files in your 1.04 release.

The cleaned up xdf I gave to BuraQ worked fine for me when viewing the appropriate ROM version. I think what may have been an issue is that several of the xdf tables are using different unit conversions than the COBB maps so the values don't directly translate between the two. (For example, I believe some of the tables in ATR use Lambda where the xdf's from Shiv convert to AFR.) I'm guessing the PID tables have a similar conversion difference.

If BuraQ was trying to update the OFT map using the values directly from Cobb ATR, they wouldn't look right, or work for that matter, unless he converted them to use the same units or compared using the actual HEX values.

I didn't get specific feedback on what was wrong, but that's my guess at this point.

[AK 335i]

Hai guys. subb'd

[BQTuning]

Originally Posted by DesertDude

The cleaned up xdf I gave to BuraQ worked fine for me when viewing the appropriate ROM version. I think what may have been an issue is that several of the xdf tables are using different unit conversions than the COBB maps so the values don't directly translate between the two. (For example, I believe some of the tables in ATR use Lambda where the xdf's from Shiv convert to AFR.)

If BuraQ was trying to update the OFT map using the values directly from Cobb ATR, they wouldn't look right, or work for that matter, unless he converted them to use the same units or compared using the actual HEX values.

I didn't get specific feedback on what was wrong, but that's my guess at this point.

No, it was the axis values that were off in the fueling and limit tables. After I got it back from you, most of the WGDC and boost control tables was ok, when I decided to go through every single table the same things you found that I found in the previous bleeped up WGDC tables started to pop up in other tables.

In Cobb ATR the units can be converted over to match the units in TP. (Example of X and Y axis is shown, base values are my own not OTS map)





However the units do not do well being "interchanged" as TP rounds the units off. So if a value shows in Cobb ATR as 11.58, in TP it will be rendered as 12, or 12.00 or 11, or 11.00 it all depends on how the XDF is being defined.

The issue with Shiv's XDF was BIG, just as you saw with the X and Y axis in the WGDC . I just decided to look at every single table.

[AK 335i]

not quite sure what any of that means. but it sounds like @Turbosid and @Buraq are doing it right

[OpenFlash]

Originally Posted by BuraQ

No, it was the axis values that were off in the fueling and limit tables. After I got it back from you, most of the WGDC and boost control tables was ok, when I decided to go through every single table the same things you found that I found in the previous bleeped up WGDC tables started to pop up in other tables.

In Cobb ATR the units can be converted over to match the units in TP. (Example of X and Y axis is shown, base values are my own not OTS map)





However the units do not do well being "interchanged" as TP rounds the units off. So if a value shows in Cobb ATR as 11.58, in TP it will be rendered as 12, or 12.00 or 11, or 11.00 it all depends on how the XDF is being defined.

The issue with Shiv's XDF was BIG, just as you saw with the X and Y axis in the WGDC . I just decided to look at every single table.

Could you please be specific and let me know what parameter you believe is misdefined in which particular XDF file so I can fix it if it needs to be fixed?

shiv