VCP User Guide - gce.cummins.com€¦ · isx g 11.9l cm2180a cummins euro5 isb 5.9l cm2880 euro3...

VEHICLE ELECTRONICS PROGRAMMING STATION

(VEPS) VCP User’s Guide

v8.1.4

Cummins Vendor Component Program (VCP)

- 2 - 12/10/14

1 OVERVIEW ................................................................................................................4

2 VEPS WIRING CONNECTIONS .............................................................................5

3 PARAMETER FILE ...................................................................................................5

SETUP RECORDS ...............................................................................................................6

PARAMETER RECORDS ....................................................................................................8

REMARK RECORDS ..........................................................................................................8

4 COMMAND LINE ......................................................................................................9

PARAMETER FILE .............................................................................................................9

VERIFICATION FILE .........................................................................................................9

REPORT FILE ....................................................................................................................9

OEM KEY ........................................................................................................................9

DOCUMENTATION FILE ....................................................................................................9

PASSWORDS ....................................................................................................................10

DEBUG / TRACE LOGGING .............................................................................................10

5 USER INTERFACE ..................................................................................................11

LEDS ..............................................................................................................................11

Blinking Yellow ...........................................................................................................11

Blinking Green ............................................................................................................11

Solid Green ..................................................................................................................11

Solid Yellow .................................................................................................................11

Solid Red .....................................................................................................................12

LIST BOX ........................................................................................................................13

BUTTONS.........................................................................................................................16

Information Button ......................................................................................................16

Report Button ..............................................................................................................17

Exit Button ...................................................................................................................17

6 CONFIGURATION UTILITY ................................................................................18

VCP STATUS WINDOW ..................................................................................................18

VCP Status Window - Show ........................................................................................18

VCP Status Window - Automatically Terminate .........................................................19

VCP Status Window - Display time .............................................................................19

COMMUNICATIONS .........................................................................................................19

RP1210 ........................................................................................................................19

Inline II – J1939 ..........................................................................................................19

REPORTS .........................................................................................................................19

ECM CONTROL..............................................................................................................20

Reset faults ..................................................................................................................20

Stop ECM Broadcast (07 engines & later) ..................................................................20


- 3 - 12/10/14

Set Real Time Clock to PC UTC Time ........................................................................20

WARNINGS & ERRORS ...................................................................................................21

Give parameter dependency warnings ........................................................................21

Suppress a parameter’s warning/error when the OEM’s value matches the ECM’s .21

GENERAL SETTINGS .......................................................................................................22

Show parameter description in Verification File ........................................................22

Write engine information to Verification File .............................................................23

Write command-line invocation Information to Verification File...............................23

Enable Write Verification ............................................................................................23

Write Trace / Debug Information ................................................................................24

RESTORE DEFAULTS ......................................................................................................24

7 VEPS OEM PROGRAMMING REFERENCE MANUAL CREATION GUIDE24

8 DOCUMENT REVISION HISTORY .....................................................................28


- 4 - 12/10/14

1 Overview The Cummins VCP is an Engine programming tool designed to help OEM’s program

engine on the assembly line. It is designed in accordance with standards for Vehicle

Electronics Programming Stations (VEPS) outlined in SAE J2461 and supports the

associated J2286 compliant parameter and verification files.

The basic operation of any VEPS VCP is to program an ECM according a parameter file,

and pass status information back to the calling program in a verification file. The names

of the parameter and verification files are passed via the command line. This is shown in

Figure 1.

Figure 1 - VEPS Operation

OEM Shop Floor

ProgramCummins VCP

Parameter

File

Verification

File

Command Line


- 5 - 12/10/14

2 VEPS Wiring Connections OEM programming of a Cummins engine over J1587 or J1939 datalinks can be

accomplished either prior to or after the engine is installed the vehicle chassis.

Programming the engine after it is installed in the chassis is recommended; however, if

this is not possible and the engine must be programmed prior to installation in the chassis,

additional precautions need to be taken to limit the potential damage to the Engine

Control Module (ECM).

• When connecting VEPS to the vehicle or ECM datalink, the datalink adaptor

power supply must have a common ground connection with the Battery (-)

connection of the ECM. The datalink adaptor should be powered from the same

power supply as the ECM. If this is not possible and the datalink adaptor has a

separate power supply, the supply must have a common ground connection with

the Battery (-) connection of the ECM.

• The ECM power connection must be made prior to energizing the ECM (Do not

"Hot Plug" the ECM).

• The ECM Battery (-) must be connected to the engine block prior to energizing

the key switch line.

• The key switch line must be de-energized prior to de-energizing the ECM after the

VEPS session. It has been observed, that under certain circumstances, the ECM

is not retaining the value of certain parameters like Low Idle Speed (10030) as

set by VEPS. This phenomenon is caused when battery power is removed from

the ECM before a complete ECM power down has completed after a VEPS

session. To ensure all of the parameter settings are properly saved in the ECM

after the VEPS sessions ends, the user needs to turn the key switch off and

allow the ECM power down completely before battery power is removed from

the ECM.

• ECM must be de-energized prior to disconnecting the power and ground

connections.

3 Parameter File The parameter file is the primary interface to the Cummins VCP. It is a text file

containing a list of parameters and values to be programmed in the ECM. The Cummins

VCP supports three SAE J2286 record formats.

• Setup Records

• Parameter Records, and

• Remarks Records


- 6 - 12/10/14

Setup Records

Two setup records are required for VEPS to program an engine ECM.

• Communications Port, and

• Engine Module Type

The communications port setup record is used to identify the port to which the datalink

adapter is connected. Here is an example that specifies COM1 as the port:

S,COMX,1

The engine module type setup record is used to specify the target ECM family for a given

parameter file. That is, this record limits the type of ECMs VEPS will program with a

given parameter file. This is to prevent a parameter file intended for say an ISB to be

loaded into an N14. Here is the format of the module type setup record:

S,MODULE,<Module Name>

Module Names are as follows:

SPECIFIER Engine Product

HDD or 98HDD ISM, ISX, & Signature 600

NCORE ISB, ISC, & ISL

Celect+ N14 & M11

ECHO ISBe

CGAS C8.3G Plus, L10 Plus & B5.9G Plus

DE ISX 02, ISM 02, & ISM 04

ECHO2 ISB 02, ISC 03 & ISL 03

TIER3C2 QSB 07, QSC 04 and QSL 04

EAGLE ISM 07 and ISX 07

ISB07(or EAGLE) ISB 07

ISC07(or EAGLE) ISC 07 or ISL 07

Euro5 ISBe Euro 4.5/5, ISLe Euro 4.5/5

CM2250 ISX 10, ISB, ISC, ISL 10

CM2180A ISL G

CM2220 ISF3.8 Euro3, ISF3.8 Euro4, ISF2.8 HD Euro4, ISF2.8 LD

Euro4

CM2150C ISDe3,ISLe3,ISBe3/ISCe3 EUP

EAGLE ISMe4 SCR

