hey there guys, been having this problem now since i have been trying to flash my car.

[19:10:13.194] using metadata XML ID read_subarush72531brz from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_subarush72531brz.xml
[19:10:13.206] J2534 API Version: 04.04
[19:10:13.206] J2534 DLL Version: 1.01.4035 Dec 16 2013 23:12:40
[19:10:13.206] Device Firmware Version: 1.14.4010
[19:10:13.206] Device Serial Number: TAwsLqbV
[19:10:30.872] reading vehicle info...
[19:10:30.880] CALID : ZA1JB01D
[19:10:30.881] CVN : 38119841
[19:10:30.888] VIN :
[19:10:30.888] starting programming session...
[19:10:30.889] turning off DTCs...
[19:10:31.219] turning off unnecessary communications...
[19:10:31.320] unlocking ECU...
[19:10:31.320] Requesting Seed...
[19:10:31.320] interface close
[19:10:31.331] interface close

any ideas?? i have tried both usb ports, and i frequently restart my computer

As above
Assuming all bitbases def files are correct


Connect tactrix to car the connection can be suspect on some cars put a rubber band arround tactrix and hook it around bracket at rear of obd port to put some backwards pressure on tactrix as opposed to upwards pressure into the socket.
Turn on ignition
Turn OFF all accessories radio fans ect
Select read or write in ECUFLASH
Dialog box will appear
WAIT at least 15 seconds even if you don't hear beeps
Then click ok to start write/read


good luck !

thats not working, for some reason its not reading the vin number. thats the only thing thats different

Check you have correct bitbase files and def files I posted up new bitbase link yesterday.
correction was made to B01D defs reciently as well

ZA1JB01D.xml Fixed incorrect Ecuflash flashing mode xml on ZA1JA01I/K/O/D a month ago

also reselect vehicle type ie BRZ just prior to read or write as ecuflash seems to "forget" sometimes

Can you read a ROM ?

i am unable to read or write to the ecu. i have the most current defintions and bases so im at a complete loss as to why its failing to read.

Well got me stumped,



That it does read cal id but not VIN is suspect. you might have to get onto the tactrix/ecuflash guys.

You could try downloading TechStream (Toyota diagnostic it will work with your Tactrix dongle. DONT load the Techstream drivers use the tactrix one already loaded Techstream will recognize these follow instructions here download V7.10 i'm using this one

Techstream will allow you to read VIN and actually set one if its blank

https://onedrive.live.com/?cid=75C93...EE49501E9A!126


This works with XP not sure if Win 7/8

try this one
http://www.ft86club.com/forums/showthread.php?t=35530

I'm on XP so have not used that one.

i have Techstream already set up and working with the OP2.
i just thought of something; about 2 months ago now the dealership replaced my engine ECU under warranty as the remote starter that they had installed for me fucked a bunch of shit up :mad0260: they still owe me $600 :mad0260: that could be why ECUflash isnt reading a VIN.

where would i go in techstream to set a vin for the ecu?

thanks.

Sounds feasible they did not set VIN

When you first connect to car techstream should dispay VIN in connection window.

To set or check VIN go to ENGINE ECU then select UTILITY ,then select VIN select ARROW at bottom of screen then read or set vin. done :happyanim: if it works

still doesnt work..............
is there a error report generated by ecuflash as im not seeing anything in the way of errors in the log window

Not that i know of.

You will have to try taxtric guys or maybe rom raider forum.

http://www.romraider.com/forum/viewt...8475&start=420

Their is another guy "DNA" having very similar problems with a A01D series ROM

canyou try another vehicle for read ?

i do not have anyone nearby me who has a 86. i might as well wait as my Openflash Tablet should be here soon

There's a typo in the B01C script, defogger switch is incorrectly input. Should be:

FFF8939F

Fixed

Anyone with the A01C rom having luck getting the defog trigger to work for logging? Also, to make sure I'm not mis-assuming what the "defog" trigger is....we're talking about the button on the fan speed selector that defrosts the rear window right? So I press in the button to start logging (and defrosting!) and push the button again to stop logging.

The original RPM trigger logs great for me, but when I comment out that trigger with ";" and put in the defog trigger, it never works. I just get the logout file but no CSV log files.