GMC MDI 2 Remote Programming — GDS2 and SPS2, No VCI on Your End
Field data from North American independent shops confirms what experienced GM programmers already know: the clear majority of remote GMC programming jobs involve module replacement — TCM, BCM, ECM, or ADAS sensor programming through GDS2 and SPS2. Sierra 1500 is the most common single remote job on GMC trucks by a wide margin. Acadia, Yukon, and Yukon XL account for the next largest share.
Every one of those jobs shares the same technical constraint. SPS2 requires a live connection to a physical MDI 2 throughout the flash — the calibration file downloads from GM’s servers while SPS2 simultaneously writes it to the module, both paths on the same PC, in the same session. A screen share gives you the remote screen. It never gives you the MDI 2.
eLinehub maps the MDI 2 at the workshop to your PC over the internet. GDS2, SPS2 within Techline Connect, and Tech2Win detect it as a locally connected USB J2534 device — the same way they would if the MDI 2 were sitting on your desk.
1. GMC Modules You Cannot Program Without a Live GDS2 or SPS2 Session
Replacing a transmission control module on a 2017 Sierra 1500 with an 8L90 puts the shop in a situation only SPS2 can resolve. The replacement TCM arrives without calibration data matched to that VIN and RPO configuration. SPS2 — running inside Techline Connect (formerly TIS2Web) — reads the module’s hardware ID through the MDI 2, queries GM’s servers for the correct calibration file, and writes it to the TCM in a single connected session. Remote desktop tools cannot carry this dual-path requirement. The technician’s PC sees the workshop screen but never sees an MDI 2, so SPS2 never finds a programmable device.
BCM replacement on an Acadia or Yukon adds further constraints. A new BCM carries no vehicle-specific data. The sequence is fixed: GDS2 pulls existing vehicle configuration via Request BCM Info for SPS, SPS2 flashes the calibration, then GDS2 runs VTD relearn and SDM serial number setup to register the airbag module. Skip or interrupt any step and the vehicle will not start with a recognized key.
On Sierra 2500 HD and 3500 HD with the L5P Duramax or L8T gas engine, ECM replacement adds a post-flash requirement: GDS2 must run crankshaft position variation learn and transmission adaptive pressure learn as sequential bidirectional procedures. GDS2 sends a command, waits for the ECU to respond, then sends the next. A screen relay introduces enough timing variance to break these cycles. eLinehub reconstructs the raw MDI 2 data stream at the same protocol timing as a direct connection.
For 2021MY and newer GMC vehicles, Techline Connect handles Secure Gateway (SGW) authentication. The SGW restricts module-level programming to authenticated sessions — but only when the session runs through a recognized J2534 interface on the same PC running Techline Connect.
On 2022.5+ Sierra 1500 and 2024+ Sierra HD, GM’s Global B (Vehicle Intelligence Platform) architecture introduces Vehicle Wide Programming (VWP) via SPS3 — a single automated session that flashes ECM, TCM, BCM, and ADAS controllers in sequence. GM Technical Service Bulletin 24-NA-113 (updated January 2025) specifies a wired MDI 2 connection and explicitly prohibits wireless dongles; if one is present, VWP is grayed out in SPS2. Independent shops are encountering this requirement now as 2022.5+ Sierras enter out-of-warranty repair cycles.
For pre-2013 GMC vehicles — older Sierras, Savanas, and Envoys — Tech2Win provides the Tech 2 emulator environment inside Techline Connect over the same USB MDI 2 connection. The eLinehub workflow is identical.
2. How eLinehub Maps the MDI 2 to Your PC
The MDI 2 connects to the workshop PC via USB and to the vehicle via the OBD-II port. eLinehub captures the MDI 2 at the USB level on the workshop side and reconstructs it as a local USB device on the technician’s PC. The technician installs the MDI Manager package — the same driver set used for a locally connected MDI 2 — and GDS2, SPS2, or Tech2Win find the device in their normal J2534 interface selection screen. No diagnostic software is installed at the workshop.
What each side provides:
Requirements | Workshop (Mechanic) | Remote Technician |
|---|---|---|
Hardware | Vehicle + MDI 2 | PC only — no VCI required |
Software | eLinehub Mechanic (free) | GDS2, Techline Connect, eLinehub Technician |
Credentials | None required | ACDelco TDS / Techline Connect subscription |
MDI 2 drivers | Not required | Installed as for local MDI 2 use |
eLinehub vs. the approaches technicians try first:
Features | Screen Share (TeamViewer, AnyDesk) | Hardware Relay (ship the VCI) | eLinehub USB Mapping |
|---|---|---|---|
GDS2 sees a local MDI 2 | ❌ No | ✅ Yes | ✅ Yes |
SPS2 dual-path (GM server + MDI 2) | ❌ No | ✅ Yes | ✅ Yes |
Post-flash bidirectional relearn (GDS2) | ❌ Unreliable | ✅ Yes | ✅ Yes |
Same-day job completion | ✅ | ❌ Shipping delay | ✅ |
MDI 2 stays at the workshop | ✅ | ❌ Ships out | ✅ |
Technician needs their own VCI | ✅ | ✅ | ❌ Not required |
Two connection modes are available. Relay mode routes the MDI 2 data through eLinehub servers — stable across any network. Direct (P2P) mode skips the relay hop and is preferred for SPS2 and SPS3 flash sessions when both sides have a wired connection. After connecting, wait for MDI 2 initialization on your PC before opening GDS2 or SPS2.
3. Three Jobs That Come Through the Shop Queue Every Week
Job 1 — TCM Programming After 8L90 or 10L80 Transmission Replacement: Sierra 1500
A shop replaces the 8L90 transmission on a 2017 Sierra 1500 5.3L. The replacement TCM arrives without VIN-matched calibration. SPS2 within Techline Connect is the only path to complete this flash — aftermarket scan tools cannot execute GM’s online calibration download.
Steps through eLinehub:
-
The shop installs the replacement transmission, connects MDI 2 to the Sierra’s OBD-II port via USB, and opens eLinehub Mechanic to create the job order.
-
The shop shares the Passcode with the remote technician.
-
The technician selects Mechanic USB in eLinehub Technician and waits for the MDI 2 to finish initializing.
-
Open SPS2 within Techline Connect. The MDI 2 appears in the J2534 device selection list — select it.
-
Enter the VIN. SPS2 reads the replacement TCM’s hardware ID, identifies the VIN-specific calibration from GM’s servers, and writes to the module.
-
After SPS2 confirms a successful write, open GDS2 and run Transmission Adaptive Pressure Learn. GDS2 commands the TCM through pressure cycles in sequence — do not disconnect during this procedure.
-
Clear DTCs, confirm no communication faults with other modules, release the vehicle.
The same workflow applies to 10L80 replacements on 2018–2021 Sierra 1500, 6L80 on older Sierra and Yukon platforms, and 6T75 TCM replacement on Acadia and Terrain transverse-mounted engines. The SPS2 procedure is identical; only the calibration file differs.
Job 2 — BCM Replacement and VTD Relearn: Acadia or Yukon
A 2020 Acadia arrives after a theft event — the BCM is damaged. A new BCM from GM parts carries no vehicle-specific data. This job requires GDS2 and SPS2 in a fixed sequence; each step depends on the previous completing without interruption.
Steps through eLinehub:
-
The shop installs the new BCM, connects MDI 2 to the Acadia’s OBD-II port, and publishes the job order.
-
The technician connects remotely, waits for MDI 2 initialization, and opens GDS2.
-
Run BCM special function Request BCM Info for SPS — reads current vehicle configuration and prepares the module for the SPS2 session.
-
Switch to SPS2 within Techline Connect. SPS2 writes the VIN, RPO option codes, and base calibration to the new BCM.
-
Return to GDS2. Run Setup SDM Serial Number in BCM to register the airbag module’s serial number — required for correct restraint operation.
-
Run Request VTD Info for SPS in GDS2, then complete the theft deterrent sequence in SPS2. After this step the vehicle recognizes authorized keys.
-
Program key fobs via GDS2 → Keyless Entry → Transmitter Programming.
-
Clear all VTD-related DTCs. Turn ignition off for 10 seconds before releasing the vehicle.
For multi-site networks: one central technician handles every Acadia or Yukon BCM job at any satellite location through this workflow — no travel required.
Job 3 — Vehicle Wide Programming on 2022.5+ Sierra 1500 and 2024+ Sierra HD
GM TSB 24-NA-113 (updated January 2025) mandates VWP for a growing list of field actions across Global B Sierra platforms. VWP flashes every eligible module in a single SPS3 session — ECM, TCM, BCM, and ADAS controllers. The TSB specifies wired MDI 2 and prohibits wireless dongles; if a wireless adapter is present, VWP is grayed out in SPS2.
Steps through eLinehub:
-
The shop connects MDI 2 to the Sierra’s OBD-II port via USB — wired only. Connect a GM-approved battery support unit; voltage fluctuation during VWP can interrupt programming and recovery may require dealer tools.
-
The shop opens eLinehub Mechanic and shares the job order.
-
The technician connects remotely and confirms the MDI 2 has initialized as a wired device.
-
Open Techline Connect → SPS2 → SPS3 Vehicle Wide Programming.
-
SPS3 retrieves current module software versions from the vehicle, then downloads required files from GM’s servers. Allow several minutes on Global B vehicles with many modules.
-
SPS3 flashes modules in sequence — do not interact with either PC or the vehicle during the active write window.
-
After completion, capture the VWP Summary screen listing updated modules and any requiring individual follow-up sessions.
⚠️ Do not close eLinehub Technician during the VWP flash. Closing the Technician software terminates the MDI 2 device mapping and interrupts the session.
4. Setup — Technician Side and Mechanic Side
Initial setup runs once per machine. After that, accepting a job and connecting to the MDI 2 takes under a minute.
Technician Side
-
Download and install eLinehub Technician. Windows 10 or 11 (64-bit) recommended; Windows 7 (64-bit) supported.
-
Install the MDI Manager package — the same GM driver set used for a locally connected MDI 2. GDS2, SPS2, and Tech2Win find the mapped MDI 2 through this driver without any software modification.
-
Keep your existing OEM credentials and subscriptions on this machine. Your ACDelco TDS or Techline Connect login, GDS2 license, and Tech2Win access remain local to your PC. The workshop never sees them.
-
Accept the job order and connect. Select Mechanic USB in eLinehub Technician, confirm the MDI 2 has initialized, and launch GDS2 or SPS2.
Mechanic Side
-
Download and install eLinehub Mechanic. The Mechanic software is free. No diagnostic software, no GM credentials, and no additional hardware are required at the workshop.
-
Connect the MDI 2 to the vehicle’s OBD-II port and to the workshop PC via USB. For SPS2 flash sessions and VWP, use the wired USB connection — not the MDI 2’s built-in WiFi mode.
-
Publish the job order and share the Passcode with the remote technician.
For step-by-step screenshots and configuration walkthroughs, see the Setup Guide links above.
5. Network Requirements for GMC Programming Sessions
Network | Full-system diagnostic scan | SPS2 single-module flash | SPS3 Vehicle Wide Programming |
|---|---|---|---|
Upload bandwidth (both sides) | 10 Mbps minimum | 10 Mbps minimum | 10 Mbps minimum |
Round-trip latency (RTT) | Under 150ms | Under 80ms | Under 80ms |
Mechanic side connection | Wired preferred | Wired required | Wired required |
Technician side connection | Wired preferred | Wired required | Wired required |
eLinehub mode | Relay or Direct | Direct (P2P) preferred | Relay |
Why wired is non-negotiable for SPS2 and VWP: SPS2 has no built-in session recovery. A write interrupted mid-flash on a BCM or TCM typically requires bench programming or dealer tools to recover. WiFi on either side introduces retransmission events that can stall the MDI 2 data stream during a write. GM’s own TSB specifies wired MDI 2 for VWP — that requirement applies to the device-to-PC connection at the workshop.
Server selection in Relay mode: eLinehub selects the nearest server automatically. Before starting a flash, check the RTT figure in the Technician interface. US-based shops on domestic servers consistently see RTT under 50ms.
Packet loss: For SPS2 flash sessions, sustained packet loss above 0.5% increases the risk of write errors. Resolve any retransmission warnings seen during a scan session before starting module programming.
6. Frequently Asked Questions
Does GDS2 see the mapped MDI 2 the same way it sees a locally connected device?
Yes. eLinehub maps the MDI 2 at the OS and driver level. GDS2 scans for J2534 interfaces and finds the mapped MDI 2 in the same hardware list where a locally connected device would appear. There is no protocol translation — the raw USB data stream is reconstructed on your side. Module communication timing, live data refresh rates, and bidirectional command response behave identically to a local connection.
Can SPS2 complete an ECM or TCM flash remotely without risking a bricked module?
From SPS2’s perspective, the MDI 2 is a local device — the risk profile is the same as programming at the vehicle. The write risk comes from connection interruption during the active flash window. Use wired ethernet on both sides, Direct (P2P) mode, and RTT under 80ms. Do not start a flash session over WiFi at either end.
Does the workshop need a GM Techline Connect subscription or GDS2 license?
No. The Mechanic software is free and requires no GM credentials. The workshop provides the vehicle, the MDI 2, and the wired OBD-II connection. Your Techline Connect subscription, ACDelco TDS login, and GDS2 license stay on the technician’s PC — never transmitted to the workshop machine.
Does eLinehub work with Tech2Win for older Sierra, Savana, and Yukon models?
Yes. Tech2Win runs inside Techline Connect and uses the MDI 2 as its hardware interface over USB — the same USB path eLinehub maps. Pre-2013 GMC vehicles that require Tech2Win work identically to GDS2 sessions on newer platforms. No separate configuration is needed.
We manage several repair locations. How does the Mechanic software deploy across sites?
Deploy the free Mechanic installer at each location — no per-site cost, no GM credentials required at the shop. Your central technician accepts jobs from any location using one Technician account and one set of OEM credentials. Each shop’s MDI 2 stays on-site. Every workshop contact is tied to a unique Passcode, so your customer list stays private to your technician account.
What happens if the internet drops during an SPS2 flash?
A drop during the calibration download phase — before writing starts — typically lets SPS2 restart cleanly. A drop during the active write window may leave the module in a partially programmed state requiring bench recovery or dealer intervention. Wired ethernet on both sides and RTT under 80ms reduce this risk to the lowest achievable outside a dealership bay.
Does eLinehub support the VCI distributor wanting to offer remote programming as a value-added service?
Yes. The Mechanic software is free and can be white-labeled for distribution to your workshop partners. Orders from that installer build route directly to your technician account — no platform-level competition from other technicians for your customer base. This suits both VCI retailers adding remote programming to their service offering and training organizations running supervised student sessions on live vehicles.
Start Your First Remote GMC Session
Fully functional trial for Technicians.
Mechanic software is free to use.
Questions about VWP configuration on Global B vehicles or multi-site deployment? Contact support@elinehub.com.