diff --git a/images/E4_streaming_server_scheme.jpg b/images/E4_streaming_server_scheme.jpg new file mode 100644 index 0000000..255014f Binary files /dev/null and b/images/E4_streaming_server_scheme.jpg differ diff --git a/stylesheets/stylesheet.css b/stylesheets/stylesheet.css index 3ee522f..94d7e25 100644 --- a/stylesheets/stylesheet.css +++ b/stylesheets/stylesheet.css @@ -244,6 +244,20 @@ ul, ol, dl { margin-bottom: 20px; } +figure { + margin: 30px; +} + +figure img { + display: block; + height: auto; + margin-left: auto; + margin-right: auto; +} + +figcaption { + padding: 10px; +} /* COMMON STYLES */ diff --git a/windows-streaming-server-commands.html b/windows-streaming-server-commands.html index f056534..5ce16af 100644 --- a/windows-streaming-server-commands.html +++ b/windows-streaming-server-commands.html @@ -54,7 +54,7 @@
Updated May, 2018

- General message structure + General Message Structure

@@ -86,12 +86,12 @@

- Commands and Responses Details + Commands and Responses Details

- List of discovered BTLE devices (manual BTLE) + List of Discovered BTLE Devices (Manual BTLE)

@@ -120,7 +120,7 @@

The strings allowed and not_allowed indicate if the devices are allowed to be used with the given API key.

- Connect device over BTLE (manual BTLE) + Connect Device over BTLE (Manual BTLE)

@@ -145,7 +145,7 @@

- List of devices connected over BTLE + List of Devices Connected over BTLE

@@ -170,8 +170,8 @@

-

- Connect to a Device +

+ Connect to a Device

@@ -198,7 +198,7 @@

- Disconnect from a Device + Disconnect from a Device

@@ -217,8 +217,8 @@

-

- Subscribe and Unsubscribe to Data Stream +

+ Subscribe and Unsubscribe to Data Stream

@@ -262,7 +262,7 @@

- Suspend and resume data streaming + Suspend and Resume Data Streaming

@@ -286,7 +286,7 @@

To pause the stream specify ON and to resume OFF.

-

Protocol Example (no manual BTLE)

+

Protocol Example (no Manual BTLE)

[OPEN TCP CONNECTION]
@@ -312,7 +312,7 @@ 

[EOF]

-

Protocol Example (manual BTLE)

+

Protocol Example (Manual BTLE)

[OPEN TCP CONNECTION]
diff --git a/windows-streaming-server-usage.html b/windows-streaming-server-usage.html
index fb9f32a..8423817 100644
--- a/windows-streaming-server-usage.html
+++ b/windows-streaming-server-usage.html
@@ -54,7 +54,7 @@ 
Updated May, 2018

- Requirements + Requirements

    @@ -65,13 +65,13 @@

- Installation + Installation

Download the latest release of the E4 streaming server for Windows from here

- Configuration + Configuration

The first time you start the server you will see the settings panel that allows you to set:

@@ -87,7 +87,7 @@

Click the "Save" button after the configurations are made.

- Using the server + Using the server

You will see the default view of the server, click the "Start" button.

@@ -115,7 +115,7 @@

- Running the server from other code or scripts + Running the Server from Other Code or Scripts

The E4 streaming server can be run without GUI, passing the connection information and API key as startup arguments:

@@ -129,7 +129,7 @@

When running the E4 streaming server without GUI, the settings won't be saved and are only active during this execution. Also, BTLE connections have to be handled manually through the commands.

- Troubleshooting + Troubleshooting

When I click "Save" in settings panel, I see the "Invalid Api key" message diff --git a/windows-streaming-server.html b/windows-streaming-server.html index 57a13be..434f53e 100644 --- a/windows-streaming-server.html +++ b/windows-streaming-server.html @@ -57,7 +57,12 @@
Updated May, 2018

The E4 streaming server allows to forward realtime data of multiple Empatica E4 devices to multiple TCP socket connections. Please note that each TCP connection can receive data from only one Empatica E4 device. To connect to multiple devices, multiple TCP connections are required.
The E4 streaming server is intended to make the data streams available to scripts and applications. However, the data streams can also be easily accessed e.g. for testing purposes with Telnet.

- + +
+ +
Figure 1: Illustration of the connectivity and function of the E4 streaming server. On one side are E4s, connected over BTLE to the E4 streaming server using the BLED112 dongle. On the other side are TCP clients, connected to the E4 streaming server through TCP connections over the network. The lines originating from the E4s illustrate the data flow from the E4 through the E4 streaming server to the subscribed TCP client. For example, the data from the first E4 is forwarded by the E4 streaming server to the first and third TCP client.
+
+

Getting Started