Anybody have a wiring schematic for the S2 cluster loom? Chasing the pinouts for splicing in a different type of cluster. Overlooked the fact that my manual covers S1 wiring only Cheers Michael
Finally getting around to trialling the R34 NEO Tiptronic conversion. With a lot of help from Eric, we got the shifter fitted up and functioning properly. Just gotta splice some 48 wires into the cluster area. Should be able to decipher most of the lighting and metering wiring from the printed board on the back of the S2 cluster, just not overly game to attempt speedometer and tacho wiring without some kind of diagram
kinda sorted. Bit of a question for the electronics gurus- The Z speedo sensor is a 0-5V signal. The signal I require is 0-10V. My understanding of the speedo is that its the switching frequency that the speedo detects. Will a small amplifier work to amplify the signal from 5V peak to 10V peak without affecting the frequency? Trying to make this a plug and play setup, and not overly keen on swapping out the speed sensors. Cheers Michael
Already moulded the R34 cluster into a Z32 housing. All the gauging, warning lights and illumination work.... apart from the speedo. R34 requires a 0-10V speed signal input, and reduces the output down to 0-5V, as a 2P signal, same as what both the Z32 ECU and planned R34 Auto ECU require. Did ask the question as to whether or not a small audio amplifier will be sufficient to amplify the signal... but he didnt know
cheers for that. Read that it allows you to manipulate the signal pulse, but how about the signal voltage? Will still come in handy for calibrating speedo, should I get it working at all. Luckily tacho is at least working and calibrated perfectly. Comparing R34 gauge to ECU talk readings. Might get a cheapo jaycar amplifier and give it a go.
Got it all sorted.... kinda. Nec question- The AT ECU, Cluster and ECU are inconnected via a TOTAL CONTROL SIGNAL wire. Was hoped this signal was generated via the cluster- turns out I was wrong. A little further investigation identified the signal to be 2V at a frequency of about 20 cycles/ms. At this high a frequency, do you think a simple 2V signal will suffice? cheers Michael
Ok, so this is what I would do... try to just use a 2V 'signal' first. If that doesn't work, use an Arduino and a capacitor to make an actual signal.
Thinking it through further - if it's TTL, then 2V makes no sense. If it's CMOS, then the same - one would consider 12V to be a low and 0V to be a high. WTH is 2V?? I wonder if the 2V pulses are some kind of timing signal. Either that or it's (as you may be thinking) a reference. Have you looked at it with a CRO (or DSO) that has a wider bandwidth? You may see that it's not actually 2V at all. EDIT: TOTAL CONTROL SIGNAL. Sounds like a Japanese way of saying "System Timing Reference" (or similar) to me. EDIT 2: Seems to be the blinking light (ie Diagnostics) signal. (http://www.scribd.com/doc/24152561/Nissan-CVT-Wiring-Diagram) EDIT 3: It's used to communicate between units, so I suppose it is used for timing. http://www.scribd.com/doc/6320551/31/ENGINE-AND-TRANSAXLE-TOTAL-CONTROL-SIGNAL-A-T http://www.scribd.com/doc/6320551/63/ANTI-LOCK-BRAKING-SIGNAL-Turbo http://www.jdmlegion.com/Assets/R34_All_Workshop_Manual.pdf Pages AT12, AT24, BR18, BR20 (with example) Stopped there as project now "abandoned"?
woah..... you lost me at hello. Situation is that there's an wire between the ECU, Cluster and AutoECU. Schematic labels it as the "Total Control Signal" wire. Having swapped the AutoECU and cluster only out of the donor vehicle, was hoping that the signal was generated from the Cluster. A check through the diagnosis section has identified the signal as 2V, with about 20 equal on-off cycles per millisecond. Signal does not change through increased RPM. Given up on the project for now. Run into a bit of a snag with Speed sensor input. Dont think the traditional signal manipulator will work in my application, as the Speed sensor is powered via the Cluster, through the sensor and to ground. Have left the adaptor harness spliced behind the cluster for nec time my interest is spiked again with it. Cheers for the help
Ok, so I know you said not to worry, but I can't help but look into this further. This document (http://www.jdmlegion.com/Assets/R34_All_Workshop_Manual.pdf) on page EC11 shows some signals that may help explain what you are looking at. Look at the names for ECM pins 39 and 79. Pin 79 also goes to the TCS/ABS control unit, which further cements what I said before about inter-unit comms. Your speed sensor you want to know about is speed sensor 2. (I picked that from reading page EC13). The speed sensor signal is described on page EC41. At 2000 RPM, for a RB20DE it should be a 5V (4.7V) pulse with about 10mS duration. For the RB25DE and DET, it should again be a 5V (4.7V) pulse, but this time with an approximate 30mS duration. Pin 79 is described on page EC44 as ECM, TCM, TCS/ABS integrated control signal (multiples communication). Basically that just means that it's the signal used to communicate between those units. I hope this info helps someone.
referring to the R34 manual, its in the EC diagnostic section. Terminal 79 on page EC49. "ECM-TCM, TCS/ABS Integrated Control Signal". 'Abandoned' as in exhaust in booked in for Thursday, and have speed signal to work out first. Will definitely revisit again. Far too many hours put into adaptor loom etc to give up now... plus its a pretty cool looking shifter and cluster arrangement.
The AT ECU adaptor harness was wired using AT-9 as a reference The Cluster adaptor harness was wired using EL-19 as a reference Regarding the speed sensor arrangement, I utilised EL-22. Speed signal back to the ECU and AutoECU was via the 2P output signal wire 30 from the cluster. Although requiring re-calibrating, was reading a km/hr reading via ecutalk which was accurate to the speedo. Unfortunately, my understanding of in-line signal manipulators is that they require a signal in (from speed sensor) to modify as a signal out (to speedo). The R34 setup, as illustrated in EL-22 doesnt seem to allow for this.
EL25 shows the speed sensor input signal. It is a sawtooth between -5V and +5V, with the timing dependant upon the speed. This is where you are going to have problems and you may have to use an arduino (or similar) to create the signal from the zed's speed sensor (and a bit of old-school signal shaping to get it "just right"). I have no idea what the zeds speed sensor input looks like.
Referring to EL-25. Am using Terminal 19, as identified as Vehicle Speed Input on EL-19. With a Z32 Speed Sensor wired as per EL-22, I am getting a reading through the speedo, albeit incorrect. Although EL-25 and EL-26 illustrate 2 Vehicle Speed Output Signals (2P on cluster wire 30 and 8P in cluster wire 31) only the 2P wire is there. This, I have wired to the AutoECU, via terminal 40 and the OEM 300zx ECU, spliced into oem 2P speedo outlet point in the cluster harness.
Probably not what you now need, however it is what you were thinking of: http://dx.com/p/mini-dc-dc-voltage-...06?rt=1&p=2&m=3&r=2&k=1&t=1&s=104301&u=126106
