Memory Access Request (DM14), Memory Access Response (DM15), and Binary Data Transfer (DM16) for read and write operations of Diagnostic Data and Control Routines. Retrieve Inactive DTCs using DM2, via active request or passive mode. Retrieve Active Diagnostic Trouble Codes (DTCs) using Diagnostic Message 1 (DM1). (Advanced users can modify the CAN database for more flexibility.) Parameter Group Number (PGN) request message (0x18EA00), and get response. (Unlocked Library version is required for RT support) 1 P a g eĢ Supported J1939 Functions: At this time, the following critical aspects of the SAE J1939 protocol specification are supported: User defined Tool, Target, and Global Source and Destination Addresses. These drivers will work on any LabVIEW Real Time (RT) targets which directly support the NI channel API, such as PXI and NI industrial PCs. Additional J1939 functionality can be easily incorporated, since the source code is entirely LabVIEW based. The J1939 CAN drivers integrate seamlessly with LabVIEW, since there are no external dll s or third party APIs involved. Since this DMC implementation is written entirely in the LabVIEW development environment, which provides functions at a layer above the base CAN channel layer, there are several benefits to be realized: The drivers allow the simultaneous capture of data from both poll-and-response J1939 packets using the DMC drivers, and broadcast CAN frames using the simplicity of the NI Channel API. This driver set is intended for use in automated testing and hardware in the loop (HiL) simulation environments. The drivers use the SAE J1939 protocol to communicate with an automotive ECU (Electronic Control Module) using NI CAN hardware that supports the channel API.
1 DMC NI-CAN Channel J1939 Drivers Project Information: Latest S/W Revision: Date: DMC Contact Information: Web: Telephone: Software Description: DMC developed this set of SAE J1939 protocol drivers for LabVIEW using the NI-CAN channel API provided by National Instruments (NI).
0 kommentar(er)
