VEHICLE ELECTRONICS PROGRAMMING STATION. (VEPS) VCP User s Guide. v8.2.0 Arun Nagari

Transcription

1 VEHICLE ELECTRONICS PROGRAMMING STATION (VEPS) VCP User s Guide v8.2.0 Arun Nagari

2 1 OVERVIEW VEPS WIRING CONNECTIONS PARAMETER FILE...5 SETUP RECORDS...6 PARAMETER RECORDS...8 REMARK RECORDS COMMAND LINE...10 PARAMETER FILE...10 VERIFICATION FILE...10 REPORT FILE...10 OEM KEY...10 DOCUMENTATION FILE...10 PASSWORDS USER INTERFACE...12 LEDS...12 Blinking Yellow...12 Blinking Green...12 Solid Green...12 Solid Yellow...12 Solid Red...12 LIST BOX...13 BUTTONS...16 Information Button...16 Report Button...17 Exit Button CONFIGURATION UTILITY...18 VCP STATUS WINDOW...18 VCP Status Window - Show...19 VCP Status Window - Automatically Terminate...19 VCP Status Window - Display time...19 COMMUNICATIONS...19 RP Inline II J REPORTS...20 ECM CONTROL...20 Reset faults...20 Stop ECM Broadcast (07 engines & later)...20 Set Real Time Clock to PC UTC Time /14/17

3 WARNINGS & ERRORS...21 Give parameter dependency warnings...21 Suppress a parameter s warning/error when the OEM s value matches the ECM s.22 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 RESTORE DEFAULTS VEPS OEM PROGRAMMING REFERENCE MANUAL CREATION GUIDE24 8 DOCUMENT REVISION HISTORY /14/17

4 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. Parameter File OEM Shop Floor Program Command Line Cummins VCP Verification File Figure 1 - VEPS Operation /14/17

5 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 /14/17

6 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: Module Names are as follows: S,MODULE,<Module Name> 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 /14/17

7 CUMMINS CUMMINS CUMMINS CUMMINS CM3230 CUMMINS CUMMINS CUMMINS CUMMINS CUMMINS CUMMINS Euro5 ISL8.9 CM2150E Euro5 ISF 3.8L CM2220A NS4 ISF 3.8L CM2220 ISB 3.9L CM2220C Euro 5 ISF 2.8L CM2220C Euro 5 ISF 3.8L CM2220C ISFe Euro6 CM2350A ISBe Euro6 CM2350A ISL 8.9L CM2350A ISB 6.7L CM2350A ISX11.9/15 CM2350A 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 Euro5 ISB 5.9L CM2880 Euro3 ISN 14L CM876 B5.9L, 6.7L, BS IV CM2880 Euro 5 ISF 3.8L CM2220C ISX15 Euro4 CM2250 Sao Paulo CM2880 ISZ 13L Euro4 CM2150E ISLe 8.9L BS3 CM2880A ISLe 8.9L BS4 CM2880A ISDe 4.5/6.7L NS4 CM2880A ISC 8.3L NS4 CM2880A ISV 5.0L CM3230 ISF 3.8L Euro6 CM2350A ISB 6.7L G CM2180A ISF 8.9L Euro6 CM2350A 2017 ISX 15L CM2350A QSB 4.5/6.7L QSL 9L 2150C 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 ISB 6.7L Euro6 OBD-C CM2350A ISB 4.5L Euro6 OBD-C CM2350A ISF 2.8L Conama P7/Euro5 CM2220C ISF 2.8L Conama L6/Euro5 CM2220C QSB7/ QSL9.3 CM /14/17

8 CUMMINS ISB6.7G CM2380 ISL8.9G CM2380 ISX11.9G CM2380 ISB5.9 CM2880 ISD4.5/6.7 CM2880 ISF2.8/3.8/4.5 CM2220 QSF2.8 CM2880 F104/F108/QSF3.8 CM2880 F112 ISB5.9 CM2880 ISFe3.8L Euro VI OBD-C CM2350A X15e6 Euro VI OBDA CM2350 X15e6 Euro VI OBDC CM2350 Table 1 - Supported Engine Programs 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 /14/17

9 REM P,10300,W,2 REM P,11340,W, /14/17

10 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)> /14/17

11 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 MASTER 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 /14/17

12 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 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 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 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 /14/17

13 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/17

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 /14/17

15 Figure 4 Parameter Error Figure 5 - Error Message Displayed /14/17

16 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 /14/17

17 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. Exit Button This button exits the VCP. Figure 7 VEPS Session Report /14/17

18 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 /14/17

19 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. 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 /14/17

20 (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 to print via a print dialog will allow a user to either specify a printer or cancel said action. This checkbox is unchecked by default. ECM Control Reset faults This combo box has three options for the user to select: Reset Faults Option None Erase Inactive Faults ECM Function No operation is performed on the ECM. 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. This option is defaulted as None. Table 2 Reset Faults Options 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. This checkbox is checked by default /14/17

21 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. This checkbox is unchecked by default. 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, P,0013,0000,N, Cruise Control Enable P,0060,0000,1.00, Cruise Control Lower Droop P,0061,0000,0.00, Cruise Control Upper Droop /14/17

22 This checkbox is checked by default. 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 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. This checkbox is unchecked by default. 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 5 th optional field) /14/17

23 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 Example 2. Parameter feature is disabled. Parameter description is NOT written in verification file. P,0000,0000,5.73 P,0007,0000, P,0005,0002,0.74 This checkbox is checked by default. 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,EF , ECM Code P,5005,0000,450.00, Horsepower P,5007,0000,12170, SC Option P,5009,0000,1870, DO Option P,5010,0000, , Calibration Version This checkbox is checked by default. 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. This checkbox is unchecked by default. 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 /14/17

24 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. This checkbox is checked by default. 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 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 /14/17

25 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 /14/17

26 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 /14/17

27 13. Click on the Create OEM Documentation button. 14. The Program Reference Manual will be generated. Save the manual to the name you desire /14/17

28 8 Document Revision History Revision Number Date Changed By Summary of Changes 6 19/04/2017 Arun Nagari Added the following products to the - Supported Engine Programs table: ISFe3.8L Euro VI OBD-C CM2350A X15e6 Euro VI OBDA CM2350 X15e6 Euro OBDC CM /11/2016 Arun Nagari Added the following products to the - Supported Engine Programs table: QSBB7/QSL9.9 CM2880 ISB6.7G CM2380 ISL8.9G CM2380 ISX11.9G CM2380 ISB5.9 CM2880 ISD4.5/6.7 CM2880 ISF2.8/3.8/4.5 CM2220 QSF2.8 CM2880 F104/F108/QSF3.8 CM2880 F112 ISB5.9 CM /04/2015 Richa Nirbhya Added the following products to the Supported Engine Programs table: ISB 6.7L Euro6 OBD-C CM2350A ISB 4.5L Euro6 OBD-C CM2350A ISF 2.8L P7/Euro5 CM2220C ISF 2.8L L6/Euro5 CM2220C 3 12/19/2014 Stephen Burgin Added the following product to the - Supported Engine Programs table: 2017 ISX 15L CM2350A 2 11/17/2014 Stephen Burgin Corrected an omission to the password command-line usage /14/17

29 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. Added the following product(s) to the - Supported Engine Programs table: 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 /14/17