Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » EEROS Architecture » Hardware Abstraction Layer
eeros_architecture:hal:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
eeros_architecture:hal:start [2017/04/30 10:41] – [Hardware Abstraction Layer] grafeeros_architecture:hal:start [2017/11/30 19:42] – [Hardware Abstraction Layer] graf
Line 3: Line 3:
   * [[eeros_architecture:hal:using_hal|]]   * [[eeros_architecture:hal:using_hal|]]
   * [[eeros_architecture:hal:configuration_file|]]   * [[eeros_architecture:hal:configuration_file|]]
 +    * [[eeros_architecture:hal:scaling|]]
 +    * [[eeros_architecture:hal:scaling_multi|]]
 +    * [[eeros_architecture:hal:config_ros|]]
   * [[eeros_architecture:hal:feature_functions|]]   * [[eeros_architecture:hal:feature_functions|]]
   * [[eeros_architecture:hal:hardware_libraries|]]   * [[eeros_architecture:hal:hardware_libraries|]]
 +    * [[eeros_architecture:hal:hardware_libraries_sim|]] 
 +  * [[eeros_architecture:hal:input_devices|]]
 ===== Configuration of the HAL ===== ===== Configuration of the HAL =====
 The inputs and outputs of the system are given by a specific hardware setup. This can vary widely among different systems. To account for many possible hardware settings we use a configuration file. This file describes the current hardware together with the necessary library to access them, see [[Configuration File]]. The inputs and outputs of the system are given by a specific hardware setup. This can vary widely among different systems. To account for many possible hardware settings we use a configuration file. This file describes the current hardware together with the necessary library to access them, see [[Configuration File]].
Line 21: Line 25:
 Now, you can pass the configuration file with Now, you can pass the configuration file with
 <code> <code>
-$ ./myApplication --config     NameOfConfigurationFile +$ ./myApplication --config     /path/to/config/NameOfConfigurationFile 
-$ ./myApplication -c           NameOfConfigurationFile    // short version +$ ./myApplication -c           /path/to/config/NameOfConfigurationFile    // short version 
-$ ./myApplication --configFile NameOfConfigurationFile    // also possible +$ ./myApplication --configFile /path/to/config/NameOfConfigurationFile    // also possible 
-$ ./myApplication -f           NameOfConfigurationFile    // short version+$ ./myApplication -f           /path/to/config/NameOfConfigurationFile    // short version
 </code> </code>
 This call causes the following actions: This call causes the following actions:
Line 32: Line 36:
   * these objects will be registered in the HAL manager   * these objects will be registered in the HAL manager
 ===== Available HAL Objects ===== ===== Available HAL Objects =====
-All input objects of the HAL have a common type base type ''InputInterface'' while the output objects have a common type ''OutputInterface''. Digital inputs or outputs are of type ''Input<bool>'' or ''Output<bool> respectively. Analog inputs or outputs are of type ''ScalableInput<double>'' or ''ScalableOutput<double> respectively. \\+All input objects of the HAL have a common type base type ''InputInterface'' while the output objects have a common type ''OutputInterface''. Digital inputs or outputs are of type ''Input<bool>'' or ''Output<bool>'' respectively. Analog inputs or outputs are of type ''ScalableInput<double>'' or ''ScalableOutput<double>'' respectively. \\
 The following functions are available: The following functions are available:
 <code cpp> <code cpp>
eeros_architecture/hal/start.txt · Last modified: 2019/03/26 11:39 by gehrig