GitLab

Moved Controllable Actuators from the API into peerfact (like directly controlling the movement between APP and tech)

LoRa network header protocol

Configuration class for actuator energy coimponents.

And UAVLOcationActuator to the SimUAVLocationActuator for peerfact

Refactored the way that energy consumation is calculated for the energy models. Now the consumation is calculated on every energy component for itself, since the state change is of no interest to the energy model. Makes the process easier.
Monitor logging can now be added to the respective energy components, if that is wished again (was removed from the energy model anyways!).

Refactored the way that energy consumation is calculated for the energy models. Now the consumation is calculated on every energy component for itself, since the state change is of no interest to the energy model. Makes the process easier.
Monitor logging can now be added to the respective energy components, if that is wished again (was removed from the energy model anyways!).

Moved energy models and components into their own packages, this is more convenient w/ a better overview

UAV Topology and UAV Movement.

Movement Models for abstract UAVs, multicoper UAVs and UAV Location actuators. Multiple files refactored for better readability.

+ Made the node debug a standalone component similar to the Monitor class positioned properly inside the api and peerfact.
+ Added filtering capabilities
+ Added logging in some classes deep in the architecture the provide node information

- removed obsolete and duplicate modular movement classes (check your
config-files, you might need to replace "modular" with "modularosm" in
some cases

- set target for movement currently only supported in the modularosm
model, feel free to extend other models by overwriting the default
implementation and create the corresponding merge requests.

- support for in-model placement of nodes

- deprecated MovementSupported
- used LocationSensor and LocationActuator
- decoupled nested listener structures used within the old models

implemented by all netlayers
updates MaxPeerCountChurnGenerator to support the interface (default
behavior still triggers the network-layer functions)

- using the Rate-API

- configuration of whether receiver-queue is taken into account is now
based on the selected TopologyView
- fixed min-time for dropped msgs to be 1 us instead of 1 ms.
- deleted obsolete (unused) CollisionAwareMac. Use 80211 instead.

All GlobalComponent are automatically added to the Binder on system
configuration.

(still, PHY-types should be deprecated against NetInterfaceNames at some
point in time)

Added support for dynamic links (property updates on range changes based
on the topology view)
First step towards integrating measurement maps into the simulator

and max for one component. 
Models MAY set a new speed as they wish (api of MovementSupported
changed to allow this behavior). Can be used, e.g., to update speed once
a target waypoint has been reached.