Tactrix OpenPort 2.0 For Techstream Use

I haven't used that particular item, but have the Mangoose (Chinese knock-off) and another compatible cable that I got from, big surprise - China. Both have been used to do TPMS updates, clear TPMS codes, run a "health check" and view information. Both much cheaper than the Mongoose one.

Here's an item link for you from the place I got mine:
MVCI Diagnostic Interface for Toyota, Honda, Volvo

Another, less expensive one:

On Sale MINI VCI for TOYOTA TIS Techstream V5.00.028

Mangoose:

http://www.uobd2.com/wholesale/mangoose-toyota-diagnostics-and-reprogramming-interface-1687.html

Search Results for Toyota TIS:

http://www.uobd2.com/search/?q=Toyota+TIS

I believe the MVCI only are compatible with Windows XP, so you'll want to confirm first. I purchased a Netbook to use with them, as it is smaller than my laptop and easier to maneuver in a car.

There's an interesting one in the search results that's cheap that appears to let you do key programming (to add keys). If it ever came down to it, might be worth giving that a shot before paying the dealer $80+ to do it.

If you'd like to borrow any cable first to try, just let me know.

 

My understanding is that the Tactrix is fine for CAN bus devices, but has problems with some K-Line devices. Smart keys and TPMS are K-Line. I'd also be suspicious of GEN3 devices that go through the gateway, such as the Body computer.

 

That's my source. I think he said TPMS worked, but smart key setup did not. The gateway problems are just a guess on my part. This is all data from a year ago, and relates to the protocols that Toyota uses. The hardware looks like it's up to the job, and a driver update could solve the Toyota specific problems.

 

WOW! You really can't beat that price! It was like $200 when I got it, so you got one heck of a deal!

I can confirm it does the health check and chime settings in your list. It also does TPMS, but I don't think that's something you're too worried with .

I think Key Programming might require the higher subscription to TechStream, not sure if you can do it in the cheap sub or the evaluation mode.

I know that I would really appreciate it if you were able to keep me (us) updated on what it can do, and what steps you took to do the different tasks (I have the Firestone Lifetime Alignment, but they don't do the zero point, I believe).

 

Do you have the steps for doing the ZPA? I don't know how much I actually trust the local Firestone - they claimed they could update the TPMS before and it wasn't until after I called them on it they said they couldn't do it on the Toyota's because it required TS. Needless to say, that didn't exactly instill trust in them. I'd almost prefer doing it myself and knowing it was correct.

One of these days, I should probably try to find the TS manual online for doing everything. But when I did their 2 day subscription earlier, I felt like I was in a library without any dewey decimal (yeah, I just went old school lol).

 

General questions about OBD2 interfaces: Are these more or less recent USB to OBD2 devices pretty much the same? There are many out there, but is it correct that if the device connects to the port and can read and write, then it is all a matter of software after that point? Are the devices tied to proprietary software, or is the OBD2 port generic enough that any software will work with any (recent) interface?

 

If OBD was really a standard, there would be 4 pins on the connector. Instead there are 16 pins. There's the old GM standard pins, the Ford pins, the European pins, the current Toyota pins, the Leaf pins.....

The connector that plugs into the OBD port has a microcomputer in it that translates some subset of the OBD possibilities into a serial protocol. That serial protocol can be delivered to a PC via USB or Bluetooth.

There are currently two major device standards in use, ELM and J2534. The cheap devices all use ELM, and most are imitations of the devices made by ELM Electronics.

ELM is ok for slow speed queries of the CAN bus on current Toyotas. There are a few premium ELM protocol devices that are fast enough to handle the full data rate on a Prius. The ELM protocol does not support the K-Line interface on the Prius, which means that TPMS, Gen2 keyfob, and Gen2 option setup cannot be supported by any software on the PC.

J2534 is required for use with Techstream. Which means the Denso interface that dealers use, the Mongoose, the Tactrix, or one of the Mongoose imitations like the Mangoose (I kid you not...). The Tactrix has really only been debugged with Subaru/Mitsubishi vehicles. I don't have any experience with the Mongoose clones.

 

They have a CD with the label "Techstream" on it. Probably an old copy of it that has been hacked to bypass the registration process.

My guess is that it will generally work. It may crash occasionally, but then Techstream does that anyway.

 

Might not be an old copy of it. It was version 4.xx when I got my same Mangoose over a year ago. It also wasn't hacked, but I know of a site that does give you codes if you give them the product ID. You can run it in evaluation mode (not sure if it unlocks everything or not) though. I just run in evaluation mode each time, because I only really use it to update TPMS for my winter tires.

I believe there's a 6.xx version of TechStream out there right now.

Neither version was all that "fast", and communication among screens takes a little while. At least it does with my laptops (netbook or regular).

 

I've got the Tactrix, and downloaded the drivers a couple days ago. Techstream will acces the TPMS, and a bunch of other stuff including warning (beeps) setting. But it always fails trying to connect to the Smart Key ECU. I need to register the remote engine start with the Smart Key ECU, but no luck yet.

Let em know if you can access the Smart Key ECU with the ManGoose. I have emailed Tactrix support, so I will report what they have to say.

 

Hi timba-n-tango,

It is a known bug in Techstream Lite (ver. 6.20.020) with Mongoose.

Vincent

 

Thanks Vincent, that could be a clue and help me out. I tried versions 4.2 and 5.1. Will try 6.2 non-Lite.

wick1ert helped me out and tried the same with his Mangoose cable and gets an access error also.

Here is what Tactrix said:

"Openport 2.0 supports these major OBD protocols:
-CAN 2.0 (CAN/ISO15765)
-K-line (ISO9141/ISO14230(KWP2000)/dual K line)
-J1850 (PWM/VPW)
Physical Layer:
OBD interface: J1962 male connector using the following pins
4: Ground
5: Ground
7: ISO 9141-2 K line
9: L line (Subaru specific)
11: Vpp (Subaru specific - switched off when not in use)
15: ISO 9141-2 L line
16: +12V
What cars use ISO 9141-2?
Most all post-1996 Chrysler, European, and Asian vehicles. So, this protocol does include your Toyota Prius."

"As you're aware, our hardware (Openport 2.0) does work with Techstream, although there may be limits to the full extent of it's compatibility. We do know that many in the tuning community have used it with varied success; the full extent of which you would find in the forums as we don't write software specifically for, or work directly with Toyota model vehicles. We are currently working on application support for Nissan, Honda and Mazda vehicles."

 

This ver. 6.20.020 is the latest, you might need to wait for their next release.

Vincent

 

OK, I am good to go now. Tried 6.20.020, and got the same error. Didn't write it down, but it is something like - Lost communications with vehicle, check interface, cable, and ignition on.

After the error, the screen was then a little different than the older versions and I noticed that it had actually created a "Smart Key Live" tab, and had the correct buttons on the left side of the tab. While the tab was mostly blank except for some image reminding me to hit F12 to log the error, once I hit the Utility button the tab populated with all the Smart Key functions. The one I needed to use for registration was there and worked fine after a couple of tries.

Nice!