Not sure how the network is managed internally. Once I can get any communications - it's like a prybar. So, I do allow for situations like you mention, but I look at it as a bridge I'll cross when I get to it. I just try to make sure I understand every byte I'm sending/receiving....I guess, you're really asking about another 'layer' of infrastructure and I don't have a smart answer. Thanks!

Good question. I would know what was happening because I'm operating the scanner. Meanwhile, the excellent and critical tool, the linux sniffer would show me what changed

All wires are run end-to-end straight through pin for pin...No signal wires are broken. I had to solder each wire because I started with two separate ends (male/female). The cable had to have different ends to work as a pass through... Some wires are disconnected here because I wanted power and ground wires separated from each end. Otherwise it's just an extension. The two can wires are never brokeen, I just soldered them to a screw terminal. That terminal gives us CANH (pin6) and CANL (pin14) to read the data flow. Pins 6 and 14 here are the standard obdii connector pins. That's it.

The thing that finally allowed me to see the info was to watch the CAN using something other than the ELM327... There's a set of commands called 'Can Utilities' on linux. A command called 'cansniffer' only shows changing CAN data - so you don't get swamped. You also have to physically tap into the CAN wires (while the TEch2, or whatever IS connected - which is tricky). You'll have to deal with a piece of electronics that will bridge whatever computer you're using to the car's CAN. I've not made a video in a while, maybe I should about this. I've concluded the monitor on the dongle is not capable (in speed and depth) to catch the data we're interested in. I use a rasberry pi with an MCP2515. It's fast and sees everything. Thanks!

@@Roudter I would enjoy if you made a video on how you did if you find the time. very interesting stuff. I will read up on that model number