FAQs

Overview

We have prepared a few frequently asked questions and answers concerning use of our T&D WebStorage API. We are continually trying to improve this section by making changes and additions upon the receipt of user questions and comments.

FAQs

Q. What are “Current Readings”?

A. Current readings refer to the most recent recorded data readings sent from the device to T&D WebStorage Service.
Because data may have not been sent for some time, the “most recent" data will be the most recently sent data and therefore may not be “current" in the sense of “now".
These readings may be but are not always real time current values.

Q. What is meant by “Current Readings Graph”?

A. Current Readings Graph refers to the archive of data that has been sent by the device to the T&D WebStorage Service. Depending upon the model type there are difference in the stored data. See below for details.
Note that T&D WebStorage Service receives recorded data in TRZ format files. This data is referred to as “Recorded Data (TRZ format)" and is not the same data as in Current Readings Graphs.

Model Upper Limit for Number of Stored Readings
in Current Readings Graph
Current Readings Graph Display
TR7A, TR-7wb/nw/wf series Up to 450 days of data The recorded data at the set recording interval is stored as a Current Readings Graph.
The number of days of data changes depending on the recording interval set for the device. For details see T&D WebStorage Service Details.
TR4A Series Up to 450 days of data The recorded data at the set recording interval is stored as a Current Readings Graph.
In addition, if ThemoREC monitoring data is set to be stored at T&D WebStorage, then the monitoring data will also be stored in the data of the Current Readings Graph. (TR41/42/45 only)
The number of days of data changes depending on the recording interval set for the device. For details see T&D WebStorage Service Details.
RTR500B Series (via HTTPS) Up to 450 days of data Of the current readings data sent by the RTR500B series Base Unit, up to 10 measurements are saved for display in the Current Readings graph.
For details about the number of measurements included in the current readings data see the following: "Q. How many measurements are included in one current readings data?"
The number of days of data changes depending on the recording interval set for the Remote Unit. For details see T&D WebStorage Service Details.

The recorded data at the set recording interval in each of the Remote Units is handled as TRZ format file data and is not compatible with Current Readings Graph.
RTR-500 Series,
RTR500B Series (via FTP)
1,500 readings For both RTR-500 and RTR500B Series Base Units, the current readings sent by XML file using FTP transmission are saved as a single piece of data with the time stamp at the time of transmission.
Therefore the recording interval settings in the Remote Units becomes unrelated and the archived data is that of the set of current readings at the time of transmission from the Base Unit.

The recorded data at the set recording interval in each of the Remote Units is handled as TRZ format file data and is not compatible with Current Readings Graph.
TR32B Up to 450 days of data The recorded data at the set recording interval is stored as a Current Readings Graph.
The number of days of data changes depending on the recording interval set for the device. For details see T&D WebStorage Service Details.
TR-700W Series 1,500 readings The archive is of current readings XML file data that was stored at the time of auto-upload to T&D WebStorage.

The recorded data at the set recording interval in each of the Remote Units is handled as TRZ format file data and is not compatible with Current Readings Graph.

Q. How does T&D WebStorage Service use Current Readings data?

The Current Readings data sent from RTR-500 series, TR-700W series, TR7A and TR-7wb/nw/wf series, TR4A series, TR32B, and RTR500B Series Base Units includes the most recently measured value of the target device(s) and several other measurements for that device.
T&D WebStorage Service stores the most recently measured value as a value that appears in the list of current readings in the "Data View" window.
In the case of TR7A and TR-7wb/nw/wf series, TR4A series, and RTR500B series (via HTTPS), the measured values are also stored for the Current Readings Graph, which can be retrieved using "Get Latest Data (300 most recent readings)”.
*The measured values transmitted from RTR-500 series and TR-700W series are also stored as Current Readings Graph data that can be displayed in a browser, but due to the use of a different storage format, acquisition from this API is currently not supported.

Q: Can I display the T&D WebStorage data in my own HTML content?

A. In order to reduce security risks, the open API does not support responses in JSONP format. Therefore, it is not possible to send a direct request from JavaScript in your HTML content to our open API and receive a response.

If you wish to use data retrieved from our open API in JavaScript on your own HTML content (hereafter referred to as “User JS"), please refer to the following method.
1) Create an server-side application that can be sued with our open API (Refer the provided Sample Program below).
2) Access the open API, and store the received JSON formatted response contents in a file name such as “response.json" in an environment that can be read by the User JS.
3) Have the User JS read the above “response.json” file and output it after having carried out the necessary formatting.

If you wish to have regular updates to the HTML content, periodically access the open API as in 2) above and update the “response.json" file.
*It is necessary to make sure that “response.json” is not cached.

Please note that we have designed our open API in this manner so as to avoid the risk of handling important authentication information in JavaScript and avoid the risk associated with releasing responses in JSONP format.

Q. Why is there a set “Rate Limit”?

A: To ensure that all users have fair access to and use of T&D WebStorage Service, we have made certain settings to distribute load.
We will continually reevaluate and fine tune these settings as deemed necessary according to usage of our open API and our server conditions.

MENU