DPA5 User Manual
DPA5 User Manual
DPA5 User Manual
Permission is granted to copy any or all portions of this manual, provided that such copies are for use with the DPA
product and that 2010-2014 Dearborn Group, Inc., (herein referred to as Dearborn Group, DG Technologies, or
DG), remains on all copies.
The accompanying software, provided for use with the DPA 5, is also copyrighted. Permission is granted to copy this
software for back-up purposes only.
IMPORTANT
To ensure your success with this product, it is essential that you read this document carefully before using the hardware.
Damage caused by misuse of the hardware is not covered under product warranty.
When using this manual, please remember the following:
This manual may be changed, in whole or in part, without notice.
DG assumes no responsibility for any damage resulting from the use of this hardware and software.
Specifications presented herein are provided for illustration purposes only and may not accurately represent the
latest revisions of hardware, software or cabling.
No license is granted, by implication or otherwise, for any patents or other rights of DG or of any third party.
DPA and the DG logo are registered trademarks of Dearborn Group, Inc. Other products that may be referenced in
this manual are trademarks of their respective manufacturers.
The DPA Product line and the products supporting the DPA have been awarded the following U.S. Patents:
DG Technologies
33604 West Eight Mile Road
Farmington Hills, MI 48335
Phone (248) 888-2000
Fax (248) 888-9977
www.dgtech.com
[email protected]
[email protected]
Table of Contents
TABLE OF CONTENTS ............................................................................................................................................................. 3
1. SAFETY FIRST ........................................................................................................................................................................ 6
2. INTRODUCING THE DPA 5 ........................................................................................................................................ 7
2.1. RP1210 OEM AND COMPONENT SOFTWARE COMPATIBILITY ................................................................................................................ 8
2.1. J2534 OEM AND COMPONENT SOFTWARE COMPATIBILITY ................................................................................................................... 8
2.2. STANDARDS AND PROTOCOLS SUPPORTED ........................................................................................................................................... 9
2.3. SYSTEM REQUIREMENTS ................................................................................................................................................................. 10
3. GETTING STARTED WITH THE DPA .................................................................................................................. 11
3.1. DRIVER INSTALLATION .................................................................................................................................................................... 11
3.2. WINDOWS SECURITY SCREEN .......................................................................................................................................................... 12
3.3. CONNECT USB CABLE TO THE DPA AND THEN TO PC .......................................................................................................................... 12
3.1. CONNECT VEHICLE-SIDE CABLE TO THE DPA ...................................................................................................................................... 12
3.2. CONNECT VEHICLE-SIDE CABLE TO THE VEHICLE .................................................................................................................................. 12
3.3. FINALIZE PC INSTALL...................................................................................................................................................................... 13
3.4. AUTOMATIC FIRMWARE UPDATE ..................................................................................................................................................... 13
4. TROUBLESHOOTING / VALIDATING YOUR DPA WITH ADAPTER VALIDATION TOOL
(AVT) ................................................................................................................................................................................................... 14
4.1. ADAPTER VALIDATION TOOL STARTUP PROGRAM ............................................................................................................................ 14
4.2. RULE OF THUMB FOR SELECTING A VEHICLE PROTOCOL FOR TESTING ...................................................................................................... 15
4.3. ADAPTER VALIDATION TOOL FOR HEAVY AND MEDIUM-DUTY VEHICLES, AVT (MD/HD) .......................................................................... 16
4.4. ADAPTER VALIDATION TOOL FOR LIGHT AND MEDIUM-DUTY VEHICLES, AVT (OBDII) .............................................................................. 21
5. SETTING UP YOUR RP1210-COMPLIANT OEM DIAGNOSTIC APPLICATIONS .................. 24
5.1. NOTES ON SELECTING AN RP1210 COMPLIANT ADAPTER..................................................................................................................... 24
5.2. CONFIGURING APPLICATIONS TO USE THE DPA 5 ................................................................................................................................ 24
5.3. ALLISON DOC .............................................................................................................................................................................. 25
5.4. BENDIX ABS DIAGNOSTICS ............................................................................................................................................................. 25
5.5. CATERPILLAR ELECTRONIC TECHNICIAN (CAT ET) ................................................................................................................................ 25
5.6. CUMMINS INSITE......................................................................................................................................................................... 26
5.7. CUMMINS POWERSPEC (5.5 OR NEWER) .......................................................................................................................................... 26
5.8. DETROIT DIESEL DIAGNOSTIC LINK V7 .............................................................................................................................................. 26
5.9. DETROIT DIESEL DIAGNOSTIC LINK VERSION 6.47 ............................................................................................................................... 27
5.10. DANA DIAGNOSTIC TOOL 2.X.X.................................................................................................................................................... 27
5.11. EATON SERVICERANGER 3.X........................................................................................................................................................ 27
5.12. FREIGHTLINER SERVICELINK (INCLUDING CASCADIA MODEL DUAL CAN CHANNELS) ........................................................................... 27
5.13. INTERNATIONAL TRUCK AND ENGINE............................................................................................................................................. 28
5.14. MERITOR-WABCO TOOLBOX ..................................................................................................................................................... 28
5.15. VOLVO/MACK VCADS PRO ....................................................................................................................................................... 29
5.16. VOLVO/MACK PREMIUM TECH TOOL (PTT) VERSION 2.X ............................................................................................................. 30
5.17. VOLVO/MACK PREMIUM TECH TOOL (PTT) VERSION 1.X ............................................................................................................. 30
6. SETTING UP YOUR J2534-COMPLIANT OEM APPLICATIONS AND DPA 5 ....................... 31
7. EXPLAINING MULTI-APPLICATION AND SINGLE-APPLICATION DRIVERS ............................ 32
7.1. WHY TWO OEM APPLICATIONS MAY NOT WORK WHEN SHARING THE DPA ........................................................................................... 32
8. RP1210 OPTIONS PROGRAM ................................................................................................................................ 33
8.1. RP1210 OPTIONS NOTES; RP1210 DPA DRIVER SETS ...................................................................................................... 33
8.2. SET OPTIONS FOR DPA DEVICE/API ..................................................................................................................................... 34
1. Safety First
It is essential that the user read this document carefully before using the hardware.
The DPA devices are to be used by those trained in the troubleshooting and diagnostics of light-duty through heavy-duty
vehicles. The user is assumed to have a very good understanding of the electronic systems contained on the vehicles
and the potential hazards related to working in a shop-floor environment.
DG understands that there are numerous safety hazards that cannot be foreseen, so we recommend that the user read
and follow all safety messages in this manual, on all of your shop equipment, from your vehicle manuals, as well as
internal shop documents and operating procedures.
Always block drive, steer, and trailer wheels both front and back when testing.
Use extreme caution when working around electricity. When diagnosing any vehicle, there is the risk of electric
shock both from battery-level voltage, vehicle voltages, and from building voltage.
Do not smoke or allow sparks or open flames near any part of the vehicle fueling system or vehicle batteries.
Always work in an adequately ventilated area, and route vehicle exhaust outdoors.
Do not use this product in an environment where fuel, fuel vapor, exhaust fumes, or other potentially hazardous
liquids, solids, or gas/vapors could collect and/or possibly ignite, such as in an unventilated area or other confined
space, including below-ground areas.
If you are attempting to use a DPA 5 with a 2013 or newer Volvo/Mack chassis with a Volvo engine and an SAE J1969
(OBDII) connector, please see Addendum I for more information on this specific vehicle platform. This addendum
addresses the specific requirements for using the DPA 5 product on this vehicle and also covers troubleshooting and
specific cables that are required.
DPA 5 with Dual CAN Channels DPA 5 with Quad CAN Channels
with Bluetooth Communications No Bluetooth Communications
The DPA 5 Dual-CAN / Bluetooth device is the most commonly sold DG DPA 5 product. This manual is geared more to
this product; however, the concepts also apply to the DPA 5 Quad-CAN. Distinctions will be made as appropriate.
Any application claiming RP1210A, RP1210B, or RP1210C compliance should work if the application and adapter
both support the same protocol(s) and operating system(s).
The DPA 5 has been validated against the following OEM and component applications:
All J2534 reprogramming and diagnostic software packages that are J2534-1 and J2534-2 compliant and use a
protocol supported by the DPA 5 should work as long as the operating system is supported by the application.
Note that not all OEMs have released J2534-2 compliant software.
Operating Systems
o Windows Vista 32-bit and 64-bit Versions
o Windows 7 32-bit and 64-bit Versions
o Windows 8 32-bit and 64-bit Versions
TMC RP1210C, TMC RP1210B, TMC RP1210A
SAE J2534-1
CE Certification
Vehicle Electronic Programming Station (VEPS) J2214/J2461
J1939
o J1939@250k Standard J1939
o J1939@500k Per J1939/14
o Automatic Baud Rate Detection Capable
CAN (ISO11898)
o Automatic Baud Rate Detection Capable
CAN@500k/J2284/GMLAN
o The IESCAN protocol name is also CAN@500k.
o Automatic Baud Rate Detection Capable
J1708/J1587
J1850 GM (Class 2) J1850VPW
o The following protocol names are supported: J1850, J1850_416K, J1850_104K. The send and read
message format was changed from RP1210A to RP1210B for this protocol. We support both formats.
The J1850 protocol name indicates the RP1210A format for sending and reading data. The
J1850_416K, J1850_104K names indicate the RP1210B format.
ISO9141-2
ISO14230 (KWP2000)
2.2.3. RP1210_ClientConnect() Modifiers Supported (CAN Automatic Baud Rate Detection, Channel)
The DPA 5 supports automatic CAN baud rate detection as required by RP1210C in preparation for J1939
moving from a speed of 250k to 500k. To support this, the DPA 5 API supports this through an application issuing
a modifier to the RP1210_ClientConnect() function call (for any CAN protocol):
o RP1210_ClientConnect( J1939:Baud=Auto)
o RP1210_ClientConnect( CAN:Baud=Auto)
o RP1210_ClientConnect( ISO15765:Baud=Auto)
o RP1210_ClientConnect( J2284:Baud=Auto)
If the application wants to know what speed they connected at, they can issue the command:
o RP1210_SendCommand(RP1210_Get_Protocol_Connection_Speed)
The DPA 5 supports 2 (Dual CAN) or 4 (Quad CAN) CAN (J1939/ISO15765/J2284) channels. To access these
channels, the DPA 5 API supports this through an application issuing a modifier to the RP1210_ClientConnect()
function call:
o RP1210_ClientConnect( J1939:Channel=X)
These two modifiers can be combined. For example, J1939:Baud=Auto;Channel=2.
Item Requirement
PC IBM-Compatible
Processor 1GHz or Faster
RAM 256MB (512MB Preferred)
USB Port USB Version 1.1 or Higher
Operating System Windows Vista (32-bit or 64-bit)
Windows 7 (32-bit or 64-bit)
Windows 8 (32-bit or 64-bit)
Attention!
Install DPA drivers from CD before connecting DPA to your PC.
If you run into problems installing the drivers or the DPA, please
do not hesitate to contact technical support at (248) 888-2000.
Attention!
The DPA drivers provided on the installation CD are installed by inserting the disc into your PCs CD-ROM drive.
The latest drivers and firmware are always available at www.dgtech.com/download.php. If you have any
questions about the install, please contact our technical support staff.
After the drivers are installed, restart your computer. While rebooting, continue following the next instructions.
WARNING!
Connect the vehicle-side cable to your DPA. Do not connect to vehicle first! Pins 6 and 8 on the DB25 connector
are power and ground and can arc if not careful, potentially blowing a fuse on the vehicle!
That screen will be followed by this screen. Your DPA 5 is now ready for use.
After you have finished installing the Windows device drivers you can begin using your DPA. If the Automatic
Firmware Update option is on (by default, it is), every time you connect to the DPA, the drivers check to see if a
newer version of firmware is available on the hard drive. If a newer version is available the user will be prompted
(see Figure 5.1) to upgrade to that version. Press Yes and the upgrade process begins automatically. After the
firmware update, restart your application.
DO NOT DISCONNECT POWER FROM THE DPA 5 DURING A FIRMWARE UPDATE!!! ALLOW THE UPDATE
TO FINISH OR YOU WILL HAVE TO MANUALLY UPDATE THE FIRMWARE!
The following is the dialog box that will be displayed if out-of-date firmware is detected. Press Yes to update.
Automatic Firmware Update is an option that is most likely turned On in your installation. Some customers
receive special drivers where this is not the case, however this paragraph assumes that this option is turned on,
and set to a value of 1. To learn more about this option, see the chapter entitled Modifying DPA Settings
RP1210 Options Program.
Most DPA technical support calls about OEM applications not working come from users who have not configured
that OEM application to use the DPA, or who have selected the incorrect protocol.
After you have followed the instructions to install the DPA drivers, connect the DPA to the vehicle and ensure the Power
LED is on. Then connect it to the PC and listen for the familiar da-ding USB device found sound. If you cannot hear this
sound, the PC cannot communicate with the DPA and you will not be able to get AVT to be successful. Try another USB
port until you hear that sound.
If you plug in a DPA (or any other USB device) and get the New Hardware Found wizard, do not click
Cancel. Go through the wizard completely! IF YOU CLICK Cancel, THE DPA WILL NOT WORK!
The light and medium-duty world is different in the standards used to write software than the medium and heavy-duty
world. For the most part (other than the new Volvo platform), it is based on the diagnostics connector. Due to the
difference, DG has changed the startup of the Adapter Validation Tool (AVT) application. Now, when you click AVT
on the desktop or from the start menu, a screen will be displayed asking the user what version of AVT to run.
Click on the MD/HD truck button if you have a 6 or 9-pin Deutsch connector. This is most typically found on
medium and heavy-duty vehicles and J1708/J1587 and J1939 are the most common protocols.
Click on the OBDII car button if you have an OBDII connector. This is most typically found on light and
medium-duty vehicles and CAN/ISO15765, J1850, ISO9141, and ISO14230 are the most common protocols.
You can use either program for the 2013 (or newer) Volvo chassis with Volvo engine that has the OBDII
connector. See Appendix I for more information on testing this platform using the MD/HD version of AVT.
OBDII Connector
AVT (OBDII) allows the user to select OBDII as a protocol and AVT will cycle through all OBDII
protocols to see what protocol the vehicle supports.
The DPA 5 supports all OBDII protocols except the J1850PWM protocol. This protocol was
prominent on Ford vehicles prior to 2005 when Ford switched to ISO15765.
Then click the Run Test button. Depending on the results of the test, both the RP1210 Status Window and
RP1210 Data Message Window will turn green (pass) or red (fail).
If the RP1210 Status Window turns red, then there is a problem causing the PC not to communicate with the
DPA. This may be something as simple as having power to the DPA or a USB issue. Disconnect the DPA from
the vehicle and PC; then reconnect them, this time connecting to another USB port on the PC.
If the RP1210 Status Window turns green and the RP1210 Data Message Window turns red, then the PC is
seeing the DPA, but not seeing messages from the data bus. Check the vehicle ignition switch and vehicle to
adapter cabling. Disconnect the DPA from the vehicle and PC; then reconnect them.
If you see data in the RP1210 Data Message Window, your DPA is installed and functioning properly! Refer to
the chapter on how to configure your OEM application to use the DPA.
Read the Test Results Discussion and Next Steps screen carefully and follow those directions to help diagnose
where the issue may be. If, after reading and following those instructions, you cannot get the DPA working,
please contact DG technical support.
Many DPA technical support calls could have been avoided by following the instructions on the Test
Results Discussion and Next Steps screen.
4.3.2. Good Connection (PC to DPA), Good Read of Data (DPA to Vehicle) Green/Green
The above screen snapshots show the PC successfully connecting to the DPA (RP1210 Status Window) and the
successful reading of data bus data (RP1210 Data Message Window) from the J1939 data bus.
A Green/Green result indicates the DPA is working perfectly and is seeing data on the data bus. The
area to work on is configuring the OEM application to use the DPA (see Chapter 7).
4.3.3. Good Connection (PC to DPA), Not Able To Read Data (DPA to Vehicle) Green/Red
The above screen snapshots show the PC successfully connecting to the DPA (RP1210 Status Window) but AVT
is not able to read data bus data (RP1210 Data Message Window) from the data bus selected (J1939).
A Green/Red result indicates the DPA is working perfectly, but it is not seeing data on the data bus that
was selected. Choose another protocol and check that the ignition switch is on.
4.3.4. Bad Connection (PC to DPA), Not Able To Read Data (DPA to Vehicle) Red/Red
The above screen snapshots show the PC not connecting to the DPA (RP1210 Status Window).
A Red/Red result indicates the PC is not seeing the DPA. Unplug DPA from vehicle and PC and
reconnect to both using a different USB port. Ensure that you hear the da-ding USB Device Found
sound. If you cannot hear the sound, reboot the PC and run AVT again.
If you have installed the DPA drivers and can get AVT to a Green/Green outcome, you should be able to
configure your diagnostic application to use the DPA. If your diagnostic application does not display DG DPA 5
Dual-CAN, USB in their VDA selection dialog box, this could indicate one of three things:
1. The application is not RP1210 compliant and does not work with the DPA.
a. Some applications require a specific, proprietary adapter.
2. Application is RP1210 compliant, but DPA does not support the protocol needed.
When the AVT software is launched, you will be told if a problem exists in the main RP121032 INI file. If you wish
to fix this issue (very highly recommended), press the Fix/Change RP121032.INI File button on the main screen.
If your PC is running Windows Vista or Windows 7, you will be prompted for administrator privileges. The
following is the dialog box that will appear when AVT is launched and a problem is found in the main RP121032
INI file.
When you press the Fix/Change RP121032.INI File button, AVT will bring up a separate program called
Fix INI that will allow you to view and fix the RP121032 INI file if there are errors detected. You can also
change the VDA that appears first in the list of the OEM diagnostic software applications.
In the example below, a bad INI file was detected (depicted by a yellow background). Note the multiple
commas and spaces between entries.
Click the Make Changes button and the INI file problem will be corrected. If you wish to make a specific
adapter first in the list, you can select that vendor in the Vendor to Make First in List before pressing the
Make Changes button.
The next picture shows the dialog box indicating that the INI file was fixed.
With the J1939 data bus moving to 500k, there is a lot of RP1210 and J1939 committee focus on VDA vendors
doing J1939 automatic baud detection to detect either a 250k or 500k J1939 data bus without creating issues.
There is also a growing need for advanced testing on vehicles that have a second CAN data bus.
The DPA 5 API Supports the following commonly used RP1210_ClientConnect() modifications:
Protocol:Baud=Auto
Protocol:Baud=XXX
Protocol:Channel=X
Protocol:Baud=Auto;Channel=X
Protocol:Baud=XXX;Channel=X
Pressing the Advanced Test button brings up the dialog box shown below.
Vendor, Device and Protocol fields are the same as described in normal testing above.
The Baud Rate drop down list box allows the user to select one of the supported protocol speeds for the selected
protocol. The entries in this list box come from the VDA vendors INI file. Click the Use Baud Rate checkbox to
activate a Protocol:Baud=XXX connection. If both the Use Baud Rate and Use Channel checkboxes are
checked, then AVT will initiate a Protocol:Baud=XXX;Channel=X connection.
The Channel drop down list box allows the user to select one of the supported channels for the selected device.
The entries in this list box come from the VDA vendors INI file. Click the Use Channel checkbox to activate a
Protocol:Channel=X connection. If both the Use Baud Rate and Use Channel checkboxes are checked, then
AVT will initiate a Protocol:Baud=XXX;Channel=X connection.
This checkbox indicates whether or not the API supports CAN (CAN, J1939, ISO15765) automatic baud
detection. Even though this variable may be set to TRUE, the next four fields indicate whether the API supports
Baud=XXX connect formats for CAN, J1939, and ISO15765. This field is just an informational field, and not all
VDA vendors will support this feature.
These checkboxes indicate whether or not the API supports setting a specific baud rate (or automatic baud
detection) for a specific protocol. These entries come from the VDA vendors INI file. These fields are just for
informational purposes. Not all VDA vendors will support this feature.
When using this dialog box to initiate an advanced test, there is no error checking done to prevent the user from
initiating a Baud=XXX or Channel=X connection to a VDA even if the vendor does not support that connection
format.
Then click the Run Test button. Depending on the results of the test, both the J2534 Status Window and J2534
Data Message Window will turn green (pass) or red (fail).
If the J2534 Status Window turns red, then there is a problem causing the PC not to communicate with the
adapter. This may be something as simple as having power to the adapter or having a USB cabling issue.
Disconnect the adapter from the vehicle and PC; then reconnect them, this time connecting to another USB port
on the PC.
If the J2534 Status Window turns green and the J2534 Data Message Window turns red, then the PC is seeing
the adapter, but not seeing messages from the vehicle. Check the vehicle ignition switch and vehicle to adapter
cabling; disconnect the adapter from the vehicle and PC; then reconnect them.
If you see data in the J2534 Data Message Window, then the adapter is installed and functioning properly.
If after following the Test Results Discussion and Next Steps screen, you cannot get the adapter to read data,
contact DG technical support.
4.4.2. Good Connection (PC to DPA), Good Read of Data (DPA to Vehicle) Green/Green
The above screen snapshots show the PC successfully connecting to the DPA and the successful reading of data
bus data from the CAN data bus. Once the test is complete, the application will display an informational screen
(image on the right) listing steps to potentially correct the issue.
4.4.3. Good Connection (PC to DPA), Not Able To Read Data (DPA to Vehicle) Green/Red
The above screen snapshots show the PC successfully connecting to the DPA but the application is not able to
read data bus data from the data bus selected (CAN). Once the test is complete, the application will display an
informational screen (image on the right) listing steps to potentially correct the issue.
4.4.4. Bad Connection (PC to DPA), Not Able To Read Data (DPA to Vehicle) Red/Red
The above screen snapshots show the PC not able to connect to the DPA at all. Once the test is complete, the
application will display an informational screen (image on the right) listing steps to potentially correct the issue.
You must set up every application (in their own individual way) to use the DPA!
Not all OEM applications save the adapter configuration! Some make the user select the adapter to be used
every time the application is opened.
1. Start program.
2. If Diagnostic Interface Selection dialog box does not appear, click on Vehicle Interface Adapter icon.
a. Select RP1210A Device Using J1708 Line: DPA 5 Dual CAN USB (or DPA 5 #[DPA 5 Bluetooth ID]
Bluetooth).
3. Click OK.
CAT ET Notes:
Enable Dual Data Link. This checkbox should be checked in most cases. However, on some older
J1708 (ATA) only vehicles, ET will not work with this checkbox checked. If ET does not connect, try un-
checking, or checking this button.
The DPA product line does not support the CAT Data Link (CDL) protocol that is still common among
certain CAT off-highway vehicles and industrial stationary equipment. CDL is a proprietary protocol and
there are no generic adapters on the market that support this protocol. If you must connect to a CDL
network, you must go to your local CAT distributor and purchase a CAT adapter.
o To find out if your vehicle/equipment is CDL or a standard protocol (J1708/ATA, J1939), you
should look at the diagnostic connector for that equipment in the service manual.
PowerSpec Notes:
PowerSpec Version 5.5 is required to use the DPA 5. Older versions of PowerSpec were not completely
RP1210-compliant.
A. If you have the Detroit Diesel Electronic Tool Suite on your desktop:
1. Start program.
2. Choose File MD Settings COM Device Window with general VDA selection
3. Select Dearborn Group DPA 5 Multi Application Window with specific port DPA 5 Dual CAN USB (or DPA
5 #[DPA 5 Bluetooth ID] Bluetooth).
1. Start program.
2. Choose File Hydraulic ABS Settings COM Device Window with general VDA selection
3. Select Dearborn Group DPA 5 Multi Application Window with specific port DPA 5 Dual CAN USB (or DPA
5 #[DPA 5 Bluetooth ID] Bluetooth).
1. Start program.
2. Choose File Settings COM Device Window with general VDA selection
3. Select Dearborn Group DPA 5 Multi Application Window with specific port DPA 5 Dual CAN USB (or DPA
5 #[DPA 5 Bluetooth ID] Bluetooth).
1. Start program.
2. Choose Tools Select Com Link Listing of adapters
3. Select Dearborn Group DPA 5 Multi Application Listing of ports DPA 5 Dual CAN USB (or DPA 5 #[DPA
5 Bluetooth ID] Bluetooth).
1. Start program.
2. Press third button from the top along the left side (has an icon that looks like a miniature interface cable.)
a. A window comes up that says Communication Device Selection and has two drop down boxes.
b. Select Dearborn Group DPA 5 Multi Application DPA 5 Dual CAN USB (or DPA 5 #[DPA 5
Bluetooth ID] Bluetooth).
5.13.6. ServiceMaxx:
1. Start Program.
2. Click the Tools menu and choose Options.
3. Select the Comm. Unit Configuration tab.
4. Select RP1210A Adapter and then select DPA 5 Dual CAN USB (or DPA 5 #[DPA 5 Bluetooth ID]
Bluetooth).
5. Select USB for the Port.
6. Select J1708 for the protocol.
7. Go to the Comm. Unit Selection tab.
a. Click Volvo Trucks VERSION2 and select RP1210A Adapter
b. Click Volvo Trucks Vehicle electronics 98 and select RP1210A Adapter
c. Click Mack Trucks V-MAC I/II/III, ITC and select RP1210A Adapter
d. Click Volvo Trucks V-MAC IV and select RP1210A Adapter
8. Click Ok.
1. Start Program.
2. Select Settings from the PTT menu.
3. Go to the Communication Unit tab:
4. Highlight RP1210 Dearborn Group DPA 5 Single Application USB.
5. Select Activate (green circle with checkmark).
6. In a few seconds, under the Status column, Activated will appear next to RP1210 Dearborn Group DPA 5
Single Application USB.
7. Select the OK Button.
o Wait a few minutes to establish connection. If connection doesn't occur, re-boot the PC.
o Do not select Connect immediately after PTT opens. Reading product data.... will appear after a little
bit of time while the connection is being established.
In general, there will be a screen that will appear at some point that allows a user to select a J2534-compliant Vendor and
Device for the reflashing event. When you see this type of screen, choose Dearborn Group, Inc. and/or the DPA 5.
7.1. Why Two OEM Applications May Not Work when Sharing the DPA
Running two or more OEM applications that were not designed to share an adapter in a situation where they are in
fact sharing the adapter is a hit-or-miss scenario. They might work well together and they may not. The two big
reasons some work well together and others don't is J1939 addressing and timing related.
Per SAE J1939, every ECM or application using a VDA must go through a process to claim a J1939 address.
According to J1939, before an ECM or application can send or receive long messages (greater than the standard
8-byte CAN messages); an address must be claimed. These long messages are sent using what is called the
J1939 Transport Protocol (TP). Long messages are used for data such as make, model, serial number, VIN, and
for reprogramming and calibration (very common in OEM diagnostic applications).
The past RP1210 specifications (RP1210-0, RP1210A, and RP1210B) implied that a Vehicle Diagnostic Adapter
(VDA) should have only 1 J1939 address. This means the VDA will handshake for TP messages to/from 1
specific J1939 address. This meant that if one application claims 249 and another application connected while
sharing the VDA (i.e. Multi-Application mode) and claimed address 250; one address will get dropped. This
means that only one of those applications will be capable of sending and receiving long TP messages. If the
application that had its address get dropped depends on these long TP messages, it may not behave properly.
Another problem is that some OEM applications dont handle the RP1210 return value "ERR_ADDRESS_LOST"
when they lose their claimed J1939 address. The application may keep running oblivious to the fact they are not
going to get any long messages; no matter how many times they request them.
The DPA 5 multi-application (MA) drivers behave in a semi-shared-addressing scenario. If the first application
claims an address like 249, and the second application claims 249, then both apps will get TP messages destined
for 249. If the second application were to claim 250, it would be denied.
The second most common reason that two OEM applications don't work well together is timing. OEM applications
expect to send a message out and read a response back from a controller in X amount of time. When two or
more applications are sharing the VDA, messages are stacked for sending in some sort of a transmit buffer and
received messages are also stacked in a receive buffer (commonly called a queue). When you stack message
requests and responses, this slows down the send/receive process and many applications timeout because of it.
The more applications sharing the VDA, the more potential there is for a delay or timeout scenario.
None of them test with another OEM application running. They assume that they
are the only application running on that PC through the VDA they are using.
This is why if you want to run multiple apps at the same time, some apps have to be started first before the
second application. Sometimes, they just won't work no matter what you do!
The DPA 5 Bluetooth Configuration Utility button will only be available if a DPA 5 API is selected.
If you want to modify an option for any DPA driver set, you select that DPA driver set with this field.
This option has long existed, and many OEM and component manufacturers using the DPA for end of line (EOL)
programming stations have used it successfully. If you encounter a diagnostic or reprogramming/reflashing
application that is having problems with the DPA using the J1939 protocol, we recommend setting this parameter
temporarily to the Off position and then retrying the application.
This parameter makes little, if any, difference during standard diagnostic sessions.
Changing this value to something besides 0 (the default) will cause the DPA drivers to start logging DPA driver and
vehicle data bus data to the DebugFile based on the selected value.
When DebugLevel is on and this option is in the 0 (Overwrite File Contents) position, the DPA drivers will erase
DebugFile and begin writing data to the file until it reaches the end of the file (1024 * DebugFileSize). When
reaching the end of the file, the DPA drivers will erase DebugFile and start writing new data to the file.
Value Action
0 Automatic firmware update is turned off. No automatic checking for new firmware.
1 Automatic firmware update is turned on. The user has a choice as to whether or
not to upgrade.
If the user selects Yes, the firmware is automatically updated. If the user chooses
No, then the drivers connect the application to the vehicle. This is the default.
2 Automatic firmware checking is turned on. The user is only told that there is new
firmware available and told they should run the DPA Firmware Updater.
When the user chooses OK, then the drivers connect the application to the vehicle.
The user can then update the DPA at their convenience.
3 Automatic firmware update is turned on. The user is told there is new firmware and
the firmware is downloaded automatically as soon as they press the OK button.
In the event that the automatic update is chosen, the DPA drivers launch the DPA Firmware Updater, which
handles the downloading of new firmware. Once the firmware has started downloading, the user should not stop
it. Aborting a firmware download may cause the device to become unresponsive and require the hardware to be
shipped back to the manufacture for repair. The following is the dialog box showing the DPA Firmware Updater
during an automatic update:
When the update is complete, the following dialog box is displayed and the DPA drivers attempt to let the
application that was suspended continue executing. Most applications can handle the interruption; however there
is a possibility that the user may have to restart their application.
DPA Bluetooth configuration is a somewhat tedious process. DG recommends first reading and
following the instructions in the DPA 5 Series Bluetooth Configuration Manual available from:
Start Programs Dearborn Group Products DPA 5 Documentation Bluetooth Configuration Manual
That document includes the following section, however details how to pair your DPA 5 to your PC are
too detailed to include in this document. This document only includes how to create the DeviceID
required in order to use the DPA 5 in Bluetooth mode with your diagnostic application.
After you have successfully paired your DPA 5 with the Bluetooth dongle and have created the Virtual
COM Port, run the Bluetooth Configuration Utility to create an RP1210 DeviceID entry that can be
seen by OEM software applications:
Start Programs Dearborn Group Products DPA 5 DPA 5 Bluetooth Configuration Utility
You must go through this configuration utility to create RP1210 DeviceID entries. If you do not, the DPA 5 in Bluetooth
mode will not work with your OEM applications!
Display existing DPA 5 Bluetooth RP1210 DeviceID pairings that are found in the DGDPA5MA.INI file, allowing you to
delete an RP1210 DeviceID pairing if you wish.
Discover DPA 5 Bluetooth devices on Virtual COM Ports and create a new RP1210 DeviceID pairing that can be used
by OEM software applications.
Note: The DPA 5 must have power in order to create the Virtual COM Port and RP1210 DeviceID pairing.
NOTE: Sometimes the detection process through the virtual COM port does not see the DPA on the first attempt.
If this is the case, try the discovery process again.
* Shunting these two pins (Term1/Term2) applies a 120-Ohm terminating resistor to the CAN/J1939 network.
* Pins that are not mentioned are reserved and should not have anything attached to them.
The utility will run once every 30 days as a user logs on. This value is configurable, but defaults to 30 days. It can also
be invoked manually from the Windows Start Menu:
The DG Driver Update utility depends on successfully connecting to the Internet (to one of DGs servers) to
retrieve the latest version information and to download the latest drivers and applications if necessary.
Many companies install firewalls and virus protection and these may block the DG server queries and responses.
If you are connected to the Internet and have issues running DG Update (getting Unable to connect to the
internet to check for updates." messages), ensure that your firewall or virus protection will allow a connection to
the following Internet host/site and port: fh.dgtech.com, port 8888. There are too many firewall and virus
programs on the market to cover in this manual, however if you contact your network administrator and give them
the host and port number, they should be able to configure your PC to allow the communication. You may also
consult the Windows help system and/or the documentation for your firewall and/or virus protection software.
When the utility runs as a user logs on, the following screen will appear in the lower right hand corner of the
screen. If you want to check for updates, ensure that your PC is connected to the Internet and click Continue.
Clicking Cancel will cause DG Update to wait until the next time it is scheduled to run. Clicking Continue will
bring up the main update screen.
The main screen appears looking like this. Depending on which products are installed on your PC, the grid will
display pertinent information about them. When selecting DG Update from the Windows Start Menu, this is the
first screen to appear.
Connect your PC to the Internet and click the Check For Updates button. Due to the nature of TCP/IP
communications, errors connecting or sending/receiving of data are slow to appear, however the user will
eventually be notified if there was a problem.
If the check for updates was successful, the second column of the grid will display information returned from the
DG server showing the most current versions and the Install Status row will change to red, green or blue.
Color Description
Green Drivers up-to-date. No update necessary.
Red Drivers are outdated. Update recommended.
Drivers on your PC are newer than current version.
Blue
This usually indicates you are running a beta copy of the DPA drivers.
In this case, all drivers are current (green), and the Download button and progress bar do not display (see next
paragraph). Clicking Exit will exit the program.
In this case, the DPA 5 drivers are out of date (red), and the Download button and progress bar show up on the
screen. The progress bar will keep you informed of the download progress should you choose to download the
latest drivers by clicking the Download button.
When you click the Download button, you will be prompted to confirm starting of the download.
Note: The DG Update application can only download and install one item at a time. The user will be prompted for
whichever one they want to update first. The reason that only one can be downloaded at a time is that the after
the drivers are unzipped the installation program begins automatically. The DG Update program must exit
because the installation program may have a newer version of the DG Driver Update utility to install.
After choosing Yes, the program will download the drivers and update the progress bar while doing so. Once the
drivers have been downloaded, the application will unzip them and start the installation process. The dialog box
will go away after the install has been started.
After the drivers have been downloaded (to the Windows temp directory if you wish to save them for other
machines), they will be unzipped and the program will exit right after starting the new driver installation. Follow
the installation instructions in the appropriate User Manual.
11.4. Advanced Settings Setting Default Time for Check for Updates
If you want to turn off, or alter the timeout period where the user is prompted to check for updates (the dialog below),
press the Advanced Settings button.
The following dialog box will be displayed. To turn off the checking prompt, set the value to zero. Otherwise, you can
set the number of days between checks.
Users not residing in the United States should contact your local DG representative.
Product Service/Repairs
Attn: RMA# xxxxxxx
DG Technologies
33604 West 8 Mile Road
Farmington Hills, MI 48335
Dearborn Group, Inc. will, at its option, repair or replace, at no cost to the customer, products which prove to be defective during the warranty
period, provided the defect or failure is not due to misuse, abuse, or alteration of the product. The customer is responsible for shipment of the
defective product to DG. This warranty does not cover damage to any item that Dearborn Group, Inc. determines has been damaged by the
customer's abuse, misuse, negligence, improper assembly, modification, or operation of the product.
A Return Merchandise Authorization (RMA) number must be issued to the customer by our Technical Support Department at (248) 888-2000
and must be included with the product being returned (for more details, see section Return Merchandise Authorization (RMA)). A DPA is
warranted for 90 days after a warranty repair, or to end of the original factory warranty period, whichever is longer.
To the maximum extent permitted by applicable law, Dearborn Group, Inc. and its suppliers provide support services on an as-is basis and
disclaim all other warranties and conditions not specifically stated herein, whether express, implied or statutory, including, but not limited to,
any warranties of merchantability or fitness for a particular purpose, lack of viruses, accuracy or completeness of responses, results, lack of
negligence or lack of workmanlike effort, and correspondence to description. The user assumes the entire risk arising out of the use or
performance of the device, its operating system components, and any support services.
To the maximum extent permitted by applicable law, in no event shall Dearborn Group, Inc. or its suppliers be liable for any special, incidental,
indirect or consequential damages whatsoever, including but not limited to: damages for loss of profit, loss of confidential or other information;
business interruption; personal injury; loss of privacy, failure to meet any duty (including good faith or of reasonable care); negligence; and any
other pecuniary or other loss related to the use of or the inability to use the device, components or support services or the provision of or
failure to provide support services or otherwise in connection with any provision, even if Dearborn Group, Inc. or any supplier has been
advised of the possibility of such damages.
Notwithstanding any damages that you might incur for any reason whatsoever (including, without limitation, all damages referenced above and
all direct or general damages), in no event shall the liability of Dearborn Group, Inc. and any of its suppliers exceed the price paid for the
device. The user assumes the entire risk and liability from the use of this device.
Dearborn Group, Inc. reserves the right to revise or update its products, software and/or any or all documentation without obligation to notify
any individual or entity.
13.2.5. Governance
The user agrees to be governed by the laws of the State of Michigan, USA, and consents to the jurisdiction of the state court of Michigan in all
disputes arising out of or relating to the use of this device.
13.2.6. Contact
Then click the Run Test button. When the test has finished running, go to the RP1210 Status Window and scroll
down to the line that reads [RP1210_ReadDetailedVersion] and look for the entry FW=. The last numbers on the
line indicates which version of firmware you have (note the yellow circle). If you are not at the correct level (see
manual cover page for which version you should be at), then you need to run the DPA Firmware Updater outlined in
the following steps.
3. Select the correct firmware file (the latest version is already selected by default). If the firmware file exists,
the Firmware box will turn green.
a. NOTE: Firmware files are located in separate sub-directories under the Utilities directory where the
DPA drivers are installed, typically:
C:\Program Files\Dearborn Group Products\DPA 5\Utilities\DPA5_Firmware\
4. Click on the Update Firmware button and select Yes if you receive a warning dialog.
5. After the download is finished, disconnect power from the DPA, wait 5 seconds and then reconnect power.
15.1. Bundling the DPA with Your OEM Installation Silent Install
DG has introduced a silent installation that software installation engineers can call that will install all DPA files that
would normally be installed by running the installation interactively.
The silent installation does not prompt the user or display a screen at any point.
After the install, a reboot of the PC is necessary.
NOTE: Please test and ensure that the command line you provide is correct. Otherwise, only the baseline
components will be installed, but the RP1210 API will not be functional.
If you are a software development engineer or system integrator and wish to use the silent installation, but you
want to change the Automatic Firmware Update setting to a value other than 1 (default), you can do so by
changing the registry value of the following variable during a post-installation event.
This variable is of the REG_SZ data type, however only the first character (0,1,2,3) is used by the RP1210
Options program and the DPA drivers.
If you are on 64-bit installation, the registry entries would have a prefix of:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\
Instead of
This product complies with FCC OET Bulletin 65 radiation exposure limits set forth for an uncontrolled environment.
Changes not expressly approved by Dearborn Group, Inc. to the DPA 5 could void the user's authority to operate the
DPA 5. The following is a sample rear label from the DPA 5 depicting the FCC and IC identifiers.
The following are the DPA 5 Bluetooth details as required to be published by the FCC.
17.2. UAC and the Dearborn Group Adapter Validation Tool (AVT)
A standard user will be able to run the AVT program and troubleshoot the PC-DPA-vehicle connection, but will not
be able to fix a problem in the RP121032.INI file without an administrator password (see the section on
troubleshooting in this document). The graphic below is from the Adapter Validation Tool (AVT), showing the
Microsoft security shield on the Fix/Change RP121032.INI File button.
Acronym Description
API Application Programming Interface
AVT Adapter Validation Tool
CAN Controller Area Network
CD Compact Disk
CD-ROM Compact Disk - Read Only Memory
DG Dearborn Group
DPA Dearborn Protocol Adapter
DTC Diagnostic Trouble Codes
ID Identification
ISO International Standards Organization
AVT Adapter Validation Tool
LED Light Emitting Diode
OBD On Board Diagnostics
OEM Original Equipment Manufacturer
PC Personal Computer
RAM Random Access Memory
RP Recommended Practice (see TMC)
SAE Society of Automotive Engineers
TMC Technology and Maintenance Council
UAC User Account Control
USB Universal Serial Bus
VDA Vehicle Datalink Adapter
There are two standards that OEMs follow when designing their CAN/J1939 network, J1939-11 and J1939-15.
19.1.1. J1939-11
The J1939-11 standard calls for twisted-pair wire with a shield. The shield is typically grounded at the engine
ECM or negative battery post and must only be grounded at one spot on the vehicle. This standard is not
commonly implemented because of the added cost of the shielding. The main issues with this network are too
many, or too few, termination resistors (see Figure G2) or breaks in wire and insulation due to kinks, and
vibration. This standard calls for the external termination resistors shown in Figure G2.
19.1.2. J1939-15
The J1939-15 standard calls for twisted-pair wire without a shield and is the most widely adopted. The main
issues with this network are breaks in the wire and insulation due to kinks, vibration and rubbing, wire and
connector corrosion, and too many, or too few, termination resistors. In the J1939-15 specification, termination
resistors are commonly found inside of ECMs which are easily activated by shunting several pins at that ECMs
connection to the vehicle wiring harness. This configuration makes it very easy to have a termination resistor
problem and is much more difficult to diagnose.
The following image shows a picture of a 120 Ohm resistor typically found within vehicle ECMs and an image of a
J1939 termination resistor that is commonly found on J1939-11 networks.
Figure G1
Image of a 120 Ohm resistor.
Brown, Red, Brown with +/- 5% tolerance (Gold)
Figure G2
Image of J1939 Terminating Resistor on J1939-11 Network (Twisted Shielded Pair)
By design, there are two terminating resistors on a CAN/J1939 network, one at both logical ends of the J1939
backbone (see images in the two paragraphs below). Oftentimes, many technicians or aftermarket add-on
accessories add a third or fourth terminating resistor to the bus, causing issues with databus communications. The
remaining sections of this chapter cover testing for the correct number of terminating resistors, as well as shorts to
ground and power (also very commonplace).
Aftermarket add-ons can cause J1939 network issues by over-terminating the J1939 databus.
Diagnostic
120 Ohm Terminating
Connector
Resistor
Faulty Telematics
or Aftermarket
Installation
To test for proper CAN/J1939 network termination requires a standard Volt/Ohm meter. Follow these steps:
1. Completely power down the vehicle by removing the positive terminal from the battery.
a. This step cannot be bypassed as invalid values will affect the test outcome!
2. With Volt/Ohm meter set to read resistance (Ohms/ setting), place the red lead on pin C (CAN/J1939 High)
and the black lead on pin D (CAN/J1939 Low) of the 9-pin diagnostic connector and note the value.
To test for CAN/J1939 shorts to ground requires a standard Volt/Ohm meter. Follow these steps:
1. Completely power down the vehicle by removing the positive terminal from the battery.
a. This step cannot be bypassed as invalid values will affect the test outcome!
2. With Volt/Ohm meter set to read resistance (Ohms/ setting), place the red lead on pin C (CAN/J1939 High)
and the black lead on pin A (Ground) of the 9-pin diagnostic connector and note the value.
3. With Volt/Ohm meter set to read resistance (Ohms/ setting), place the red lead on pin D (CAN/J1939 Low)
and the black lead on pin A (Ground) of the 9-pin diagnostic connector and note the value.
To test for CAN/J1939 shorts to power requires a standard Volt/Ohm meter. Follow these steps:
1. Reconnect the vehicle battery, ensure ignition is in the ON position, and diagnostic connector has power.
a. With Volt/Ohm meter set to read DC voltages (Volts/V setting), place the red lead on pin B (Power)
and the black lead on pin A (Ground) and ensure the diagnostic connector has roughly 12 Volts.
2. With Volt/Ohm meter set to read DC voltages (Volts/V setting), place the red lead on pin B (Power) and the
black lead on pin C (CAN/J1939 High) of the 9-pin diagnostic connector and note the value.
3. With Volt/Ohm meter set to read DC voltages (Volts/V setting), place the red lead on pin B (Power) and the
black lead on pin D (CAN/J1939 Low) of the 9-pin diagnostic connector and note the value.
To test for controllers transmitting on the databus (commonly called Roll Call) and potentially leaving the databus
because of an error condition (called CAN BUS_OFF) requires a Dearborn Group DPA device, a personal computer
(PC) with drivers for that DPA device installed, and a copy of DG Diagnostics software (free with purchase of a DPA
device).
1. Reconnect the vehicle battery, ensure ignition is in the ON position, and diagnostic connector has power.
a. With Volt/Ohm meter set to read DC voltages (Volts/V setting), place the red lead on pin B (Power) and
the black lead on pin A (Ground) and ensure the diagnostic connector has roughly 12 Volts.
2. Connect DPA device to the vehicle/equipment diagnostic connector and to the PC.
3. Start DG Diagnostics by using the shortcut icon on the desktop (select the MD/HD Truck icon). On the Home
tab, select the correct DPA and Device and click the Connect button.
4. Go to the Components tab (see image below). Wait for 30 seconds to ensure all ECUs transmitting are listed
(top arrow). Make note of all the ECUs in the list.
a. If all ECUs are not transmitting refer to the OEM literature on how to diagnose that component.
5. Press the Reset Lists button and wait another 30 seconds. Make note of all the ECUs in the list. If an ECU has
disappeared, then that controller has went into a BUS_OFF state indicating something is wrong with that ECUs
ability to transmit on the CAN/J1939 data bus. Refer to the OEM literature on how to fully diagnose that
component.
This cable is for use with a second PC running a simulator or other software.
Banana Jacks
Beginning in 2013, Volvo has introduced a new diagnostic connector for a Volvo/Mack chassis with a Volvo engine. It is
based in part on the SAE standard J1962 connector (see image below). It will have two separate CAN channels with
the ISO15765 protocol on CAN Channel 1 and J1939 on CAN channel 2. It will also have J1708 in the connector as well.
Since there is a second CAN channel and a J1708 channel that are not part of the J1962 OBDII standard, this has
required every diagnostic adapter vendor to develop a new cable (or set of cables) for this specific platform. The following
diagram shows the pinouts of this connector:
The following sections explain what cables to use, and how to run the Adapter Validation Tool (AVT) to troubleshoot the
DPA 5 connectivity to this platform.
The DG-DPA5-9OBDII-CABLE has an OBDII connector that meets the needs of Volvo PTT on this vehicle
platform as well as light-duty, medium-duty, and heavy-duty OBDII vehicles using the following protocols:
This cable only works for Volvo PTT, DG Diagnostics (OBDII), or third-party applications like Palmer ScanXL,
PocketFleet Diagnostics or RA Consulting Silver Scan Tool. A user cannot connect to a component
application like Allison, Eaton, Meritor-WABCO or Bendix through this cable!!!
This cable also has a standard J1939 Type II (250k and 500k) connector. This keeps the user from having to
switch cables between an OBDII vehicle and a standard Deutsch 9-pin vehicle using J1939 and/or J1708/J1587.
The DG-V13-XOVER-CABLE has a special purpose, it crosses over CAN Channel 2 to CAN Channel 1 (and vice
versa). It also passes through J1708. This cable is used in conjunction with the DG-DPA5-9OBDII-CABLE.
This special connector cable only works for component applications like Eaton, Allison, Meritor-WABCO, Bendix,
etc. A user cannot connect to PTT with this adapter cable in place!!!
When a component application connects to J1939, it expects it to be on CAN Channel 1. Since J1939 on this
platform is on CAN Channel 2, a special OBDII connector cable was needed.
After installing Classic Start 8, rebooting, and then logging in, click your desktop icon (left photo) and then click
the Start button (right photo). Classic Start 8 provides the Start Menu functionality.
Windows 8 Default User Interface Showing The Classic Start 8 Application Providing Classic
Desktop Life Tile. Windows Start Menu Functionality.
To use the Life Tiles, you can use the scrollbar at the bottom of the screen or you can use the arrow keys to scroll
to the right until you find the DG applications (DG icons). Clicking on an icon runs that application.
The following example shows a DPA 4 Plus, however the process is the same for all DG adapter products. Press
the Windows Start button, find the My Computer entry and then right click on Properties. Select the Hardware
tab and press the Device Manager button.
Find the USB Tools (Dearborn Group) entry. Notice the yellow exclamation point. This means the drivers are
not registering properly. Select the entry, right click and select Update Driver.
The following screen will appear. Select Install from a list or specific location (Advanced) and then press the
Next button.
Select the Search for the best driver in these locations radio button. Then check the Include this location in
the search: checkbox, then press the Browse button.
You must now locate the correct directory for the USB device drivers. The typical install base directory for DG
products is C:\Dearborn Group Products\ however the user can change this at install time. Go to the base
directory, press the [+] plus sign and choose the correct product subdirectory (this example shows the DPA 4
Plus directory). Then press the [+] plus sign on the USBDeviceDrivers folder and select the 32Bit subfolder and
press Ok.
This screen will then appear showing progress as the USB device drivers are registered. On an even smaller
number of machines with Windows XP SP3, this process will hang and the computer will freeze (usually on the
file NCGen.sys or NCPnP.sys file). In this case, see the next section.
After the device is successfully registered, this screen will appear and you will then be able to use your adapter.
If this screen (below) is displayed for more than 5 minutes, try to start any other program to see if the PC is frozen.
If the PC is frozen:
1. Unplug the adapter.
2. Reboot the PC.
3. Press F8 repeatedly as machine boots. When the Safe Mode Menu appears, choose the Safe Mode entry.
4. After the PC boots into Safe Mode, plug in the adapter to every USB port and run the New Hardware Wizard.
5. Reboot the PC and then you will be able to use the adapter.