EAGLE GX15 CM871

CUMMINS ISBe3 6.7L CM2150E

ISLe 9.5L CM2150E

QSZ 13L CM2150E

ISB 4.5/ 6.7, Euro5 CM2150E


- 7 - 12/10/14

Euro5 ISL8.9 CM2150E

Euro5 ISF 3.8L CM2220A

NS4 ISF 3.8L CM2220

ISB 3.9L CM2220C

Euro 5 ISF 2.8L CM2220C


ISFe Euro6 CM2350A

ISBe Euro6 CM2350A

ISL 8.9L CM2350A

ISB 6.7L CM2350A

ISX11.9/15 CM2350A

CUMMINS NS4 ISDe6.7/ ISDe4.5/ ISBe5.9 CM2150E

NS4 ISDe6.7 CM2150E

BSIII 5.9L CM2150E

NS4 ISF 3.8L CM2220C

ISF 2.8L Euro 5 CM2220C

ISX G 11.9L CM2180A

CUMMINS Euro5 ISB 5.9L CM2880

Euro3 ISN 14L CM876

B5.9L, 6.7L, BS IV CM2880


ISX15 Euro4 CM2250

Sao Paulo CM2880

CUMMINS ISZ 13L Euro4 CM2150E

CUMMINS ISLe 8.9L BS3 CM2880A

ISLe 8.9L BS4 CM2880A

ISDe 4.5/6.7L NS4 CM2880A

ISC 8.3L NS4 CM2880A

CM3230 ISV 5.0L CM3230

CUMMINS ISF 3.8L Euro6 CM2350A

ISB 6.7L G CM2180A


CUMMINS QSB 4.5/6.7L QSL 9L 2150C

CUMMINS ISF 2.8L Euro5 CM2220C

ISL 9.5L NS5 CM2880A

2017 ISB 6.7L CM2350A

ISB 4.5/6.7L JP16 CM2350A

ISB 4.5/6.7L Euro6 CM2350A

Table 1 - Supported Engine Programs


- 8 - 12/10/14

Parameter Records

Parameter Records indicated which parameters and values to program in the ECM. The

parameter file may contain any number of parameter records, in any order. The format for

parameter records must be as follows:

P,<VEPS name>,<command>,<value>,<comment>

The VEPS names for each parameter are defined in the OEM reference manuals for each

engine. The command field may take on the value of R (read), W (write), or B (both)

although specifying B has the same effect as specifying W. Values must be numeric for

trims, Y or N for features, and ASCII for Dataplate.

Remark Records

Remark records are used to place comments in the parameter file, and are ignored by the

application. The format of a remark record is shown below:

REM <remark>

An example of a parameter file for a 2010 module is shown below.

S,COMX,1

S,MODULE,CUMMINS

P,10000,W,100

P,20011,W,Y

P,21781,W,Y

P,12280,W,4599

P,12310,W,4000

P,12860,W,3000

P,12870,W,2000

P,12479,W,Y

REM P,10300,W,2

REM P,11340,W,5


- 9 - 12/10/14

4 Command Line VEPS parameter and verification files must be passed as command line arguments to the

VCP. The VCP will also generate a report file and documentation file if specified on the

command line

Parameter File

-p <Path and File name for the parameter file>

Use this command line option to specify the name of the parameter file to be used to

program the ECM. If the –p option is omitted, the VCP will look for a file named

ceco600.par located in the Current Working Directory. A valid parameter file is

required for VCP operation.

Verification File

-v <Path and File name for the parameter file>

Use this command line option to specify the name of the verification file to receive the

results of the programming session. If the –v option is omitted, the VCP will create a file

named ceco600.ver in the Common Application Data folder.

Report File

-r <Path and File name for the parameter file>

Use this option to save a comma delimited version of the VEPS Session report in the

specified file. This option is provided as a means to save session reports since the VCP

will not save or redisplay previously generated session reports. Report files can be

viewed later by importing them into most spreadsheets.

OEM Key

-i <Report Identifier>

Use this option to place a unique identifier in the header of the session report. This

option is provided as a means to associate a report with a specific vehicle. Typically the

report identifier is a VIN or customer order number, but it may also be a model number,

or other identifying string..

Documentation File

-d <Path and File Name (oemdoc.csv)>


- 10 - 12/10/14

Use this option as the first step towards generating the OEM Programming Reference

Manual. Adding this option creates a file in the target path containing parameter

information extracted from the ECM. Once this file is created, the user may proceed to

open a copy of the OEM Documentation Generator.doc (Microsoft Word)

document (found in the \Documentation folder) and execute a macro that will “build” a

list of programmable parameters specific to that ECM.

Important items to note:

• For the macro to work, the target file must be named oemdoc.csv

• The macro expects the target file to reside in the same location as the Word

document itself.

• The macro is a one-time destructive process to the Word doc itself. It is

recommended practice to “copy & paste” the original OEM Documentation

Generator.doc to the target folder and work from there. Alternatively, once

generated, the resulting document can be saved to a different name or renamed at

a later time.

Passwords

-pw <VEPS name> <password> …

Use of this option provides the OEM with an alternative means of providing ECM

password information to the VCP (as opposed to a parameter file). A single option can

handle as many password parameters as the VCP (or ECM) supports. The preferred

syntax (following the –pw option) is the VEPS Name followed by the password (repeat

the pattern for additional passwords); all elements separated by whitespace. The

passwords themselves follow the same restrictions as their parameter file counterparts.

Example:

ceco600.exe -p c:\VCP\Cummins\abc.par –pw 00099 MASTER 00061 OEMPWD

…which is equivalent to:

P,00099,W,MASTER P,00061,W,OEMPWD

Note that use of this option does not replace existing password parameter information in

the parameter file. In other words, the presence of the password information in the

parameter file overrides corresponding information provided through this option.

Debug / Trace Logging

-l <Path and File Name>

-la <Path and File Name>


- 11 - 12/10/14

Use of this option enables the Debug / Trace logging feature and writes the collected

information to the target file name. Normally, this option is not necessary for essential

VCP operation. However, using this option can provide additional information to a

Cummins support representative in troubleshooting programmatic issues. The difference

between the –l and –la options is how the VCP treats an existing file name. If the –l

option is used, any existing file and data will be overwritten. Alternatively, the –la option

will append new data to an existing file.

Note: If Write Trace / Debug is checked in the VCP Configuration Utility, this implies

the –l option with file name Debug.xml written to the Common Application Data

folder (i.e. \ProgramData\Cummins\CumminsVCP).

The following example illustrates the use of the command line parameters:

ceco600.exe -p c:\VCP\Cummins\abc.par -v c:\VCP\Cummins\abc.ver –r c:\VCP\Cummins\abc.vrp –i 123456

In the previous example, the VCP (ceco600.exe) will look for the parameter file

(abc.par) in the directory c:\VCP\Cummins. The VCP will write the verification file

(abc.ver) in the directory c:\VCP\Cummins. The VCP will write the report file

