RidgeRun Video Stabilization Library/API Reference/Adding New Sensors: Difference between revisions

Line 18: Line 18:


=== Defining the Start method ===
=== Defining the Start method ===
This method receives a constant Sensor Parameter configuration. This configuration is conformed of the frequency that the sensor has to cover (in Hz), the sample rate of the measurements (in Hz) and the sensor id that helps to distinguish the number of the sensor connected.  
This method receives a constant Sensor Parameter configuration. This configuration includes the sensor's operating frequency (in Hz), the sample rate of the measurements (in Hz), and the sensor ID, which helps distinguish the connected sensors.  


<syntaxhighlight lang=c++>
<syntaxhighlight lang=c++>
Line 32: Line 32:


=== Defining the Stop method ===
=== Defining the Stop method ===
This method ends disables the possibility to receive data from the sensor when it is called. It does not receive any parameter, so the logic to stop the sensor is managed internally.
This method disables data reception from the sensor when called. It does not receive any parameters, so the logic to stop the sensor is managed internally.
   
   
<syntaxhighlight lang=c++>
<syntaxhighlight lang=c++>
Line 46: Line 46:


=== Defining the Get method ===
=== Defining the Get method ===
This method gets data from the IMU sensor. It receives a sensor payload parameter that is conformed of data from the accelerometer(m/s2), gyroscope (milligravitational) and magnetometer (if needed). The data of each of this is defined as: x-asis data, y-axis data and z-axis data, with its correspondent timestamp (in microseconds). The values received from the measurements must be saved on the payload to expose it to the user-space.  
This method gets data from the IMU sensor. It receives a sensor payload parameter that consists of data from the accelerometer (m/), gyroscope (milligravitational), and magnetometer (if needed). The data for each axis (x, y, z) includes the corresponding timestamp (in microseconds). The measured values must be saved in the payload to be accessible to the user-space.


<syntaxhighlight lang=c++>
<syntaxhighlight lang=c++>
102

edits