Skip to content

Assembly Profile

The JSON based Assembly description file (Assembly Profile) represents an Assembly with all its devices, connections, specifics and other properties crucial for automation. The data model is updated from time to time to incorporate new features and improvements (such as device multiplexers). Feature requested can be dropped with a TAR ticket here: support page. Creating and maintaining of a description file is the task of veHaaS maintainers.

Especially when using an Assembly for development tasks together with the veHaaS Web UI you may not get in direct touch with this data model. You will rather use the interface WebUI control elements derived from it (e.g. device switch on/off) and information provided by it. The Assembly description file is mainly used as input for the veHaaS Backend then required working artefact for the tester.

For automation tasks direct access to the Assembly description file may be required. Parsing is done using a Python module called pes-vehaas-interpreter.

WIP: When an Assembly is allocated, the veHaaS VM will contain the current version of the Assembly description in a standard path.

As an example, the description file of Assembly-1000 can be found in the Assembly -> setup tab.

Core elements of the description file are:

  • an assembly_name
  • the used datamodel_version processed by the interpreter
  • hais description of hardware automation interfaces HAI with IP number and a device to relay map.
  • list of assembly devices which are typically a microcontroller or microprocessor board, debugger, network interfaces, test equipment, analysis & measurement devices and other devices which can be switched on and off by the HAI. If applicable IP address and nominal supply are defined as well.
  • wired_connections describe communication path between the devices with different categories like DEBUG, USB, CAN_FD, ETH and others.
  • multiplexers can be used for setup variants like transceiver type selection.

An Assembly description file may be provided with a minimum set of information for complex HiLs. Automation is based here in most cases on a Vector VT System and an ePlan documentation.