Raptor-Dev-Serial: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Raptor-Dev Serial Library}} | {{DISPLAYTITLE:Raptor-Dev Serial Library}} | ||
{{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[ | {{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[Raptor-Dev]] > [[Raptor-Dev-Libraries | Raptor-Dev Library]] > '''Raptor-Dev Serial Library''' | ||
[[File:RaptorSerial.png|right|frame|Raptor™ Serial]] | [[File:RaptorSerial.png|right|frame|Raptor™ Serial]] | ||
Latest revision as of 15:06, 6 April 2015
New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev Library > Raptor-Dev Serial Library
The blocks in this subsystem are access ECU hardware serial resources (if supported) such as RS232 and RS485.
Blocks
| Block | Description | Appearance |
|---|---|---|
Serial Definition |
This block is used to create a serial bus resource and map it to a particular hardware I/O point. This block will generate all the code necessary to connect and coordinate all the Raptor serial blocks with the hardware interface. Each serial bus that will be used in the model must include a serial definition block. Only one serial definition block can exist for any particular hardware resource. |
 |
Serial Rx |
This block is used to receive serial data. There is only one receive queu for each serial bus which is used by all serial Rx block for that bus. |
 |
Serial Trigger |
The serial trigger block is used to execute code when a data byte is recieved on a serial port. |
 |
Serial Tx |
This block is used to transmit a byte on the serial bus. The data is queued for transmit whenever the block is executed. There is only a single transmit queue for each serial resource. |
 |