Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Tutorials » Control a Single Motor
getting_started:tutorials:oneaxis

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
getting_started:tutorials:oneaxis [2019/10/14 16:28] – [Develop your own Application] grafgetting_started:tutorials:oneaxis [2026/05/28 14:08] (current) – [Test Application] ursgraf
Line 15: Line 15:
  
 =====Experimental Setup===== =====Experimental Setup=====
-A maxon motor controller (50V / 5A) delivers the necessary power. The motor we use has the following properties:+The motor we use has the following properties:
  
 |  **Properties**              ^  Value            ^  Unit         ^ |  **Properties**              ^  Value            ^  Unit         ^
Line 26: Line 26:
   * [[oneaxis_bbb|]]     * [[oneaxis_bbb|]]  
   * [[oneaxis_cb20|]]   * [[oneaxis_cb20|]]
 +  * [[oneaxis_microzed|]]
  
 =====Build Application===== =====Build Application=====
  
-  - Download EEROS, hardware wrapper libraries, and simple motor application described in [[getting_started:install_and_setup_development_environment|]]. Make sure that the following entry in ''config.sh.in'' is as follows <code> +  - Proceed with [[getting_started:write_app|]] and select the right target. Scroll down to ''Use Existing Project''. 
-use_custom_application=true +  - After cloning the project, navigate to the directory ''simple-motor-control'' where you can find the code of the application.
-</code> +
-  - After cloning with the clone script, navigate to the directory ''simple-motor-control'' where you can find the code of the application. +
-  - [[getting_started:compile_eeros|]] together with the application.+
   - [[getting_started:deploy|]] to the target system if necessary.   - [[getting_started:deploy|]] to the target system if necessary.
  
-=====Test Application=====+=====Run Application=====
  
 You will find different hardware configuration files depending on the hardware platform. You will find different hardware configuration files depending on the hardware platform.
   * HwConfigComedi.json   * HwConfigComedi.json
-  * HwConfigFlink.json +  * HwConfigFlinkCB20.json 
-  * HwConfigBBB.json+  * HwConfigBBBlue.json 
 +  * HwConfigFlinkMicrozed.json
  
 Start our application by choosing the appropriate configuration file, e.g.: Start our application by choosing the appropriate configuration file, e.g.:
Line 47: Line 46:
 $ sudo ./simpleMotorControl -c HwConfigBBB.json $ sudo ./simpleMotorControl -c HwConfigBBB.json
 </code> </code>
 +The application starts and will soon enter the //powerOn// safety level. Upon pressing the //ready// button, the motor will first do a homing and will then start moving. While moving the motor position is logged once per second. By activating the emergency button, the safety system will immediately switch to an emergency state. Deactivating this button causes the system to switch back to the //powerOn// mode.
  
 ===== Develop your own Application Further ===== ===== Develop your own Application Further =====
-For further development we recommend to use an integrated development environment as described in [[getting_started:say_hello|]]. You do not have to create a new project, because you already have downloaded and built the simple motor controller project. Hence, you import the project together with the EEROS and wrapper libraries into KDevelop as described in [[getting_started:say_hello#Use_KDevelop_with_Existing_Build_Configuration|Use KDevelop with Existing Build Configuration]].+For further development we recommend to use an integrated development environment as described in [[getting_started:kdevelop|]]. You do not have to create a new project, because you already have downloaded and built the simple motor controller project. Import the project together with the EEROS and wrapper libraries into KDevelop or Visual Studio Code.
  
  
Line 58: Line 58:
 ==== Safety System ==== ==== Safety System ====
 Safety levels and events are declared in ''SMCSafetyProperties.hpp''. ''SMCSafetyProperties.cpp'' initializes these objects, defines critical inputs and outputs, defines level actions, and adds the levels to the safety system. The levels and events causing transitions between those levels are shown in the next figure. Safety levels and events are declared in ''SMCSafetyProperties.hpp''. ''SMCSafetyProperties.cpp'' initializes these objects, defines critical inputs and outputs, defines level actions, and adds the levels to the safety system. The levels and events causing transitions between those levels are shown in the next figure.
-[{{ :getting_started:tutorials:safetysystemoneaxis.png?600 |//Safety levels and events//}}]+[{{ :getting_started:tutorials:safetysystemoneaxis.jpg?700 |//Safety levels and events//}}]
  
-Two critical inputs are defined: "emergency" and "readySig1". "enable" is a critical output. Critical inputs and outputs are checked and set by each safety level. For example "enable" is set to ''true'' as soon as the safety level is equal or higher than ''powerOn''. "emergency" is unchecked for the two lowest levels and leads to level change to level ''emergency'' for higher levels. +A critical input is defined: //emergency//. //enable// is a critical output. Critical inputs and outputs are checked and set by each safety level. For example //enable// is set to ''true'' as soon as the safety level is equal or higher than //powerOn//. //emergency// is unchecked for the two lowest levels and leads to level change to level //emergency// for higher levels. 
  
 ==== Sequencer ==== ==== Sequencer ====
-The sequencer runs a sequence which turns the motor each second a tenth of a full turn. +The sequencer does the homing and runs a moving sequence which turns the motor each second a tenth of a full turn. 
getting_started/tutorials/oneaxis.1571063322.txt.gz · Last modified: by graf