9. Transmit stored data#

Terminal System v1.23.0

Data that could not be sent in real time due to network instability, or data that was blocked by filters and not sent in real time, is stored in the Terminal System as "unsent data".

When resend is turned on in [intdash] menu > [Sending / Receiving], unsent data is sent in parallel while real-time data is being sent. If a large amount of unsent data accumulates, it may take some time before all data is sent.

If you have turned off the resend process in [intdash] menu > [Sending / Receiving], the unsent data will not be resent automatically.

To transmit stored data efficiently, you can use the resend mode or download the data to a configuration PC.

9.1. Send only unsent data (resend mode)#

In resend mode, no new data will be acquired, only the stored data waiting for resend will be transmitted. The resend mode is performed according to the "Resending" settings in [intdash] > [Sending / Receiving]. See Configure settings for sending data to the server ([intdash] > [Sending / Receiving]) for details on the settings.

Attention

Clicking Resend Mode [Start] will restart the intdash service in resend mode, which will stop the running measurement.

To use the resend mode, go to [intdash] > [Status] and click Resend Mode [Start].

The decrease in unsent data indicates that resending is in progress.

After the resend is complete, please shut down the Terminal System. Alternatively, restart the intdash service and the next measurement will start in normal mode.

9.2. Resend the data to the server via the configuration PC ([intdash]> [Unsent Data])#

The data waiting for retransmission stored in the Terminal System can be downloaded to the configuration PC.

Data downloaded to the configuration PC can be uploaded to the intdash server using the dedicated application "intdash-edge-uploader".

This makes it possible to upload data later via an internal LAN, etc., even when all data cannot be uploaded at the time of measurement (e.g., when network bandwidth is limited).

Note

Please contact us for information on how to get the intdash-edge-uploader.

9.2.1. Uploading unsent data with intdash-edge-uploader (Windows)#

To download the data to the configuration PC and upload it to the intdash server, do the following.

Note

To perform the following steps, you will need intdash-edge-uploader.exe, a dedicated CLI application for Windows.

  1. In the [intdash] menu > [Unsent Data], click [Download].

    All the data stored in the Terminal System awaiting resend will be downloaded as a single zip file.

  2. Start a command prompt on the configuration PC.

  3. (Only if your Internet connection is available through a proxy server) Execute the following command to set the proxy server information in the command prompt.

    set HTTP_PROXY=http://[<user>:<pass>@]<ProxyAddress>[:<port>]
    set HTTPS_PROXY=http://[<user>:<pass>@]<ProxyAddress>[:<port>]
    
    • <user> : User name to access the proxy server (optional).

    • <pass> : Password for accessing the proxy server (optional).

    • <ProxyAddress> : IP address or name of the proxy server (FQDN).

    • <port> : Port number of the proxy server (optional).

    Example: If your proxy server is http://proxy.net with port 8080:

    set HTTP_PROXY=http://proxy.net:8080
    set HTTPS_PROXY=http://proxy.net:8080
    
  4. Type the following command to run intdash-edge-uploader.exe. The ^ (caret) is entered to escape newlines.

    C:\Users\UserName\> <path_to_intdash-edge-uploader> ^
    -s <ServerAddress> -e <EdgeUUID> -t <APIToken> ^
    <measurement_data>
    
    • <path_to_intdash-edge-uploader>: Path to the executable intdash-edge-uploader.exe.

    • <ServerAddress>: intdash server name.

    • <EdgeUUID>: The UUID of the edge which retrieved the data (the edge UUID assigned to the Terminal System).

    • <APIToken>: The user's API token (not the edge's client secret).

    • <measurement_data>: Full path of the downloaded unsent data (zip file).

    The following is an example of an actual command.

    C:\Users\UserName\> C:Users\UserName\Desktop\intdash-edge-uploader\Win64\intdash-edge-uploader.exe ^
    -s example.intdash.jp ^
    -e 01234567-0123-0123-0123-0123456789abcdef ^
    -t abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUV ^
    C:\Users\UserName\Desktop\000000001_1563766531.000000000
    

    Note

    Drag and drop the file icon to the command prompt to enter the path of the file. It is convenient to use this function when specifying the executable file or the measurement data.

  5. The intdash server's name and edge UUID will be displayed, make sure they are correct.

    Upload settings:
    - Server : example.intdash.jp
    - Edge UUID : 01234567-0123-0123-0123-0123456789abcdef
    
  6. When the transmission starts, the progress will be displayed as shown below.

    Processing...
    2/100% (232/239)
    

    Note

    The numbers in brackets on the right side of the percentage are "Remaining unsent data/total unsent data".

    When the transmission is complete, a list of transmitted measurements will be displayed and you will be returned to the original prompt.

  7. Exit the command prompt.

9.2.2. Uploading unsent data with intdash-edge-uploader (macOS)#

To download the data to the configuration PC and upload it to the intdash server, do the following.

Note

To perform the following steps, you will need intdash-edge-uploader, a dedicated CLI application for Mac.

  1. In the [intdash] menu > [Unsent Data], click [Download].

    All the data stored in the Terminal System awaiting resend will be downloaded as a single zip file.

  2. Start a terminal on the configuration PC.

  3. (Only if your Internet connection is available through a proxy server) Execute the following command to set the proxy server information in the command prompt.

    export HTTP_PROXY=http://[<user>:<pass>@]<ProxyAddress>[:<port>]
    export HTTPS_PROXY=http://[<user>:<pass>@]<ProxyAddress>[:<port>]
    
    • <user> : User name to access the proxy server (optional).

    • <pass> : Password for accessing the proxy server (optional).

    • <ProxyAddress> : IP address or name of the proxy server (FQDN).

    • <port> : Port number of the proxy server (optional).

    Example: If your proxy server is http://proxy.net with port 8080:

    export HTTP_PROXY=http://proxy.net:8080
    export HTTPS_PROXY=http://proxy.net:8080
    
  4. Type the following command to run intdash-edge-uploader. The \ (backslash) is entered to escape a newline.

    UserName$ <path_to_UploaderForMac> \
    -s <ServerAddress> -e <EdgeUUID> -t <APIToken> \
    <measurement_data>
    
    • <path_to_intdash-edge-uploader>: Path to the executable intdash-edge-uploader.

    • <ServerAddress>: intdash server name.

    • <EdgeUUID>: The UUID of the edge which retrieved the data (the edge UUID assigned to the Terminal System).

    • <APIToken>: The user's API token (not the edge's client secret).

    • <measurement_data>: Path of the downloaded unsent data (zip file).

    The following is an example of an actual command.

    UserName$ /Users/UserName/Desktop/intdash-edge-uploader/Darwin/intdash-edge-uploader \
    -s example.intdash.jp \
    -e 01234567-0123-0123-0123-0123456789abcdef \
    -t abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUV \
    /Users/UserName/Downloads/000000001_1563766531.000000000
    

    Note

    Drag and drop the file icon to the terminal and the path to the file will be entered. It is useful to use this function when specifying the executable file or the measurement data.

  5. The intdash server's name and edge UUID will be displayed, make sure they are correct.

    Upload settings:
    - Server : example.intdash.jp
    - Edge UUID : 01234567-0123-0123-0123-0123456789abcdef
    
  6. When the transmission starts, the progress will be displayed as shown below.

    Processing...
    2/100% (232/239)
    

    Note

    The numbers in brackets on the right side of the percentage are "Remaining unsent data/total unsent data".

    When the transmission is complete, a list of transmitted measurements will be displayed and you will be returned to the original prompt.

  7. Exit the terminal.