Interface problem

Thanks for testing and sharing the details — that helps a lot. OpenPort 2.0 and SM3 — both are standard USB / J2534 interfaces, so they map across without any trouble. When ODIS doesn't list a J2534 tool, it's almost always because that tool's J2534 driver isn't installed on the remote (Technician) PC, or the interface hasn't been selected as the active PassThru device inside ODIS. For the SM3 in particular, the Technician software shows the Windows device status right next to it — if that's showing Code 28, it's Windows letting you know the SM3 driver isn't installed on that PC yet. You can look up any error code at this address (copy it into your browser): https://bit.ly/4wpUmKj Install the matching driver on the Technician side for each tool, select the interface in ODIS, and run it again — that usually clears the "mapped but not seen" case for both. On network-adapter bridging in general — one thing worth checking on the Mechanic side: third-party virtual-network tools (VPN clients, ZeroTier, or USB-sharing utilities) create their own virtual adapters and can interfere with the bridge. It's best to turn those off during a session so they don't compete with the connection. That alone often clears up an unstable or failed bridge. VNCI (the red one) — since ODIS already detects it, the connection itself is working. The interface/firmware update it's asking for is best done once with the VNCI connected locally to a PC first; that kind of update doesn't tolerate interruptions well, so completing it locally and then using the device remotely is the smoother path. If you'd like to go through any of these step by step, just drop us a line at support@elinehub.com and we'll walk you through it.