RP1210: Difference between revisions
Jump to navigation
Jump to search
(Created page with 'The RP1210 interface, specified by the Technology and Maintenance Council (TMC), was designed to standardize the interface between Windows™-based software applications running …') |
No edit summary |
||
| Line 5: | Line 5: | ||
[[File:rp1210.png]] | [[File:rp1210.png]] | ||
As a result there are a variety of RP1210-compliant hardware interfaces on the market | As a result there are a variety of RP1210-compliant hardware interfaces on the market, including Kvaser cables available from New Eagle. | ||
Additional information can be found at: https://www.kvaser.com/about-can/can-standards/rp1210/ | Additional information can be found at: https://www.kvaser.com/about-can/can-standards/rp1210/ | ||
Revision as of 21:31, 29 November 2016
The RP1210 interface, specified by the Technology and Maintenance Council (TMC), was designed to standardize the interface between Windows™-based software applications running on a PC and control network interface hardware. This standard is often required by vehicle manufacturers within the heavy truck market. A couple of the advantages of doing this are:
- A common device can be used to interface to numerous manufacturers' control modules
- A particular manufacturer's software can communicate using any number of devices
As a result there are a variety of RP1210-compliant hardware interfaces on the market, including Kvaser cables available from New Eagle.
Additional information can be found at: https://www.kvaser.com/about-can/can-standards/rp1210/