CG FC200 “Three Items Not Ready” Function

What this new “Three item not ready” function in CG FC200 programmer is for?

Here is the clue.

Three item not ready= Three Not-Ready Monitors (three readiness monitors not ready function.)

It’s to set monitors for emissions, it might be useful for some.

 

Having three monitors in a “Not Ready” state for emissions testing can cause a vehicle to fail, especially for model year 2001 and newer vehicles.

For example, Having issues with emissions readiness for inspection. 3 systems are not ready. Heated catalyst, EGR system and secondary air system.

For vehicles from model years 1996 through 2000, the limit is two “Not Ready” monitors.

 

Elaboration:

Emissions Testing and Readiness Monitors:
Emissions testing involves checking various systems to ensure they are functioning correctly and meeting emissions standards. On-board diagnostics (OBD) monitors play a crucial role in this process. They continuously monitor the vehicle’s emissions systems.

“Not Ready” Status:
If a monitor is “Not Ready,” it means the system hasn’t completed its self-test or hasn’t been able to run the required test conditions. This can happen for various reasons, including a recent battery disconnection, a power issue, or an incomplete drive cycle.

Impact on Emissions Test:
If too many monitors are “Not Ready,” the vehicle may fail the emissions test.

 

FC200 will fix this issue within software directly.

FC200 now supports the following “Three readiness monitors not ready” function ECUs:

• DELPHI: MT22.1, ME22.1.1, MT22U
• Jiangling/Foton/Great Wall: EDC17C81/EDC17C63/EDC17C53
• Jaguar Land Rover: MED17.0.1, MED17.0, MED17.9.7, MED17.9.8, MED17.9.9, MED17.8.31, MED17.8.32
• M7.9.7, M7.9.7.1, ME7.9.7, ME7.9.7.1
• Fiat: ME17.3.0
• Wuling SIM2K-D51, SIM2K-51.4
• Silver housing: ME17, ME17.8.8, MED17, MED17.8.10, MED17.8.2, MED17.8.21
• Black housing (Black): ECU6.1, ME17, ME17.U.6, UP6
• Hyundai Kia: MEG17.9.12, MEG17.9.13, MEG17.9.2, MEG17.9.21, MEG17.9.8, ME17.9.1, ME17.9.11, ME17.9.11.1, ME17.9.21, ME17.9.21.1, MED17.9.30, MED17.9.8, EDC17CP14, ME17.9.8
• Volkswagen Skoda ME7.5.20, MED17.1.6, MED17.1, MED17.5, MED17.5.1, MED17.5.2, ME17.5.22, MED17.1.10, MED17.5.20, MED17.5.25, MED17.5.5, EDC17CP14
• BMW N20/N55/B38/N13 ECUs: MEVD17.2.5, MEVD17.2.4, MEVD17.2.9, MEVD17.2.P, MEVD17.2, MEVD17.2.6, MEVD17.2.G, MEVD17.2.K, MEVD17.2.3
• GM E37\E38\E39\E39A\E78\E80\E83\E84 ECU
• DCM7.1AP and MG1US008.

Keep updating…

Read and Write Renault SID310 ECU with CG FC200

The CGDI FC200 is a versatile programming tool that has gained attention for its ability to handle a wide range of electronic control units (ECUs). In this review, we’ll explore its functionality using the Siemens SID310 (also known as Continental) ECU as an example.

 

Setting the Stage: Preparing the SID310 ECU

The SID310, manufactured by Continental (also known as Siemens), is a common ECU found in vehicles like the Renault Talisman. To begin, the ECU is opened up to enable boot mode—a critical step for accessing its internal programming. This is where the FC200 comes into play, offering a seamless interface for reading and writing data.

 

Connecting the Device: Once the ECU is prepped, the FC200 is connected according to the provided pinout diagram. The setup is straightforward, and the software interface is intuitive. In this case, we select the Renault Talisman profile in the FC200 program.

 

 

 

 

 

Reading the Password: The first task is to extract the ECU’s password. The FC200 quickly reads it, though in this example, the password was already saved from a prior session, so no need to store it again.

 

 

 

Boot Mode Activation: With the password in hand, the ECU is connected in boot mode. The FC200 establishes a secure connection, prompting for the password to unlock further access.

 

 

Reading the Flash Memory: Next, the FC200 reads the ECU’s full flash dump. Read Dflash and Pflash data respectively. This step is crucial for creating backups before making changes.

 

  

 

 

Writing the New Firmware: The FC200 uploads the modified file back to the ECU. The process is smooth, with the device handling communication with its server to ensure accuracy. Once the write is complete, the ECU is ready.

 

 

Once the checksum was recalculated (via server support), the updated firmware was written back to the ECU. The process concluded successfully, and the ECU was ready for reinstallation. The device was sealed with gasket maker to ensure proper protection before being reinstalled in the vehicle.

Verdict

The CGDI FC200 is a powerful and reliable tool, offering extensive functionality for its price. While some features require a license, its performance and compatibility make it a worthwhile investment for professionals working with diverse ECU systems. If you’re considering purchasing it, this tool comes highly recommended.