CAN model
  OCERA Home  /  Download  /  Components  /  Communication  /  CAN model (0.1)
  Training and support
    POSIX Streams

  Resource management
    Generic Scheduler patch
    Preemption+RTLinux patch
    RTLinux API on Linux
    QoS Manager
    Linux/CBS Scheduler

  Scheduling
    Application Scheduler
    TLSF Memory Allocator
    POSIX CPU Clocks
    POSIX Barriers
    POSIX Message Queues
    POSIX Signals
    POSIX Timers
    POSIX Trace
    RTLinux/CBS Scheduler
    RTLinux CC
    GNAT for RTLinux
    RTLinux ide/fs
    RTLinux Java
    RTLinux Terminal
    RTLinux UDP/IP
    Stand-Alone RTLinux
    XtratuM

  Fault-tolerance
    FT Application Monitor
    FT Controller

  Communication
    CANopen device
    CAN/CANopen monitor
    Virtual CAN API
    RT Ethernet Analyzer
    Linux CAN Driver
    ORTE
    CAN model
    Verification of RTOS

CAN model by timed automata /Petri Nets

   Description
Keywords: Real-Time, CAN, Petri Nets, communications
Description: This component is theoretical study offering methodology tool support for analysis of distributed system consisting of n independent processors and deterministic communication bus (CAN). In order to verify distributed RT system, application designer needs to create a model of application tasks and to interconnect this model with the communication bus model provided by this component. Finally he/she needs to define system properties to be verified (deadlock, missed deadline etc.). This component can be used either in a design phase or it can be used to verify existing implementation.
   General information
Author(s): Jan Krakora (CTU) and Zdenek Hanzalek (CTU)
Participants: Czech Technical University in Prague
Workpackage: Development of communication components (WP7)
Component homepage: http://www.ocera.org
Licenses: GPL
Current version: 0.1
Status: Analysis
   Download
Current version: 0.1 [Not available yet] [src]
Note: This component cannot be used directly. It has to be used within OCERA framework. Sources are provided only for documentation and portability purposes.

 Status codes: Analysis >> Design >> Alpha >> Beta >> Testing >> Stable

© OCERA Project. webmaster@ocera.org
Maintained by: Sergio Sáez   Last update: Wed Jan 10 16:56:58 2007