Changes between Version 4 and Version 5 of Burt-Research/SystemOverview


Ignore:
Timestamp:
Jan 17, 2018, 10:41:25 PM (16 months ago)
Author:
al
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Burt-Research/SystemOverview

    v4 v5  
    1313
    1414CoAP communicates based on Representational State Transfer (REST) architecture and supports four modes of REST which are PUT, GET, POST, and DELETE. A client sends a request with any one of the four modes and the server will respond with a reply in accordance with the request. The CoAP supports two modes: reliable and non-reliable. For instance, we use the reliable mode for activating the robot and non-reliable mode for sending force data. Reliability in CoAP is handled by using Confirmable (CON) messages. For every CON message send to the server, this will be replied by Acknowledge (ACK) packages to the client. In essence, CoAP's job is to define the URI structure (a hierarchy of objects accessible by GET/POST); handle GET/POST requests; handle the ACKs for confirmable transmissions; deal with dropped, reordered, or duplicate packets. MessagePack's job is to encode/decode structured data without resorting to encoding numbers as text.
     15
     16== Software Architecture - Hierarchy ==
     17
     18The below software architecture illustrates the hierarchy of the two libraries that the Research Environment consists of. BurtSharp is a C# client program to communicate with the Mainboard firmware through a CoAP/UDP-based server to control the BURT robot, and BurtSharp.UnityInterface is an extension to BurtSharp that allows use with Unity. Researchers can use these two libraries to test the control and haptic capabilities and can develop their own research tools.
     19
     20
     21{{{
     22#!div class="left" align="left"
     23
     24[[Image(htdocs:therapy/SystemOverview/SystemArchitecture.PNG)]]
     25
     26}}}
     27
    1528
    1629== BurtSharp Message Types ==