PDA

View Full Version : tcm read issues on lbz/lmm



smudge122
June 10th, 2012, 02:05 AM
I recently update my v7.5 and v8 software and also bootblock/firmware on my flashscan. I did the mistake of updating firmware/bootblock before checking the version i had....not sure if this is where my problem starts. I can read, scan lbz/lmm ecms but not the tcm. In v8 I get error message "controller type can not be determined". Same in v7.5 I didnt have an issues with a Lb7 tcm. Before i brick my flashscan, I figure I'd ask do some research. ?????

smudge122
June 10th, 2012, 02:08 AM
The flashscan shows bootblock version 2.07.04 and firmware 2.07.32 in firmware details tab. I'm just second guessing myself about if it took or not.

smudge122
June 10th, 2012, 10:11 AM
update....i can read the tcm using v7.5 but not v8

joecar
June 11th, 2012, 04:55 AM
Did you also program the updated BBx config files into your V2...?

smudge122
June 11th, 2012, 01:52 PM
no i haven't.....i've beeen researching on how to do that

joecar
June 11th, 2012, 05:56 PM
V8 S&T software, click BBx, click Scan, edit the pidlist (delete the ones for ECM's other than your own, add pidlists for your own ECM), cick Tune, edit the ECM list (delete the ones other than your own), click Save, click Program All (click down arrow next to Program).

smudge122
June 21st, 2012, 01:21 PM
I'm getting an ERROR $0194: write failure. Do i have to formant config files before i program all.

Blacky
June 21st, 2012, 02:29 PM
I'm getting an ERROR $0194: write failure. Do i have to formant config files before i program all.
Yes, That would be the best thing to do.
Regards
Paul

smudge122
June 24th, 2012, 04:31 AM
ok i can read it and i still get "efilive can not accurately determine the controller type" please send %s to support at efilive.com for analysis

joecar
June 25th, 2012, 01:59 AM
Can you post a screenshot of that here...

Also, did you email the file to support at efilive.com...?

smudge122
July 4th, 2012, 04:36 AM
I noticed there was a software and firmware upgrade as of June 22 and that update seemed to clear the v8 read issues. All is good Thx for the help