Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB

Quote:

Originally Posted by Compelica (Post 3599146)

To understand this correctly... if the car was started from a remote start and the command is not resent within 5 seconds, the engine would kill itself (fuel cut) or will the entire car turn off?

And to prevent this shutoff from happening, the override command has to be sent?

if you don't continue to send the same message to the ECU for at least once per 5 second the car WILL shut off - meaning engine and acc . It completely shuts off and not just cut fuel to engine. Full shutdown regardless of the gear status be it drive, reverse, neutral,...

One more important thing I forgot to mention is that the car will ONLY start in Park or Neutral gear when sending the remote command. This also provides less code for me to in terms of the checklist compensation before starting.

Quote:

In this case, the 'chip key is present' command is NOT the same as disabling the immobilizer, to allow the car to start and continue running?

With the headlight/taillights you can basically adopt some form of follow-me-home setup with the Arduino too, lots of possibilities. Would love to work on something more programmable in the future but will have to use with what I have for now.

If you need any testing with the canbus commands I can help out for sure. As mentioned before I'm using an ELM327 to send/receive commands, though it's a bit limited as ELM327 can't send more than a certain number of bytes in a single frame (IIRC turning on gauge lights require payloads larger than what ELM327 can support). I'm on a 2015 MT GT86 prefacelift.

Certainly exciting - one step closer towards a DIY remote start :)

Yes, the fob 'chipped' key command is only just for status reading. It doesn't change anything regarding the status of the key.
Disabling the immobilizer would be godsend though if I can find the key/seed and the algorithm performed between the immobilizer and the bus system. Quite difficult I must say.
So best way is basically going straight at the ecu and find a way to send a command that would trick the ecu that the key is detected nearby and it's a valid one. I haven't gotten to that yet.
If you know your way around here is the canbus id for the smark key system:
CanID: 0x750 (Main Body)
PID: (0xB5)
:thumbsup:

I don't understands what you mean by the "follow-me-home" phrase. That's interesting lol.

I basically have two CANBUS connected to the car at same time to be able to write/decode/ready the CANBUS messages:
Tactrix Openport 2.0 and CANduino (which is basically an arduino nano but with built in canbus Transceiver ).

Tactrix plugged in to the obd 2.
CANduino connects to the CANbus through the unused CANbus plug (close at the firewall) behind the radio system.

incase you are interested:
https://www.tindie.com/products/mass...-with-can-bus/