(abc.vrp) in the directory c:\VCP\Cummins. The OEM key “123456” will be printed

in header of the VEPS session report.

5 User Interface

LEDs

LEDs are used to give a visual status of the programming session. There are 5 ways in

which the LEDs provide status information.

Blinking Yellow

The VCP is attempting to initialize communication with the Engine.

Blinking Green

The VCP has established communication with the ECM and is programming the

specified parameters.

Solid Green

Successful VEPS session. There are no parameter errors.

Solid Yellow

A parameter error has occurred. The VEPS session was successful, but at least

one parameter has an error. If the user clicks on the parameter error icon, then a


- 12 - 12/10/14

message box will appear with a detailed description of the error, as shown in

Figure 5

Solid Red

A fatal error has occurred. The VCP has terminated communications with the

ECM. The cause of the error is displayed in the list box.


- 13 - 12/10/14

List Box

During the VCP session, runtime status messages are displayed in the list box on the main

window. These status messages are used primarily to inform the user of status and for

trouble shooting.

Figure 2 – VCP Status


- 14 - 12/10/14

Once the VCP has finished programming the ECM, the List Box displays the

programmed parameters as shown in Figure 3.

Figure 3 – End of Session

If an error occurred on one of the programmed parameters, the list box displays a yellow

exclamation icon next to the parameter(s) which encountered the error (See Figure 4).

All parameter errors will be shown in the list box first.

If the parameter had an error, the user may double click on the icon or VEPS Name of the

parameter to display a detail error message. This is shown in Figure 5


- 15 - 12/10/14

Figure 4 – Parameter Error

Figure 5 - Error Message Displayed


- 16 - 12/10/14

Buttons

There are three Buttons on the main window; Information Button, Report Button, and

Exit Button. These buttons are disabled until the VEPS session is completed.

Information Button

Pressing the Information Button will display advanced information about the ECM, ECM

Calibration, and VCP Software. This information is often valuable when trouble

shooting the application.

Figure 6 - Information Dialog


- 17 - 12/10/14

Report Button

Pressing the report button will display the VEPS session report in a “print preview “style

window. The report may be printed from this screen, or the user may simply exit to the

main window.

Figure 7 – VEPS Session Report

Exit Button

This button exits the VCP.


- 18 - 12/10/14

6 Configuration Utility A configuration utility program is installed alongside the Cummins VCP software. This

utility allows the user to modify some aspects of the VCP operation. The configuration

utility may be accessed via the Windows Control Panel (if deployed via Windows

Installer) or by double-clicking the vcpconfig.cpl found in the VEPS VCP

installation folder.

Figure 8 - VCP Configuration Utility

VCP Status Window

The User Interface can be assigned various behaviors based on the calling environment,

and how the VCP is integrated with the OEM’s VEPS system.

VCP Status Window - Show

This checkbox determines if the VCP user interface is to be displayed. If the user

prefers to automatically hide the user interface during programming, then this box

should be unchecked.

This checkbox is checked by default.


- 19 - 12/10/14

VCP Status Window - Automatically Terminate

This checkbox should be checked if the user desires that the user interface

automatically terminate at the end of the VEPS session, instead of waiting for the

user to press the Exit button. This option may be used to return control to the

calling program without any additional user interaction.

This checkbox is unchecked by default.

VCP Status Window - Display time

This value is only valid when the user has configured the VCP to automatically

terminate. This value is the amount of time, in seconds, that the user interface

will stay active after the VCP session has ended.

The default value is 5 seconds.

Communications

RP1210

If one or more RP1210 drivers have been installed on the system, the VCP will

detect it and enable the RP1210 radio button. If RP1210 is selected, the user must

specify which Vendor’s RP1210 driver to use (if there is more than one), and the

protocol and device which is being used. When using RP1210, the COM port

specified in the parameter file is ignored, the correct comport must be selected in

the Device combo box.

Inline II – J1939

When specifying the Inline II, the VCP will try to communicate with the engine

using the protocol that has been selected by the J1708 / J1939 radio buttons. If

communications cannot be established with the chosen protocol, the VCP will

attempt the alternate protocol before failing. Choosing the protocol that is

currently in use will decrease the time needed for the VCP to establish

communication with the Engine. The COM port is selected in the VEPS

parameter file. See Section 3.

There is no default preference for communications, although first time installation of the

VCP will have RP1210 checked with the first available vendor & options selected

(assuming a single RP1210 device is available). If the VCP is upgraded (or uninstalled),

the Communication settings will be remembered.

Reports

VEPS session reports can be configured to print automatically after the VCP completes

programming. If this option is selected, the user can opt to print to the operating system’s

default printer, or print via the print dialog. The advantage of choosing a default printer

is one of automatically printing reports without any additional user interaction. Choosing


- 20 - 12/10/14

to print via a print dialog will allow a user to either specify a printer or cancel said action.


ECM Control

Reset faults

This combo box has three options for the user to select:

Reset Faults Option ECM Function

None No operation is performed on the ECM.

Erase Inactive Faults After all parameters are programmed, the

VCP will attempt to erase all Inactive

Faults in the ECM.

Reset All Faults – 07 & later engines An option available only to Cummins

2007 engines & later. After all parameters

are programmed, the VCP will attempt to

erase all Cummins and OBD related

faults.

Table 2 – Reset Faults Options

This option is defaulted as “None”.

Stop ECM Broadcast (07 engines & later)

This setting allows OEMs to program Cummins 2007 and later engines

with/without reduced ECM broadcast traffic.

Enabling this feature will request the ECM to stop broadcast to gain increased

performance by reducing bus traffic. Once the VCP has successfully programmed

the ECM, it will request the ECM to resume broadcast. This is the preferred

behavior of the VCP.

However, if the OEM suspects leaving this feature enabled is causing issues, they

may instead opt to disable (uncheck) this feature, thus allowing the ECM to

continue responding to other devices as well.


Set Real Time Clock to PC UTC Time

This setting allows OEMs to set Real Time Clock to the host PC’s UTC time.

This feature is engine-specific and typically only supported in Euro 4/4.5/5

products.



- 21 - 12/10/14

Measurement Units

• If English is selected, parameter values will be interpreted using English units.

• If Metric is selected, parameter values will be interpreted using Metric units.

English is the default selection.

Warnings & Errors

Give parameter dependency warnings

Many of the dependencies that are enforced by the VCP can be disabled. These

warnings are intended to inform the user that a parameter will have no effect due

to the state of a related parameter. Cummins recommends that these dependency

warnings be left on to give feedback on potential problems with the parameter set

which is being programmed into the ECM. If this checkbox is unchecked, the

VCP will still enforce dependencies which must be enforced to maintain the

integrity of the ECM’s data.

A pop up warning message will appear when unchecking “Give parameter

dependency warnings” option in configuration utility.

Example 1. Feature enabled. Feature-parameter errors are recorded in the

verification file.

… S,PERROR,T,

P,0013,0000,N, Cruise Control Enable

