Unichip issue - cannot start car

[355rockit]

I installed the Unichip into the FR-S on Friday and on Sunday did a spirited drive with the car club (218 miles). When I was close to home after the drive, the car would not be very responsive in 1st gear and then other times would lurch forward. I am using 91 Octane with the '92 - TRD CAI/All Headers/All Catback' map. After a couple of other members said that I should not use 92 octane map, I flashed back to the original maps that were on the unit when I received it. The member that sold it to me said that it had the original FR-S maps. The car will not start now. It tries to turn over, but no luck. I unplugged the Unichip harness again and plugged in the USB harness and tried to connect to the Unchip reflash software, but it doesn't respond. I tried two computers and same thing... unit connects for a second and then disconnects. I am not sure if the Unichip module has failed which is why the car won't start. Any ideas?

[phrosty]

Bummer, sounds like it's busted if it won't respond at all to USB.

[355rockit]

Originally Posted by phrosty

Bummer, sounds like it's busted if it won't respond at all to USB.

Worked great when it worked. The drive I did was with a bunch of Ferraris, Porsches, Lotus and a Ford GT. The other guys were very impressed by the FR-S performance.


I deinstalled the Unichip harness and the car starts and runs fine now. When I get more info on what the issue might be, I'll reinstall.

[355rockit]

Jack at Unichip said it might have been a bad remap flash (even though Unichip software said the maps imported fine). He suggested I reflash firmware. Apparently it will take several tries to actually flash the firmware successfully.

[355rockit]

It took 4 tries, but the Unichip finally flashed the firmware. It turns out that the backup maps that I made using the reflash software had an issue. After flashing firmware I powered down and unhooked the USB. On hooking it back up to the computer I had the same no connection issue. This time I reflashed firmware and then used remap to import the 2 maps I had previously used (92 and 89 octane TRD CAI/all headers map). I then did a USB disconnect and exited the software and then reconnected. The Unichip connected fine this time. Strange issue. Now I just need to find a 91 octane TRD CAI/All Header map to try.

[s2d4]

Or just get rid of it, you are really not doing yourself any favours with it.

[355rockit]

Originally Posted by s2d4

Or just get rid of it, you are really not doing yourself any favours with it.

Did someone spit in your cornflakes this morning?

[s2d4]

Originally Posted by 355rockit

Did someone spit in your cornflakes this morning?

No, unless telling it like it is means someone spat in my cornflakes, then Yes.

Also, noticed the guy that thanked my post? He used to have a unichip too.

[355rockit]

Originally Posted by s2d4

No, unless telling it like it is means someone spat in my cornflakes, then Yes.

Also, noticed the guy that thanked my post? He used to have a unichip too.

It would be nice to know more details into why you are not a fan of Unichip and not just a remark to get rid of it. I had some weird issues, but willing to give it another chance. Jack at Unichip said that 92 octane map I am using will work fine with 91 octance gas. More input into your experience with Unichip will be helpful.

[phrosty]

Originally Posted by 355rockit

It would be nice to know more details into why you are not a fan of Unichip and not just a remark to get rid of it. I had some weird issues, but willing to give it another chance. Jack at Unichip said that 92 octane map I am using will work fine with 91 octance gas. More input into your experience with Unichip will be helpful.

Unichip works fine, but now we have OFT which gives better perf and more customizability at the small risk of possible warranty issues. I've had both, they are very good products. I don't know why some people are hating on Unichip.

[steve99]

Nothing wrong with the concept of Unichip piggyback devices to "tune" a car.

However with bRZ/86 having a re-flashable ECU,s (and high re-flash cycle)

If ecu was not re-flashable or had low flash cycle or tables/ecu code was not decompiled then Piggyback devices made perfect sense and were only option unless you wanted to replace entire ecu at great expense with something like motec. However they can only alter sensor inputs to "trick" ecu into adjusting its outputs, and you have to "wire" them in.

Now with 86/brz having a flash-able ecu with high cycle count ability, piggy back devices are less attractive.

You have the ability to flash ecu no wiring required, flash back to stock in minutes, far greater control as you can actually alter all the tables and parameters and even add code to ecu. Far greater flexibility and power than a piggyback device.

[355rockit]

Originally Posted by steve99

Nothing wrong with the concept of Unichip piggyback devices to "tune" a car.

However with bRZ/86 having a re-flashable ECU,s (and high re-flash cycle)

If ecu was not re-flashable or had low flash cycle or tables/ecu code was not decompiled then Piggyback devices made perfect sense and were only option unless you wanted to replace entire ecu at great expense with something like motec. However they can only alter sensor inputs to "trick" ecu into adjusting its outputs, and you have to "wire" them in.

Now with 86/brz having a flash-able ecu with high cycle count ability, piggy back devices are less attractive.

You have the ability to flash ecu no wiring required, flash back to stock in minutes, far greater control as you can actually alter all the tables and parameters and even add code to ecu. Far greater flexibility and power than a piggyback device.

If one uses OFT and flashes back to stock, is there any date code or other indication that the ECU firmware was flashed? If the dealer reflashes the ECU for a service bulletin, will they be able to see what the last flash date was? This is one item that is keeping me away from OFT while under warranty.

[Boofneenee]

Originally Posted by 355rockit

If one uses OFT and flashes back to stock, is there any date code or other indication that the ECU firmware was flashed? If the dealer reflashes the ECU for a service bulletin, will they be able to see what the last flash date was? This is one item that is keeping me away from OFT while under warranty.

Their may be but i have not seen proof of a counter that the dealer has to prove a flash. I would imagine by now with all this talk someone credible would come forward with proof. Having said that if the dealer wants to find out bad enough whats stopping then from sending the ecu to toyoya headquarters for analysis. Im sure ghere they could figure out but i doubt they would go through the effort.

I think a reflash done right is safer than a piggyback amd that alone is more important then dealing with a dealer for warranty issues. With the oft u have proven effective and safe tunes with active real time data analysis. I fear electrical problems with the piggyback

[steve99]

Originally Posted by 355rockit

If one uses OFT and flashes back to stock, is there any date code or other indication that the ECU firmware was flashed? If the dealer reflashes the ECU for a service bulletin, will they be able to see what the last flash date was? This is one item that is keeping me away from OFT while under warranty.

As others have said no one can offer a 100 percent guarantee
Howver no on has found a flash counter and there are many with TECHSTREAM which is software dealers use to analyse diagnose and flash 86 brz.
I have looked with Techstream no flash counter accessable
it does access two counters one is distance since dtc reset and also time/distance since dtc logged
Both are reset to zero on ecu flash as ecu is reset as part of flash process. But the ecu is also reeset on battery removal or it goes flat or ecu fuse is removed or these counters are easily reset with cheap obd scan devices. ie not proof of a reflash.
Tthe ecu does not appear to have a real time clock so no date info stored or real time info.

OFT flashes back exact stock rom no encryption or lockout or embeded licience info ect.

Maybe locked away somewhere is something we are all missing but it likely if it exists it would require dealer to remove ecu and send for analysis or get some specialist toyota subaru dude onsite and this aint going to happen in normal service.

If it was a VW golf i would say they would definitly know they log everything dates time engine parameters with every dtc zillions of realtime counters ect, but ours does not appear to have this level of sofistication. Was looking at a mates with VW VAG software logging was very comprehnsive and far exceeded ours