Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Tutorials » controlsystem3
getting_started:tutorials:controlsystem3

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
Next revisionBoth sides next revision
getting_started:tutorials:controlsystem3 [2019/03/11 10:02] – grafgetting_started:tutorials:controlsystem3 [2020/01/29 15:12] – graf
Line 11: Line 11:
 The system uses an output. For this reason you will need to install a simple simulator, see [[getting_started:install_wrapper#simulator|]]. The following command will run the example  The system uses an output. For this reason you will need to install a simple simulator, see [[getting_started:install_wrapper#simulator|]]. The following command will run the example 
 <code> <code>
-$ ./blockTest2 -c BlockTest2Config.json+$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./blockTest2 -c BlockTest2Config.json
 </code> </code>
  
Line 19: Line 19:
   - In order to test what happens if you read from an unconnected input comment line number 44 and recompile. This removes the connection between the constant block and the gain block. As soon as the time domain tries to run the gain block a ''NotConnectedFault'' is thrown. This causes the time domain to trigger a ''go to emergency'' event. In the safety level ''emergency'' the time domain is stopped to prevent further faults.   - In order to test what happens if you read from an unconnected input comment line number 44 and recompile. This removes the connection between the constant block and the gain block. As soon as the time domain tries to run the gain block a ''NotConnectedFault'' is thrown. This causes the time domain to trigger a ''go to emergency'' event. In the safety level ''emergency'' the time domain is stopped to prevent further faults.
   - Please add line 44 and remove line 39, recompile and run the test. The constant block has no value assigned to it. This causes the time domain to calculate the peripheral output value to be NaN and a ''NaNOutputFault'' is thrown. This causes the time domain to trigger a ''go to emergency'' event. In the safety level ''emergency'' the time domain is stopped to prevent further faults.   - Please add line 44 and remove line 39, recompile and run the test. The constant block has no value assigned to it. This causes the time domain to calculate the peripheral output value to be NaN and a ''NaNOutputFault'' is thrown. This causes the time domain to trigger a ''go to emergency'' event. In the safety level ''emergency'' the time domain is stopped to prevent further faults.
-