P,0060,0959,1.00, Cruise Control Lower Droop

P,0061,0959,0.00, Cruise Control Upper Droop

…

Example 2. Feature disabled. Feature-parameter errors are NOT recorded in the

verification file.

… S,PERROR,F,




…


Suppress a parameter’s warning/error when the OEM’s value matches the ECM’s

If this checkbox is checked, the VCP will perform a parameter value comparison

between the OEM requested value and the current value in the ECM. If the


- 22 - 12/10/14

parameter values match, then no write operation will be performed and,

additionally, any potential warning/error (if exists) will be suppressed.

There are both advantages and disadvantages to enabling this checkbox:

Advantages

• Minimizes the number of warnings/errors reported.

• Serves as a filter mechanism for reporting. Limits warning/error reporting

to only value-changing parameters.

Disadvantages

• Introduces inconsistent behavior to VCP error/warning detection and

reporting.

• Hides dependency warnings that may provide otherwise valuable

information towards correctly configuring the engine. For example, the

OEM may be attempting to adjust an effectively disabled feature, but since

the OEM value matched the value already in the ECM, such a dependency

warning was suppressed.

• The engine’s calibrated (i.e. default) value may not always represent a

valid state in the ECM. Enabling the checkbox might prevent the VCP

from reporting such issues.

Alternatively, unchecking this checkbox would ensure both the Cummins and/or

OEM values represent a valid setting in the ECM after a programming session.

Unchecking this checkbox is highly recommended.


General Settings

Show parameter description in Verification File

If this checkbox is checked, then all parameters listed in the SAE J2286

Verification File (.ver) will have their corresponding parameter description

appended. The parameter description will be the last value in the parameter

record, and it will be delimited by a comma (i.e. a 5th optional field).

Example 1. Parameter feature is enabled. Parameter description is written in

verification file.

… P,0000,0000,5.73, Rear Axle Ratio

P,0007,0000,520.00, Tire Revolutions per Mile

P,0005,0002,0.74, Transmission Top Gear Ratio

…


- 23 - 12/10/14

Example 2. Parameter feature is disabled. Parameter description is NOT written

in verification file.

… P,0000,0000,5.73

P,0007,0000,520.00

P,0005,0002,0.74

…


Write engine information to Verification File

The VCP will always read the Engine Serial Number from the engine. This

information is displayed on the user interface. If the user wishes to have this

information written to the verification file, then this checkbox should be checked.

Example demonstrating engine information written to the verification file:

… P,5001,0000,ISX12/15 CM2350A, Engine Type

P,5003,0000,EF10044.16, ECM Code

P,5005,0000,450.00, Horsepower

P,5007,0000,12170, SC Option

P,5009,0000,1870, DO Option

P,5010,0000,9.30.0.6, Calibration Version

…


Write command-line invocation Information to Verification File

This setting adds the program invocation information to the third line of the

verification file. If this is disabled, the third line of the verification file will be a

blank line.


Enable Write Verification

To verify that parameters were correctly written to the ECM, at the end of the

VCP session, the program will complete a second read of all parameters from the

ECM. The VCP program will then compare these values with the values in the

parameter file to verify that the values are correct. The process of reading the

ECM values the second time adds time to the VCP session.



- 24 - 12/10/14

Write Trace / Debug Information

This setting allows both the VCP and the supporting communication library

Common Components to log information to their respective files which can later

be used for debugging. This setting should only be set if directed by the Cummins

VEPS team.

Notes:

• The default location for these files is in the Common Application Data

folder.

• The default filename for VCP debugging is Debug.xml

• The default filename(s) for logging Common Components errors is

CError.xml & CError.txt (deprecated).

• See Command Line topic to learn about naming and redirecting the debug

file output to a user defined location.


Restore Defaults

Clicking this button will automatically change the VCP settings back to their defaults.

Note that the user must click the Ok button for these changes to take effect.

7 VEPS OEM Programming Reference Manual Creation

Guide

The following 3 conditions are assumed:

-Cummins VCP has been configured correctly and can successfully program the module

for which a programming reference manual will be generated

-PC has Microsoft© Word installed

-This guide is based on Microsoft© Word 2007

1. Create a desktop shortcut to the file: C:\Program Files\Cummins\VEPS VCP 8\ceco600.exe

2. Right-click on the shortcut and select “Properties”. Click on the “Shortcut” tab.

3. Append the option “-p pathtoparfile\yourfile.par -d oemdoc.csv” to the end of the

existing Target textbox. The “oemdoc.csv” file may be written to any directory, but must

be named “oemdoc.csv”.

Example command line:

"C:\Program Files\Cummins\VEPS VCP 8\ceco600.exe" -p

C:\ProgramData\temp\test.par -d C:\ProgramData\temp\oemdoc.csv


- 25 - 12/10/14

4. The .par file in the command line used to generate the programming reference manual

should have the correct Specifier (i.e. EAGLE, CUMMINS, …) in the setup records as

per your product. Parameter records are not required in the .par file to create OEM

documentation, but are allowed.

5. Connect ECM to the VEPS PC using a datalink adaptor.

6. Run VEPS by double-clicking the desktop shortcut.

7. Once the VEPS session is completed, close the VEPS window. It is important to close

the VEPS window before proceeding to the next step.


- 26 - 12/10/14

8. Find the newly created oemdoc.csv file in the location you specified in the command line.

In this example, it is: C:\ProgramData\temp\oemdoc.csv.

9. Copy the file OEM Documentation Generator.doc to the same directory as the

oemdoc.csv file. The file OEM Documentation Generator.doc is located (by

default) in the directory: C:\Program Files\Cummins\VEP VCP 8\Documentation\

10. Launch OEM Documentation.doc. The document will open in Microsoft© Word.

11. Macros must be Enabled in Microsoft© Word to use the documentation generator. If a

Security Warning is displayed, select Options, then “Enable this content”

12. Select the Add-Ins tab.


- 27 - 12/10/14

13. Click on the “Create OEM Documentation” button.

14. The Program Reference Manual will be generated. Save the manual to the name you

desire.


- 28 - 12/10/14

8 Document Revision History

Revision

Number Date Changed By Summary of Changes

2 11/17/2014 Stephen Burgin Corrected an omission to the password

command-line usage.

Added the following product(s) to the -

Supported Engine Programs table:

• ISF 2.8L Euro5 CM2220C

• ISL 9.5L NS5 CM2880A

• 2017 ISB 6.7L CM2350A

• ISB 4.5/6.7L JP16 CM2350A

• ISB 4.5/6.7L Euro6

CM2350A

Re-organized & updated the Configuration

Utility section to reflect changes made in the

v8.1.4 release.

1 8/28/2014 Stephen Burgin Changed module specifier of “ISZ 13L Euro4

CM2150E” from EAGLE to CUMMINS.



• QSB 4.5/6.7L QSL 9L 2150C

Removed “Rio CM2350A” from the -

Supported Engine Programs table.

