Mini-VCI, Toyotas Techstream, clones, cracked software - questions

The Mini-VCI was originally the product of an outfit named XHorse.

It's now an extreme example of counterfeiting gone so far as to drive XHorse completely out of building their own product, as I understand it. There may be a few people on PriusChat who have very old Mini VCIs that were actually made by XHorse and not counterfeit. You won't find those when shopping now.

Of course the ones you can buy now still often do say XHorse in the listing, and on the label, and in the firmware version string, as of course they are copies of XHorse's hardware and XHorse's firmware.

Certainly there are others making VIM dongles who really are doing their own work. If you have around $500 to spend, the Mongoose Pro from DrewTech is the one Toyota endorses, and DrewTech is a company that was behind the drafting of the J2534 standard itself.

But there are also cheap "Mangoose" knockoffs of that, which you'll want to avoid if you don't want to support ripoffs of DrewTech.

A little lower on the price scale, the Tactrix Openport 2.0 is from a San Francisco outfit that still does their own work (last I checked), at around $170.

They also have counterfeiters circling them in the water. Those counterfeits don't change the name at all (no giveaway like Mongoose/Mangoose). They'll be named and look exactly like Tactrix Openports, but you'll think "hey, less than $170, what a great price!". Don't buy those, if you don't want to support ripping off Tactrix.

A little further down in price are the VxDiag products. I don't know much about that company, but it is another player in the space, different from the sea of counterfeit Mini VCIs.

 

Funny I have all three of those VCIs or cables or whatever you want to call them from several other purchases of various software while all this was getting underway they're all original pieces too and I almost paid nothing for them and they all work as stated so I haven't had any of these Jay standard VCI cables that didn't work they worked limitedly at best and some of them worked unlimitedly that I could tell so I don't know without getting a hold of one and trying to use it what else you can do most of them you can return if you buy them etc etc so no problem I've had good luck with the one that came from the unit in the Panasonic case that I bought from a dealer that went out of business haven't had any trouble with that I make sure that VCI cable gets coiled and put up in a drawer when it's not in use generally speaking I don't carry it around a lot The tactrix the same way. Cheaper ones I'll let float around the shop no problem as they break I just throw them out

 

I watch a YouTube channel, South Main Auto. The guy is working on every make/model of car. A large part of his work involves diagnostics via a tablet (or tablets?) talking to the car via the OBD port. Not sure exactly WHAT he's using, but he's very familiar with it. I get the sense he has a paid subscription that allows him at least limited access to all the manufacturers special software.

 

Sap on will cost ya . Any of that stuff out of Kenosha will cost you a fortune Blue point all of it but then again that is their business automotive repair the computers thing is stumbled them up quite a bit or the code reader OBD2 things. But now newer laws and regulations make it really difficult The j standard cables now none of them need to come with software anymore because of that j standard when you plug them up they're supposed to be recognized and know what they're supposed to be doing so when they're not made correctly in the pins aren't done correctly whatever then they don't work and then we get to talking

 

I think I know who you mean. No periods, commas, paragraphs, horrible spelling....
No one understands what he/she is writing about.
MANY have tried to help this person, but to no avail.

it's safer to block it, then to give you wrong advice because you misunderstand what was typed.


PS. Man, is it difficult to read and understand your posts...
I'm not a native English - maybe it contributes to my difficulties..

 

I have a lot of snap on tools here most of them I have gotten from friends who have died and/or retired complete boxes minimal amount of electronics and lots of tools and specialty tools I just never bought into a lot of the snap on electronics they were coming online when I was moving on to some other things some of the j standard cables that I have right here when I plug them up to a new Windows machine they are recognized almost immediately I can look up and tell you what names are applied to the device and how it's listed in the windows I'm not a real computer expert but they didn't need firmware when I used them that I remember The earlier original versions had a disc somewhere little disks but some of the newer clones that I've replaced because of broken pieces and what have you as I remember did not need a CD or a software download I don't know why

 

