- Location
- SA
- First Name
- Bill
- Drive
- 2000 Galant Type-V
1997 MK Triton GLS [6G74 conversion]
2019 i30 N-Line
Hey Guys,
I thought I’d start this thread as a bit of a brain dump of what I’ve been working on for the last few years with a big help from Steve - TME_Steve & Kenneth. Basically, I got sick of seeing the same crap VR4 EcuFlash definitions, so I’ve gone to the effort of disassembling the VR4 ROM.
First and foremost - my disassembly is very much based on assumption. It's by no means accurate - but I’m hoping with the help of the greater VR4 community, I can get my disassembly more accurate, which in turn means more comprehensive definitions.
What I present to the VR4 community is my version of definitions (work that I’ve done so far). I took the current version of definitions that are going around, cleaned it up, and then corrected/confirmed them with the actual disassembly. I'm hoping for feedback in this thread (names, whether tables are working), and I will correct the definitions and republish the new version so at any point everyone can access the latest versions. I will also post my findings in this thread, as I’ve found a lot of little things that might be handy for everyone (what the various MUT locations are - plus an EvoScan XML file for you to have fun with, what unused Pins on the ECU can be used as input/outputs)
I know there has already been a lot of work, and I’ve taken parts of what’s already been done. So it's difficult to give credit to everyone that has worked on this already. Having said that, a few people that I’d like to credit so far:
Enjoy.
See Github for latest defs: https://github.com/OZVR4/ecuflash-defs
Cheers,
Bill
PS. By using these definitions and information, I accept no responsibility for any damage (blown motor, bricked ecu, death/injury, etc) or costs incurred (fines, defects, void insurance, cost for repairs, etc) in relation to this definitions. They are provided as-is, and by downloading and using them, you are accepting all responsibility.
I thought I’d start this thread as a bit of a brain dump of what I’ve been working on for the last few years with a big help from Steve - TME_Steve & Kenneth. Basically, I got sick of seeing the same crap VR4 EcuFlash definitions, so I’ve gone to the effort of disassembling the VR4 ROM.
First and foremost - my disassembly is very much based on assumption. It's by no means accurate - but I’m hoping with the help of the greater VR4 community, I can get my disassembly more accurate, which in turn means more comprehensive definitions.
What I present to the VR4 community is my version of definitions (work that I’ve done so far). I took the current version of definitions that are going around, cleaned it up, and then corrected/confirmed them with the actual disassembly. I'm hoping for feedback in this thread (names, whether tables are working), and I will correct the definitions and republish the new version so at any point everyone can access the latest versions. I will also post my findings in this thread, as I’ve found a lot of little things that might be handy for everyone (what the various MUT locations are - plus an EvoScan XML file for you to have fun with, what unused Pins on the ECU can be used as input/outputs)
I know there has already been a lot of work, and I’ve taken parts of what’s already been done. So it's difficult to give credit to everyone that has worked on this already. Having said that, a few people that I’d like to credit so far:
- Steve (TME_Steve) - His wealth of information has been invaluable to know what’s going on
- Kenneth - Bits and pieces that Kenneth has given me has helped me a little bit to disassemble.
- Ceddy – Info he’s posted on his Evo work has also helped with understanding disassembly.
- WytWun - his work on Magna definitions has helped answer some questions relating to unknown tables
- kc427 - provided some insights to various tables, such as fan control
- GLen20 - picked up an error with incorrect load scaling applied to tables/axis.
Enjoy.
See Github for latest defs: https://github.com/OZVR4/ecuflash-defs
Cheers,
Bill
PS. By using these definitions and information, I accept no responsibility for any damage (blown motor, bricked ecu, death/injury, etc) or costs incurred (fines, defects, void insurance, cost for repairs, etc) in relation to this definitions. They are provided as-is, and by downloading and using them, you are accepting all responsibility.