Raptor-Dev-J1939-PGN-Tx: Difference between revisions
Ssienkowski (talk | contribs) (Created page with 'Return to the main Raptor page Return to J1939 page right|frame|Raptor J1939 PGN Tx <p>The blocks in this subsyste…') |
m (moved Raptor:J1939 PGN Tx to Raptor-Dev-J1939-PGN-Tx) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[ | {{DISPLAYTITLE:Raptor-Dev J1939 PGN Tx}} | ||
{{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[Raptor-Dev | Raptor-Dev]] > [[Raptor-Dev-J1939-Library|Raptor-Dev J1939 Library]] > '''Raptor-Dev J1939 PGN Tx''' | |||
[[File:RaptorJ1939PGNTx.JPG|right|frame|Raptor™ J1939 PGN Tx]] | |||
[[File:RaptorJ1939PGNTx.JPG|right|frame| | |||
<p>The blocks in this subsystem can be used to send various PGNs on the J1939 bus. Each block implements the correct triggering mechanisms to send the PGN at the rate specified in the J1939 specification. The PGN Tx blocks use the SPN library mechanism to collect the SPN data required. Some PGN Tx blocks must be located in a periodically executed subsystem to update their output. It is highly recommended that all PGN Tx blocks be placed in a subsystem which is executed regularly.</p> | <p>The blocks in this subsystem can be used to send various PGNs on the J1939 bus. Each block implements the correct triggering mechanisms to send the PGN at the rate specified in the J1939 specification. The PGN Tx blocks use the SPN library mechanism to collect the SPN data required. Some PGN Tx blocks must be located in a periodically executed subsystem to update their output. It is highly recommended that all PGN Tx blocks be placed in a subsystem which is executed regularly.</p> | ||
Latest revision as of 19:04, 24 March 2015
New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev J1939 Library > Raptor-Dev J1939 PGN Tx
The blocks in this subsystem can be used to send various PGNs on the J1939 bus. Each block implements the correct triggering mechanisms to send the PGN at the rate specified in the J1939 specification. The PGN Tx blocks use the SPN library mechanism to collect the SPN data required. Some PGN Tx blocks must be located in a periodically executed subsystem to update their output. It is highly recommended that all PGN Tx blocks be placed in a subsystem which is executed regularly.
Blocks
Block | Description | Appearance |
---|---|---|
CBI |
This block implements PGN 65212 Compression/Service Brake Information. Use neweagle_j1939_spn_write blocks to set the data sent by this block. |
|
CI |
This block implements PGN 65259 Component Identification. |
|
EC1 |
This block implements PGN 65251 Engine Configuration 1. Use neweagle_j1939_spn_write blocks to set the data sent by this block. |
|
ECUID |
This block implements PGN 64965 ECU Identification Information. |
|
LTFI |
This block implements PGN 65209 Trip Fuel Information (Liquid). Use neweagle_j1939_spn_write blocks to set the data sent by this block. |
|
Single Frame PGN Tx Options |
This block is used with the raptor_j1939_pgn_tx block to dynamically set the priority and destination address of a message. |
|
Single Frame PGN Tx |
This block implements all single frame PGN's. It must be used with the neweagle_spn_write block to set the SPN data being transmitted. |
|
SOFT |
This block implements PGN 65242 Software Identification. |
|
VI |
This block implements PGN 65260 Vehicle Identification. |