I've used a GoDiag J2534 cable which is around 30 bucks I think. It works just like the tactrix. The only difference is that you need to rename the godiag drivers to the tactrix dll that the software looks for.

 

More big news:

https://github.com/Rx8Man/Rx8Man/releases/tag/1.20

RX8Man has released a combined logger and ECU dump/reflash tool that supports ANY J2534 device. I don't think anything has been tested aside from a tactrix, but it is ready for someone to try!
Big note: Reading your ECU ROM will not ever cause it to be bricked, so if you're willing to dump a ROM with a different device, now is a great time!

 

Has anyone got a diagram for the boot recovery circuit? Struggling to get my head around the pull up/ pull down resistors.

My first attempt at a reflash has gone poorly and I've currently got a neat paperweight on my desk

 

Post your RX8man app log in AppData/Rx8Man and we can see what the reflash error may have been?

Also, I will update the boot mode post to be a little more clear. Give me a few!

 

Unfortunately the folder is empty, but it was writing blocks, then had an OBD11$ error.

After removing the ecu from the car I see it's been reflashed by a local tuning company with a "Stage 1 Mail in tune", is there a chance the two different tuning software have disagreed?

the ecu is an N3YMED, I had to do a bit of fiddling with the other JDM definitions to get it to read my ECU.

Bin file has been removed to prevent anyones toes ebing stepped on, have left the def file to suit the n3ymed/60E0E600 ecu.

 

Updated the Boot mode post with a schematic for ya.

If the ECU has been tuned previously, it's possible seed/key magic word has changed.. but if that were the case it also shouldn't let you dump the ROM.. hmm.

I have had issue with flashing third party vendor maps on some hardware though... may be something similar. I'll look at the ROM.

 

Awesome, thanks for that.

Will keep you updated once the hardware arrives and I get a chance to have a go, i've got another ECU on it's way, but I'd like to know the reflashing will work for me before I get into playing with that one too.

 

Can you also post the ROM you were trying to flash?

 

Made a change to the cold rev limit as a simple first test before I looked into tidying up the OMP etc.

 

Those files are binary same, so something is kinda wonky on your end if you did in fact make some changes.

 

Yeah, would appear I saved to the original dump as well as the new one, have attached the first dump I did.

Will ammend my orignal upload too

 

Sending you a PM

 

I'm posting the resolutuon for anyone who encounters a similar issue later on, attempted to reflash the ecu with the new RX8Man software after reverting my laptop to Win10 and it took the file no worries this time.

Cheers equinox!

 

I updated the git repo with FastLemons defs, which appear to be mostly correct. They don't have as many as the USDM ROM I usualyl work with, but porting them should be easy for someone that really cares to use that ROM as a baseline.

I think this opens the door for some JDM ROMs to be easily defined in the future too..

I did notice that the DTC list seems to not be aligned quite right.. but I did also notice this for some other ROM defs too, so it may just be a matter of finding the correct start of the table in the ROMs and appending each index appropriately.

Either way, yay more defs.

https://github.com/equinox311/RX8Defs

 

I've been through and found the DTC list, I have ammened my def file, but will need to trial some DTCs on/off to test it.

Both the JDM ROMs I have don't appear to use the 03 or 05 flag for any DTCs like the USDM ones do, unless it's hidden in a different table.

Have also added a JDM auto 4 port rom into the Def file, which appears to share many of the same table refs as the 6 port map.

 

Wanna shoot me those ROMs somehow.. stock or not, would like to confirm defs and stuff... but if they are known stock I'd also like to add them to the stock ROMs repo

 

Pushed those defs to main + added some immo deletes.. will update immo delete scripts as I found a few bugs

 

This open source tool is awesome! I got it to work with a Godiag cable as well from ebay. Definitions weren't there for fan trigger controls for my version so I added them based on equinox's definitions for his version. I managed to tweak fan trigger temps, oil metering load, and idle. At first I thought I bricked the ecu when the write failed, the car wouldn't start and nothing was reading from the obd2 port. But I used jumper cables to a running car to my battery and tried it again and it worked!

Added tables for fan trigger temps for 60E1B900.

 

Badass! I'll make those additions to the mainline defs.

Also: I was contacted by someone from the company OBDXPro and they are sending me some cables to test out RX8Man with. If they work, which I am thinking they will, they might be a great alternative for Tactric cables and open this software up to more users.

Will report back with my findings!

 

I have a question. I have a 6-port EU RX-8. I used Rx8Man and a GODIAG Nano to dump the ECU. When I load the file in RomRaider with the latest definition file from equinox311, it gets recognized as a 4-port 60E0G500 (N3ZGEC).

If I check my dump at address "0006CE40", it shows "00SSW-N3ZHEC000.", so it should be recognized as a 6-port, right?

Is it safe to modify and flash the file even if it is identified incorrectly?

 

Post the ROM, it's probably just a naming error in the defs as that information is just metadata.

 

If I swap the order of NZ3HEC and NZ3GEC in the definition file—so that NZ3HEC appears later in the file—it gets recognized correctly. It seems like RomRaider doesn’t actually care which one it is, but just reads everything sequentially from top to bottom.But the key thing is that it’s recognized as 60E0G500?

 

Yep that's correct. it's just a clerical error within ROMraider. All the calibrations appear correctly for that ROM.