OFT - The File Selected Is Not Compliant

[Kody]

Quick question for anyone who may have experienced this problem before...

I've been using the OFT for a little over a year now and love it, I've used both the 91 and 93 stage 1 tunes. I've flashed about 3 or 4 times and know the steps involved in the flashing process (or so I thought).

I'm moving to Atlanta soon and am wanting to flash to the 91 tune (currently at 93) just in case I need to fill up somewhere and they don't have 93 octane gas. However when I attempt to load the 91 tune for my car into the tablet it gives me the 'The file selected is not compliant' message. If I try to load the 93 tune it all works fine.

My CAL ID is: ZA1J900C (US 6MT). I am attempting to load the 'Stg 1 900C' tune onto the table. 93 loads fine, 91 gives me that message...

Anyone else ever have this issue/know how to fix?

Thanks!

[Shiv@Openflash]

Originally Posted by Kody

Quick question for anyone who may have experienced this problem before...

I've been using the OFT for a little over a year now and love it, I've used both the 91 and 93 stage 1 tunes. I've flashed about 3 or 4 times and know the steps involved in the flashing process (or so I thought).

I'm moving to Atlanta soon and am wanting to flash to the 91 tune (currently at 93) just in case I need to fill up somewhere and they don't have 93 octane gas. However when I attempt to load the 91 tune for my car into the tablet it gives me the 'The file selected is not compliant' message. If I try to load the 93 tune it all works fine.

My CAL ID is: ZA1J900C (US 6MT). I am attempting to load the 'Stg 1 900C' tune onto the table. 93 loads fine, 91 gives me that message...

Anyone else ever have this issue/know how to fix?

Thanks!

I recall there being a problem in one of the older map releases were there was a mislabeled map file. Maybe that is what you are running into. What version map are you running?

[Kody]

Originally Posted by Shiv@Openflash

I recall there being a problem in one of the older map releases were there was a mislabeled map file. Maybe that is what you are running into. What version map are you running?

Well, I deleted the map that was on there (the 93 tune) earlier just to see if that somehow was messing anything up ...so I'm not 100% sure. I do know that it was pretty much the first officially released 2.x map that had the 93 octane option for stage 1.

[headlikeahole]

Was a solution ever found for this? I just installed my opt and im running whatever tunes came on the tablet. When I try to add v1.59 or v2.XX tunes to my tablet I get the message "the file selected is non compliant"

Does it matter what the default program is for the .bin files. My computer automatically chose vlc as default program. I'm new to all this and I have no idea what the problem is.

Edit: ok so I was able to write the 2.067 tune onto the opt. however its A00C when the files that came on the tablet are A01C. Does this matter? My CAL is A00C and it gave me the checksum good message so im guessing im good?

[Shiv@Openflash]

Originally Posted by headlikeahole

Was a solution ever found for this? I just installed my opt and im running whatever tunes came on the tablet. When I try to add v1.59 or v2.XX tunes to my tablet I get the message "the file selected is non compliant"

Does it matter what the default program is for the .bin files. My computer automatically chose vlc as default program. I'm new to all this and I have no idea what the problem is.

Edit: ok so I was able to write the 2.067 tune onto the opt. however its A00C when the files that came on the tablet are A01C. Does this matter? My CAL is A00C and it gave me the checksum good message so im guessing im good?

The calibration ID typo in that particular tune file (Stage 1 900C) was fixed a long time ago. I'm not aware of any other similar issues. If you are getting that error, you are trying to upload a file with a mismatching calibration ID. For example, if your CAL ID Is ZA1JD00C, you will only be able to load D00C tune files.

Shiv

[headlikeahole]

Originally Posted by Shiv@Openflash

The calibration ID typo in that particular tune file (Stage 1 900C) was fixed a long time ago. I'm not aware of any other similar issues. If you are getting that error, you are trying to upload a file with a mismatching calibration ID. For example, if your CAL ID Is ZA1JD00C, you will only be able to load D00C tune files.

Shiv

Yeah I was able to upload the appropriate tune A00C for CAL ID A00C. My question now is that the preloaded tunes (and the one my OFT got me to flash my ECU with) was A01C. Does that matter?

[Shiv@Openflash]

Originally Posted by headlikeahole

Yeah I was able to upload the appropriate tune A00C for CAL ID A00C. My question now is that the preloaded tunes (and the one my OFT got me to flash my ECU with) was A01C. Does that matter?

Nope it doesn't matter. Your native CAL ID was in face A00C. It just showed A01C because the OTS maps that were ran were A01C based.

[yunheng]

Hi,

In regards to previous post, is it safe to say that i can upload a tune file of A01J to a ECU with native calibration A02J by changing the file name to A02J?

Sorry it might be a dumb question, but my car is a late 2014 model and it came with A02J calibration id.

[steve99]

Originally Posted by yunheng

Hi,

In regards to previous post, is it safe to say that i can upload a tune file of A01J to a ECU with native calibration A02J by changing the file name to A02J?

Sorry it might be a dumb question, but my car is a late 2014 model and it came with A02J calibration id.

No don't do that you need correct rom type.