tutorial-service-enocean.md

@@ -33,9 +33,17 @@ Every EnOcean device has to have an entry in the Address Management of ENOSAR. A
 A entry for a device has:
 * Identifier: An unique ID in ENOSAR to identify the device (ENOSAR ID)(e.g.: switch1, socket1)
 * Technology: For the EnOcean Service `org.enosar.service.io.enocean`
-* Receiver Information: Consists out of 2 information's. The EnOcean device ID and the packet description. The syntax is `0x[EnOcean ID in hex].[EEP]`:
+* Receiver Information: Consists out of 2 information's. The EnOcean device ID and the EEP packet description. The syntax is `0x[EnOcean ID in hex].[EEP]`:
     * EnOcean ID: Is the unique ID of the EnOcean device. The EnOcean ID is displayed in the terminal when the device sends a message and is not in the Address Management.
-    * EEP: Describes the data packet that is sent of the device. This information can be found in the manual of the device (EnOcean Equipment Profile (EEP)). All implemented data packets are listed in [Implemented Devices/Packets](#implDev)
+    * EEP: Describes the data packet that is sent of the device. This information can be found in the manual of the device (EnOcean Equipment Profile (EEP)). All in ENOSAR implemented data packets are listed in [Implemented Devices/Packets](#implDev)
+
+Here is an example for an entry in the Address Management:
+
+![enoceanAddress](/uploads/a44fdb345e7fb7315aa192c221fae7fe/enoceanAddress.png)
+
+Here is an example where you can see de EnOcean ID of an device in the console:
+
+![enoceanAdr](/uploads/7e40d255175221352020909319cdbedb/enoceanAdr.png)
 
 If the device has a teach in function the EEP entry is not necessary. The teach in adds the Packed description automatically when a teach in is done.