Techstream with wifi VCI plug experience

Does anyone have any experience with a WiFi connection to an OBDII plug as opposed to a USB connection to the OBDII plug.

I do know this:
* wifi is established between devices (not between software). ie: the obdii connector and the laptop that I am using.
* Techstream software is written independent of devices it is connected to.
* Drivers connect the TEchstream software to the hardware (such as USB etc). Currently, for Techstream operating on Windows (any version), Microsoft provides the Drivers for Techstream data to be placed on the USB bus.

So the question boils down to whether drivers for WiFi know where to fetch the commands issued by Techstream and know where to place the data once it is fetched from the CAN bus (located in the car).

(please...no guessing....)

 

Good Afternoon BigFan!
Somewhere in this site, I posted a lengthy explanation.

The crux is that USB based OBDII based systems in the reasonable price range are likely to contain a rip off USB interface chip that does not work consistently (while the original more expensive chip worked just fine). In the article I explain the details.

Purchasing a wifi based OBDII eliminates the risk of purchasing the OBDII USB interface chip. The choice of wifi has nothing to do with the actual benefits of wifi per se.

In the sequence of communication that contained the detailed explanation, there was a fantastic mechanic who added to the conversation. He actually bought the wifi or bluetooth version of a specific brand that we both thought might actually deliver a robust product at a reasonable price. You should see if you can find his contribution to this topic and ask him for his experience. I think he has been using it for 6 months or more.

If you can't find the conversations I allude to , let me know and I will look them up and point you to them (or send you copies if I can figure out how to do that).

Be aware: I am not a mechanic. I am a research scientist with electrical and mechanical engineering degrees. Hence my interest was soley to find out why my damn OBDII did not work and what I could do to fix it.

 

Good Evening

If you go back to my detailed response, you will find out that the OBDII USB port versions that gave people problems were NOT due to a missing wire or intentional whatever. the problem was that they were using a chip (see article for vendor and chips id) that was a knockoff.
the chip pins are identical. the chip innards obviously not. My guess is that while they may have copied the original circuit, they had timing problems that we, as users, encountered.

regarding programming, Both OBDII versions are just as easy to program. The reason is that, in the last decade, most applications make operating system calls that handle most of the difficult time dependent code. (ie: drivers to the usb port was probably written by microsoft.) the code for these devices is all about coordinating command and response and presenting the results in memory in a manner that Techstream is expecting.

I have forgotten who is a reputable manufacturer. You probably chose one who used a bonafide USB interface chip.

Enjoy your experiences in life. it is short as I am finding out at the age of 71. just believe you can do anything at any age...maybe just a bit slower.