Body ECU Ignition Feed Question

mav2287

Member
I am working on installing a remote start on my 08 4runner using the factory fob. (Yes I know it would be like 10 times easier to use an aftermarket one...but I just really like the factory fob and don't want another one). The install is pretty easy to do as far as picking up the lock signal to activate the remote start and then starting the car. The problem is that you can't use the fob when the engine is running. So your locked out of the car once it starts.

I have been working on this for a while and far what I have learned is that the fob will unlock the car if the key is in the ignitor and even if it is turned to accessory. It is when you actually turn it to run that the unlock button on the fob stops working.

In a post over at the 12Volt here, 04 4runner remote start w/factory remote , they talk about possibly cutting a connection from the ignition to the body ecu that may be the ignition feed, but the post goes cold and we don't know if it worked. The thought was that the body ecu would think that the car is not running and allow the fob to unlock the car. I don't have the wiring diagrams so I can't back trace it and it's snowy and icy here so I won't be able to do testing for at least a few months. I am hoping someone knows about the body ecu.

My though is I could put a normally closed relay in between. The body ecu would act normally and always have access to the ignition feed except when the remote start powers up that relay and disconnecting that wire. The Body ECU would then think the car is not running and let me use my fob to unlock it again.

I am hoping it is just a positive or negative ignition feed wire. Anyone have any insight on this? Or maybe a Pinout of the connector for the Body ECU?
 
Register to hide this ad
Most likely it won't work because the Main Body ECU probably has other uses for the "Ignition" signal beyond just turning off the keyless entry function. I would imagine severing it would confuse the system some. I could be wrong though.
 
That is part of the reason I was hoping for a pin out. I would really like to be able to see what all it does. I don't know of much that changes as far as what happens between acc and run. The engine ECU is the one that should be doing the work at that point.

The real question is does it have a key sense wire I could disconnect like I am hoping. If it does I can just pop that out of the connector and see what happens.
 
That is part of the reason I was hoping for a pin out. I would really like to be able to see what all it does. I don't know of much that changes as far as what happens between acc and run. The engine ECU is the one that should be doing the work at that point.

The real question is does it have a key sense wire I could disconnect like I am hoping. If it does I can just pop that out of the connector and see what happens.

So... a couple of years later (and while it's really cold here!!!) I'm revisiting the remote start issues. I still would like to use a factory keyfob.

I (think) I answered many of your questions in the trhead on the the 12 volt forum that you linked to. I went back and added diagrams and info.

The answers are below.

I'm looking carefully at the Fortin Evo-one solution.
It includes an optional harness to make the install much easier.
Anyone have any info on it?

https://www.sonicelectronix.com/item_91515_Fortin-EVO-ONE-Digital-Remote-Start-and-Security-System-and-Data-Interface.html?utm_source=google&utm_medium=cpc&utm_campaign=Shopping-Campaign-General&gclid=Cj0KCQiA7dHSBRDEARIsAJhAHwiu6W_jsmpVDNelXojp73TTJK-2yT6S2MjBCQFl-HvVTpgqAJPrpusaArYAEALw_wcB

------------------------------------------

The answer is to unlock, the body ECU needs to think that the ignition switch is off. I posted where and how I think you can do that, and I don't believe (but haven't tested it) that it will cause problems. The body ECU is focused on the truck's body, not on engine management, so I would expect that a modification wouldn't change the fact that the engine is running.

To be able to lock the doors, the body ECU looks at the ignition input, and the key sense input, so you would have to be able to deal with both of those wires.



Note: I've recently discovered some remote start applications for my '08 that offer a "T-Harness" for the hook up, and appear to require very minimal connections beyond plugging in the harness... I'm intrigued.

One thing to note: If your remote start turns off by timing out, or you program a way to remotely turn the truck back off, you will need to find a way to trigger the driver's side door wire to make the truck think that the driver's door was opened and then closed. This is what makes the truck turn off the headlights when they are in automatic mode. If you don't do that, the headlights will stay on, not turn off, and end up draining your battery. It seems that it can be done if your system has an "alarm re-trigger" function. See http://www.toyota-4runner.org/4th-gen-t4rs/227276-remote-start-auto-headlamps.html#post2505539 for more info.
 

So I've confirmed that the Fortin Evo-one requires a separate RF transmitter for use on 4th Gens. It won't work with the factory remote. It does have a wire that can be grounded to remotely trigger the system, so I will look to see if there are any "hacks" that I can think of using something like a PAC TR7 to trigger the remote start using a signal received by the TR7 because of a factory remote action, such as (perhaps) locking the door three times in succession (if that turns out to send three lock commands from the body ECU). I'll have to think through this some, and maybe do some testing. For example, I wouldn't want someone pressing the lock BUTTON inside the truck three times to make the truck start up... that's not a desirable side-effect... but maybe two well-positioned diodes could prevent this side-effect by isolating the remote start ground-sense trigger so that it can read an unlock ground pulse from the body ECU, but not be affected by any lock pulses caused by someone physically pressing the lock button inside the truck itself -- assuming that such a side effect even exists to cause a problem.

If I end up going this route, or finding out anything useful, I'll be happy to update this thread.

Regarding the headlight turn off issue... the evo-one can handle it. A post on their form said to

1. Connect the DARK BLUE (A8) to the door trigger wire and enable option 32.3. This will pulse the door trigger on remote start shut down to replicate door open. The auto lights will turn off 30 seconds later.
Door trigger is RED/BLACK @ driver kick panel OR Body ECU middle 24-pin white connector, Pin 23
 
Last edited:
Something similar to this actually came up in another thread not to long ago along the same alines. http://www.toyota-4runner.org/4th-gen-t4rs/232473-oem-fob-remote-start-solved.html

The only thing that worries me about disconnecting the body controller is that the system has a CAN network sending messages so even though it might look like everything is ok it might get nasty quick.

If you read the thread I mentioned above my solution was to watch for a unlock or lock signal from the receiver so you could then mimic a door lock switch push. Then if you wanted to get fancy you could flash the hazards, but the factory beep beep buzzer is the real PIA to get working if you wanted to make it seem 120% OEM looking and sounding. At some point I will crack that too, but I got another kid due in about 2 weeks so it won't be anytime soon.
 
Something similar to this actually came up in another thread not to long ago along the same alines. http://www.toyota-4runner.org/4th-gen-t4rs/232473-oem-fob-remote-start-solved.html

The only thing that worries me about disconnecting the body controller is that the system has a CAN network sending messages so even though it might look like everything is ok it might get nasty quick.

If you read the thread I mentioned above my solution was to watch for a unlock or lock signal from the receiver so you could then mimic a door lock switch push. Then if you wanted to get fancy you could flash the hazards, but the factory beep beep buzzer is the real PIA to get working if you wanted to make it seem 120% OEM looking and sounding. At some point I will crack that too, but I got another kid due in about 2 weeks so it won't be anytime soon.

First my disclaimer... I haven't done this yet, so I'm working off of theory and what "should" work.

With that out of the way, your canbus explanation is exactly why I believe that the body ECU trick SHOULD work.
The Body ECU isn't reading CANBUS messages. Although, in theory, everything could be connected to the canbus, and
send and receive messages over it, that's not how the 4th gen was designed.

On the 4th Gen the CANBUS use is far
more limited than it *could* be. I'm assuming it's used for engine management, maybe antilock brakes (maybe not), and some other
critical operation items on the truck. On the 4th gen, the canbus IS NOT used for many other functions where it theoretically could have been used, such as locking and unlocking doors, starting the truck, activating and deactivating the engine immobilizer system, controlling the heat and A/C and more. So, the Body ECU doesn't use the CANBUS, isn't connected to the CANBUS, and the CANBUS and the body ECU know nothing about each other and don't impact each other directly.

So, here's what's needed to make the remote lock and unlock doors while the truck is running under the control of a remote starter:

In short, you need to do two things regarding remote start:

First) Only ground the key sense wire at the ignition harness while the engine is cranking. Otherwise, leave it alone. The truck needs to think that the key is in the ignition to let the engine start. Once it's started, the key sense wire shouldn't impact the engine running, so you no longer need to "fool" the truck into thinking that a key is in the ignition, and -- in fact -- if the truck DOES think that the key is in the ignition, then the trucks Body ECU will ignore a request from the remote control to lock the doors.