0 4/31/2014 Stephen Burgin For a detailed list of changes to the VCP, see

the accompanying Release Notice document.

VEHICLE ELECTRONICS PROGRAMMING STATION

(VEPS) VCP User’s Guide

v8.1.4


- 2 - 12/10/14

1� OVERVIEW ................................................................................................................4�

2� VEPS WIRING CONNECTIONS .............................................................................5�

3� PARAMETER FILE ...................................................................................................5�

SETUP RECORDS ...............................................................................................................6�

PARAMETER RECORDS ....................................................................................................8�

REMARK RECORDS ..........................................................................................................8�

4� COMMAND LINE ......................................................................................................9�

PARAMETER FILE .............................................................................................................9�

VERIFICATION FILE .........................................................................................................9�

REPORT FILE ....................................................................................................................9�

OEM KEY ........................................................................................................................9�

DOCUMENTATION FILE ....................................................................................................9�

PASSWORDS ....................................................................................................................10�

DEBUG / TRACE LOGGING .............................................................................................10�

5� USER INTERFACE ..................................................................................................11�

LEDS ..............................................................................................................................11�

Blinking Yellow ...........................................................................................................11�

Blinking Green ............................................................................................................11�

Solid Green ..................................................................................................................11�

Solid Yellow .................................................................................................................11�

Solid Red .....................................................................................................................12�

LIST BOX ........................................................................................................................13�

BUTTONS.........................................................................................................................16�

Information Button ......................................................................................................16�

Report Button ..............................................................................................................17�

Exit Button ...................................................................................................................17�

6� CONFIGURATION UTILITY ................................................................................18�

VCP STATUS WINDOW ..................................................................................................18�

VCP Status Window - Show ........................................................................................18�

VCP Status Window - Automatically Terminate .........................................................19�

VCP Status Window - Display time .............................................................................19�

COMMUNICATIONS .........................................................................................................19�

RP1210 ........................................................................................................................19�

Inline II – J1939 ..........................................................................................................19�

REPORTS .........................................................................................................................19�

ECM CONTROL..............................................................................................................20�

Reset faults ..................................................................................................................20�

Stop ECM Broadcast (07 engines & later) ..................................................................20�


- 3 - 12/10/14

Set Real Time Clock to PC UTC Time ........................................................................20�

WARNINGS & ERRORS ...................................................................................................21�

Give parameter dependency warnings ........................................................................21�

Suppress a parameter’s warning/error when the OEM’s value matches the ECM’s .21�

GENERAL SETTINGS .......................................................................................................22�

Show parameter description in Verification File ........................................................22�

Write engine information to Verification File .............................................................23�

Write command-line invocation Information to Verification File...............................23�

Enable Write Verification ............................................................................................23�

Write Trace / Debug Information ................................................................................24�

RESTORE DEFAULTS ......................................................................................................24�

7� VEPS OEM PROGRAMMING REFERENCE MANUAL CREATION GUIDE24�

8� DOCUMENT REVISION HISTORY .....................................................................28�


- 4 - 12/10/14

1 Overview The Cummins VCP is an Engine programming tool designed to help OEM’s program

engine on the assembly line. It is designed in accordance with standards for Vehicle

Electronics Programming Stations (VEPS) outlined in SAE J2461 and supports the

associated J2286 compliant parameter and verification files.

The basic operation of any VEPS VCP is to program an ECM according a parameter file,

and pass status information back to the calling program in a verification file. The names

of the parameter and verification files are passed via the command line. This is shown in

Figure 1.

Figure 1 - VEPS Operation

OEM Shop Floor

ProgramCummins VCP

Parameter

File

Verification

File

Command Line


- 5 - 12/10/14

2 VEPS Wiring Connections OEM programming of a Cummins engine over J1587 or J1939 datalinks can be

accomplished either prior to or after the engine is installed the vehicle chassis.

Programming the engine after it is installed in the chassis is recommended; however, if

this is not possible and the engine must be programmed prior to installation in the chassis,

additional precautions need to be taken to limit the potential damage to the Engine

Control Module (ECM).

• When connecting VEPS to the vehicle or ECM datalink, the datalink adaptor

power supply must have a common ground connection with the Battery (-)

connection of the ECM. The datalink adaptor should be powered from the same

power supply as the ECM. If this is not possible and the datalink adaptor has a

separate power supply, the supply must have a common ground connection with

the Battery (-) connection of the ECM.

• The ECM power connection must be made prior to energizing the ECM (Do not

"Hot Plug" the ECM).

• The ECM Battery (-) must be connected to the engine block prior to energizing

the key switch line.

• The key switch line must be de-energized prior to de-energizing the ECM after the

VEPS session. It has been observed, that under certain circumstances, the ECM

is not retaining the value of certain parameters like Low Idle Speed (10030) as

set by VEPS. This phenomenon is caused when battery power is removed from

the ECM before a complete ECM power down has completed after a VEPS

session. To ensure all of the parameter settings are properly saved in the ECM

after the VEPS sessions ends, the user needs to turn the key switch off and

allow the ECM power down completely before battery power is removed from

the ECM.

• ECM must be de-energized prior to disconnecting the power and ground

connections.

�

3 Parameter File The parameter file is the primary interface to the Cummins VCP. It is a text file

containing a list of parameters and values to be programmed in the ECM. The Cummins

VCP supports three SAE J2286 record formats.

• Setup Records

• Parameter Records, and

• Remarks Records


- 6 - 12/10/14

Setup Records

Two setup records are required for VEPS to program an engine ECM.

• Communications Port, and

• Engine Module Type

The communications port setup record is used to identify the port to which the datalink

adapter is connected. Here is an example that specifies COM1 as the port:

S,COMX,1

The engine module type setup record is used to specify the target ECM family for a given

parameter file. That is, this record limits the type of ECMs VEPS will program with a

given parameter file. This is to prevent a parameter file intended for say an ISB to be

loaded into an N14. Here is the format of the module type setup record:

S,MODULE,<Module Name>

Module Names are as follows:

SPECIFIER Engine Product

HDD or 98HDD ISM, ISX, & Signature 600

NCORE ISB, ISC, & ISL

Celect+ N14 & M11

ECHO ISBe

CGAS C8.3G Plus, L10 Plus & B5.9G Plus

DE ISX 02, ISM 02, & ISM 04

ECHO2 ISB 02, ISC 03 & ISL 03

TIER3C2 QSB 07, QSC 04 and QSL 04

EAGLE ISM 07 and ISX 07

ISB07(or EAGLE) ISB 07

ISC07(or EAGLE) ISC 07 or ISL 07

Euro5 ISBe Euro 4.5/5, ISLe Euro 4.5/5

CM2250 ISX 10, ISB, ISC, ISL 10

CM2180A ISL G

CM2220 ISF3.8 Euro3, ISF3.8 Euro4, ISF2.8 HD Euro4, ISF2.8 LD

Euro4

CM2150C ISDe3,ISLe3,ISBe3/ISCe3 EUP

EAGLE ISMe4 SCR

