RP1210 API, Version 2.2
Running Applications on CAN, SAE J1939, ISO15765 and SAE J1708/J1587 Networks

RP1210 API

The RP1210 API is an open interface between windowsbased applications and in-vehicle communication networks. This interface offers functionality for bus systems as well as for higher layer protocols. Its areas of use are very diverse and depend on the implemented application.

The RP1210 specification was developed as a “Recommended Engineering and Maintenance Practice” by the Technology & Maintenance Council (TMC) of the American Trucking Association (ATA). Especially in the USA, voluntary conformance to this recommended practice has gained the support of commercial trucking companies, OEMs and suppliers.

Typical RP1210 applications involve diagnostic tools in the heavy-duty vehicle field, such as those used in the service area. Vector’s RP1210 API can be used to operate these tools during development, including with Vector interface hardware.


  • Comfortable channel mapping enabled by full integration in the configuration dialog of the Vector hardware interfaces

  • Multiple clients per channel

  • Full multithreading capability including different optional wait modes, e.g. waiting for tx indications of messages or completion of higher layer protocol transactions.

  • Compatibility to RP1210-0, RP1210-A, RP1210-B and RP1210-C


Application Architecture utilizing the RP1210 API

The Vector RP1210 API (Application Programming Interface) provides a collection of functions that are essential for clients to establish physical connections to different types of networks as well as sending and receiving data specific to the used protocol standard.
Through a common interface Windows applications thus can connect to multiple networks via various hardware adapters.

The RP1210 specification is a recommended engineering and maintenance practice that is developed by the Technology & Maintenance Council (TMC) of the American Trucking Association (ATA), Inc.


CAN (extract)

  • Standard (11-bit identifier) & extended (29-bit identifier)format
  • Hardware based CAN-ID filtering
  • Concurrent cyclic Broadcast Message delivery option

SAE J1939 (extract)

  • Data Link Layer: Parameter Group (PG-) Data & Transport Protocol Handling (BAM & CMDT)
  • Network Layer: Dynamic address management (claiming/protection of address)
  • Various filtering possibilities (e.g. PGN, source and destination address)
  • Concurrent cyclic Broadcast PG delivery option

ISO15765 (extract)

  • Support ISO15765 (CAN based diagnostic transport

SAE J1708/J1587 (extract)

  • Optional checksum generation & error validation
  • Message Identifier filtering possibilities
  • Concurrent cyclic Broadcast Message delivery option

Hardware Interfaces

The RP1210 API can be used together with Vector interface hardware and the related bus transceivers.

Product Name
PC Interface
Support for

(necessary Tranceiver)
Support for
VN1610 / VN1611
USB 2.0 Highspeed
USB 2.0 Highspeed
yes (J1708piggy)
USB 2.0 Highspeed
yes (CANpiggy)
yes (J1708piggy)
VN5610A / VN5640
USB 2.0 / USB 3.0
ExpressCard 54
yes (CANcab)
yes (J1708cab)
yes (CANcab)
yes (J1708cab)
yes (CANpiggy)
yes (J1708piggy)
PCI Express
yes (CANpiggy)
yes (J1708piggy)
CANboardXL pxi
Compact PCI/PXI
yes (CANpiggy)
yes (J1708piggy)


Product Descriptions

Fact Sheet: Most important facts at a glance (PDF, 2 pages)


Show more
  • Microsoft Windows 2000 / XP /Vista
    (32 bit)
  • Microsoft Windows 7 / 8 / 8.1 / 10
    (32 bit and 64 bit)
Show more

Do you have technical questions and are you looking for suitable answers? Our knowledge base provides the most important FAQs for you.

Show more


Show more

News / Events

Technical Article: More Performance with AUTOSAR Adaptive

AUTOSAR Adaptive is an essential software component that will make a significant contribution to the development of high-performance ECUs in the future.

PREEvision as a Reliable Guide for First Steps in AUTOSAR Adaptive

Vector simplifies the introduction of AUTOSAR Adaptive: The model-based E/E development environment PREEvision comprehensively supports users in expanding existing software and hardware architectures with the capabilities of the AUTOSAR Adaptive Platform.

Technical Article: Overcoming Logging Challenges in ADAS Development Projects

The more tasks that driver assistance systems assume along the way to autonomous driving, the greater the number of

sensors in the vehicle from different suppliers. Real road traffic provides the ideal reference data for testing – in endless

variety. For this purpose, OEMs and system suppliers are sending test vehicles equipped with high-end data loggers onto

the streets to collect data. That data is then used to precisely ”re-simulate“ certain traffic situations in the laboratory

to test new or refined ADAS sensing and control logic. Instead of implementing numerous sensor-specific logging systems,

what is required are scalable approaches and strategies.

vVIRTUALtarget webinar announcements: "Virtual Developing and Testing AUTOSAR Software"

vVIRTUALtarget - realizing AUTOSAR projects in the fast lane

Show all news (232)
Show more
Show more
Show more