This white paper is intended to explain the benefits of this recommended practice, and provide direction when evaluating the various products from vendors of vehicle software or interface hardware. Additionally, this paper gives an overview of the issues to be considered and decisions to be made when evaluating vendor solutions.
Finally, this document discusses RP-1210 compliant MPSI solutions and how these products interface when using RP-1210 based applications
Why RP–1210?
In today’s transportation industry, vehicle control using electronics has become commonplace. As a result, vehicles and their subsystems provide better and more efficient operation, information, and performance.
While the benefits of the use of electronics may be obvious, the results have been a significant increase in system complexity.
To take advantage of the features provided by these systems and to assist the technician in diagnosing them, a number of companies have introduced personal computer (PC) based software solutions.
Examples of currently available PC software include Caterpillar Electronic TechnicianTM, Cummins Insite, Detroit Diesel Power Service, Freightliner’s Service Pro, and MPSI’s Vehicle Data Systems.
Today’s typical fleet has a number of vehicle/engine/system combinations used for specific applications. Walk into fleet location today and you will find a mix of trucks, engines, transmissions, axles, and anti-lock braking systems, etc, from several different manufacturers. To diagnose the mix of systems, several fleets find themselves loading software from the various manufacturers onto a single shop PC.
The problem is that certain applications require different vehicle-interface specific adapters in order to communicate properly with the vehicle. This is an added level of complexity and cost that is highly undesirable.
RP–1210 was developed to allow software applications to coexist on a single PC platform, and to provide a means of allowing any software application to use a single, RP–1210 compliant, vehicle interface box. RP–1210 eliminates the need to maintain manufacturer specific interface boxes.
What is RP–1210?
One of the benefits of Windows™ operating systems is their ability to allow software applications to use several different types and brands of accessories without each application having to understand how those accessories work.
For example, it does not matter what kind of printer
you are using when creating a document. What you see on your computer screen is pretty much, what you can expect to get on your paper copy. The information you get on your screen when using an internet browser does not depend on the make of your modem, or how it handles sending or receiving data; it does not even matter how your modem is hooked up to your computer (except for speed of course).
This product/manufacturer independence has been accomplished by establishing and using a standard set of commands and messages between Windows™ and the hardware device. Basically, the manufacturer of the component is responsible for developing and providing a file or series of files known as device drivers or dynamic link libraries (DLLs). The drivers and DLLs are responsible for handling the messages received from, and sent to Windows™ in the appropriate manner with their specific piece of hardware. These files either are provided with your operating system, or are provided on diskettes or CD-ROMS that come with the device.
So, what does all this mean?
What the S-12 subcommittee sought to accomplish was to provide the same standards to vehicle diagnostic application software and vehicle interface adapters. That is exactly what RP–1210 does. RP–1210 has established a standard set of guidelines for software developers and vehicle interface hardware manufacturers that allows any RP–1210 compliant software application to communicate successfully with any RP–1210 compatible vehicle interface adapter.
In the near future, it will not be necessary for you to purchase a manufacturer specific vehicle interface adapter; instead, you will be able to choose from a variety of manufacturers, selecting the one that best suits your needs.
Is it finalized?
No. Just like every other technology, operating systems and vehicle systems are constantly undergoing change. As a result, not long after RP1210 1.0 was adopted, the RP was re-opened to incorporate modifications due to technological and performance enhancements. The good news is that the members of the task force have all agreed that backward compatibility is required. Therefore, any current RP–1210 application will be inherently compatible with RP–1210 version 2.0 once it is adopted.
What you should look for when selecting application software and vehicle interface adapters.
With the acceptance of RP–1210, all manufacturers who currently use diagnostic applications, or are planning to develop a diagnostic application have stated that they will be converting or developing their application to comply with the RP–1210 standard. Based upon current information, the conversion of most existing applications to comply with RP–1210 is expected to be complete within the coming year (as of this writing, 1998).
When reviewing software and product information from a supplier, investigate these three critical areas.
Backward Compatibility
Platform Dependence/Independence
Product Support
Backward Compatibility
Check to see if your existing applications are compatible with the vehicle interface adapter you are selecting. Avoid requiring your technician to change adapters every time he/she wants to connect to a vehicle. This adds additional time to the operation, and increases the wear and tear on the equipment and presents the possibly for losing that adapter. Several manufacturers of vehicle interface devices have tested their products on existing applications, and should be able to tell you if their adapter is compatible with both existing applications and RP–1210 based applications.
Platform Dependence/Independence
Software developers are capable of creating their applications to run on specific operating systems, or various, multiple operating systems. For example, Windows 3.1™ and Windows for Workgroups™ are
16-bit operating systems, while Windows 95™ and Windows NT™ are 32-bit operating systems, each with their own unique capabilities. When writing software applications, developers may have elected to write the application to support both operating systems, or they may have chosen a specific operating system due to its specific performance enhancements or capabilities.
If you are limited to either 16-bit or 32-bit operating systems, make sure that the products (both the software application and the vehicle interface adapter) that you are considering are compatible with that operating system.
If you use more than one operating system, make sure that the software application will run on the operating systems you have and that the vehicle interface adapter will interface to that application successfully on both platforms.
The following table is a sample evaluation of applications and vehicle interface adapters. In the example, application A is a pre RP–1210 application, B is a 16-bit Windows application, and C is a 32-bit Windows application. The table indicates that since interface adapter B would work on all applications and operating systems that you currently have or plan to purchase, it would be the best choice for you.
Application/Type
Interface Adapter
Win 3.1
Win 95
A: 16-Bit, Non RP–1210 A
No
No
A: 16-Bit, Non RP–1210 B
Yes
Yes
B: 16-Bit, RP–1210 A
Yes
No
B: 16-Bit, RP–1210 B
Yes
Yes
C: 32-Bit RP–1210 A
No
Yes
C: 32-Bit RP–1210 B
No
Yes
Product Support
When choosing application software, make sure that the company you are selecting has the experience required to understand the subtleties of the vehicle system or application you are using, and that they offer product support that is satisfactory for your needs. You should specifically, check that the coverage offered supports the makeup of your fleet. If a bug or problem is identified, ensure that the vendor has the capability to diagnose the problem and provide a timely fix.
The same goes for hardware interface products: choose your RP–1210 vehicle interface adapter based upon the experience of the company within your industry, and its applicability to the systems that you service. They are the company who will be best suited to identify nuances related to the various vehicle components. Evaluate their ability to provide updates to you, their methods of providing them, and the cost.
RP–1210 Compliant MPSI Products
Background
MPSI has been involved in vehicle interface devices since 1980, and has been the leader in hand-held diagnostic tools ever since, for the heavy-duty industry. Our Pro-Link 9000 still serves as the standard handheld diagnostic tool, providing application support for almost all of the electronically controlled systems on heavy-duty vehicles and passenger cars. In the development of each application, MPSI has worked closely with the manufacturer, ensuring that the application developed is adequate to diagnose the system, and that the data provided to the technician is accurate and relevant.
RP–1210
MPSI has been actively involved throughout the development of the RP–1210 recommended practice, and offers a line of products that are compatible with RP–1210 based applications as well as applications that preceded RP–1210.
The MagiKey Line
At the present time, MPSI offers two vehicle interface products that are fully compatible with
pre and post RP–1210 applications.
MagiKey Parallel Data Module (PDM)
The Parallel Data Module is a vehicle interface adapter that is designed to connect to the PC’s parallel interface port. It is compatible with DDEC I, ATEC I, SAE J1708, SAE J1939, and CAN, thus providing vehicle connectivity for both existing and future diagnostic and service applications. The PDM includes all necessary cables and adapters, and includes an installation diskette that installs all necessary drivers. The PDM is compatible with both pre and post RP–1210 applications.
MagiKey Serial Data Module (SDM)
The Serial Data Module is a vehicle interface adapter that is designed to connect to the PC’s serial interface port (COM1, or COM2). It is compatible with SAE J1708 thus providing vehicle connectivity for all existing service applications. The SDM includes all necessary cables and adapters, and includes an installation diskette that installs all necessary drivers. The SDM is compatible with both pre and post
RP–1210 applications.
PDM and SDM Updates
MPSI provides interface updates as required at no charge for both products. These updates are available via our Web site "mpsilink.com", and can be downloaded at any time.
Warranty
Both products are backed by MPSI’s one-year warranty.
This paper was developed by:
WPI Micro Processor Systems, Inc.
6405 Nineteen Mile Road
Sterling Heights, Michigan 48314-2115
