Jump to content
SAU Community

Recommended Posts

Hi

I got a new remote key but I can't program it according to the service manual of the G35, according to the manual, the hazard light should flash, however, instead flashing, all doors are unlocked, after that I follow the instructions but nothing, any idea? I followed this instructions.

1. Close and lock all doors with the driver’s side power lock/unlock switch.

2. Insert key into ignition and remove it from the ignition key cylinder at least six times within 10 seconds. Your Hazard

Lamps will flash if you have performed this step successfully. NOTE: Withdraw key completely from ignition cylinder

each time. If this procedure is performed too fast, system will not enter programming mode.

3. Insert key into the ignition cylinder and turn to the ACC position.

4. Within 5 seconds, push ANY button on the remote transmitter. Your Hazard Lamps should flash. NOTE: Do not press

the button more than one time in the above step. If the button is pressed more than one time, the programming

procedure will not be successful.

5. If there are any remaining transmitters (including the old ones), unlock then lock all doors using the driver’s side

power lock/unlock switch and within 5 seconds, push ANY button on the next remote. Your Hazard Lamps should

flash. Repeat this step for each transmitter (including any existing transmitters).

6. Turn the key to the OFF position, remove keys from the ignition, unlock doors using the driver’s side power lock/unlock switch and open the driver side door.

cheers

Link to comment
https://www.sau.com.au/forums/topic/398118-programming-remote-control/
Share on other sites

  • 2 weeks later...
  • 6 years later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • Ok interesting i guess ill wait till using a manual gauge before making assumptions.
    • Not in any way a logical conclusion. Also, looking at those logs, I struggle to see how that much oil pressure can go away that fast unless you are sucking air into the pickup. Meanwhile the ECU voltage is chucking a huge wobbly which seems to be tied to the throttle position. 100% throttle results in decreasing voltage. It's a mess.
    • So didn't get around to installing a manual oil pressure gauge and then decided to take the car for a cruisey drive to a cars and coffee and brought the laptop along with to get another log using more gears to see if its an oil pressure issue under acceleration or after. this log has 3 gears of WOT where as previous had 2 and the oil pressure dropped once on the brakes, and the same again happens here which is interesting as it shows it can hold oil pressure while under acceleration but once slowing or just the lower RPM after a pull pressure drops. I will be chucking a manual oil pressure gauge on to confirm but so far this makes me feel it is not an electrical issue. Something else i realised is the pressure sensor also is giving temperature information and the temp stays steady the whole time which makes me feel like the sensor itself is showing a true pressure reading.
    • LOL.... fk...   there goes 25K to make 200kW
    • For sure the later RB26 variants had a different setup (6 cam voltage sender?), but the RB25DE/DET share the same ECU pinout/PCB footprint, and at the ECU plug it ends up being 'throttle sensor in' & 'throttle sensor out' (to A/T TCU) ...you stick a multimeter on these pins and you'll find them directly connected (0 ohms) ; I had an pair of Nissan ECUs on the bench long ago, and I noticed this throttle sensor in/out link, actually linked to an op-amp ...which was unpopulated on the NA board, but present on the T board and I went 'ah-ha!' in some moment of clarity... ...it wouldn't surprise me if they changed strategy here though (in the software and actual monitoring of this signal), because they did with other stuff (A/T signals).. and 0.45v as a trigger point makes sense, as that's what the external TCU units expect at idle ; kudos, thanks for that insight...I suppose it boils down to whether or not Consult can display real time data of that signal's voltage... ...in any event, it presents the same target...ie; rotate TPS unit to achieve 0.45v to suit both ECU&TCU, and where do you goto from there? Just disconnect TPSwitch connector and/or that plus TPSensor connector....or do you go for the throat and disconnect IACV solenoid and see if it still stalls? (probably throws a recoverable fault code and goes for default idle strategy?)...
×
×
  • Create New...