This SAW component allows to stream data from most cisst/SAW components with little or no new code. It compiles on Windows, Linux and likely MacOS. It has been tested with:

• Linux
• Streaming prmStateJoint data from sawIntuitiveResearchKit and sawIntuitiveDaVinci

It currently supports UDP sockets and the data is serialized using the JSON format. It is used to stream data from the different da Vinci robots (at JHU) to HoloLens displays. On the HoloLens side, one can use the open source package dvrk-xr. It can be used to receive and send data to any other SAW component (see https://github.com/jhu-cisst/cisst/wiki/cisst-libraries-and-SAW-components)

Based on user requests, we could add:

• TCP support
• Different serialization formats (plain text, binary...)

• License: http://github.com/jhu-cisst/cisst/blob/master/license.txt
• JHU-LCSR software: http://jhu-lcsr.github.io/software/

• cisst libraries: https://github.com/jhu-cisst/cisst

You can create and add the mtsSocketStreamer component manually in your main C/C++ code but we strongly recommend using the cisstMultiTask manager ability to load a configuration file to add and connect components. Most cisst/SAW (including dVRK) programs have already been updated with the code below so you likely don't need to add this and can skip to the next section. See https://github.com/jhu-dvrk/sawIntuitiveResearchKit/blob/master/applications/mainQtConsoleJSON.cpp.

There is first a command line option to specify one or more configuration files for the component manager:

    cmnCommandLineOptions options;
    std::list<std::string> managerConfig;
    options.AddOptionMultipleValues("m", "component-manager",
                                    "JSON files to configure component manager",
                                    cmnCommandLineOptions::OPTIONAL_OPTION, &managerConfig);

Then one has to use the configuration files to configure the component manager:

    mtsManagerLocal * componentManager = mtsManagerLocal::GetInstance();
    if (!componentManager->ConfigureJSON(managerConfig)) {
        CMN_LOG_INIT_ERROR << "Configure: failed to configure component manager, check cisstLog for error messages" << std::endl;
        return -1;
    }

The configuration files for the component manager will look like (more examples can be found at https://github.com/jhu-dvrk/sawIntuitiveResearchKit/tree/master/share/socket-streamer):

/* -*- Mode: Javascript; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
{
    "components":
    [
        {
            "shared-library": "sawSocketStreamer",
            "class-name": "mtsSocketStreamer",
            "constructor-arg": {
                "Name": "streamerMTML",
                "Period": 0.01
            },
            "configure-parameter": "streamerMTML.json"
        }
        ,
        {
            "shared-library": "sawSocketStreamer",
            "class-name": "mtsSocketStreamer",
            "constructor-arg": {
                "Name": "streamerMTMR",
                "Period": 0.01
            },
            "configure-parameter": "streamerMTMR.json"
        }
    ]
    ,
    "connections":
    [
        {
            "required": {
                "component": "streamerMTML",
                "interface": "Required"
            }
            ,
            "provided": {
                "component": "MTML",
                "interface": "Robot"
            }
        }
        ,
        {
            "required": {
                "component": "streamerMTMR",
                "interface": "Required"
            }
            ,
            "provided": {
                "component": "MTMR",
                "interface": "Robot"
            }
        }
    ]
}

Each component created need a configuration file that specifies which read command to use to retrieve the data as well as the data type. For example:

/* -*- Mode: Javascript; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
{
    "ip": "10.194.86.119",
    "port": "48054",
    "read-commands": [
        {
            "name": "measured_js",
            "type": "prmStateJoint"
        }
    ]
    ,
    "void-commands": ["hold", "free"]
    ,
    "write-commands": [
        {
            "name": "servo_jp",
            "type": "prmPositionJointSet"
        }
    ]
    ,
    "write-events": ["operating_state"]
}

To test the read commands and events, you can use the nc tool on Linux. The main options are l to listen and u for UDP protocol. Then you need to add the IP address and port. With the example above, try:

nc -lu 10.194.86.119 48054

At that point you should see a continous stream of text in JSON format.

To test the void and write commands, you need to create your own code and send the command name and payload in JSON format. For void commands, send an empty string (""). You can find an example in Python in the sawIntuitiveResearchKit repository under share/socket-streamer: https://github.com/jhu-dvrk/sawIntuitiveResearchKit/blob/devel/share/socket-streamer/example.py

This is based on code that can be found in the share directory. This code was originally written by An Chi Chen and Muhammad Hadi when they were students at Johns Hopkins. Their goal was to visualize and control a dVRK PSM from Unity.

The main parts are setting up the socket in the start():

    // udp using socket
    data = new byte[1024];
    IPEndPoint ip = new IPEndPoint(IPAddress.Any, 48051);    // ensure that this port is the same as the one youre sending data from
    socket = new Socket(AddressFamily.InterNetwork, SocketType.Dgram, ProtocolType.Udp);
    socket.Bind(ip);
    IPEndPoint sender = new IPEndPoint(IPAddress.Any, 0);
    remote = (EndPoint)(sender);

And then you can read from the socket using:

    // read in message from dVRK
    data = new byte[1024];
    socket.ReceiveFrom(data, ref remote);
    dVRK_msg = Encoding.UTF8.GetString(data);    // dVRK_msg will then contain the data

Finally an example of how you would send data:

    // send json strings to dVRK
    send_msg = Encoding.UTF8.GetBytes(pose_message);    // pose_message is string to send
    socket.SendTo(send_msg, remote);