EAGLE GX15 CM871

CUMMINS ISBe3 6.7L CM2150E

ISLe 9.5L CM2150E

QSZ 13L CM2150E

ISB 4.5/ 6.7, Euro5 CM2150E


- 7 - 12/10/14

Euro5 ISL8.9 CM2150E

Euro5 ISF 3.8L CM2220A

NS4 ISF 3.8L CM2220

ISB 3.9L CM2220C



ISFe Euro6 CM2350A

ISBe Euro6 CM2350A

ISL 8.9L CM2350A

ISB 6.7L CM2350A

ISX11.9/15 CM2350A

CUMMINS NS4 ISDe6.7/ ISDe4.5/ ISBe5.9 CM2150E

NS4 ISDe6.7 CM2150E

BSIII 5.9L CM2150E

NS4 ISF 3.8L CM2220C

ISF 2.8L Euro 5 CM2220C

ISX G 11.9L CM2180A

CUMMINS Euro5 ISB 5.9L CM2880

Euro3 ISN 14L CM876

B5.9L, 6.7L, BS IV CM2880


ISX15 Euro4 CM2250

Sao Paulo CM2880

CUMMINS ISZ 13L Euro4 CM2150E

CUMMINS ISLe 8.9L BS3 CM2880A

ISLe 8.9L BS4 CM2880A

ISDe 4.5/6.7L NS4 CM2880A

ISC 8.3L NS4 CM2880A

CM3230 ISV 5.0L CM3230


ISB 6.7L G CM2180A


CUMMINS QSB 4.5/6.7L QSL 9L 2150C

CUMMINS ISF 2.8L Euro5 CM2220C

ISL 9.5L NS5 CM2880A

2017 ISB 6.7L CM2350A

ISB 4.5/6.7L JP16 CM2350A

ISB 4.5/6.7L Euro6 CM2350A

Table 1 - Supported Engine Programs


- 8 - 12/10/14

Parameter Records

Parameter Records indicated which parameters and values to program in the ECM. The

parameter file may contain any number of parameter records, in any order. The format for

parameter records must be as follows:

P,<VEPS name>,<command>,<value>,<comment>

The VEPS names for each parameter are defined in the OEM reference manuals for each

engine. The command field may take on the value of R (read), W (write), or B (both)

although specifying B has the same effect as specifying W. Values must be numeric for

trims, Y or N for features, and ASCII for Dataplate.

Remark Records

Remark records are used to place comments in the parameter file, and are ignored by the

application. The format of a remark record is shown below:

REM <remark>

An example of a parameter file for a 2010 module is shown below.

S,COMX,1

S,MODULE,CUMMINS

P,10000,W,100

P,20011,W,Y

P,21781,W,Y

P,12280,W,4599

P,12310,W,4000

P,12860,W,3000

P,12870,W,2000

P,12479,W,Y

REM P,10300,W,2

REM P,11340,W,5


- 9 - 12/10/14

4 Command Line VEPS parameter and verification files must be passed as command line arguments to the

VCP. The VCP will also generate a report file and documentation file if specified on the

command line

Parameter File

-p <Path and File name for the parameter file>

Use this command line option to specify the name of the parameter file to be used to

program the ECM. If the –p option is omitted, the VCP will look for a file named

ceco600.par located in the Current Working Directory. A valid parameter file is

required for VCP operation.

Verification File

-v <Path and File name for the parameter file>

Use this command line option to specify the name of the verification file to receive the

results of the programming session. If the –v option is omitted, the VCP will create a file

named ceco600.ver in the Common Application Data folder.

Report File

-r <Path and File name for the parameter file>

Use this option to save a comma delimited version of the VEPS Session report in the

specified file. This option is provided as a means to save session reports since the VCP

will not save or redisplay previously generated session reports. Report files can be

viewed later by importing them into most spreadsheets.

OEM Key

-i <Report Identifier>

Use this option to place a unique identifier in the header of the session report. This

option is provided as a means to associate a report with a specific vehicle. Typically the

report identifier is a VIN or customer order number, but it may also be a model number,

or other identifying string..

Documentation File

-d <Path and File Name (oemdoc.csv)>


- 10 - 12/10/14

Use this option as the first step towards generating the OEM Programming Reference

Manual. Adding this option creates a file in the target path containing parameter

information extracted from the ECM. Once this file is created, the user may proceed to

open a copy of the OEM Documentation Generator.doc (Microsoft Word)

document (found in the \Documentation folder) and execute a macro that will “build” a

list of programmable parameters specific to that ECM.

Important items to note:

• For the macro to work, the target file must be named oemdoc.csv

• The macro expects the target file to reside in the same location as the Word

document itself.

• The macro is a one-time destructive process to the Word doc itself. It is

recommended practice to “copy & paste” the original OEM Documentation

Generator.doc to the target folder and work from there. Alternatively, once

generated, the resulting document can be saved to a different name or renamed at

a later time.

Passwords

-pw <VEPS name> <password> …

Use of this option provides the OEM with an alternative means of providing ECM

password information to the VCP (as opposed to a parameter file). A single option can

handle as many password parameters as the VCP (or ECM) supports. The preferred

syntax (following the –pw option) is the VEPS Name followed by the password (repeat

the pattern for additional passwords); all elements separated by whitespace. The

passwords themselves follow the same restrictions as their parameter file counterparts.

Example:

ceco600.exe -p c:\VCP\Cummins\abc.par –pw 00099 MASTER 00061 OEMPWD

…which is equivalent to:

P,00099,W,MASTER P,00061,W,OEMPWD

Note that use of this option does not replace existing password parameter information in

the parameter file. In other words, the presence of the password information in the

parameter file overrides corresponding information provided through this option.

Debug / Trace Logging

-l <Path and File Name>

-la <Path and File Name>


- 11 - 12/10/14

Use of this option enables the Debug / Trace logging feature and writes the collected

information to the target file name. Normally, this option is not necessary for essential

VCP operation. However, using this option can provide additional information to a

Cummins support representative in troubleshooting programmatic issues. The difference

between the –l and –la options is how the VCP treats an existing file name. If the –l

option is used, any existing file and data will be overwritten. Alternatively, the –la option

will append new data to an existing file.

Note: If Write Trace / Debug is checked in the VCP Configuration Utility, this implies

the –l option with file name Debug.xml written to the Common Application Data

folder (i.e. \ProgramData\Cummins\CumminsVCP).

The following example illustrates the use of the command line parameters:

ceco600.exe -p c:\VCP\Cummins\abc.par -v c:\VCP\Cummins\abc.ver –r c:\VCP\Cummins\abc.vrp –i 123456

In the previous example, the VCP (ceco600.exe) will look for the parameter file

(abc.par) in the directory c:\VCP\Cummins. The VCP will write the verification file

(abc.ver) in the directory c:\VCP\Cummins. The VCP will write the report file

(abc.vrp) in the directory c:\VCP\Cummins. The OEM key “123456” will be printed

