Techstream 'DOP Security' feature & other TS q's

Howdy folks,
I just recently purchased Techstream along with a Mini-VCI (J2534) cable. After many twists, turns, hoops jumped through, I have it 'working'. I was able to program a fob for my truck(yippee!), but was hoping to do MANY other things and so I have some questions for the experts out there (here)
1) What is 'DOP Security' and has anyone enabled it and should I do it?? any drawbacks??
2) Why would SO MANY of my ECU's be listed as "ECU not supported or not responding"??? (see picture below) I could see it if my truck didn't have options that applied to these systems, but out of 17 systems listed on the selection menu, only 6 are "ECU communication OK" (available). Even the TPMS, SRS Airbag, occupant detection ECU's are unavailable and I KNOW the truck is equipped with these systems.
Any help is really appreciated!
Rookie Techstreamer!

 

Most times "ECU not supported or not responding" items can be because wrong Mini-VCI cable version or even software version.
Which Mini-VCI cable did you buy, v1.4.1 or v2.0.4 ?
If it's v1.4.1, that stands a good chance of being your problem.

What Windows operating system are you using ?

The following might not be needed if you know what version cable you have but,...if you're using Windows XP, there is a file that should have come with your Techstream download named FirmwareUpdateTool.exe. If you execute that file, select Device Info, you can see firmware version of cable. That executable file will NOT work if you're using Win 10.
* Reminders when using Techstream.....do NOT be connected to the internet !

 

Bubba,
Thanks for the response!
First, on the version of cable. I don't really know.....When I got it, I was doing some reading and 'trying to protect my laptop', I installed from the iH8mud website and installed it behind a 'virtual box' setup using Windows XP....but, when I started having the problems with "ECU not supported or not responding" issues, I got frustrated and just installed 'directly' on my laptop with the software provided with the cable. My laptop runs Windows 10-home edition. I just looked at it on Windows XP using the FirmwareUpdateTool and it shows version 1.4.8 ???
So do you think my cable/version is the issue? If so, where do I get the correct cable? (I certainly didn't know what I was doing when I bought this first one - their support has been VERY responsive (but unable to solve my issue - slight language barrier as I believe they are in China) I'm willing to invest a little more money to get access to the ECU's that I need.
I appreciate your advice!!
Thanks...George

 

@geoyodas8 , just making sure….the 1.4.8 you’re speaking of is indeed the one in the
Firmware box where mine says 2.0.4 ?

As for where to get MCI cable 2.0.4, other than google search, that’s all I got. Both my cables, 1.4.1 and 2.0.4 were purchased many years back before the market got crazy with folks offering these cables.

I can say that our 2017 Highlander has to have 2.0.4 cable or I’d have same issues as you. Won’t say your ver 17 of Techstream is a problem for your 2013 Tundra but ver 12.00.whatever works on our 17 High and my 04 Tundra. If you do get a 2.0.4 cable and want to try a different version of Techstream, send me a PM. Over the years I held on to many versions and weeded out the versions that gave me and others issues. It’s a rabbit hole but worth it IMHO, once one gets it running.

 

@BubbaW, Actually, the 1.4.8 is in the top left corner of the screenshot(attached). For whatever reason, it won't populate like your Firmware Update tool did.
So...I am running it on version 12.20.024 on the XP (32 bit) Oracle Virtual box, and version 17.00.20 on my Win 10-Home (64 bit) system with the same cable and I get the EXACT same available ECUs, so you must be right on the money about it being the cable. I really didn't even know there were different 'version' of the cable. They all "LOOK" the same online when I bought it.
So.....I guess I need to hunt down the 2.0.4 cable and try again....
I really do appreciate your help. I've tried to hunt down this info YouTube, other forums, etc, etc.....but it seems that everyone has different experiences with it and so putting together the bits/pieces to make it work is the trick!
I'll see what I can do to get another cable (2.0.4) and try again!
Thanks again for the offer...I will PM if/when I can get the right cable.

Duh....now when I look again at my screenshot...I guess its the version of XHorse Firmware Update tool (1.4.8)......not sure how to find out my version of the actual cable