RP1210: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
As a result, there are a variety of RP1210-compliant hardware interfaces on the market, including Kvaser cables available from New Eagle. | 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 on the '''[https://www.kvaser.com/about-can/can-standards/rp1210/ | Additional information can be found on the Kvaser '''[https://www.kvaser.com/about-can/can-standards/rp1210/ Introduction to RP1210]''' page. | ||
Latest revision as of 16:41, 15 February 2023
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 on the Kvaser Introduction to RP1210 page.