Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » For Developers » signal_probe_block
for_developers:signal_probe_block

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
for_developers:signal_probe_block [2016/08/15 15:53] – [The csv file] gehrigfor_developers:signal_probe_block [2017/09/24 15:36] – [How the signal probe block works] graf
Line 2: Line 2:
  
 ===== How the signal probe block works ===== ===== How the signal probe block works =====
-The //signalProbeBlock// can be connected to signals like every other block. The //signalProbeBlock// saves the value and the timestamp of each connected signal after each call in a buffer. If the buffer is full, the oldest value will be overridden. The size of the buffer is about 10'000 values, which holds about 10 seconds of data. The size of the buffer can be defined at the declaration of the //signalProbeBlock//. 
  
-The measurement stops when the application is terminated or it can be stopped, when a certain safety level is reached. At the end, the measurements are written in a file with a csv compatible format. +===== How to implement the signalProbeBlock =====
- +
-The measured data is written in a buffer in RAM because writing in a file would influence the real time performance of the system. +
- +
-===== How to implement the //signalProbeBlock// =====+
 To use the //signalProbeBlock// code has to be implemented at three different places. If the measurement should be stopped by a level change of the safety system, some lines of code have to be added to the safety system. To use the //signalProbeBlock// code has to be implemented at three different places. If the measurement should be stopped by a level change of the safety system, some lines of code have to be added to the safety system.