Release 0.23.0

• New features and enhancements:
  • Ignore incoming messages that are considered outdated (i.e. they contain a timestamp that is older than the last accepted message on the same topic) or arrive while the vehicle’s connection topic indicates it is offline.
  • Explicitly set the MQTT client’s maximum number of in-flight messages to 1 to ensure messages are published in the given order.

Release 0.22.0

• Fixes:
  • When translating the vehicle's reported state, ignore nodeStates and edgeStates belonging to the horizon. Not doing so resulted in the vehicle not being assigned a new transport order after withdrawing a previous one.
  • Before sending a drive order's first movement command to the vehicle, check whether the vehicle reports any edgeStates or nodeStates. If yes, send a cancelOrder to ensure the vehicle may accept the new order.

Release 0.21.0

• New features and enhancements:
  • Implement distance check before sending new movement commands to a vehicle. A new vehicle property (vda5050:maxDistanceBase) defines the maximum distance that may be covered by currently queued commands.
• Changes affecting developers:
  • Update openTCS baseline dependency to 6.0.0.

Release 0.20.0

• New features and enhancements:
  • Allow null for optional properties in JSON messages.
  • Support action mapping for transport order destinations.
  • Fields that are marked as NOT_SUPPORTED via a vehicle's properties are now removed from order messages sent to that vehicle.
• Fixes:
  • Some of the fields that are optional according to the VDA5050 specification are now also correctly treated as such in the driver implementations.
• Changes affecting developers:
  • Update Gradle wrapper to 8.7.

Release 0.19.0

• New features and enhancements:
  • In case the property vda5050:vehicleLengthLoaded or vda5050:vehicleLengthUnloaded is not set, the vehicle length configured in the plant model is used as the default value for the respective property.
• Fixes:
  • Dont send cancel order actions when the vehicles changes its operating mode and is actively rejecting an order.
• Changes affecting developers:
  • Update JUnit to 5.10.1.
  • Update ApprovalTests to 22.3.3.
  • Update Mockito to 5.8.0.

Release 0.18.0

• New features and enhancements:
  • Always consider both edgeStates and nodeStates when checking whether the final movement of an order has been completed.

Release 0.17.0

• New features and enhancements:
  • Check vehicle property vda5050:movementCommandCompletedCondition to decide when a movement command should be considered complete.
  • Introduce vehicle property vda5050:extendedDeviationRangePadding to make the padding distance added to the extended deviation range of a node configurable.

Release 0.16.0

• New features and enhancements:
  • When extending the allowed deviation radius for the first node on a route to include the vehicle position, ensure that it is really only extended but never reduced. I.e. always use the deviation of the node as the minimum allowed deviation, even if the vehicle is closer than that to the node's coordinates.
• Changes affecting developers:
  • Update Gradle wrapper to 8.4.
  • Update Jackson to 2.15.3.
  • Update everit-json-schema to 1.14.3.
  • Update Checkstyle to 10.12.4.
  • Update Mockito to 5.6.0.
  • Update ApprovalTests to 22.2.0.

Release 0.15.0

• New features and enhancements:
  • When resolving the vehicle's reported position to a point in the plant model, consider the mapId, too.
  • The paused state and informational messages are now mapped to a vehicle's properties using the keys vda5050:paused, vda5050:information.info and vda5050:information.debug.
• Fixes:
  • Actually accept state messages lacking the paused flag.
  • If configured, correctly withdraw the transport order assigned to a vehicle when its operation mode changes.
• Other changes:
  • Update openTCS baseline dependency to 5.11.0.

Release 0.14.0

• Fixes:
  • Fix transport order withdrawal after order rejections.
  • Avoid NullPointerExceptions in a couple of places.
  • Correctly compute the sequence ID for horizon elements.
  • When checking whether all nodes and edges of an order have been completed, ignore the horizon.