Second) The body ECU's input (sensor wire) for the secondary ignition needs to be disconnected once the engine is running
under the control of the remote start unit.
At all other times, the wire should remain in its normal connected state. Use a relay with its "normally open" and "normally closed" pins to do this -- but don't forget to include a flyback diode to prevent against voltage spikes when the relay coil switches from energized to turned off (google it if you're not familiar -- this is an important concept when adding relays).


Now: Here's why it will work.


The door remote module (located in the D pillar in the back) always detects button presses from the remote, and always sends out the correct pulses on the "RDA" line to send a properly encoded message indicating what button was pressed. This MUST be the case, because the door remote unit only has three main wires (the fourth, program wire is only used to pair a new remote to the truck).

So the three wires are +12V, Ground, and RDA -- it uses RDA to send an encoded signal indicating whatever button presses it received from the wireless remote, and it always sends out this encoded signal over the RDA wire, regardless of the state of other systems.


Now: The Body ECU is what decides whether and how to act on button presses that it decodes from the RDA signals sent from the door remote module.

So, if you turn off the truck, exit the vehicle, and press the "lock" button on the remote while the passenger door is open, you get that annoying long beep, which tells you that a door is still open. It's the Body ECU that makes those decisions, and also determines what actions to take such as lock the doors, unlock the doors, send out one of several different sounds, flash the turn signal lights, lock the doors, unlock the doors, etc.

