|
Software Tuning Discuss all software tuning topics. |
|
Thread Tools | Search this Thread |
04-02-2014, 08:23 PM | #1 |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging
EcuFlash Tactrix Info for Reading Writing Updating ROM calibration and logging for BRZ 86 FRS
See attached Stock ROM files at end of post List of Region / Transmission codes: Last letter of ROM Calibration ID (Calid) MANUAL: A = "Other" (Japan, High FD), C = US / Canada, E = Korea, G = Europe / Australia / South Africa (High FD), H = Europe / Australia / South Africa (Low FD) , J = Middle East, N = China, P = "Other" (Japan, Low FD) AUTOMATIC: B = "Other" (Japan), D = USA / Canada, F = Korea, I = Europe / Australia / South Africa, K = Middle East, O = China Note In 2016 it appears the above letter designations no longer apply at least in Australia the 2016 Toyota and Subaru seem to have different ROM designations Toyota using F10G manual and subaru brz using F20P but roms appears almost identical. The 2016 BRZ auto using F20Q Rom Compatibility G series ZA1J700G, 900G , A00G A01G all compatible with ZA1JA02G ZA1JD00G for late 2014/2015 cars only ZA1JF10G for late 2016 Toyota ZA1JK00P 2017 manual Subaru Australia (new logic red intake manifold) ZA1JK00G 2017 European (old logic, standard intake manifold) P Series manual Australia 2016 ZA1JF20P 2016 BRZ Manual - appears to be virtually identical to ZA1JF10G 2016 Toyota 2017 K00G and K00P are NOT the same 2018 Australian ZA1JN00P 2018 australian manaul (this is very likely same as ZA1JN00Q, not confirmed) I series Auto ZA1JA700I , 900I A01I all compatible with ZA1JA02I ZA1JE00I for late 2014/2015 cars only ZA1JK01I 2017 Auto European (old logic standard intake manifold) S Series Auto ZA1JK00S 2017 Australian Auto (old logic standard intake) ZA1JN00S 2018 Australian Auto Note ZA1JK00S and ZA1JK01I auto roms are interchangeable Q Series Australia auto 2016 ZA1JF20Q 2016 BRZ Auto C Series ZA1JA700C ,900C, A00C ,A01C , B00C all compatible with ZA1JB01C ZA1JD00C for late 2014/2015 cars only ZA1JF00C F40C for late 2015 cars ZA1JK00C Late 2016/17 (note this new logic rom has two fuelling and timing tables, red intake) D Series ZA1JA700D, 900D,A00D,A01D,B00D all compatible with ZA1JB01D ZA1JD00D for late 2014/2015 cars only sorry not sure on other regions, suspect roms up to mid 2014 compatible then changes to vehicle late 2014 onwards requires different rom. K00x roms are for 2017 cars only, do not flash earlier roms to 2017 cars else you will trigger a security lockout and car will not start . you will need to perform the ECU replacement ecu resync proceedure to get car to start after flashing back a 2017 rom. Disclaimer: ************************************************** ************************************************** ** Information is provided in good faith however their may be errors or omissions. You take all responsibility & risk. There is support for Ecuflash & Tactrix adapter at. Contact www.tactrix.com The EcuFlash Software allows rom edititing and is available from www.tactrix.com under downloads Ecuflash/Tactrix will read and write any ROM type to your vehicle it does not check it’s the correct one i.e. Manual/Auto or ROM series A/C/D/G/K ect it just writes. You may not be able to read or write to vehicles that have had encrypted/locked ROM’s written to them. (same for other tuning platforms) If you overwrite your “stock” Ecutek or BRZ Edit ROM you may loose your license info. It’s always possible to “brick” or get your ECU into a state where it’s not recoverable. (Same as any other tuning platform) The Definition files for Ecuflash and RomRaider are different and done by the open source guys The 32BITBASE file for Ecuflash is also produced by opensource guys at RomRaider www.romraider.com You will need some basic computer skills This is not a complete “how to do it guide” just collating the info in one place. I am not trying to scare you just inform you of the facts. ************************************************** ************************************************** ** Tactrix/Ecuflash is a reliable and proven flashing method but please read warning below WARNING : Always make sure your definition file matches your ROM. Do NOT rely on the name of the ROM file. The internal Calibration ID may not be the same as the file name. Always open the ROM in ECUFLASH and check some tables such as the "Primary Open Loop Fuel Table" and the "Base Timing B" check that the values in these tables look ok and the table Axis both X and Y look ok. If they don't then it likely that the Definition file and the ROM are mismatched. If you FLASH or EDIT a ROM using an incorrect Definition you WILL Brick your ECU. Your only option then will be to use SH Boot mode which requires ECU removal, making and interface and soldering direct to circuit board and downloading a ROM via SH Boot mode (see below). This is not easy and is beyond the capabilities of most people. your other option is purchase a new ECU. This procedure has not been tested yet on a BRZ ECU http://www.tactrix.com/index.php?option=com_content&view=article&id=66:re flashing-subaru-sh705x-ecus-using-the-renesas-boot-mode&catid=42:ecu-repair&Itemid=41 Note : Entering SH boot mode will delete the User ROM Mat and the BOOT ROM Mat, as yet no one has successfully read the BOOT Rom Mat area so even with SH Boot mode you cannot recover your ECU yet, hopefully the Tactrix guys will work out how to read this area soon. It if you believe you have bricked the ecu and tried re-writing without turning car ignition off and its still failed Then try this procedure first 1. Switch off ignition 2. Remove negitive battery terminal 3. Depress brake pedal to bleed off any residual power 4. Re-connect battery 5. Immediately try to reflash car with a known good rom, stock rom is best. Flash rom at first turn on of ignition. 6. If still no go repeat but leave battery disconnected for at least 30 minutes. hopefully your back in bussiness Tips to Avoid Flashing Problems or Bricking your ECU http://www.ft86club.com/forums/showthread.php?p=2489551 Replacing a Bricked ECU with new or used ECU (engine control Module) http://www.ft86club.com/forums/showthread.php?t=102810 If you want more support and backup then you should look elsewhere Open Flash Tablet Ecutek BRZ Edit no doubt their are others or a Tuner. Warning : Their are some el-cheapo clones of Tactrix adapter on the market. These may cause issues and possibly brick your ECU. Its best to buy the original product from TACTRIX www.tactrix.com , the support you get from those guys is well worth it. BRZ/86 flashing requires the latest hardware/firmware/software in the tactrix adapter. Tactrix Open Port 2 is hardware Dongle/Adapter to interface between you cars OBD-2 Port and your PC/Laptop. It can also log engine data if an SD card is installed and appropriate logcfg.txt file is on SD card. EcuFlash is the software that enables you read and Write ROM’s (Tunes) to your Car via the Tactrix adapter. It can only be used to write or edit ROM’s if you have the correct definition files for your ROM type. You may not be able to read or write to vehicles that have had encrypted/locked ROM’s written to them, same as other tuning platforms. For more info and support on EcuFlash Software and Taxtrix OP2 Dongle/Adapter go to www.tactrix.com The Definition files for Ecuflash and RomRaider are different and done by the open source guys The 32BITBASE file for Ecuflash is also produced by opensource guys. You can also use RomRaider to edit the ROM files www.romraider.com. You will need the RomRaider definition files for your ROM type. Here https://github.com/TD-D/SubaruDefs/t.../RomRaider/ecu Alternate Romraider definitions with added tables and metric conversions here by @Kodename47 http://www.ft86club.com/forums/showp...&postcount=411 You will need Tactrix Open Port 2 - But one from www.tactrix.com Ecuflash Software (BRZ Beta Version) from www.tactrix.com website 32BITBASE file for BRZ from Github see links below Ecuflash Definition files for your ROM type - from Github see links below Laptop (Windows) Optional Romraider Software - www.romraider.com site RomRaider Definition files - from Github see links above If you want to edit roms with Romraider instead of Ecuflash Install ECUFlash software and Tactrix adapter drivers. Download from TACTRIX website downloads page http://www.tactrix.com/index.php?opt...d=36&Itemid=57 make sure you update the 32Bitbase and definition files for ECUFLASH from GITHUB links below as the ones supplied in the download may not be the latest versions WARNING : If your upgrading ECUFLASH previously installed the 32BITBASE and DEF files will be moved to a backup directory, be sure to copy them back as the ones in the software release are not the latest ones required for BRZ/86 Plug in Tactrix cable and allow drivers to be installed If they dont install they can be downloaded from here http://www.tactrix.com/index.php?opt...d=38&Itemid=61 Open ECU_Flash: Update Firmware in Tactrix cable In ECUFlash, click "Help" - select "Licensing" on newer software this is not required. If Tactrix firmware is out of date (in the Tactrix dongle/adapter), it will be updated here automatically Obtain desired ECUFlash - Definition files: (check for updated regularly) click on the file. click on "Raw" tab. Click on your browser's 'File save as' and save it in the directory shown below https://github.com/TD-D/SubaruDefs/t...20standard/BRZ Place this file eg.(ZA1JA01C.xml) in directory: C:\Program Files\OpenECU\EcuFlash\rommetadata\subaru\BRZ\2012 \ You will also need to get base file 32BITBASE.xml from here: (check for updates regularly) click on the file. click on "Raw" tab. Click on your browser's 'File save as' and save it in the C:\Program Files\OpenECU\EcuFlash\rommetadata\subaru\Bases folder. https://github.com/TD-D/SubaruDefs/b.../32BITBASE.xml Flashing A ROM Tactrix/Ecuflash is a reliable and proven flashing method but please read warning above in red re checking definitions and ROM match before flashing. See Attached files for STOCK ROM's if you want to update to latest calibration When reading or writing a ROM, Ignition must be fully on (do not start car). When you click read/write in EcuFlash a dialog box will appear, Wait 15 seconds before you click ok. A read should be pretty quick less than 1 minute use "save as" and save it a bin file if you want to use RomRaider to edit. A Write will be longer just over a minute Before EcuFlash write's a ROM it will ERASE your current ROM, then WRITE will take place. Action will be logged on screen. Don't disturb connection during read or write & don't mess with switches in your car eg lights ect. Make sure your car battery is good turn off all accessories radio fax Air conditioner ect Ensure laptop battery is charged and no power saving modes active on laptop ie turn off HDD or screen ect. Make sure you select BRZ as vehicle type. Make sure you allow Ecuflash to correct checksum if it asks to do so, do not flash a rom without correcting checksum. Either the Tactrix adapter has thin/short pins or the socket in 86/BRZ is a bit loose but connection can be intermittent. Either use a short OBD extension cable or put a bit of forward/backward pressure on Tactrix adapter (I used rubber band) to ensure solid connection. You can also try bending in the pins on the Tactrix adapter slightly inwards. If you get a failed write don’t panic, check connection, settings def files, bases ect and write again. Write again without turning the ignition off as this will leave ECU in program mode. Write should only take about 1 minute You can READ a ROM without a Definition, but you won’t be able to WRITE or EDIT it without a definition. EcuFlash will only write rom if you have definition file for your ROM. So the simple and effective way to protect your car is to have only ecu definition for your ECU type in the C:\Program Files\OpenECU\EcuFlash\rommetadata\subaru\BRZ\2012 \ directory. Make sure you select the correct vehicle type ie BRZ. Creating a bare bones definition for flashing a ROM with no existing definition Useful if your car has old ROM not defined and you want to try update and be able to flash back to old ROM or you have pulled really new ROM from a car and no definition yet. Open the rom with no definition in Ecuflash, it will tell you it does not have a definition, do you want to create one. You press yes, and then click on from scratch. Then you choose SH72531 under memory module, and Subarubrz flashing method. The unique identifier is at 8000 and 8 bytes long. Fill the rom info in with the year, model etc. - not critical that this is accurate if you're just using it to flash. Click Finish, and when you're back in Ecuflash, click on file, and 'Save Models'. This should allow you to flash ROM but not edit as no tables defined. There should be a definition for pretty much all the roms out there, unless they are seriously old or very new. How to Convert any RomRaider Editor def to a EcuFlash def
its a command line utility so you will need to run it from a DOS or command window The full page on romraider here http://www.romraider.com/forum/viewtopic.php?t=8449 you will generally need to correct a couple of things flash method mem model and other initial header values as per below in the ecuflash def after running the conversion utility < rom> <romid> <xmlid>ZA1JF00C</xmlid> <internalidaddress>8000</internalidaddress> <internalidstring>ZA1JF00C</internalidstring> <ecuid>A929703007</ecuid> <year>2016</year> <market>USDM</market> <make>Subaru</make> <model>BRZ</model> <submodel>FA20</submodel> <transmission>MT</transmission> <memmodel>SH72531</memmodel> <flashmethod>subarubrz</flashmethod> <checksummodule>subarudbw</checksummodule> Related Threads EcuFlash general Discussion Page 19 has good info. http://www.ft86club.com/forums/showthread.php?t=47322 Ecuflash/Tactrix logging thread http://www.ft86club.com/forums/showt...light=ecuflash Status Lights in Tactrix Adapter About the status lights on the OP2: RED - OBD port or Innovate port data is being received (power to adapter) GREEN - OBD port data is being sent BLUE+RED - SD card activity (read or write) * This means that when logging is working properly, you should see RED and GREEN flashing often, and BLUE flashing occasionally when a new block of log data is written. * The current version of the Tactrix software has no power management, and the OBD port is always on, so it is possible to drain your battery if you leave the OP2 plugged in for several days while your car is off. * Until there is a GUI, you will need to know the parameter IDs and scalings of the parameters you want to log in order to set up the logcfg.txt properly. Its certainly possible for more experienced users to share set-up logcfg.txt files with others. Once EcuFlash logging is available this problem will go away. Logging with Tactrix rear wideband 02 sensor (aftermarket sensor required) http://www.ft86club.com/forums/showp...&postcount=133 Logging Information for Tactrix Adapter see also thread http://www.ft86club.com/forums/showt...light=ecuflash Below is for information only, see actual logcfg.txt files at bottom of post Currently only RAM addresses for C/D (USA) and G/I (Australian/European) ROM’s are known. ; sample logging configuration file for openport 2.0 ; must be named logcfg.txt and be placed in the root directory of the ; microSD card inserted in the openport in order to work ; this sample logs using the SSM protocol over CAN, which only works ; with newer CAN-based Subarus. ; ; note that everything is the same as the K-line example, except that "type=ssmcan" ;----------------ssm---------------- ; log channel settings ; we are logging SSM via CAN type = ssmcan ; each parameter gets a name you chose paramname = RPM ; the paramid is used in the SSM request ; ; unfortunately SSM over CAN does not support reading RAM addresses via the paramid, ; so it is not possible to read internal values. you can still do this via the K-line ; but the ECU only supports doing one protocol at a time paramid = 0x0E ; how many bits in the returned value (defaults to 8, so you usually don't need to specify this) databits = 16 ; how to scale the results using a RPN ( Reverse Polish notation - Wikipedia, the free encyclopedia Reverse Polish notation - Wikipedia, the free encyclopedia ) notation, with data and operators seperated by commas ; the operators are as following: ; + : add ; - : subtract ; * : multiply ; / : divide ; ; x : represents the raw (unscaled) parameter ; 123.456 : example of a constant ; ; if no scaling is specified, the raw value will be used ; ; the OP2 has no FPU - it must do floating point calculations in software which can ; create performance issues, so be efficient in your RPN expressions by doing the following: ; ; * minimize the number of operations; e.g. ((x * 2) + 1) * 2 => x * 4 + 2 ; * don't divide by a constant when you can multiply instead; e.g. x / 4 => x * 0.25 ; * don't make constant expressions that can instead be pre-calculated; e.g. x * 3 / 4 => x * 0.75 ; some samples of logging "bitfield" values that are not whole bytes ; if you want to log more that one of these efficiently, group them by ; paramid and the OP2 will only issue a single request to get all of ; the bits within each paramid paramname = ignition_sw paramid = 0x62 databits = 1 offsetbits = 3 ; to still acquire a parameter (perhaps for triggering or a calculation) ; but not record it in the log, set isvisible equal to zero (it is 1 by default) isvisible = 0 paramname = AC_sw ;-------------calculated parameter--------------- ; ; you can derive calculated parameters from other parameters ; using RPN expressions ; type = calc paramname = IDC scalingrpn = RPM,IPW,*,0.0008333333,* ;-------------triggers--------------- ; ; note that parameters must be previously defined ; before defining triggers using them ; ; triggers allow you to control when logging starts and stops ; this example sets up triggers such that logging only occurs ; when the engine is running (RPM > 0) ; ; triggers consist of a condition (a RPN expression using comparison operators) ; and an action. the RPN comparison operators match those in the C language: ; ; > < >= <= == != && || ; ; if the condition evaluates to a non-zero value, that action is taken conditionrpn = RPM,0,> action = start conditionrpn = RPM,0,== action = stop ; here is a second triggering example using the rear defogger switch ; uncomment it and comment out the sample above to use it ;conditionrpn = defogger_sw,1,== ;action = start ;conditionrpn = defogger_sw,0,== ;action = stop Preparing SD card for use in Tactrix Adapter Before you use the SD card, put it in the Tactrix unit and format the card accordingly. Right click > Format. Just choose the FAT32 Default. Then copy over the logcfg.txt file to the sd card and you should be set. See ones below. When you plug it up to your car's OBDII port while it's off, Tactrix should be Red slow flashing green. When you twist the key to ON position - it should turn a stable red. When you turn the car on, it should be red flashing green and blue(this means it is logging and saving data. No blue flashes means no data being saved. If it is still doing the weird rainbow transition colors - the code is incorrect or something has been done incorrectly. It should create a “logcfg.out” text file with some debug info. If all is good you should also get a logxxx.csv file created with the data which you can import into excel or similar. If you get a logcfg.out and no log data its either not talking to the ECU, not triggered , or does not understand your parameters. Actual Working logcfg.txt files for logging below Note only C and G series ROM’s available at this time. Note rename to "logcfg.txt" must be in root directory of SD card in Tactrix adapter. Note: If you have a new B00C or B01C series ROM the C series logcfg.txt files will not work you will need to substitute in the RAM addresses supplied in the file "B00C_B01C_RAM_Addresses.txt" into the current C series logcfg.txt files. Hopefully the scaling s are the same. Use example C_series_B01C_logcfg.txt below should also work for B00C ROM Additional RAM addresses for logging parameters courtesy of Td-d A00C/A01C Oil temp Ram address FFF8DC08 Ram_Engine_Oil_Temperature B01C/B01D Oil temp address Ram_Engine_Oil_Temperature FFF8DC20 ZA1JA02G definitions by Kodename47 untill Td-d adds them to github http://www.ft86club.com/forums/showp...&postcount=411 Has been found that I rom can be logged with G rom logcfg.txt file D rom can be logged with C rom logcfg.txt file Last edited by steve99; 02-16-2021 at 05:09 AM. Reason: Added more 2019 2020 stock roms |
The Following 38 Users Say Thank You to steve99 For This Useful Post: | aagun (06-09-2015), avishenoy1 (05-02-2016), Bodalenko (03-05-2017), CxG (04-06-2018), D-VO (08-03-2014), Deepseadiver (04-09-2014), etc (09-28-2016), Future (04-04-2014), GhostOp86 (07-05-2015), glorydays (04-16-2014), gt7877 (10-09-2020), Guff (04-07-2016), indy (02-07-2016), jprice130 (04-02-2014), JPxM0Dz (09-16-2016), keen as (08-08-2018), Lakitu (07-08-2018), mad_sb (04-18-2014), MFB (08-05-2014), ML (04-04-2014), platinumEX (11-03-2021), sav (02-23-2015), solidONE (07-28-2015), SportInjected (04-16-2014), Sportsguy83 (04-16-2014), stugray (04-22-2014), thambu19 (11-06-2015), TLD (01-18-2019), tomm.brz (04-22-2018), troek (08-05-2014), turbocat (04-25-2014), Ultramaroon (07-06-2017), Valentino (06-28-2015), vynervt (04-03-2014), Wayno (04-16-2016), Wepeel (04-03-2014), zeppy (04-04-2014), zmz0305 (09-14-2016) |
04-04-2014, 12:08 PM | #2 |
Senior Member
Join Date: Sep 2012
Drives: 13 White MT FR-S
Location: Gastonia, NC
Posts: 1,843
Thanks: 977
Thanked 1,137 Times in 524 Posts
Mentioned: 41 Post(s)
Tagged: 0 Thread(s)
|
Thank you so much for making this! I have been wanting to get into this and didn't know where to start.
__________________
|
The Following User Says Thank You to ML For This Useful Post: | gt7877 (10-09-2020) |
04-04-2014, 04:45 PM | #3 |
Senior Member
Join Date: Apr 2013
Drives: frs
Location: nj
Posts: 723
Thanks: 237
Thanked 347 Times in 232 Posts
Mentioned: 58 Post(s)
Tagged: 0 Thread(s)
|
the simple and effective way to protect your car from writing wrong ROM is to have a single ecu definition file for your ECU (eg I have just ZA1JA01C definition file)
Last edited by vgi; 04-04-2014 at 06:08 PM. |
04-04-2014, 04:58 PM | #4 |
Senior Member
Join Date: Jun 2012
Drives: 13 CSB BRZ Ltd
Location: United States
Posts: 1,035
Thanks: 147
Thanked 530 Times in 286 Posts
Mentioned: 39 Post(s)
Tagged: 0 Thread(s)
|
Nice post.
__________________
2011 BMW M3 (No torque dip)
2013 Subaru BRZ - SOLD - Build Thread |
The Following User Says Thank You to Acree For This Useful Post: | gt7877 (10-09-2020) |
04-04-2014, 05:17 PM | #5 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
From memory the @SkullWorks problem was early on and he just got a later release version to "recover" his ecu from a failed write. I have had a couple of failed write, which have been recovered fine with latest version. Manual and Auto ROM's are different ROM series so I believe they would be different ?? Was just pointing out that with other platforms their are more "safeguards" in place that actually prevent you writing wrong ROM. ie they look at current ROM type in vehicle before write. Will make a few changes |
|
The Following User Says Thank You to steve99 For This Useful Post: | gt7877 (10-09-2020) |
04-04-2014, 07:18 PM | #6 |
Senior Member
Join Date: Dec 2013
Drives: 2013 FRS
Location: NL, Canada
Posts: 187
Thanks: 37
Thanked 37 Times in 28 Posts
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
|
@steve99
Thanks for the great post. Could you check the hyperlinks in the OP? They seem truncated. I'd like to try out a few things once they're fixed |
04-04-2014, 07:29 PM | #7 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
fixed |
|
The Following User Says Thank You to steve99 For This Useful Post: | gt7877 (10-09-2020) |
04-06-2014, 10:52 AM | #8 |
Senior Member
Join Date: Sep 2012
Drives: 13 White MT FR-S
Location: Gastonia, NC
Posts: 1,843
Thanks: 977
Thanked 1,137 Times in 524 Posts
Mentioned: 41 Post(s)
Tagged: 0 Thread(s)
|
I am having a seemingly weird issue with RR. I am trying to open the OFT OFS .bin roms, and have the .xml definitions from OFT site added to RR, and it STILL says it can't read/find the correct .xml definitions.
NVM I got it sorted. I had to use the defs from here:https://github.com/TD-D/SubaruDefs/t...20standard/BRZ, and not the ones from OFT site.
__________________
Last edited by ML; 04-06-2014 at 04:25 PM. |
04-08-2014, 10:40 PM | #9 |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
added aditional C series ROM logcfg.txt file to OP
|
The Following User Says Thank You to steve99 For This Useful Post: | gt7877 (10-09-2020) |
04-16-2014, 02:41 AM | #10 |
Senior Member
Join Date: Jan 2014
Drives: .
Location: South Africa
Posts: 304
Thanks: 309
Thanked 239 Times in 122 Posts
Mentioned: 10 Post(s)
Tagged: 0 Thread(s)
|
Thank you steve99 for a very informative post!
Perhaps someone can help me please, I keep getting the "unable to read xml definitions romraider" error in the RomRaider Editor. I have downloaded my ROM definition file and added it using the ECU Definition Manager. When I pulled my ROM with ECUFlash it said my CALID : ZA1JA01G and that is the exact XML file I downloaded: https://github.com/TD-D/SubaruDefs/b...Z/ZA1JA01G.xml ECUFlash also gives me an error: [07:53:09.223] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata [07:53:09.273] Error parsing xml of file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/BRZ/2013/ZA1JA01G.xml: Parse error at line 31, column 72: unexpected character What am I missing?? :-/ I have read the FAQ of the RR site and has done everything they said. EDIT: I was being an idiot...lol. Maybe anyone who is struggling with the same error can learn from me: Download using the RAW tabe in GitHub. :-) All working now. You would have throught I would have learnt after downloading off that site hundreds of times Last edited by Dammod; 02-04-2015 at 02:40 AM. |
04-16-2014, 03:25 AM | #11 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
make sure you use raw mode and save page as option on browser save it as a text file , then rename to the exact ROM TYPE NAME . xml see original post. And its a zero in the rom name not letter O. It sounds like you getting none xml characteres in your definition files like possibly hlml stuff use raw option to download page. |
|
The Following User Says Thank You to steve99 For This Useful Post: | gt7877 (10-09-2020) |
04-16-2014, 03:08 PM | #12 | |
Senior Member
Join Date: Jan 2014
Drives: .
Location: South Africa
Posts: 304
Thanks: 309
Thanked 239 Times in 122 Posts
Mentioned: 10 Post(s)
Tagged: 0 Thread(s)
|
Quote:
Am I correcting in saying we are still not able to LOG using RomRaider for the BRZ? |
|
The Following User Says Thank You to Dammod For This Useful Post: | gt7877 (10-09-2020) |
04-16-2014, 06:28 PM | #13 |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,988 Times in 2,982 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
|
|
|
Tags |
ecuflash, tactrix, taxtrix, tuning |
Thread Tools | Search this Thread |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ECUFlash - Getting close! | xjohnx | Software Tuning | 698 | 03-22-2015 01:10 PM |
EcuTek Flash finished but now it shows only a Partial Flash... | Cross | Software Tuning | 32 | 02-12-2014 11:55 AM |
Tactrix Openport | jamesm | Engine, Exhaust, Bolt-Ons | 1 | 01-28-2014 09:27 PM |
Visconti Tuning - Latest BRZ Flash Info | Visconti | Software Tuning | 6530 | 12-24-2013 11:18 PM |
Overboost Protection With OFT/EcuFlash? | FrX | Software Tuning | 9 | 10-23-2013 08:27 AM |