in header of the VEPS session report.

�

5 User Interface

LEDs

LEDs are used to give a visual status of the programming session. There are 5 ways in

which the LEDs provide status information.

Blinking Yellow

The VCP is attempting to initialize communication with the Engine.

Blinking Green

The VCP has established communication with the ECM and is programming the

specified parameters.

Solid Green

Successful VEPS session. There are no parameter errors.

Solid Yellow

A parameter error has occurred. The VEPS session was successful, but at least

one parameter has an error. If the user clicks on the parameter error icon, then a


- 12 - 12/10/14

message box will appear with a detailed description of the error, as shown in

Figure 5

Solid Red

A fatal error has occurred. The VCP has terminated communications with the

ECM. The cause of the error is displayed in the list box.


- 13 - 12/10/14

List Box

During the VCP session, runtime status messages are displayed in the list box on the main

window. These status messages are used primarily to inform the user of status and for

trouble shooting.

Figure 2 – VCP Status


- 14 - 12/10/14

Once the VCP has finished programming the ECM, the List Box displays the

programmed parameters as shown in Figure 3.

Figure 3 – End of Session

If an error occurred on one of the programmed parameters, the list box displays a yellow

exclamation icon next to the parameter(s) which encountered the error (See Figure 4).

All parameter errors will be shown in the list box first.

If the parameter had an error, the user may double click on the icon or VEPS Name of the

parameter to display a detail error message. This is shown in Figure 5


- 15 - 12/10/14

Figure 4 – Parameter Error

Figure 5 - Error Message Displayed


- 16 - 12/10/14

Buttons

There are three Buttons on the main window; Information Button, Report Button, and

Exit Button. These buttons are disabled until the VEPS session is completed.

Information Button

Pressing the Information Button will display advanced information about the ECM, ECM

Calibration, and VCP Software. This information is often valuable when trouble

shooting the application.

Figure 6 - Information Dialog


- 17 - 12/10/14

Report Button

Pressing the report button will display the VEPS session report in a “print preview “style

window. The report may be printed from this screen, or the user may simply exit to the

main window.

Figure 7 – VEPS Session Report

Exit Button

This button exits the VCP.


- 18 - 12/10/14

6 Configuration Utility A configuration utility program is installed alongside the Cummins VCP software. This

utility allows the user to modify some aspects of the VCP operation. The configuration

utility may be accessed via the Windows Control Panel (if deployed via Windows

Installer) or by double-clicking the vcpconfig.cpl found in the VEPS VCP

installation folder.

Figure 8 - VCP Configuration Utility

VCP Status Window

The User Interface can be assigned various behaviors based on the calling environment,

and how the VCP is integrated with the OEM’s VEPS system.

VCP Status Window - Show

This checkbox determines if the VCP user interface is to be displayed. If the user

prefers to automatically hide the user interface during programming, then this box

should be unchecked.



- 19 - 12/10/14

VCP Status Window - Automatically Terminate

This checkbox should be checked if the user desires that the user interface

automatically terminate at the end of the VEPS session, instead of waiting for the

user to press the Exit button. This option may be used to return control to the

calling program without any additional user interaction.


VCP Status Window - Display time

This value is only valid when the user has configured the VCP to automatically

terminate. This value is the amount of time, in seconds, that the user interface

will stay active after the VCP session has ended.

The default value is 5 seconds.

Communications

RP1210

If one or more RP1210 drivers have been installed on the system, the VCP will

detect it and enable the RP1210 radio button. If RP1210 is selected, the user must

specify which Vendor’s RP1210 driver to use (if there is more than one), and the

protocol and device which is being used. When using RP1210, the COM port

specified in the parameter file is ignored, the correct comport must be selected in

the Device combo box.

Inline II – J1939

When specifying the Inline II, the VCP will try to communicate with the engine

using the protocol that has been selected by the J1708 / J1939 radio buttons. If

communications cannot be established with the chosen protocol, the VCP will

attempt the alternate protocol before failing. Choosing the protocol that is

currently in use will decrease the time needed for the VCP to establish

communication with the Engine. The COM port is selected in the VEPS

parameter file. See Section 3.

There is no default preference for communications, although first time installation of the

VCP will have RP1210 checked with the first available vendor & options selected

(assuming a single RP1210 device is available). If the VCP is upgraded (or uninstalled),

the Communication settings will be remembered.

Reports

VEPS session reports can be configured to print automatically after the VCP completes

programming. If this option is selected, the user can opt to print to the operating system’s

default printer, or print via the print dialog. The advantage of choosing a default printer

is one of automatically printing reports without any additional user interaction. Choosing


- 20 - 12/10/14

to print via a print dialog will allow a user to either specify a printer or cancel said action.


ECM Control

Reset faults

This combo box has three options for the user to select:

Reset Faults Option ECM Function

None No operation is performed on the ECM.

Erase Inactive Faults After all parameters are programmed, the

VCP will attempt to erase all Inactive

Faults in the ECM.

Reset All Faults – 07 & later engines An option available only to Cummins

2007 engines & later. After all parameters

are programmed, the VCP will attempt to

erase all Cummins and OBD related

faults.

Table 2 – Reset Faults Options

This option is defaulted as “None”.

Stop ECM Broadcast (07 engines & later)

This setting allows OEMs to program Cummins 2007 and later engines

with/without reduced ECM broadcast traffic.

Enabling this feature will request the ECM to stop broadcast to gain increased

performance by reducing bus traffic. Once the VCP has successfully programmed

the ECM, it will request the ECM to resume broadcast. This is the preferred

behavior of the VCP.

However, if the OEM suspects leaving this feature enabled is causing issues, they

may instead opt to disable (uncheck) this feature, thus allowing the ECM to

continue responding to other devices as well.


Set Real Time Clock to PC UTC Time

This setting allows OEMs to set Real Time Clock to the host PC’s UTC time.

This feature is engine-specific and typically only supported in Euro 4/4.5/5

products.



- 21 - 12/10/14

Measurement Units

• If English is selected, parameter values will be interpreted using English units.

• If Metric is selected, parameter values will be interpreted using Metric units.

English is the default selection.

Warnings & Errors

Give parameter dependency warnings

Many of the dependencies that are enforced by the VCP can be disabled. These

warnings are intended to inform the user that a parameter will have no effect due

to the state of a related parameter. Cummins recommends that these dependency

warnings be left on to give feedback on potential problems with the parameter set

which is being programmed into the ECM. If this checkbox is unchecked, the

VCP will still enforce dependencies which must be enforced to maintain the

integrity of the ECM’s data.

A pop up warning message will appear when unchecking “Give parameter

dependency warnings” option in configuration utility.

Example 1. Feature enabled. Feature-parameter errors are recorded in the

verification file.

… S,PERROR,T,




…

Example 2. Feature disabled. Feature-parameter errors are NOT recorded in the

verification file.

… S,PERROR,F,




…


Suppress a parameter’s warning/error when the OEM’s value matches the ECM’s

