CoRE Simulation Models for Real-time Networks

Changes between Version 4 and Version 5 of ANDL_Documentation


Ignore:
Timestamp:
05/18/16 13:52:32 (3 years ago)
Author:
Till Steinbach
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ANDL_Documentation

    v4 v5  
    5656
    5757=== network ===
    58 This is the mandatory part of the ANDL. It contains of 3 mandatory subsections. They are devices, connections and communication. The first one is used to describe the network participants. The second one sets the connection between them. In the last section all messages are defined that should traverse the network. The next example shows the start of the network component. The network name is specified as smallNetwork.
     58This is the mandatory part of the ANDL. It contains of 3 mandatory subsections. They are devices, connections and communication. The first one is used to describe the network participants. The second one sets the connection between them. In the last section all messages are defined that should traverse the network. The next example shows the start of the network component. The network name in this example is specified as smallNetwork.
    5959{{{
    6060#!sh
     
    6363
    6464==== devices ====
    65 In the devices section network participants are configured. The syntax is like in the types component. On device can extend an device type.  In the following example are 2 canLink(canbus1, canbus2),1 ethernetLink(ethcable1), 1 switch(switch1), 2 gateways(gateway1, gateway2) and 2 nodes(canNode1, canNode2) defined. The semicolons can be replaced with an ``\{\}'' block for the definition of additional parameters.
     65Network participants are configured in the devices section. The syntax is similar to the types component. A device can extend a device type.  In the following example there are two canLink (canbus1, canbus2), one ethernetLink (ethcable1), one switch (switch1), two gateways (gateway1, gateway2) and two nodes (canNode1, canNode2) defined. The semicolons can be replaced with an ``\{\}'' block for the definition of additional parameters.
    6666{{{
    6767#!sh
     
    8080
    8181==== connections ====
    82 The elements in the devices section can be used now to build the network infrastructure. Each connection is a member of a segment. Segments are later be used to define the different message representations. For Ethernet connections there are two network participants connected via one ethernetLink. For CAN connections one participant plugged to one canLink. The connections example shows to segements(backbone and canbus) for the individual connections. A special feature for ethernetLink is the ``new'' keyword. It enables the possibility to instance a new ethernetLink with a defined type. This reduces the configuration effort instead of defining each cable in the devices section.
     82The elements in the devices section can be used now to build the network infrastructure. Each connection is a member of a segment. Segments are later used to define the different message representations. For Ethernet connections there are two network participants connected via one ethernetLink. For CAN connections one participant plugged to one canLink. The connections example shows two segments (backbone and canbus) for the individual connections. A special feature for ethernetLink is the ``new'' keyword. It enables the possibility to instance a new ethernetLink with a defined type. This reduces the configuration effort instead of defining each cable in the devices section.
    8383{{{
    8484#!sh