Now. It's documented in the factory manuals that:

1) The Body ECU will ignore an unlock RDA signal from the door remote module when Body ECU senses that the ignition is on. It senses this via pin 10 on the body ECU -- which is the secondary ignition input to the body ECU. So if you use a relay to disconnect that input wire while the truck is running under control of the remote start, then the Body ECU will handle and process the unlock command for you -- INCLUDING issuing the correct, factory beep.
Make note about the need for diode isolation if you are also using that wire to power your immobilizer bypass module. The info is in the links referenced to the 12 volt forum.

2) Regarding a lock signal sent by the door remote module to the body ECU, the body ECU will ignore the lock signal if either of two things are present.
a) The body senses the truck is in the "on" state, based on reading the input state of the "SIG" (Secondary ignition) wire on pin 10 of the body ECU. We've addressed that issue above (see "1)" ) by adding a relay with the flyback protection diode.
or
b) The body ECU believes that a key is in the ignition, based on reading the value of the key sense wire from the ignition harness.

So, if while the truck it is running on remote smart, if after unlocking the door with the remote, you want to re-lock the door, you will also have to make sure that the body ECU does not believe that a key is in the ignition based on it's readling of the key senses wire from the ignition harnngess.
While you can accomplish this several ways, the easiest is to hook up your remote start to the keysense wire using an output from the remote start unit that sends a ground signal ONLY WHILE THE STARTER MOTOR IS CRANKING, and otherwise leaves that output disconnected. This, the easiest solution, means that the body ECU will only believe that a key is in the ignition while the engine is cranking. Once the cranking stops and the truck is running, the body ECU will think that there is no key in the ignition and based on this (plus the solution from "1)" above that makes the body ECU think that the ignition is off), the Body ECU will process lock and unlock signals received from the door remote module, and the behaviour (including beeps and light flashes) will be 100% factory. As an interesting note, the rear window roll down feature should also work (I believe), because the body ECU will believe that the truck is not running, and the key isn't in the ignition, therefore the body ECU should behave as if the truck were turned off with no key in the ignition.

If you want to test this theory, get in the truck. Start it with the key. Turn off the truck and remove the key (but don't do anything else), and then while sitting there inside the truck, see if you can use the remote to lock the doors, unlock the doors, and roll down the rear window. I'd bet that you CAN do this, and the reason is because the Body ECU thinks that the car is turned off becuse of no signal from the secondary ignition input (pin 10), and it believes that the key isn't in the ignition, based on not reading a ground from the key sense wire on the ignition harness.

The proposed solutions above (in"1)" and "2)" ) would make the body ECU believe the same thing once the truck is running because of the remote start, and "viola", your remote will work to lock and unlock the doors, even when the truck is running via the remote starter. !!!

Would it be appropriate to write "Q.E.D." at this point? (That's a math reference to having finished a mathematical proof.)

... or is that premature, since -- just like math -- this is still theory. For some, you have to move beyond the "white board" analysis, and conduct an experiment to prove that the theory is correct! (and sometimes, an experiment shows that the theory was NOT correct!) -- but I'll stand by my analysis here unless and until someone tries it and tells me that their truck blew up because of these suggestions (!!!) hehe !

;-)

-Phil

----------
P.S. -- If I install a remote start in my 2008 4runner, (assuming I install it myself), I WILL hook it up according to my predictions, and I WILL post back here with an update to thump my chest and proclaim that all is well in the world (!!!), or (alternatively) to confess that Mr. Smarty pants (in this context, that would be me, by the way) isn't so smart after-all, and the drivelling and droning that I spewed here turned out to be flawed and my solution didn't actually work (thumbs down!).

We'll either all party hard, or I'll officially eat crow in public... :fish: and you guys will still party hard, as you laugh and point at
me sulking in the corner while wearing a dunce cap. (LOL!)

-Phil. :-)
 
