Known issues with the October 2015 Public Pre-Release

[Blacky]

Also, all the AD wideband settings in the sae_generic are looking for AD1 not AD2.

I have updated the generic file to the one above.

I have just uploaded the corrected sae_generic.txt file. It now specifies EXT.AD2 (instead of EXT.AD1) for all AFR PIDs that are supposed to be based on AD2.

Regards
Paul

[ProperTuningOG]

Calculated PIDs have never been displayed on FlashScan's screen during black box logging. FlashScan is not capable of computing and therefor not able to display calculated PIDs.
Paul

Sorry, you are correct. I had my laptop going last time. LOL

Thanks for the help.

Josh

[auspeed]

Hi im not ensure its related to this update but I get the following error when trying to log on an e38 that I full flashed over top of a hp 2 bar COS. I have another e38 that i have tried and it worked fine, (it was stock)Is this error related to being a HP tuned car? The OS i fully flashed is: 12653674

[Blacky]

Hi im not ensure its related to this update but I get the following error when trying to log on an e38 that I full flashed over top of a hp 2 bar COS. I have another e38 that i have tried and it worked fine, (it was stock)Is this error related to being a HP tuned car? The OS i fully flashed is: 12653674

Do you happen to have any external PIDs selected, i./e. EXT.AD1?
If so, try unselecting them.

Regards
Paul

[auspeed]

Do you happen to have any external PIDs selected, i./e. EXT.AD1?
If so, try unselecting them.

Regards
Paul

Thanks Blacky, I did have AD1 selected, I re validated my pids & updated the sae_generic.txt as per previous post & got it working.... Thankyou