Looking for wiring diagram with vr4 coils setup, galant diagrams are useless as they running on dizzy cap, can anyone point me in the right direction pretty please
Printable View
Looking for wiring diagram with vr4 coils setup, galant diagrams are useless as they running on dizzy cap, can anyone point me in the right direction pretty please
PDF16 of the Jap manuals https://www.clubvr4.com/forum/showth...p-Manual-PDF-s
Page 13
I thought it might be in the russian manual but the entire ignition section is missing :(
best i can offer sorry. With the pinout of the plug, compare to the 4G COP setup in the EU manuals, get wire colours and firing order, track back to ecu.
Thanks Jake, I find out what Im after by opening my spare loom, after my COP loom spectacular failure, with lots of smoke, tape used (Self-Amalgamating Rubber Tape) cant cope with heat and just turn in liquid rubber and shorten cables, lucky enough i was stationery but brown pants moment for sure, so im looking to redo it whole but from the source to have as little connections as possible, here are my findings
Power to coils come from ecu on 1 wire(Black/white) pin12 con4
Attachment 83088
To IFS pin 4
Attachment 83089
then black/white) pin 3 from IFS goin back to firewall :huh2: and its split to 3 separate wires going BACK to coilpacks
Attachment 83090
All 3 GND wires meet there
Attachment 83091
Now need to rethink how to simply it to make as little connections as possible to lower risk of failure, seem like 3 power wires are actually one wire comes from IFS, same with GND so that's potential of elimination of 4 connections :thinking:
Signals obviously comes straight from ECU so they must stay as they are.
Sorry dont have a scanner handy - but here's diagram you're after
Hey bill @BCX what is the number of the document for the VR4 wiring diagram?
i could do with one of those if i have the number i can look out for one of those on the PDF manual website.
I'm hoping to scan this document in once I can head into work, have been working from home cos of covid.
If i do, will upload it.
that would be great.
but do you the doc number for reference.
I've got 1038S74 & 1038S75Quote:
Originally Posted by Davezj
Thanks Bil,
i seem to saying this a lot recently.
reputation points coming your way
No problems, I just wish I had more time to dedicate to my VR4 and the community.
Lots of projects, so little time!
Quick question for you on the def files.
and just to confirm, the romid section at the top of the def files, if i am using a 7202 ecu i have to change all the memmodel lines to H8539F from the H8539FA (for 7203 ecu).
i did notice you have the VR4base def file has memmodel set to h8359af which will probably stop it from working.
am i right in thinking this.
i have a 7202 ECU with auto box and i would like to include the VR4_ AT_ base.xml
so as i see it, the EMKS11.xml calls the 20030010.xml which in turn calls the VR4Base.xml
so if i want to use the VR4_AT_base.xml i need to add a line to say <include>vr4_AT_base</include> in the vr4Base.xml to call the VR4_AT-Base.xml from the VR4base.xml.
i know this is the very basic stuff of def file manipulation, i just want to confirm i am doing it right?
which ever 2003001x.xml (or EMKS11) that is matched to the internal id of the rom, thats really the one you need to change between h8539f and h8539fa - the vr4base.xml value is ignored/overwritten by the 2003001x.xmlQuote:
Originally Posted by Davezj
To be safe, you could change all xmls to be sure though.
The other behaviour i've seen is, depending on which read template used to suck the rom off the ecu i think will then override whats in the XML.
to confirm before reflashing/bricking your ecu, check under here:
Attachment 83111
ultimately, if this isn't right, then you need to save rom, edit xmls and reopen.
note: either read template for h8539f or h8539fa will read a 7202 or 7203. its when you are writing back that you have potential to brick your ecu. hence a visual inspection of the processor version is advised and then double check.
vr4_AT_Base.xml is used to open the ROM off the TCU (not ecu)Quote:
Originally Posted by Davezj
to read the TCU rom, you'll need re-pin the reflash connector and move the pin over one. Your reflash connect on the vehicle side will have 2 wires - 1 reflashes the ECU (standard location when you buy the reflash connector), other one reflashes the TCU.
once you've got the rom, provided ecuflash is pointing to folder that contains these definitions, then it should open up automatically.
if it doesn't, upload the rom and I'll have a look.
but the reason you cant just inherit vr4_at_base is cos TCU and ECU are different control units and run different code.
Hope that makes sense?
Later Mitsubishis that use the SuperH processors (Evo 7-GTA, Magna/Diamante) have both transmission and engine code on the same chip/rom/control unit (in superh world, usually see this as 256kb roms vs 512kb roms)
Thanks again Bill, you are a star.
sorry i was being a muppet with respect to the VR4_AT_BASE.xml
i am not sure why i got confused with the VR4_AT_base and the TCU i know they are separate control units and you have to swap the pins to read the TCU.
just a muppet moment. LOL