The ArbitratorService is used to control robotic systems using behaviours. The following setting options are currently available.

Adding a behaviour.

XML configuration

Important note: The availability of a service depends on the license purchased and whether the service has been registered in the configuration file ./etc/factory.xml of the Service Factory (changes require server restart!). There you will also find the responsible configuration file for a service, otherwise you can also edit the configuration file of the service directly in the GUI of the service (changes require a service restart!).

Adding a behaviour

A behaviour is represented by a class implementing a particular interface. Adding the behaviour is done by using a unique ID.

<Call name="addBehavior">
	<Arg>id</Arg>
	<Arg>
		<New class="com.ebd.example.ExampleBehavior"/>
	</Arg>
</Call>

Log level dependencies

Changes to the log level of the LogService have no influence on the logging behaviour of the ArbitratorService.

If the service is set to verbose, each time a behaviour is executed, it will be reported with the ID and the index involved.