Step 1 Controller Programming (1st Week) 1 The Correct Payload Needs To Be Identified From The CUOS

Step 1. Controller Programming (1st week) 1. The correct payload needs to be identified from the CUOS document. 2. The Controllers must be blank with the BLANK Payload before programming them with the correct payload. 3. Dummy VINs should be used to program the controllers to avoid wrong payload upload on JDCP. In case Dummy VINs could not be used, the order number used for carrying out the FITs, should be reprogrammed with the original payload and the VIN should be deleted from GFPTx DTF Fits Product Group. 4. The Factory integration tool GFPTx and JD Common Loader should be used to program the controllers. The version used for the tools should be the same as on the production PCs. 5. The correct sequence for powering controller for Programming is as below: U_Battery ON→ 5 sec → ELX ON → Programming → ELX OFF →U_Battery OFF 6. Post programming, the programming logs for every programming session (for all payloads) must be logged at M:\Pruefstaende\Software_Master\Factory Integration Test. The programming logs for failed programming attempts also need to be saved.

11.11.2025 10:49