Performing remote configuration of our data loggers with ydocTerminal in combination with our Java Data Collector is straightforward. However, many clients — which we fully encourage — prefer to use their own (third-party or cloud-based) data collection software. Such platforms typically offer multiple ways to ingest data (for example, importing CSV files via FTP or receiving JSON messages via MQTT). Enabling interactive remote configuration through these systems, however, is a different matter and often requires substantial development effort, if it is possible at all.
To simplify this, we implemented a method that offloads configuration complexity from the developers of these platforms, allowing them to focus on what matters most: working with the collected data. The core idea is to provide a separate “side path” for configuration — a path that is only used when configuration is required, so it does not unnecessarily consume battery power.
This method uses a tunnel server that establishes secure, peer-to-peer encrypted communication channels between the data loggers and ydocTerminal.
When a user wants to configure a data logger, they can use ydocTerminal to schedule a “side-path” connection. This is done by sending a configuration request to the same MQTT broker, FTP server, or HTTP server that is already used by the data loggers and the data collection software. After the data logger completes its next scheduled data transfer, it will retrieve and process this request from the broker/server.
Note: Both the data logger and the PC running ydocTerminal must use (NTP) time synchronization.
To schedule a remote configuration session in ydocTerminal, navigate to:
File → New → Schedule a remote connection
Specify the serial number (S/N) of the data logger you want to configure and choose a convenient time for the remote session. Keep in mind:
- A tunnel cannot be established before the data logger’s next scheduled data transfer interval.
- A tunnel can only be established if ydocTerminal is running at the scheduled moment.
- When active, ydocTerminal will automatically open a terminal window a few minutes before the scheduled time.
Type of Server
- MQTT-broker
- FTP(S)-server
- HTTP(S)-server
Server address: The same address, port and path (URL) as used by the data logger (e.g. your-data-our-care.com/logfiles)
User/Password: The same credentials used by the data logger must be used, as they form part of the encryption keys.
Tunnel Server Properties This is the server that facilitates the secure, encrypted communication channel between the data logger and ydocTerminal. By default, our server (tunnel.ydoc.biz) is used. There is no need for concern — we cannot eavesdrop on your data, as all communication is peer-to-peer encrypted using security keys that are not known to the tunnel server. If you still have reservations, you are free to run your own tunnel server (ydocDataCollector) on your own Java Virtual Machine.
Prerequisites
- FTP: The user must have read, write, and delete permissions, and the FTP server/collector must not automatically delete any .tlr files.
- HTTP: The HTTP server must forward the request to the data logger using a custom HTTP response header (see the Data Logger Manual for details).
Tip: If it is not feasible to meet the prerequisites on your primary data collection platform, you may consider using a secondary data transfer method solely for remote configuration purposes. For example, you can run a free instance of ydocDataCollector on a Java Virtual Machine. You can configure the data logger to send only a small heartbeat message to this secondary endpoint once per day, minimizing both power consumption and unnecessary data transfer. This gives you the ability to schedule a remote configuration session for the following day—or any later time that is convenient for you.