Package: inet.tutorials.protocol
ServerHost5
compound module(no description)
Usage diagram
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.
Used in
| Name | Type | Description |
|---|---|---|
| Network5 | network | (no description) |
Properties
| Name | Value | Description |
|---|---|---|
| display | i=device/pc |
Gates
| Name | Direction | Size | Description |
|---|---|---|---|
| in | input |
Unassigned submodule parameters
| Name | Type | Default value | Description |
|---|---|---|---|
| app.displayStringTextFormat | string | "received %p pk (%l)" |
determines the text that is written on top of the submodule |
| app.clockModule | string | "" |
relative path of a module that implements IClock(1,2); optional |
| app.consumptionInterval | double | 0s |
elapsed time between subsequent packets allowed to be pushed by the connected packet producer, 0 means any number of packets can be pushed at the same simulation time |
| app.scheduleForAbsoluteTime | bool | true |
when a clock is used relative means that setting the clock will not affect the simulation time of the event |
| fcsChecker.displayStringTextFormat | string | "dropped %d/%p pk (%k/%l)" |
determines the text that is written on top of the submodule |
| fcsChecker.backpressure | bool | false | |
| fcsChecker.headerPosition | string | "back" | |
| receiver.displayStringTextFormat | string | "processed %p pk (%l)" |
determines the text that is written on top of the submodule |
| receiver.datarate | double |
Source code
module ServerHost5 { parameters: @display("i=device/pc"); gates: input in; submodules: app: PassivePacketSink { @display("p=150,100"); } fcsChecker: FcsHeaderChecker { @display("p=150,200"); } receiver: PacketReceiver { @display("p=150,300"); } connections: in --> receiver.in; receiver.out --> fcsChecker.in; fcsChecker.out --> app.in; }File: tutorials/protocol/Network5.ned