Raptor-Dev: Difference between revisions
Jump to navigation
Jump to search
| Line 50: | Line 50: | ||
=Raptor Application Libraries= | =Raptor Application Libraries= | ||
==Raptor J1939 Library== | ==Raptor J1939 Library== | ||
<p>The Raptor J1939 Library offers an easy approach to add J1939 support to any existing or new Raptor project. It abstracts all of the complex network management and transmission requirements of the J1939 protocol allowing fast development of a J1939 compatible application. The J1939 Library seamlessly interfaces with the OBD Fault Manager blocks to provide a large number of J1939 Diagnostic Messages. All of the functions required to create an OBD-HD compliant application are included in the Raptor J1939 Library.</p> | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Revision as of 15:14, 4 March 2015
Getting Started
Standard Raptor Libraries
These libraries are included with the purchase of a Raptor-Dev license
Raptor Library
|
|
|
|
|
|
|
|
| |
|
|
|
Raptor Data Logging Library
Raptor Display Library
|
|
|
|
|
|
Raptor Application Libraries
Raptor J1939 Library
The Raptor J1939 Library offers an easy approach to add J1939 support to any existing or new Raptor project. It abstracts all of the complex network management and transmission requirements of the J1939 protocol allowing fast development of a J1939 compatible application. The J1939 Library seamlessly interfaces with the OBD Fault Manager blocks to provide a large number of J1939 Diagnostic Messages. All of the functions required to create an OBD-HD compliant application are included in the Raptor J1939 Library.
|
|
|
|
|
|