Anyone program a used fob sks key gen 2 before? Help!!

Which of the pins are shown not working on yours? I could do a quick comparison to mine.

If mine's the same (and successfully registers fobs) then the issue must be something else.

 

Here you go

 

Weirdly, that's exactly the same result Techstream gives me. Both for my ersatz Mini VCI and for my Tactrix.

The Mini VCI flakes out reading the engine data list. The Tactrix doesn't. There's certainly some difference (or differences) between them, but I'm not sure what stock to put in that particular Techstream line check.

 

Gen2 uses the K line to program keyfobs. Don't know about Gen3/4.

 

I think I may have done things that use the K line, using my dongles that show up in this "line check" as having no K line. I'm a little unsure how much stock to put in the line check.

 

Gen2 uses the K line for TPMS, Body, Immobilizer (transponder), and SKS (keyfob circuit board).

Gen3 uses CAN for TPMS, Body, & SKS. The sequences appear to be similar (the same?) as the Gen2 K line sequences except that there is a CAN address of 750 followed by the K line address and data. The CAN protocol for translated K line devices is apparently not supported by some CAN readers.

So OBD2 interfaces have to cope with CAN, K line messages translated to CAN, and real K line. Not all OBD2 interfaces get all of them right...

 

I've definitely successfully completed a transponder registration (fob works when inserted in the slot) on a Gen 2. Using my Mini VCI that Techstream claims not to have a working K line.

I did not successfully register the same fob to SKS, but I assumed that was because the fob wasn't virginized. (I haven't sent it off yet to the locksmith that thinks they can probably revirginize a gen 2 fob.) I successfully completed other SKS operations (like "forget your former fobs").

This doesn't surprise me considering Techstream and the mini VCI also work on Gen 1, which has no CAN bus at all (and has one of the "CAN" pins in its DLC connector dedicated to something else!).

The one thing I question most in this picture is that "signal check" function in Techstream.

 

When I switch between MVCI and Openport, I'm not changing anything other than a drop-down choice under "VIM Select". I don't expect the software to show me any changed or different tabs or options. Which dongle I'm using only affects which operations successfully work, and which ones end up flaking out with some error code.

 

Back about 10 years ago I studied the interface between Techstream and adapters like MVCI and Openport. The protocol is generally described in the Drewtech J2543 documentation. But Techstream utilizes at least one undocumented protocol extension. Whether it's intentional, or just a remnant of the development process is unclear. Anyway, there is a bit that Techstream uses to say "this message already has the checksum in it". The usage didn't seem to follow any obvious rule, but the effect on the Openport device was that it failed with some messages. I wouldn't expect the Openport people to implement an undocumented Toyota protocol extension since they target Subaru rather than Toyota.

The idea that a clone of a copy of the supported Drewtech device would reliably implement an undocumented protocol extension seems rather remote. So the messages that utilize the undocumented protocol probably fail. Maybe the keyfob registration ones.

 

Well...Crap. Let us know if you have any luck.

 

i believe the cable you want
is the Xhorse TIS Diagnostic Cable for Toyota TechStream which supports diagnostics and active tests. This is $35/$25 on Amazon/eBay respectively.

At this price, i would suggest that everyone who has techstream might look into picking one up.

Posted via the PriusChat mobile app.

 

Link?

My mini VCI is an Xhorse clone. Can the one you are using program TPMS sensors?

 

Kavietski: this cable only supports 32 bit -specifically XP.

Luckily, i was just gifted 3 windows xp laptops. 2 x Dell and 1 Samsung.

Posted via the PriusChat mobile app.