...

• node_id: Identification string of the middleware instance in the DDS network
• period_nanoseconds: Length of each period in which the HLC is triggered, in nanoseconds
• simulated_time: True if the current setup uses simulated time, else false
• wait_for_start: Whether the middleware should wait for the LCC's start signal, should be true (false only for debugging purposes)
  
• vehicle_id: Single ID of a vehicle the middleware is supposed to be responsible for
• vehicle_ids: IDs of the vehicles the HLC(s) that the middleware 'controls' are responsible for (usually just one ID)
  
• vehicle_amount: Set amount of vehicles instead of vehicle ID, sets IDs 1 - vehicle_amount (restricted to 256)
• dds_domain: Domain ID of the domain in which the LCC, vehicle etc. participate
  
• domain_number: Local domain ID of the middleware and the HLC
  
• dds_initial_peer: Should be explained in Lab Control Center (Usage) (TODO) 
  

Other parameters

• offset_nanoseconds: Set the offset of the communication w.r.t. ~1970 (TODO, real time) or 0 (simulated time); should usually not be changed
  
• use_param_server: Irrelevant parameter, false is default (true currently not required, would break the middleware)
• log_topic: Topic name of the logging topic (logs that are collected by the LCC)
• hlc_state_topic: Topic name of the vehicle state list topic for the vehicle information sent to the HLC
• vehicle_state_topic: Topic name of the vehicle states sent by the vehicles
• hlc_trajectory_topic: Topic name of the trajectory commands sent by the HLC
• vehicle_trajectory_topic: Topic name of the trajectory commands sent to the vehicles
• hlc_speed_curvature_topic: Topic name of the speed curvature commands sent by the HLC
• vehicle_speed_curvature_topic: Topic name of the speed curvature commands sent to the vehicles
• hlc_direct_topic: Topic name of the direct control commands sent by the HLC
• vehicle_direct_topic: Topic name of the direct control commands sent to the vehicles

Communication between HLC and Middleware

The IDL type for the DDS communication of HLC and middleware is mentioned here and located here: https://git.rwth-aachen.de/CPM/Project/Lab/software/blob/master/hlc/middleware/idl/VehicleStateList.idl

Further communication includes the propagation / exchange of start and stop signals. All relevant data types are e.g. used in the init script for Matlab, which is mentioned in the Matlab section.

What the HLC scripts need to include

...