Smok Visteon 70F35 Series

Need help?

Do you have a question about the Smok Visteon 70F35 Series and is the answer not in the manual?

Summary

Getting Started

System Requirements

Lists the necessary tools and licenses for performing dashboard operations.

Getting Help

Provides step-by-step guidance for using UHDS and Jtag tools for car operations.

Learn Keys

Learn Key Requirements

Outlines the essential items needed, including original and new keys, and required tools.

Learn Key Procedure

Details the step-by-step process for programming new keys to the vehicle.

Learn Dashboard

Dashboard Learning Requirements

Specifies the necessary components and data for learning a new dashboard.

Dashboard Learning Procedure

Describes the sequential steps for integrating a used dashboard into the car.

Read Immo Data CS and CP

Immo Data Reading Procedure

Explains how to extract Immo data and Component Protection information via Jtag.

Learn Used ECU

ECU Learning Requirements

Lists the data needed from the donor ECU and original ECU for successful learning.

ECU Learning Procedure

Details the steps to integrate a donor ECU by transferring its Immo data.

Learn Used TCU

TCU Learning Requirements

Specifies the CS and PW data required from donor and original TCUs.

TCU Learning Procedure

Outlines the process for transferring Immo data to a donor TCU.

Learn Used ELV

ELV Learning Requirements

Lists the CS and PW data needed from donor and original ELVs.

ELV Learning Procedure

Details the steps for integrating a donor ELV by updating its Immo data.

Visteon 70 F3525 Connection

Visteon 70 F3525 Diagram

Illustrates the physical connections for the Visteon 70F3525 dashboard.

Visteon 70 F3529 v1 Connections

Method 1 Connection Diagram

Shows the wiring for the Visteon 70F3529 v1 using Method 1.

Method 2 Connection Diagram

Illustrates the Visteon 70F3529 v1 connection using Method 2.

Visteon 70 F3529 v2 Connections

Method 1 Connection Diagram

Provides wiring details for the Visteon 70F3529 v2 using Method 1.

Method 2 Connection Diagram

Shows the Visteon 70F3529 v2 connection layout for Method 2.

Method 2 (without lift Pin) Diagram

Illustrates Visteon 70F3529 v2 connection for Method 2 without lifting a pin.

Visteon 70 F3532 Connection

Visteon 70 F3532 Diagram

Shows the specific wiring diagram for the Visteon 70F3532 dashboard.

The Visteon 70F35xx device is a tool primarily designed for working with Visteon and Johnson Control dashboards, specifically those found in VW/Skoda vehicles. Its main functions revolve around odometer (KM) adjustments, key learning, and the management of immobilizer (immo) data and component protection (CP) for various vehicle modules, including the dashboard, Engine Control Unit (ECU), Transmission Control Unit (TCU), and Electronic Steering Lock (ELV).

Function Description:

The device offers several key functionalities:

Odometer (KM) Adjustment:
- Read KM OBD: Allows reading the current odometer value via the On-Board Diagnostics (OBD) port.
- Write KM OBD: Enables writing a new odometer value via OBD. This operation requires the dashboard to be first reset to 0 km.
- Prepare Dashboard by Jtag (reset Km 0): This is a crucial step for KM adjustment. It involves connecting the Jtag tool to the dashboard's Printed Circuit Board (PCB) and using the "Prepare Flash" function in the UHDS software. This process resets the dashboard's odometer to 0 km and creates a backup of the MCU's flash and dataflash. After this preparation, the dashboard can be reconnected to the car, and a new KM value can be set via OBD. This preparation step is a one-time operation for each KM adjustment; if a new KM adjustment is needed later, the dashboard must be prepared again from the beginning.
Key Learning:
- The key learning procedure involves reading a full backup of the dashboard's data via Jtag, then using the "Security Block Editor" to decode immo data, including the Component Security (CS) value.
- An original key from the car and a new key to be learned are required, along with the UHDS tool and KeyMaker II tool.
- The KeyMaker II is used to read the CS-Key from the original key (after providing the decoded CS from the security block editor) and then to "Make Dealer Key" for the new key, again using the decoded CS.
- Finally, the prepared dealer key is learned to the car by connecting the UHDS to the car's OBD port and using the "Learn Key" function in the "Main" tab. All existing and new keys must be learned one by one. For keyless systems, the key must be held near the steering column coil.
Immobilizer (Immo) Data and Component Protection (CP) Management:
- Read Immo Data CS and CP: This operation requires Jtag connection to the dashboard. It involves reading a full backup, then using the "Security Block Editor" to decode all immo and CP data, which can then be saved to a text file.
- Learning Used ECU, TCU, and ELV to the Car: This is a complex process for integrating a donor (used) module into a vehicle. It requires specific data from both the donor module and the original module (or the original dashboard/key).
  - For ECU, TCU, and ELV:
