How to Check: Search the GFF log for “Terminal 30 voltage” or DTC U140000 – Function restriction
due to low voltage. Then compare model voltage values:
‒

If 005F shows normal voltage (>12V) and 0075 shows low (20%

‒

GPS Reception: Valid, >4 or more Satellites visible

•

Expected Result: LTE Reception Level should be above 20% with valid GPS lock.

•

Failure Indicator: LTE below 20%, despite active/valid status and minimal satellite visibility.

•

Resolution: Park the vehicle in a open-sky location with strong LTE coverage. Perform test plan.
Afterward, upload GFF log with all measured values.

3.5 VKMS Issue
•

Objective: Identify failures in VKMS activation that prevent proper configuration of the control module
0075.

•

How to Check: Review the GFF log for the following indicators:

•

Control Module 0075: check for:

•

‒

STATUS: Routine Aborted

‒

RESULT: Incorrect Results

‒

ERROR-CODE: 33 (Note: not all VKMS issues included in this code)

Also look for DTCs such as:
‒

0075 B18B0F0-VKMS: Missing adaptation

‒

0075 B18B0F1-VKMS: No basic data supply available

•

Expected Result: VKMS test completes successfully with confirmation that “VKMS data OK” is shown
on all ECU’s.

•

Failure Indicators: VKMS test plan fails or aborts, often showing ERROR-CODE: 33or the listed DTCs.

•

Resolution:
‒

Run the Replacement Test Plan (RTP) and wait for a 10-minute bus sleep (which includes
VKMS, or

‒

Perform the VKMS Test Plan via ODIS

‒

If it fails, retry at the next full hour + as few minutes (e.g. (9:28 > 10:05)

‒

Confirm “VKMS data OK” across all ECU’s

‒

Exit diagnostics, lock the vehicle, move the key at least 50 ft. (> 15 meters) away and wait 30
minutes

‒

Perform an ignition cycle and verify connectivity status in Elsa2Go

‒

Request updated GFF logs for validation

3.6 DTC’s to Monitor- Perform diagnosis and repair per ODIS Test Plan
DTC Code

Description

Implication

B20004B, B200047

Faulty Control Module

Indicates possible hardware or
software corruption in the module.

B14D796

Emergency Call/Comm Module
Internal Malfunction

Internal failure of -J949- OCU
module.

U101300

Control Module Not Coded

Module not fully coded; requires
software configuration

B200500

Data Record Invalid related to
eCall-flashing red light

ECU configuration is incomplete
or corrupt.

3.7 eCall – Flashing Red Light (SOS)
•

Objective: Address the red SOS light caused by invalid or missing data record in the module.

•

How to Check: Search the GFF log for DTC:
‒

B200500 – Data Record Invalid related to eCall

•

Expected Result: No presence of B200500 and green light active on SOS button.

•

Failure Indicator:

•

‒

Red flashing SOS light in vehicle

‒

GFF log confirms B200500

Resolution: Run the Replacement Test Plan (RTP) and upload GFF logs with all the measured values.

3.8 MNO Data Parameter / Connection Issue
•

Objective: Validate the OCU’s ability to connect to the mobile network and backend by reviewing Data
and TCP connection states.

•

How to Check: Use the GFF log to inspect these parameters under address 0075 (-J949-):
‒

/Param DataRecor/Param DataConneState > should be active

‒

/Param DataRecor/Param TCPConneState > should be active

•

Expected Result: Both parameters must be active for successful network and backend communication.

•

Failure Indicator: If either value is not active, communication cannot be established.

•

Reference – OCU Measured Parameters (Example):

Paramenter

Value

Expected / Notes

/Param_DataRecor/Param_DataConneState

not active

Should be active

/Param_DataRecor/Param_TCPConneState

not active

Should be active

/Param_DataRecor/Param_MobilCountCode

311

/Param_DataRecor/Param_MobilNetwoCode 480
/Param_DataRecor/Param_MobilNetwoValid

valid

/Param_DataRecor/Param_NetwoType

LTE

/Param_DataRecor/Param_RadioCellNumbe 86150422

/Param_DataRecor/Param_RecepLevel

18

/Param_MatchRecorDataIdent

1A63

/Param_RecorDataIdent

Network_Connectivity

/Param_RespoServiId

98

•

MNO & APN Reference Table:

Network

MCC

MNC

APN

Bootstrap

310

410

info.m2mcubic.com

Verizon

311

480

vzwb2binternet

T-Mobile

310

260

b2bvwg.tmous

Rogers

302

820

b2b.vwgroup

Part 4: Next Steps
4.1.Create a VTA/TAC Car Net Web ticket.
For the replacement of the -J949- module, all the test steps described above must be performed prior to
creating the VTA/TAC Car Net Web ticket. DO NOT REPLACE THE -J949- MODULE A SECOND TIME
WITHOUT SPECIFIC DIRECTION FROM VW.
4.2. The VW Helpline Web Ticket needs to include the following information in addition to the customary
information submitted with all VTA/TAC Car Net Web tickets:
•

All information should be related to the replacement -J949-, do not include any information associated
with the original -J949-.

•

IMEI for the replacement -J949-.

•

Verification that the vehicle was in an area with known good cell coverage.

•

From ODIS Measured Values:
‒

Number of tracked satellites

‒

Country recognition for mobile network

‒

Mobile network operator

‒

Reception level antenna 1

‒

Network type

Figure 5. SC17

Figure 6. SC19

Warranty
Information only.

Required Parts and Tools
No Special Parts required.
No Special Tools required.

Additional Information
All part and service references provided in this Technical Bulletin are subject to change and/or removal.
Always check with your Parts Dept. and Repair Manuals for the latest information.
© 2025 Volkswagen Group of America, Inc. All rights reserved. Information contained in this document is
based on the latest information available at the time of printing and is subject to the copyright and other
intellectual property rights of Volkswagen Group of America, Inc., its affiliated companies and its licensors.
All rights are reserved to make changes at any time without notice. No part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical,
photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites,
without the prior expressed written permission of the publisher.