Mazda3 Forums banner

1 - 20 of 124 Posts

·
Registered
Joined
·
5,028 Posts
Discussion Starter #1 (Edited)
Seeings there is no information, that I can find anyhow, im starting this thread to discuss mazdaedit from epifanSoftware ( http://www.epifansoft.com/mazdaEdit.html )


There are 3 versions of the application which are discussed in detail on the vendors site (http://www.epifansoft.com/mazdaEdit-versions-prices.html). They are
  • Pro - basically for the professional tuner, big difference here is that u have direct access to the HEX file ( very very dangerous ) and can tune multiple tunes associated with different VIN numbers
  • Personal - Trial+ Locked to 1 VIN thats it and u can dump adjust and upload the hex
  • Trial/lite - Basically Logging and view of hex
Unless otherwise noted we are only talking about the Personal version however I think its all basically the same with a few little +’s and –‘s. Also, for you to be able to log, dump and program HEX files you will need the vendor recommended ODBII interface.


Another thing to consider is that the software is designed for people who know what they are doing and can figure stuff out = SO BE WARNED: you are on your own =
  • online / official documentation is currently limited
  • there isn’t a large community of MZ3 mazdaedit users
  • Not many/any template tunes to work from ( and their usage ay be restricted)
  • At fault of the vendor: You may damage and or destroy your car by adjusting the ECU configurations your self(NOT JOKING)
that said
  • if you are familiar with tuning most of the stuff exposed in mazdaedit will be recognizable and the concepts ( injector scaling, maf scaling, etc) are the same….
  • Huge flexibility and potentially much easier to tune than the FIC/Piggyback
  • Most modern day tuners will be able to work with the app and you also have dynotronics there 2 (for a fee of course which is TBO quite reasonable)
MazdaEdit - Typically available maps (as of March 2014 - mileage may vary):

  • Calculated Torque? Drive by Wire
  • Closed - Open Loop Accel Treshold - High Det Closed / Open Loop
  • Closed - Open Loop Accel Treshold - Low Det Closed / Open Loop
  • Closed - Open Loop Load Treshold A Closed / Open Loop
  • Closed - Open Loop Load Treshold B Closed / Open Loop
  • Closed - Open Loop Load Treshold C Closed / Open Loop
  • Closed - Open Loop Load Treshold D Closed / Open Loop
  • Closed - Open Loop Load Treshold E Closed / Open Loop
  • Closed - Open Loop Load Treshold F Closed / Open Loop
  • Closed Loop Fuel target? Fuel
  • DTC List Diagnostic Trouble Codes
  • EGR? #1 EGR
  • EGR? #2 EGR
  • EGR? #3 EGR
  • EGR? #3 A EGR
  • EGR? #3 B EGR
  • EGR? #3 C EGR
  • EGR? #3 D EGR
  • Engine Load Compensation Engine Load
  • Engine Load Compensation Trim Engine Load
  • Engine Load Limit #2 A
  • Engine Load Limit #2 B
  • Engine Load Limit #2 C
  • Engine Load Limit A Engine Load
  • Engine Load Limit B Engine Load
  • Engine Volume Other
  • Fuel Closed Loop - High Det Fuel
  • Fuel Closed Loop - Low Det Fuel
  • Fuel Closed Loop - Low Det 2 Fuel
  • Fuel Compensation Fuel
  • Fuel Compensation 2 Fuel
  • Fuel Compensation vs Temp Fuel
  • Fuel Open Loop - High Det Fuel
  • Fuel Open Loop - Low Det Fuel
  • Fuel Open Loop - Low Det 2 Fuel
  • Fuel Trim Long Term Load Zones Fuel
  • Gear Ratio A Other
  • Gear Ratio B Other
  • Gear Ratio C Other
  • Idle #1 Idle Control
  • Idle #1 A Idle Control
  • Idle #2 Idle Control
  • Idle Ignition Timing A Ignition
  • Idle Ignition Timing B Ignition
  • Ignition Addition - Coolant A Ignition \ Compensations
  • Ignition Addition - Coolant B Ignition \ Compensations
  • Ignition Addition - Coolant C Ignition \ Compensations
  • Ignition Compensation IAT vs ECT A Ignition \ Compensations
  • Ignition Compensation IAT vs ECT B Ignition \ Compensations
  • Ignition Compensation IAT vs ECT C Ignition \ Compensations
  • Ignition Compensation IAT vs ECT Multiplier Ignition Timing \ Temperature compensation
  • Ignition Compensation? 1 Ignition \ Compensations
  • Ignition Compensation? 2 Ignition \ Compensations
  • Ignition Correction? Ignition \ Compensations
  • Ignition Dwell Ignition
  • Ignition Timing HL Closed Loop - High Det Ignition
  • Ignition Timing HL Closed Loop - Low Det Ignition
  • Ignition Timing HL Maximum A Ignition
  • Ignition Timing HL Maximum B Ignition
  • Ignition Timing HL Open Loop - High Det Ignition
  • Ignition Timing HL Open Loop - Low Det Ignition
  • Ignition Timing LL Closed Loop - High Det Ignition
  • Ignition Timing LL Closed Loop - Low Det Ignition
  • Ignition Timing LL Maximum Ignition
  • Ignition Timing LL Open Loop - High Det Ignition
  • Ignition Timing LL Open Loop - Low Det Ignition
  • Injector Lag Time Fuel \ Injector Scaling
  • Injector Scaling Fuel \ Injector Scaling
  • Intake VVT Cams control
  • Intake VVT B Cams control
  • Knock Correction Add Ignition
  • Knock Correction Decrement Value Ignition \ Knock Control
  • Knock Correction Increment Value Ignition \ Knock Control
  • Knock Correction Max RPM Ignition \ Knock Control
  • Knock Correction Min ECT Ignition \ Knock Control
  • Knock Correction Min RPM Ignition \ Knock Control
  • Knock Correction Mul Ignition
  • Knock Sensor Scalling Sensor
  • Load Corr? Engine Load
  • MAF #1 Sensor
  • MAF #2 Sensor
  • MAP Sensor Scalar A Sensor
  • MAP Sensor Scalar B Sensor
  • Maximum Allowed Knock Retard A Ignition \ Knock Control
  • Maximum Allowed Knock Retard B Ignition \ Knock Control
  • Maximum Timing Ignition
  • Minimum Timing A Ignition
  • Minimum Timing B Ignition
  • RPM Limit A Limiters
  • RPM Limit B
  • RPM Limiter Limiters
  • RPM Limiter Throttle Close Limiters
  • RPM x11 1000 Axises
  • RPM x11 500 Axises
  • RPM x13 500 Axises
  • RPM x17 500 Axises
  • RPM x7 1200 Axises
  • Requested Torque Base? Drive by Wire
  • Speed Lim Limiters
  • Speed Limit Throttle Close
  • Target Idle? Idle Control
  • Throttle Linear 1 Drive by Wire
  • Throttle Linear 2 Drive by Wire
  • Throttle Linear 3 Drive by Wire
  • Throttle Linear 4 Drive by Wire
  • Throttle Linear 5 Drive by Wire
  • Throttle Linear 6 Drive by Wire
  • Throttle Linear 7 Drive by Wire
  • Throttle Linear 8 Drive by Wire
  • Throttle Linear 9 Drive by Wire
  • Unkn Enrichment #1 Test \ Unkn Set #1
  • Unkn Enrichment #2 Test \ Unkn Set #2
  • Unkn Enrichment #2 A Test \ Unkn Set #2
  • Unkn Enrichment #2 B Test \ Unkn Set #2
  • Unkn Ignition Timing #2 Test \ Unkn Set #2
  • Unkn Ignition Timing #2 A Test \ Unkn Set #2
  • Unkn Ignition Timing #2 B Test \ Unkn Set #2
  • Unkn Ignition? Ignition
  • Unkn Ignition? 2 Ignition
  • Unkn Limit Closed / Open Loop
  • Unkn Load Limit Engine Load
  • Unkn Load Limit A Engine Load
  • Unkn Load Limit B Engine Load
  • Unkn Load Limit C Engine Load
  • Unkn Load Limit D Engine Load
  • Unkn Load Limit E Engine Load
  • Unkn Requested Torque #1 Test \ Unkn Set #1
  • Unkn Requested Torque #2 Test \ Unkn Set #2
  • Unkn Requested Torque #2 A Test \ Unkn Set #2
  • Unkn Requested Torque #2 B Test \ Unkn Set #2
  • Unkn Th Liner Drive by Wire
  • VE A Volumetric efficiency
  • VE B Volumetric efficiency
  • VE C Volumetric efficiency


 

·
Registered
Joined
·
5,028 Posts
Discussion Starter #2 (Edited)
MazdaEdit discussion

Order and Install
There is a little back and forth on this to get license codes so it’s a multi-day affair and not an "install and go" type if thing, that said the vendor is very responsive.

You will need the following to do the install

  • OP2 device
  • USB Cable
  • Windows Laptop
  • VIN number of your car
  • Access to your car ( for some steps )
  • a working OBDII port
  • a healthy car battery ( you may be keeping the ignition on for prolonged periods of time 20~30 minutes )
Part 1 - Install and software License

  1. Order Software ( obviously )
  2. Receive email from the vendor which has the software download link
  3. Download the EXE and install it = accept license agreement and next next next...
  4. Launch MAZDAEDIT, it will present a dialog requesting that you enter in the license code for the software. That same dialog has the Hardware Fingerprint Code which you need to take note off for the next step ( you can copy it into the clipboard or write it down )
  5. email the vendor with the Hardware Fingerprint Code, what name you want the lic. to be associated to and indicate the make/model/year of your car
Part 2 - Software Activation, Device (OP2) and VIN Licensing
  1. receive email from Vendor with License code
  2. Install the OP2 drivers (download & install) from http://www.tactrix.com/index.php: two options are
    • Driver only= under Download /"download Drivers + J2534 DLL"
    • ECUFlash + Driver: under Download / "Download EcuFlash"
  3. Connect PC to the Car via the OP2 OBDII interface
  4. Launch MAZDAEDIT and input license code information.. ( I just opened the app. then opened the email with the code and registration name, received from the vendor, and copied and pasted each to the relevant input in the application )
  5. Select Main Menu/Help/Device Link
  6. Note Device id and car VIN + email that information to vendor
Note: A pop up will appear indicating the success or failure of the license registration. If successful, all is good. If not successful repeat the process carefully ensuring all information are correctly input ( copy and past is best) and if it fails again take a screen shoot and email it to the vendor detailing what you did.

Part 3 - Device (OP2) and VIN Activation

  1. You will recieve a return email with
    • Device key ( key.txt )
    • VIN key (key_vin.txt )
  2. Launch Mazdaedit
  3. Connect the op2 to the cars obdII port and to the laptop
  4. Open key.txt and select Main Menu/Help/Device Link and copy and past the text in key.txt into the device key input area and select Ok
  5. Open key_vin.txt and select Main Menu/Help/VIN and copy and past the text in key_vin.txt into the vin key input area and select OK
Note: A pop up will appear indicating the success or failure of each registration ( one popup per registration). If successful, all is good. If not successful repeat the process carefully ensuring all information are correctly input ( copy and past is best) and if it fails again take a screen shoot and email it to the vendor detailing what you did.

Part 4 - ECU Dump

  1. Connect the op2 to the cars obdII port and to the laptop
  2. Turn the ignition on
  3. Launch Mazdaedit
  4. Confirm that you can connect to the ECU by firing up the logger and connecting.
    • If it connects close the logger and go to the next step
    • If it does not connect you will need to figure out whats going on before proceeding ( confirm the OP2 is connected, that MazdaEdit can see the OP2 and after that its more than likely the OP2 is not seated correctly
  5. Within Mazdaedit select Tools/Flash Utility
  6. Select, from the dropdown to the right of the Flash Utility window, the template the vendor has told you to use (in their last email). There are two, each relating to different ECU types:
    • "Mazda3.Mazda6 2.0NA, 2.3NA CAN ECU [512kb]"
    • "Mazda3.Mazda6 2.0NA, 2.3NA ECU [1Mb]"
  7. Go to options\"read ECU for epifanSoftware" and start a dump. The process takes about
    • 12 minutes for the "Mazda3.Mazda6 2.0NA, 2.3NA CAN ECU [512kb]"
    • 26 minutes for the "Mazda3.Mazda6 2.0NA, 2.3NA ECU [1Mb]" ECU
  8. Save the dump file, using the disk icon on the Flash Utility tool bar
  9. email that dump file to the vendor
NOTE: like every other modern car, your Mazda is one of many and Mazda may have used one of two types of ECU on your car. This is not apparent to the vendor until the first review of your dump file is completed = there is a chance that you will have to repeat this process twice, once with the 512Kb and once with the 1Mb template = Be Patient

Part 5 - Template and BIN install


  1. You will receive an email from the vendor with a download of the required
    • Def file ( mep.eed file)
    • BIN file ( HEX Binary file for your ECU)
  2. Overwrite the mep.eed file in "C:\Program Files\MazdaEdit Personal\" with the downloaded def file
  3. Copy the bin file to "C:\Program Files\mazdaEdit\xxxx\" or to where ever you want
  4. Make a copy/backup of your bin file ( eg MyEcu.Hex -> MyEcu.Hex.Back) and make it read only as a "just in case"
  5. launch MazdaEdit and open your BIN/HEX file
Updates From Vendor
If you receive an update directly from the vendor the only thing you have to watch out for is the eep file. The update is basically a fresh install and it overwrites your custom eep file so you will have copy your EEP file back ( See "Part 5 - Template and BIN install" steps 1 and 2)
NOTE:

  • if you installed mazdaedit into a directory other than the default "C:\Program Files\mazdaEdit" that's where you need to put the bin and def files
  • When saving the files to the mazdaedit directory Windows will more tha likely tell you do not have the rights to do so. All you need to do is save the files to another directory, ad copy them using explorer ( which will prompt for ad grant the rights required)
 

·
Registered
Joined
·
5,028 Posts
Discussion Starter #3 (Edited)
MazdaEdit discussion

The Mazdaedit application is made up of a number of modules which are


  • MazdaEdit: Which is really the launch pad for all the other modules
  • Logging: allows you to log information from your Car for review
  • ROM/MAP Editor: Allows you to view and modify your ROM files/s
  • Flash Utility: Allows you to Dump and Flash your ECU
When combined you basically have all the tools to work on your ECU tune.

MEP Menus:



A> Main MEP Menu... Icons from left to right are

  • Open Hex
  • Save XML Description
  • ODBII Logger
  • MAZDA CAN Logger
  • Flash Utility
  • Log Viewer

MazdaEdit


Logging


Once you are up and running this is really the first thing to do. In my opinion if you don't log and record and baseline you may as well give up now.

Why? Well if you are making changes you need to know where you were and where you are now = was what you did beneficial or not ( Directly or Indirectly), did anything else change or was it just the same pre and post change. Additionally, it's a vital input to tuning and tells you what you need to do. Basically, take the guess work out of it and let the logs do the work.


Another thing to consider about base lining = any and all issues should be fixed before you start messing about... eg if your LTFT numbers are greater than 3 or less than -3 there is something wrong and you should fix the issue before doing anything else = always start from a position of correctness and tune to that position after a change....

There are two types of logger


  • OBDII
  • Mazda CAN
The OBDII logger is a fairly standard OBDII logging facility and the Mazda CAN logging facility captures all of the Mazda specific ECU stuff. Its a fairly good logger but I would recommend that you also have excel and or similar to hand to review and play with the results.

epifansoft have done a very good job with the documentation on how to use the application and you can download it from here :http://www.epifansoft.com/ecuEdit-downloads.html

The only big diffrence for MazdaEdit users is that you will have already installed the logger, so don't go and install ecuEdit, and you access logger via mazdaedit Vs ecuEdit. In other words jump straight to chapter 4.

Get familiar with the logger, its incredibly important and critical to success = if u cant see it, you cant measure it and if you cant measure it you cant manage it.


I would recommend that you keep the number of monitored items to a minimum and specific to the exercise you are undertaking ( the more items the slower the update the less accurate the log) and that a number of templates be created and tested before you get cracking. These can be used when you log and save a ton of time...

  • Fueling = LTFT, STFT, AFR, OL/CL status and RPM
  • Timing and load = Ignition timing, Load, rpm, etc
  • All = Basically everything that is interesting
ROM/MAP Editor

This is where the action and danger is. All key processes of the engine and how it operates are accessible here = you can really do some good or damage so be cautious.

When you open a HEX you are presented with an array of information ranging from Ignition to Fueling.

Before your start changing anything get familiar with the interface and set your preferences.

File:

View




Tools:






Flash Utility




The flash utility does what it says on the box, it flashes the ECU.

The flash utility can be accessed thru the main MEP application ( under the tools menu option) or thru the MAP editor ( under the tools menu option)

Before you start there are a few things to consider





  • consistency - is the flash a continuation of what is on the ecu now? = IMO it should be, if not it will be impossible to check correctness
  • correctness - is what u are flashing to the ecu correct ? = double check your changes and compare the current map to the one already flashed to the ecu ... If there are any unexpected changes or error u will spot it now...
  • version control = what is the current flash in the ecu ? - if u don't track it you will not be able to tell very easily so put a process in place like "after every flash copy the hex file to I directory called 'live'" =!that way the most recent file in the live directory will be current + you can even track back if a change does work well....
The Flash utility:


Icons - Left to right =

  • Open ECU Rom to flash
  • Save read ECU rom to Disk
  • Open reread ECU ROM in the Editor
  • Read ECU
  • Flash the ECU with loaded ROM
  • Template : selection of 2 ROM types 1Mb and 512Mb
The flash process is as follows



  • Launch flash utility. If launched
    • directly from MEP then you will need to load a HEX
    • from ROM/MAP Editor you are good to go
  • Connect the OP2 to the car and laptop
  • Turn the ignition key to full OFF ( If u don't the flash will fail)
  • Hit the Flash button in the toolbar ( little gray box with arrow pointing at it)
  • Turn on ignition and hit ok and wait for the flash to complete = about 6 minutes
  • Turn ignition full off when prompted and hit OK
  • Turn On ignition when prompted and hit OK
  • Turn ignition full off when prompted and hit OK
  • Done
If the flash process fails, and it does now and then,

  • DO NOT attempt to start the car this could be a very bad thing to do.
  • Re-seat the OP2 adapter and connections to the laptop
  • repeat process
 

·
Registered
Joined
·
5,028 Posts
Discussion Starter #5 (Edited)
Tables

The following are the table listings and descriptions broken out into


  • Confirmed
  • Unknown/To Be Confirmed
And each table will be described in the following way


  • Table Name: Name of the Table
  • Map Source/s: Confirmed models, Years and ECU size
  • Section/Type: 1D, 2D, 3D map
  • Description: Missive describing the table
  • What it Does: What it does
  • X and Y Axis: what are the axis's in the table
  • Relationships: What other tables relate to the table
Confirmed

>> Diagnostic Trouble Codes / 1D Maps
Table Name: Multiple
Map Source: MZ3 2006 1Mb
Section/Type: 1D Maps/1D
Description: Various codes and their status
What it Does: Turn on or off the evaluation process for a specific health check process. There are two cells, and the first appears to be always off. The second cell is "x01" for on and "x00" for off. If off the ECU will not evaluate or test the item, if On it will. For example, if the second 02 sensor is disconnected and the reliant table entry is x01; a CELL of p0140 will occur and the check engine light will illuminate... however if the second cell is adjusted from x01 to x00 the ECU will not check for this error and will not trigger a CELL
X and Y Axis: N/A
Relationships: ECU Diagnostics and reporting
>> Diagnostic Trouble Codes / 3D Maps / DTC List and Mask tables
Table Name: DTC List and Mask tables
Map Source: MZ3 2006 1Mb
Section/Type: 3D Maps/3D
Description: DTC HEX information
What it Does: Do not really know how to interpret this information. All info is in HEX and do not believe it would be wise to adjust any information in either table
X and Y Axis: N/A
Relationships: ECU Diagnostics and reporting

>> Fuel / 1D Maps
Table Name: Injector Scaling
Map Source: MZ3 2006 1Mb
Section/Type: 1D Maps/1D
Description: Engine fuel injector scaler
What it Does: represents and allows u to adjust the the size of the injectors
X and Y Axis: N/A
Relationships: Injector Lag Time

>> Fuel /3D Maps
Table Name: Injector Lag Time
Map Source: MZ3 2006 1Mb
Section/Type: 3D Maps/3D
Description: Fuel injector scaler
What it Does: represents and allows u to adjust the the size of the injectors. The MAP reading is in scaled from 102 to -15 / 0 is sea level / Positive KPa's are measurement of vacuum and negative KPA's are positive = its inverted.... 1bar is 0, 0bar is 102 and -15 KPA would be 1.x bar
X and Y Axis: KPa ( MAP) X Voltage.
Relationships: Injector Scaling

Unknown/To Be Confirmed
Table Name: D01
Map Source: MZ3 2006 1Mb
Section/Type: 2D Maps/2D
Description: Unknown function
What it Does: Unknown function
X and Y Axis: Unknown / Unknown
Relationships: Unknown​
 

·
Registered
Joined
·
77 Posts
Thanks for copying and pasting the available map list Epifan sent me, here. This should be a super useful thread even for the non-turbo guys. Can't wait to order my Tactrix cable!

According to Epifan though, some of the maps may have detailed descriptions like Evo version of EcuEdit. It's sometimes a little hard to tell exactly what he's saying since he's Russian and a lot of his stuff is translated.

I guess you can read his responses and decide for yourself...

http://www.epifansoft.com/phpBB3/mazdaedit-map-definitions-for-mazda3-t1144.html
 

·
Registered
Joined
·
8,599 Posts
Subbing. You're tuning this yourself, or is DT going to step in?

What was the cost for the softwre/license/hardware?
 

·
Registered
Joined
·
5,028 Posts
Discussion Starter #9
Yep that's what this is ... No glory just info ... Mazdaedit only ... Not build specific just add as info becomes available ... Don't know how ill tune may go to dt maybe not tbo ... Need to look at what's out of the box ... Regardless the info regarding mazdaedit should probably end up here


No sig for me
 

·
Registered
Joined
·
749 Posts
Yep that's what this is ... No glory just info ... Mazdaedit only ... Not build specific just add as info becomes available ... Don't know how ill tune may go to dt maybe not tbo ... Need to look at what's out of the box ... Regardless the info regarding mazdaedit should probably end up here


No sig for me

just let me know if you need a hand, happy to help. My logic is that the more folks do this and learn, the more the platform will move forward.

99.5 % of tuning is simple logic, and the rest is simple trial and error.

The nice thing about the ME software is you can make of it what you will; of the 800+ tables in the early ecus only a very few are defined (late models are more complex and way less defined). We have defined quite a few here in house, and I think we are up to 300+ on the 2004-2009 mitsu based ecus.

If you run into an issue, let me know and I will be more than happy to point you the right way.

Good luck!!!
 

·
Registered
Joined
·
77 Posts
Ps direct from vendor cost I think may be a little more or about the same as dt ....


No sig for me
This is correct...

I'm not a paid supporter or Dynotronics or anything, BUT I would recommend going through him for the MazdaEdit license for 2 reasons:

A.) For some reason, DT is able to offer the MazdaEdit personal software license for $25 cheaper than directly from EpifanSoftware themselves ($225 vs $250)

B.) Also... if you go to the Epifan website and get ready to check out, there are only 2 methods of payment and BOTH are through some sort of online 3rd party. Furthermore I googled the both of them and they have more bad feedback than good so I'll leave that up to you. Check them out: Avangate and Plimus, both of which I've never heard of and would be weary to send that much $$$

Dynotronics is right here in the USA, located Texas and accepts credit card directly or paypal so if any issues should arise, your chances of getting your money back and not getting the shaft are much better with Dynotronics I'd assume.

Happy tuning!
 

·
Registered
Joined
·
5,028 Posts
Discussion Starter #13
This is correct...

I'm not a paid supporter or Dynotronics or anything, BUT I would recommend going through him for the MazdaEdit license for 2 reasons:

A.) For some reason, DT is able to offer the MazdaEdit personal software license for $25 cheaper than directly from EpifanSoftware themselves ($225 vs $250)

B.) Also... if you go to the Epifan website and get ready to check out, there are only 2 methods of payment and BOTH are through some sort of online 3rd party. Furthermore I googled the both of them and they have more bad feedback than good so I'll leave that up to you. Check them out: Avangate and Plimus, both of which I've never heard of and would be weary to send that much $$$

Dynotronics is right here in the USA, located Texas and accepts credit card directly or paypal so if any issues should arise, your chances of getting your money back and not getting the shaft are much better with Dynotronics I'd assume.

Happy tuning!
I agree but I bought straight from the vendor... if there are issues ill let u know

sent off the device serial no and vin tonight... so far a very smooth process ... 3 days so far + 1 waiting for the OP2....
 

·
Registered
Joined
·
77 Posts
Driver's for openport come with their free flash software for Evo's. You only need to download EcuFlash from the tactrix website and use it to setup the drivers for openport. Then use MazdaEdit.
 
1 - 20 of 124 Posts
Top