File: Applications/KBRTestApp/KBRTestApp.ned
Compound module for a simple test application using the KBR interface
Author: Bernhard Heep
The following diagram shows usage relationships between modules, networks and channels. Unresolved module (and channel) types are missing from the diagram. Click here to see the full picture.
If a module type shows up more than once, that means it has been defined in more than one NED file.
KBRTestApp | Simple module of the KBR test application |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
from_lowerTier | input | gate from the lower tier |
from_upperTier | input | gate from the upper tier |
trace_in | input | gate for trace file commands |
to_udp | output | gate to the UDP layer |
to_lowerTier | output | gate to the lower tier |
to_upperTier | output | gate to the upper tier |
Name | Type | Description |
---|---|---|
kbrTestApp.debugOutput | bool | enable debug output |
kbrTestApp.testMsgInterval | numeric | interval for sending test messages |
kbrTestApp.msgHandleBufSize | numeric | how many MsgHandles to store in circular buffer |
kbrTestApp.lookupNodeIds | bool | lookup only existing nodeIDs |
kbrTestApp.activeNetwInitPhase | bool | is app active in network init phase? |
module KBRTestAppModules gates: in: from_udp; // gate from the UDP layer in: from_lowerTier; // gate from the lower tier in: from_upperTier; // gate from the upper tier in: trace_in; // gate for trace file commands out: to_udp; // gate to the UDP layer out: to_lowerTier; // gate to the lower tier out: to_upperTier; // gate to the upper tier submodules: kbrTestApp: KBRTestApp; display: "i=block/app"; connections nocheck: from_lowerTier --> kbrTestApp.from_lowerTier; to_lowerTier <-- kbrTestApp.to_lowerTier; from_udp --> kbrTestApp.from_udp; to_udp <-- kbrTestApp.to_udp; trace_in --> kbrTestApp.trace_in; endmodule