Changes between Version 9 and Version 10 of Software/GatewayDBus

Timestamp:

07/20/10 14:55:46 (14 years ago)

Author:

art

Comment:

--

Software/GatewayDBus

@@ -50 +50 @@
    ]
 }}}
-Here the first byte of the signal indicates the '''source''' node of the IBus, here 192=0xC0, and the second byte indicates the '''destination''' node, here 104=0x68. The third component of the message is always an unsigned integer indicating the amount of '''data''' passed with the message, in this example 2 bytes. And lastly an array containing the data bytes is submitted, in this case {50=0x32, 16=0x10}. 
+Here the first byte of the signal indicates the '''source''' node of the IBus, here 192=0xC0='''MID''', and the second byte indicates the '''destination''' node, here 104=0x68='''RADIO'''. The third component of the message is always an unsigned integer indicating the amount of '''data''' passed with the message, in this example 2 bytes. And lastly an array containing the data bytes is submitted, in this case {50=0x32, 16=0x10}. 
 
-Signals in this form received over the D-Bus are accepted by OpenBM-Gateway and translated into IBus message frames and sent over the wire.
+Signals in this form received over the D-Bus are accepted by OpenBM-Gateway and translated into IBus message frames. Finally they are sent over the wire. There is collision/retransmit logic implemented in the software, so the probability that message will be not delivered is very low.
+
+== FAQ ==
+
+1. ''When starting '''openbm-gateway''' I see following error message:''
+{{{
+error: D-Bus Connection Error (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
+}}}
+This error is typically caused by missing rights to connect to the D-Bus or when executed by the root. Correct the user rights to allow connections to the D-Bus.
 
 ----