Architecture:Unique Event Codes - Revision history

Jlblanco: /* Normalized events for modules with standardized "Function Executor IF" */

2009-05-28T21:11:23Z

‎Normalized events for modules with standardized "Function Executor IF"

2009-05-24T22:17:26Z

‎Special cases

2009-05-22T22:44:43Z

‎Normalized events for HAD modules

2009-05-22T10:11:21Z

‎Normalized events for HAD modules

2009-05-22T09:59:30Z

‎Normalized events for HAD modules

2009-05-22T09:58:57Z

‎Normalized events for HAD modules

2009-05-22T09:58:35Z

‎Normalized events for modules with the standardized "Common Sensory IF"

2009-05-22T09:58:06Z

‎Normalized events for modules with the standardized "Common Sensory IF"

2009-05-17T21:55:44Z

‎Normalized events for modules with the standardized Common Sensory IF

2009-05-17T21:47:05Z

‎Event Codes

@@ Line 60: / Line 60: @@
 <tr><td>BA_Speech</td> <td>2000</td></tr>
 <tr><td>FE_HumanRobotInterfaces	</td> <td>2500</td></tr>
-<tr><td>FE_ReactiveNavigation	</td> <td>2505</td></tr>
+<tr><td>FE_ReactiveNavigation	</td> <td>60: End Navigation<br> 70: Error navigation <br> 80: Start navigation </td></tr>
 <tr><td>FE_PathFollowing	</td> <td>2510</td></tr>
 <tr><td>FE_DoorOpening	</td> <td>2515</td></tr>

@@ Line 67: / Line 67: @@
 </center>
-== Special cases ==
+== Others ==
 <center>
 <table border="1">
 <tr><td>'''Module name'''</td>
-<td>'''Code for onActionTermination events'''</td></tr>
+<td>'''Event code'''</td></tr>
-<tr><td>DRV_SPEECH</td> <td>5000</td></tr>
+<tr><td>Localization_Publisher</td> <td>6000 (On new estimate available)</td></tr>
 </table>
 </center>

@@ Line 20: / Line 20: @@
 <tr><td>HAD_Laser_Hokuyo:0-3</td><td> 1205:1208 (on new laser scan) </td></tr>
 <tr><td>HAD_MobileBase_Simulator</td><td> 1210 (on new laser scan) </td></tr>
 <tr><td>...</td><td>  </td> </tr>
 </table>

@@ Line 19: / Line 19: @@
 <td>'''Code for onNewObservation events'''</td>
 <tr><td>HAD_Laser_Hokuyo:0-3</td><td> 1205:1208 (on new laser scan) </td></tr>
 <tr><td>...</td><td>  </td> </tr>
 </table>

@@ Line 19: / Line 19: @@
 <td>'''Code for onNewObservation events'''</td>
 <tr><td>HAD_Laser_Hokuyo:0-3</td><td> 1205:1208 (on new laser scan) </td></tr>
-<tr><td>...</td><td>  </td><td>  </td></tr>
+<tr><td>...</td><td>  </td> </tr>
 </table>
 </center>

@@ Line 12: / Line 12: @@
-== Normalized events for modules with the standardized "Common Sensory IF" ==
+== Normalized events for HAD modules ==
 <center>
@@ Line 21: / Line 21: @@
 <tr><td>HAD_Laser_Hokuyo:0-3</td><td> 1205:1208 (on new laser scan) </td><td>-</td></tr>
 <tr><td>...</td><td>  </td><td>  </td></tr>
 <tr><td>BS_IncrementalEgoMotion</td><td>1000</td><td>1001</td></tr>
 <tr><td>BS_RangeSensors	</td><td>1005</td><td>1006</td></tr>

← Older revision		Revision as of 21:47, 17 May 2009
Line 9:		Line 9:
	Events are a form of asynchronous communications between modules allowed by the BABEL framework. Each event is represented by a symbolic name within each module, but nothing avoids two programmers to accidentally set the same value for different events.		Events are a form of asynchronous communications between modules allowed by the BABEL framework. Each event is represented by a symbolic name within each module, but nothing avoids two programmers to accidentally set the same value for different events.

−	To avoid such problems, '''please, use and update''' these tables to ensure that ~~events~~ IDs remain unique.	+	To avoid such problems, '''please, use and update''' these tables to ensure that event IDs remain unique.