Expected Behavior

Per wiki "Getting Started With a Raspberry Pi 3 and the Bosch XDK": "The sensors from the XDK should now be visible in the Sensors & Devices app in the web user interface."

Actual Behavior

After last step in wiki (bin/Linux/armv7l/macchina), got the following result:
bin/Linux/armv7l/macchina: error while loading shared libraries: libPocoOSP.so.2: cannot open shar

Describe the bug
The device controlboard has been deprecated in favor of controlboardwrapper2. Therefore, the documentation available at http://www.yarp.it/yarp_without_yarp.html that relies on controlboard for the test scenario needs to be updated accordingly.

To Reproduce
Launch:

$ yarpdev --device controlboard --subdevice test_motor --name /motor --axes 5

**Sc

A task to document the design of the POC implementation, mostly to get feedback from other devs without them having to dig through code.

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All

We call spin_log() in main() (while processing the command line arguments). spin_log_init() is called afterwards. This means that we potentially call spin_log() while the log has not been initialized yet. In particular, this means that log messages generated while processing the command line arguments do not appear on stdout even if we specify -o (but go to syslog instead).

Should we

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All

Only some of the pages have even 1 comment on them and even then, it is by no means comprehensive enough. If someone could take the time to comment the code. that would be great.

Heres a list of files for yas to look at:

• includes/functions.inc.php (Most Important, as it is the most complex).
• includes/headers.inc.php.
• includes/nav.inc.php.
• _article/

Add documentation for each method within this client library that maps to an M2X API call.

Guidelines & Tips:

• Use appropriate syntax for this programming language
• Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
• All