Last edited:
First my disclaimer... I haven't done this yet, so I'm working off of theory and what "should" work.

With that out of the way, your canbus explanation is exactly why I believe that the body ECU trick SHOULD work.
The Body ECU isn't reading CANBUS messages. Although, in theory, everything could be connected to the canbus, and
send and receive messages over it, that's not how the 4th gen was designed.

On the 4th Gen the CANBUS use is far
more limited than it *could* be. I'm assuming it's used for engine management, maybe antilock brakes (maybe not), and some other
critical operation items on the truck. On the 4th gen, the canbus IS NOT used for many other functions where it theoretically could have been used, such as locking and unlocking doors, starting the truck, activating and deactivating the engine immobilizer system, controlling the heat and A/C and more. So, the Body ECU doesn't use the CANBUS, isn't connected to the CANBUS, and the CANBUS and the body ECU know nothing about each other and don't impact each other directly.

So, here's what's needed to make the remote lock and unlock doors while the truck is running under the control of a remote starter:

In short, you need to do two things regarding remote start:

First) Only ground the key sense wire at the ignition harness while the engine is cranking. Otherwise, leave it alone. The truck needs to think that the key is in the ignition to let the engine start. Once it's started, the key sense wire shouldn't impact the engine running, so you no longer need to "fool" the truck into thinking that a key is in the ignition, and -- in fact -- if the truck DOES think that the key is in the ignition, then the trucks Body ECU will ignore a request from the remote control to lock the doors.

Second) The body ECU's input (sensor wire) for the secondary ignition needs to be disconnected once the engine is running
under the control of the remote start unit.
At all other times, the wire should remain in its normal connected state. Use a relay with its "normally open" and "normally closed" pins to do this -- but don't forget to include a flyback diode to prevent against voltage spikes when the relay coil switches from energized to turned off (google it if you're not familiar -- this is an important concept when adding relays).


Now: Here's why it will work.


The door remote module (located in the D pillar in the back) always detects button presses from the remote, and always sends out the correct pulses on the "RDA" line to send a properly encoded message indicating what button was pressed. This MUST be the case, because the door remote unit only has three main wires (the fourth, program wire is only used to pair a new remote to the truck).

So the three wires are +12V, Ground, and RDA -- it uses RDA to send an encoded signal indicating whatever button presses it received from the wireless remote, and it always sends out this encoded signal over the RDA wire, regardless of the state of other systems.


Now: The Body ECU is what decides whether and how to act on button presses that it decodes from the RDA signals sent from the door remote module.

So, if you turn off the truck, exit the vehicle, and press the "lock" button on the remote while the passenger door is open, you get that annoying long beep, which tells you that a door is still open. It's the Body ECU that makes those decisions, and also determines what actions to take such as lock the doors, unlock the doors, send out one of several different sounds, flash the turn signal lights, lock the doors, unlock the doors, etc.

Now. It's documented in the factory manuals that:

1) The Body ECU will ignore an unlock RDA signal from the door remote module when Body ECU senses that the ignition is on. It senses this via pin 10 on the body ECU -- which is the secondary ignition input to the body ECU. So if you use a relay to disconnect that input wire while the truck is running under control of the remote start, then the Body ECU will handle and process the unlock command for you -- INCLUDING issuing the correct, factory beep.
Make note about the need for diode isolation if you are also using that wire to power your immobilizer bypass module. The info is in the links referenced to the 12 volt forum.

2) Regarding a lock signal sent by the door remote module to the body ECU, the body ECU will ignore the lock signal if either of two things are present.
a) The body senses the truck is in the "on" state, based on reading the input state of the "SIG" (Secondary ignition) wire on pin 10 of the body ECU. We've addressed that issue above (see "1)" ) by adding a relay with the flyback protection diode.
or
b) The body ECU believes that a key is in the ignition, based on reading the value of the key sense wire from the ignition harness.

