Raptor-Dev-Modbus-Library: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
{{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[Raptor-Dev | Raptor-Dev]] > '''Raptor-Dev Modbus Library''' | {{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[Raptor-Dev | Raptor-Dev]] > '''Raptor-Dev Modbus Library''' | ||
<p>This library takes care of all low-level Modbus protocol details under the hood, so the end-user need only choose which signals he/she wishes to transmit or receive over the Modbus channel.</p> | <p>This library takes care of all low-level Modbus protocol details under the hood, so the end-user need only choose which signals he/she wishes to transmit or receive over the Modbus channel.</p> | ||
< | {| class="wikitable" | ||
|- | |||
! scope="col" style="width: 15%;"| Block | |||
! scope="col" style="width: 60%;"| Description | |||
! scope="col" style="width: 25%;"| Appearance | |||
|- | |||
! <h5>[[Raptor:Application Monitor|Application Monitor]]</h5> | |||
| <p>The application monitor provides a mechanism for monitoring and controlling the execution of a model on a Raptor target. The application monitor can monitor thread execution time and pause the application if a single thread's processor usage is over the defined limit or if the processor idle time is below a minimum. Adding the application monitor block to the model allows enabling additional code generation which will provide this functionality. Note: Not all Raptor targets use a pre-emptive operating system. This means that an infinite loop in a task may cause the module to reset rather than stop the application through the application monitor.</p> | |||
| [[file:RaptorApplicationMonitor.jpg|frameless|border|Application Monitor block|center]] | |||
|- | |||
!<h5>[[Raptor:Application Monitor Measure|Application Monitor Measure]]</h5> | |||
|<p> </p> | |||
|[[File:RaptorModbus.jpg|frameless|border|Application Monitor Measure block|center]] | |||
|} | |||
Revision as of 19:49, 6 April 2015
New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev Modbus Library
This library takes care of all low-level Modbus protocol details under the hood, so the end-user need only choose which signals he/she wishes to transmit or receive over the Modbus channel.
| Block | Description | Appearance |
|---|---|---|
Application Monitor |
The application monitor provides a mechanism for monitoring and controlling the execution of a model on a Raptor target. The application monitor can monitor thread execution time and pause the application if a single thread's processor usage is over the defined limit or if the processor idle time is below a minimum. Adding the application monitor block to the model allows enabling additional code generation which will provide this functionality. Note: Not all Raptor targets use a pre-emptive operating system. This means that an infinite loop in a task may cause the module to reset rather than stop the application through the application monitor. |
 |
Application Monitor Measure |
|
 |