Official tutorial

Tutorial

From server selection to daily use — how to map correctly.

On this page

How to choose a server

Customer and engineer must use the same server Prefer the server closer to both sides Different servers = mapping will fail

Correct example

Recommended · Shorter path

Customer (Jiangsu) and engineer (Hangzhou) both use the Shanghai primary node. Traffic relays through Shanghai — shorter path, lower latency.

Beijing · Backup Not used Shanghai · Primary Jiangsu · Customer Vehicle location Hangzhou · Engineer Green: relay via Shanghai (short path) Schematic map of China · East focus

Wrong example

Not recommended · Detour

If both choose Beijing backup, traffic detours north then back — a much longer path and higher latency.

Shanghai · Primary Not used Beijing · Backup Jiangsu · Customer Vehicle location Hangzhou · Engineer Red: detour via Beijing (longer path, higher latency) Schematic map of China · East focus
02

USB mapping

Only needed for a USB diagnostic cable. Skip this for DoIP / ENET Ethernet mapping.

Get USB Share
  1. 1

    Download the matching versions

    Customer PC: version 6.2. Engineer PC: version 11.0. Click Next through setup; if asked to reboot, choose No.

  2. 2

    Customer shares the device

    Plug the cable into the car and PC, then share that device in the tool.

  3. 3

    Engineer connects

    Open the same tool and connect. The cable should appear in Device Manager.

  4. 4

    Both sides pick Client

    In Suucar, customer and engineer both pick Engineer (Client) — the in-app role name, not Bridge — then the same server.

03

Sign-in and daily mapping

Wiring, sign-in, and silent (CMD) login steps will use the same module layout.

Coming soon

More tutorial sections will be added soon.