So, if while the truck it is running on remote smart, if after unlocking the door with the remote, you want to re-lock the door, you will also have to make sure that the body ECU does not believe that a key is in the ignition based on it's readling of the key senses wire from the ignition harnngess.
While you can accomplish this several ways, the easiest is to hook up your remote start to the keysense wire using an output from the remote start unit that sends a ground signal ONLY WHILE THE STARTER MOTOR IS CRANKING, and otherwise leaves that output disconnected. This, the easiest solution, means that the body ECU will only believe that a key is in the ignition while the engine is cranking. Once the cranking stops and the truck is running, the body ECU will think that there is no key in the ignition and based on this (plus the solution from "1)" above that makes the body ECU think that the ignition is off), the Body ECU will process lock and unlock signals received from the door remote module, and the behaviour (including beeps and light flashes) will be 100% factory. As an interesting note, the rear window roll down feature should also work (I believe), because the body ECU will believe that the truck is not running, and the key isn't in the ignition, therefore the body ECU should behave as if the truck were turned off with no key in the ignition.

If you want to test this theory, get in the truck. Start it with the key. Turn off the truck and remove the key (but don't do anything else), and then while sitting there inside the truck, see if you can use the remote to lock the doors, unlock the doors, and roll down the rear window. I'd bet that you CAN do this, and the reason is because the Body ECU thinks that the car is turned off becuse of no signal from the secondary ignition input (pin 10), and it believes that the key isn't in the ignition, based on not reading a ground from the key sense wire on the ignition harness.

The proposed solutions above (in"1)" and "2)" ) would make the body ECU believe the same thing once the truck is running because of the remote start, and "viola", your remote will work to lock and unlock the doors, even when the truck is running via the remote starter. !!!

Would it be appropriate to write "Q.E.D." at this point? (That's a math reference to having finished a mathematical proof.)

... or is that premature, since -- just like math -- this is still theory. For some, you have to move beyond the "white board" analysis, and conduct an experiment to prove that the theory is correct! (and sometimes, an experiment shows that the theory was NOT correct!) -- but I'll stand by my analysis here unless and until someone tries it and tells me that their truck blew up because of these suggestions (!!!) hehe !

;-)

-Phil

----------
P.S. -- If I install a remote start in my 2008 4runner, (assuming I install it myself), I WILL hook it up according to my predictions, and I WILL post back here with an update to thump my chest and proclaim that all is well in the world (!!!), or (alternatively) to confess that Mr. Smarty pants (in this context, that would be me, by the way) isn't so smart after-all, and the drivelling and droning that I spewed here turned out to be flawed and my solution didn't actually work (thumbs down!).

We'll either all party hard, or I'll officially eat crow in public... :fish: and you guys will still party hard, as you laugh and point at
me sulking in the corner while wearing a dunce cap. (LOL!)

-Phil. :-)

It all sounds good, but like you already said gotta wire it up and hit the switch, lol. I would be really excited to see a write up on this and hear how it goes. I would much rather have you be right and not have side effects. That would make this A LOT easier. I am just worried because when I sniffed packets on the CAN it seemed like anything you did on that truck would send some kind of message on the network, but here to hoping your right and it really is that easy!
 
It all sounds good, but like you already said gotta wire it up and hit the switch, lol. I would be really excited to see a write up on this and hear how it goes. I would much rather have you be right and not have side effects. That would make this A LOT easier. I am just worried because when I sniffed packets on the CAN it seemed like anything you did on that truck would send some kind of message on the network, but here to hoping your right and it really is that easy!

Has anyone tried this? Anyone have the answer?
[MENTION=93434]gshadow325[/MENTION], I know I owe you a call, but I tagged you in this post in case you have any insights. :)


After studying the wiring diagrams, and seeing what is connected to the Body ECU, I think that there would be some side effects, such as the daytime running lights , which are controlled by the body ECU, may go of.

Also the Defroster and Rear Defroster ad connected to the Body ECU, so they may go off too -- not sure.

The OBD2 is connected to the Body ECU, so I don't know if any error codes would be thrown, ...

and, lastly, anti-theft unit communicates with the Body ECU,

bodyECU_to_theftECU.png

so only testing would show if there are any negative side effects.

So, after further research, I've gone from being optimistic, to who knows...? :lol::lol: ...

but *someone* needs to try it (!!!). :)

Has anyone tried this?
-Phil
 

Attachments

  • bodyECU_to_theftECU.png
    bodyECU_to_theftECU.png
    105.8 KB · Views: 1,275

Members online

Forum statistics

Threads
278,309
Messages
3,554,068
Members
248,016
Latest member
Advally Service

Trending content

Back
Top