J2534 is a Windows API standard. (Some folks at Microsoft must have popped some very rare champagne when it was officially adopted.)

It specifies the functions that must be present in a Windows .DLL that has to come with the dongle (or be available for download, or whatever). When you make a selection in the VIM Select menu in Techstream or similar J2534-based software, you're really selecting one of the DLL files installed on the computer and mentioned in the registry. Then Techstream will open that DLL and use the functions in it to talk to the dongle and the car.

The J2534 standard doesn't care a whit about the dongle's hardware, or firmware, or how it connects to the computer, as long as the right DLL that's supplied for it knows how to talk to it.

The specification for the DLL includes functions for communicating in a bunch of different protocols (CAN, ISO 9141, etc.) and also for doing other things like measuring voltage at certain pins of the J1962 connector, or applying a selected voltage to certain pins, or grounding them (which allows the software to do the stuff on Toyotas that involves grounding the Tc or Ts pins, and so on).

Not every J2534 dongle can actually do all of those J2534-specified things. There is a cable test function available in Techstream where it will check whether the connected dongle can do the things Techstream expects. There is also a "J2534 bus analysis tool" that can be downloaded at no cost from DrewTech and used to put any J2534 dongle through its paces.

It is also possible, given how cheaply some available dongles are being made, for a dongle to have in theory the ability to do all those things, but to do them very unreliably, or with high error rates, or timeouts, etc. Those kinds of issues can be harder to spot with a simple function check.

 

You will break laws using the knockoffs and the hacked Techstream software. Which is what often gets recommended around here especially by those who buy the $30 hardware with "free" software download. The instructions specifically say don't go online with it and many members suggest installing on beater xp machines. One of these days Priuschat is likely to be sued.

There are many "universal" scanners in the $500 and up range that also require yearly maintenance fees. Ivan on Pine Hollow Auto Diagnostics has explored the options as has the Toyota Tech on the Car Care Nut channel. Updating vehicle firmware seems to be the dividing point where the legal Techstream shines the brightest.

 

Probably worth mentioning that there are plenty of non-knockoff dongles available in the marketplace. They cost more than the cheap counterfeit Mini-VCIs, but still not a lot, and that's a one-time cost.

And the obvious alternative to using a hacked Techstream that came with a dongle is to download the genuine article, and buy the $65 two-day activation whenever you want to use it. That still comes in well ahead of what you'd likely pay at a dealer just to get codes read, and especially if you are actively diagnosing something, going back during those two days and reading more stuff, running active tests, etc. That would get painful fast, at dealer rates.

 

In the interest of full disclosure, I've been happy with the Tactrix on my Gen 3; it can complete a brake bleed, and it can get ECM data list info, and the Mini VCI that I was using before that was unable to do those things. Those were the reasons I tried the Tactrix in the first place.

But the Tactrix has failed to completely register new TPMS IDs for me (Techstream accepts them, and tries to set them, but then reports an error, and after reconnecting, the new IDs are shown, but the TPMS light is still on), and that operation went fine when I retried with the ol' mini VCI.

That's on a Gen 3. I believe I have also run into some Gen 2 things that worked with the Mini VCI and not with the Tactrix.

I assume everything would work without glitches if I were to drop $495 on the DrewTech, but so far I haven't pulled that trigger.

I have a hunch that when a Tactrix is unable to complete some operation, it's probably a design issue (maybe they just plain left out some J2534 feature that Techstream needs for that operation; I think Tactrix had its origins more in the Subaru community), and when there's something a Mini VCI flakes out on, it might be more likely a sample defect (those things are just built so cheaply, they might not all completely work, and different units might flake out differently). But verifying that hunch might be pretty hard.

I think I also have a VxDiag dongle around here somewhere, that so far I've never really unboxed or tried.

 

FWIW, in that list,

• J1850VPW is not listed in the Openport list
• I assume iso 14230 is an update to iso 14229...but maybe not

I will go look a bit to learn about J1850VPW