If this checkbox is checked, the VCP will perform a parameter value comparison

between the OEM requested value and the current value in the ECM. If the


- 22 - 12/10/14

parameter values match, then no write operation will be performed and,

additionally, any potential warning/error (if exists) will be suppressed.

There are both advantages and disadvantages to enabling this checkbox:

Advantages

• Minimizes the number of warnings/errors reported.

• Serves as a filter mechanism for reporting. Limits warning/error reporting

to only value-changing parameters.

Disadvantages

• Introduces inconsistent behavior to VCP error/warning detection and

reporting.

• Hides dependency warnings that may provide otherwise valuable

information towards correctly configuring the engine. For example, the

OEM may be attempting to adjust an effectively disabled feature, but since

the OEM value matched the value already in the ECM, such a dependency

warning was suppressed.

• The engine’s calibrated (i.e. default) value may not always represent a

valid state in the ECM. Enabling the checkbox might prevent the VCP

from reporting such issues.

Alternatively, unchecking this checkbox would ensure both the Cummins and/or

OEM values represent a valid setting in the ECM after a programming session.

Unchecking this checkbox is highly recommended.


General Settings

Show parameter description in Verification File

If this checkbox is checked, then all parameters listed in the SAE J2286

Verification File (.ver) will have their corresponding parameter description

appended. The parameter description will be the last value in the parameter

record, and it will be delimited by a comma (i.e. a 5th optional field).

Example 1. Parameter feature is enabled. Parameter description is written in

verification file.

… P,0000,0000,5.73, Rear Axle Ratio

P,0007,0000,520.00, Tire Revolutions per Mile

P,0005,0002,0.74, Transmission Top Gear Ratio

…


- 23 - 12/10/14

Example 2. Parameter feature is disabled. Parameter description is NOT written

in verification file.

… P,0000,0000,5.73

P,0007,0000,520.00

P,0005,0002,0.74

…


Write engine information to Verification File

The VCP will always read the Engine Serial Number from the engine. This

information is displayed on the user interface. If the user wishes to have this

information written to the verification file, then this checkbox should be checked.

Example demonstrating engine information written to the verification file:

… P,5001,0000,ISX12/15 CM2350A, Engine Type

P,5003,0000,EF10044.16, ECM Code

P,5005,0000,450.00, Horsepower

P,5007,0000,12170, SC Option

P,5009,0000,1870, DO Option

P,5010,0000,9.30.0.6, Calibration Version

…


Write command-line invocation Information to Verification File

This setting adds the program invocation information to the third line of the

verification file. If this is disabled, the third line of the verification file will be a

blank line.


Enable Write Verification

To verify that parameters were correctly written to the ECM, at the end of the

VCP session, the program will complete a second read of all parameters from the

ECM. The VCP program will then compare these values with the values in the

parameter file to verify that the values are correct. The process of reading the

ECM values the second time adds time to the VCP session.



- 24 - 12/10/14

Write Trace / Debug Information

This setting allows both the VCP and the supporting communication library

Common Components to log information to their respective files which can later

be used for debugging. This setting should only be set if directed by the Cummins

VEPS team.

Notes:

• The default location for these files is in the Common Application Data

folder.

• The default filename for VCP debugging is Debug.xml

• The default filename(s) for logging Common Components errors is

CError.xml & CError.txt (deprecated).

• See Command Line topic to learn about naming and redirecting the debug

file output to a user defined location.


Restore Defaults

Clicking this button will automatically change the VCP settings back to their defaults.

Note that the user must click the Ok button for these changes to take effect.

7 VEPS OEM Programming Reference Manual Creation

Guide

The following 3 conditions are assumed:

-Cummins VCP has been configured correctly and can successfully program the module

for which a programming reference manual will be generated

-PC has Microsoft© Word installed

-This guide is based on Microsoft© Word 2007

1. Create a desktop shortcut to the file: C:\Program Files\Cummins\VEPS VCP 8\ceco600.exe

2. Right-click on the shortcut and select “Properties”. Click on the “Shortcut” tab.

3. Append the option “-p pathtoparfile\yourfile.par -d oemdoc.csv” to the end of the

existing Target textbox. The “oemdoc.csv” file may be written to any directory, but must

be named “oemdoc.csv”.

Example command line:

"C:\Program Files\Cummins\VEPS VCP 8\ceco600.exe" -p

C:\ProgramData\temp\test.par -d C:\ProgramData\temp\oemdoc.csv


- 25 - 12/10/14

4. The .par file in the command line used to generate the programming reference manual

should have the correct Specifier (i.e. EAGLE, CUMMINS, …) in the setup records as

per your product. Parameter records are not required in the .par file to create OEM

documentation, but are allowed.

5. Connect ECM to the VEPS PC using a datalink adaptor.

6. Run VEPS by double-clicking the desktop shortcut.

7. Once the VEPS session is completed, close the VEPS window. It is important to close

the VEPS window before proceeding to the next step.


- 26 - 12/10/14

8. Find the newly created oemdoc.csv file in the location you specified in the command line.

In this example, it is: C:\ProgramData\temp\oemdoc.csv.

9. Copy the file OEM Documentation Generator.doc to the same directory as the

oemdoc.csv file. The file OEM Documentation Generator.doc is located (by

default) in the directory: C:\Program Files\Cummins\VEP VCP 8\Documentation\

10. Launch OEM Documentation.doc. The document will open in Microsoft© Word.

11. Macros must be Enabled in Microsoft© Word to use the documentation generator. If a

Security Warning is displayed, select Options, then “Enable this content”

12. Select the Add-Ins tab.


- 27 - 12/10/14

13. Click on the “Create OEM Documentation” button.

14. The Program Reference Manual will be generated. Save the manual to the name you

desire.


- 28 - 12/10/14

8 Document Revision History

Revision

Number Date Changed By Summary of Changes

2 11/17/2014 Stephen Burgin Corrected an omission to the password

command-line usage.



• ISF 2.8L Euro5 CM2220C

• ISL 9.5L NS5 CM2880A

• 2017 ISB 6.7L CM2350A

• ISB 4.5/6.7L JP16 CM2350A

• ISB 4.5/6.7L Euro6

CM2350A

Re-organized & updated the Configuration

Utility section to reflect changes made in the

v8.1.4 release.

1 8/28/2014 Stephen Burgin Changed module specifier of “ISZ 13L Euro4

CM2150E” from EAGLE to CUMMINS.



• QSB 4.5/6.7L QSL 9L 2150C

Removed “Rio CM2350A” from the -

Supported Engine Programs table.

0 4/31/2014 Stephen Burgin For a detailed list of changes to the VCP, see

the accompanying Release Notice document.

VCP User Guide - gce.cummins.com€¦ · isx g 11.9l cm2180a cummins euro5 isb 5.9l cm2880 euro3...

Documents

Transcript of VCP User Guide - gce.cummins.com€¦ · isx g 11.9l cm2180a cummins euro5 isb 5.9l cm2880 euro3...