First, immo data from the original dashboard is read via Jtag and decoded using the "Security Block Editor" to obtain CS, CP, CP Key, VIN, PW (power class), and CNF (config).
Immo data from the donor module is also read via Jtag and decoded to obtain its CS.
The KeyMaker II is used with the original key to read the CS-Key, providing the decoded CS from the original dash.
In the UHDS software, under the respective module's panel (ECU, TCU, or ELV), the "Target (new) Immo data" fields are filled with the data from the original module (or decoded from the CS-key). The "Source (old) immo data" fields are filled with the CS from the donor module.
After changing the immo data, the MAC (Module Access Code) needs to be learned by going to the "immo5" panel and filling the "Target (new) Immo data Dashboard" field with the CS decoded from the dashboard, then pressing "Login".
Finally, component protection needs to be learned by filling the "Component Protection Access key (CP key)" and "Current Access key" with data from the donor dashboard, and the "New Access key" with data from the original dashboard, then pressing "Apply". The "Component Protection CP" fields are then filled with the access key and CP from the original dashboard, followed by "Apply".
If the ABS coding string was lost, it needs to be written back using VCDS or another tool.

Important Technical Specifications:

Supported MCUs: The device supports Visteon 70F3525 and 70F3529 MCUs.
Required Tools:
- Jtag Tool
- UHDS Tool
- KeyMaker II tool
Required Licenses:
- JG0043 (NEC V850E2 Sec) Jtag License
- JG0022 (NEC V850E2 Sec) Jtag License
- VW0045 (VW JC 70F35xx) UHDS License
Supported Boards: The manual lists numerous part numbers for supported Visteon/Johnson Control dashboards, indicating a wide range of compatibility across different VW/Skoda models. These include part numbers starting with 517, 3G5, 3G0, 5E0, 5G0, 5G1, 5TA, and 5GG.
Connection Methods: The manual illustrates various Jtag connection methods for different dashboard versions (e.g., Visteon 70F3525, Visteon 70F3529 v1 Method 1, Visteon 70F3529 v1 Method 2, Visteon 70F3529 v2 Method 1, Visteon 70F3529 v2 Method 2, Visteon 70F3532). These methods often involve soldering wires to specific points on the PCB and sometimes require soldering a 2.2K resistor between red and grey wires, or cutting a specific track, or pulling up a specific pin.

Usage Features:

Software Interface: The operations are performed using the UHDS software, which includes an XCAN module for selecting the vehicle type and specific panels for different functions (e.g., "Main," "Immo5," "ECU," "TCU," "ELV," "Kessy," "Security Block Editor," "ECU Dump Tool").
Step-by-Step Procedures: The manual provides detailed, step-by-step instructions for each operation, including specific button presses and data entry requirements.
Backup Functionality: The Jtag "Prepare Flash" function automatically creates backups of the MCU's flash and dataflash, which is crucial for recovery or reference.
Data Decoding: The "Security Block Editor" is a key feature for decoding complex immo and CP data from raw backups, making it accessible for manipulation.
Flexibility in Connection: For some dashboards, multiple Jtag connection methods are provided, allowing the user to choose the most convenient or suitable one.
Hands-Free Option: The device addresses issues with hands-free functionality, providing a "login" button in the "Kessy" panel if the feature is not working after other operations.

Maintenance Features:

Software Updates: Users are advised to check for the latest updates of Jtag and UHDS software to ensure optimal performance and compatibility.
Careful Soldering: The procedures frequently mention soldering wires as per provided pictures, emphasizing the need for precise and careful soldering to avoid damage to the PCB.
Data Preservation: The ability to save decoded immo data to text files ensures that critical information can be stored and reused, preventing data loss.
Understanding Module Differences: The manual explicitly states that Component Security (CS) values differ between the Dashboard, ECU, TCU, and ELV, highlighting the importance of understanding and correctly managing these distinct values for each module.
Power Class (PW) Management: The device acknowledges that PW is stored in the flash of ECU/TCU and is dependent on the loaded software/firmware, while it can be changed in the dashboard and ELV via immo data modification. This distinction is important for successful module adaptation.

In summary, the Visteon 70F35xx device, used in conjunction with the UHDS and KeyMaker II tools, is a comprehensive solution for advanced diagnostics and programming of Visteon/Johnson Control dashboards in VW/Skoda vehicles, particularly for odometer correction, key programming, and the adaptation of used control modules by managing their immobilizer and component protection data. Its reliance on Jtag connections and detailed software procedures underscores its professional application.