Taori Logger Studio is a web-based remote control and data management interface for Taori data loggers. It connects to your loggers over the network, reads sensor configurations, retrieves data from the database, and lets you process and download measurements — all from one place.
The interface is divided into several pages, accessible via the icon rail on the left edge of the screen: Logger Control, Dashboard, Sensor Configuration, Sensor Database, Data Processing, and Data Explorer.
The turquoise dropdown in the top bar is used to select which logger you are working with. Your selection is remembered across pages.
Use the icons in the rail on the left edge to navigate between pages — hover over an icon to see its name. The currently active page is highlighted with a turquoise accent line. All pages share the same logger selection. On small screens the rail collapses into a dropdown menu behind the ☰ button in the top bar.
The sun/moon button in the top bar switches between the dark theme and a high-contrast light theme designed for outdoor use in bright sunlight. Your choice is saved in the browser and applies to all pages. The sign-in page always uses the dark theme.
This card connects directly to the selected logger and requests its current status. It displays a live readout of four key indicators and the current supply voltage.
| Now Logging | Whether the logger is actively recording measurements. |
| Database Connection | Whether the logger can reach the database server to upload data. |
| Timeserver Connection | Whether the logger's NTP time synchronisation is working. |
| RTC Connection | Whether the on-board real-time clock is reachable. |
| Power (V) | Current supply voltage in volts. |
Two buttons at the bottom allow you to remotely Run (start logging) or Stop (halt logging) the selected logger.
This card queries the database monitoring system and displays the latest alert status for two automated checks associated with the selected logger.
| Data Transmission | Triggered (CRIT) when no measurement has arrived from the logger for more than 24 hours. |
| Power | Triggered (CRIT) when the latest supply voltage is below 8 V or above 14 V. Also shows the most recently recorded voltage value. |
Each alert shows its status level (OK, WARN, or CRIT) and the timestamp of the last check.
Enter the new name in the text field and click Apply. Use lowercase letters, numbers, and hyphens (e.g. site-north-01). The name becomes the database measurement identifier for all sensors on this logger.
To save battery power, you can restrict the time window during which the logger accepts remote connections (e.g. SSH or this web interface) to a single one-hour slot per day.
Select a wake-up window (UTC) from the dropdown and click Apply. The logger will only be reachable during that hour. Outside of that window it will be in a low-power sleep state.
Set the option to Always on to keep the logger continuously reachable, at the cost of higher power consumption.
Controls how frequently the logger uploads recorded measurements to the database. A longer interval means fewer uploads and significantly lower power consumption.
| 15 – 720 min | Standard interval range for battery-powered deployments. |
| 1 day | Maximum power saving; suitable for slow-changing environmental parameters. |
| Real-time | Uploads immediately after every measurement. Only use when on mains power. |
Select the desired interval and click Apply.
Displays the current power saving configuration retrieved from the logger, including which power-saving modes are active and their current parameter values.
The Dashboard gives you a fast “is everything running?” overview of all your loggers on one screen, so you don't need a separate tool just to confirm everything is healthy. It is organised into tabs along the top: one fixed Overview tab plus any custom dashboards you create yourself.
A time range selector in the toolbar applies to the active tab: Last 24 h, 7 days (default), 30 days, or 90 days. Click ↻ Refresh to reload the data. The Dashboard does not update live — loggers only send new values every few minutes to hours, so a manual refresh is all you need.
The Overview tab needs no setup. It shows one health tile per logger in your projects, each summarising that logger's condition at a glance:
| Battery voltage | The latest supply voltage, shown large and colour-coded: green = healthy, amber = low, red = critical. |
| Status dot | A coloured dot beside the logger name mirrors the battery state, and turns red when the logger has not reported for a while. |
| Logging / Idle | Whether the logger is currently recording measurements. |
| Last contact | How long ago the logger last reported (e.g. “seen 2 h ago”). |
| stale | A red badge shown when the last contact is older than expected for the logger's send interval — a hint that it may be offline. |
| Alerts | A red badge with a count when there are open alerts for the logger in the selected range. Hover it to read the latest alert message. |
| Battery curve | The logger's battery-voltage curve (with volts on the axis) over the selected time range; hover it to read exact values. |
Beyond the built-in tabs you can build your own dashboards for the measurements that matter to you. Each is a grid of mini-charts, one per (logger + parameter) you choose. Your dashboards are saved to your account, so they reappear on your next visit and on any device.
This page lets you view and configure the sensors connected to the selected logger. Sensors are organised by protocol across three tabs: SDI-12, Analog, and Pulse. Port boxes at the top of each tab show which ports are in use (highlighted) and which are empty.
When you add or edit a sensor you can link it to a Sensor Model from the Sensor Database. That link is what lets the system store readable parameter names and units alongside the incoming data automatically — so you no longer relabel data by hand afterwards.
Each add/edit form (on all three tabs) has a Sensor Model dropdown listing the models defined in the Sensor Database. Choosing a model tells the system which physical quantity each of the sensor's channels represents. On every upload the logger's raw channels are then resolved to the model's parameter and unit — and, for analog/pulse sensors, converted from the raw signal (mV, counts) to a physical value using the model's slope/intercept.
The logger supports up to 12 SDI-12 ports. The table shows each port's protocol, sensor type, measurement interval, and sensor name.
The logger supports up to 4 analog ports. These are typically used for 0–10 V or 4–20 mA sensors.
The logger supports up to 2 pulse counter ports, typically used for rain gauges or flow meters. The workflow is identical to the Analog tab: use + Add / Edit to configure a port and Remove to delete a sensor assignment.
The Sensor Database is the catalogue of sensor models and, for each model, the channels (measurement values) it reports. It replaces logger-side programming: once a model is defined here and linked to a sensor in Sensor Configuration, every measurement is stored with the correct parameter name and unit automatically.
The top table lists all known sensor models. Each has a manufacturer, model name, an optional description, and a sensor type (SDI-12, Analog, Pulse, or RS232).
A sensor sends one or more values in a fixed order — value 1 is channel 1, and so on (check the sensor's handbook). For each channel you record what it measures:
| Parameter | The measured quantity, e.g. SoilMoisture or Temperature. |
| Unit | The physical unit, e.g. % or °C. |
| Raw unit | For analog/pulse sensors: the unit of the raw signal (e.g. mV, counts). |
| Slope / Intercept | Convert the raw signal to the physical value: physical = raw × slope + intercept. For pulse sensors, slope is the amount per pulse. SDI-12 channels are already physical (slope 1, intercept 0). |
The Data Explorer page has a two-panel layout: an interactive map on the left showing all logger locations, and a data panel on the right for filtering, visualising, and downloading data from the database.
All loggers that have GPS coordinates registered in the database appear as pins on the map. Click a pin to open a popup showing the logger's latitude, longitude, supply voltage, and last-seen timestamp.
The map opens in satellite view (Esri World Imagery) by default, centred on Freiburg im Breisgau until the logger locations have loaded. Use the 🛰 Satellite Map / ☀ Street Map button in the top-right corner of the map to switch between the satellite imagery and the OpenStreetMap street layer — the button always shows the view you will switch to.
Click a logger card in the right panel to select it. Once selected, the data filter form unlocks.
| Source | Raw (as measured) — the value as stored (mV / counts for analog & pulse sensors). Calibrated (physical) — the raw signal converted to a physical value via the sensor model / calibration. Processed (computed) — derived series created on the Data Processing page. |
| Cumulative | For a Calibrated source only: show a running sum instead of individual values (useful for pulse totals such as rainfall). |
| Measurement | Open the dropdown and tick one or more parameters to overlay several series on the same chart. |
You can flag periods of data with a quality grade so anyone reading the data knows how far to trust it. Grades appear in the preview table and the CSV, and colour the chart points: good, fair, poor.
Calibration converts a raw sensor signal to a physical value: physical = raw × slope + intercept. A model's default calibration comes from the Sensor Database; here you can set a calibration that applies from a chosen date onward — useful when a sensor is re-calibrated in the field, while older data keeps its previous factors.
Set the From and To datetime fields to define the query window. Click ↔ Max range to automatically fill in the earliest and latest timestamps available in the database for the current filter selection.
Click ▶ Preview to fetch data from the database and display it in an overlay panel at the bottom of the map, without downloading a file.
The preview panel can be viewed in two modes, switchable with the toggle buttons in the panel header:
| Table | Displays raw rows with timestamp, field name, and value. |
| Chart | Plots values over time. Drag on the chart to zoom in on a time range. Scroll to zoom at the cursor position. Click ↻ Reset zoom to return to the full view. |
Close the preview with the ✕ button in the panel header.
Click ↓ Download CSV to export the currently filtered data as a comma-separated values file. The file contains timestamps, field names, values, and all associated tags.
If one or more loggers are present in the database but have no GPS coordinates registered, a pink badge appears on the + Add Logger Location section showing how many are missing. Expand the section to register their location.
Expand the 📷 Station Photos section to update or replace the photo for an existing logger station. Select the logger from the dropdown, choose a new image file, and save.
Incoming measurements are already labelled with the correct parameter name and unit automatically (via the Sensor Database), so there is no manual relabelling step here anymore. This page is for deriving new time series from existing data and saving them back as Processed Data — for example hourly averages, daily totals, or a value computed with a formula.
Two kinds of calculation are available: Aggregation and Formula. Results are saved as new series alongside the originals and never overwrite them.
Choose the Logger whose data you want to work with. The parameter dropdowns in the calculation panels below are then filled from that logger's available measurements.
Pick the input Source — Raw data (sensor channels) or Processed data (already-derived series) — and the time window to read. Tick Entire time range to include all history, or set From and To manually.
Aggregate an existing parameter over a fixed time window and save the result as a new dataset in the database.
| Parameter | The parameter to aggregate (from the selected logger's measurements). |
| Function | Mean, Sum, Min, Max, Median, Count, First, Last, or Standard Deviation. |
| Every | The time window size (e.g. every 1 hour). |
| Output name | Name for the resulting time series (e.g. AirTemp_hourly_mean). |
| Output unit | Unit tag for the new time series. |
Write a custom mathematical formula that combines several parameters from the selected logger. The result is saved to the database as a new dataset with a user-defined parameter name and unit.
The variables available in the formula correspond to the parameters available for the selected logger. The formula is evaluated point-by-point over the selected time range.
The Administration page is only visible to the admin account. It is where users, projects, and logger-to-project assignments are managed. Project accounts do not see this page in the navigation rail.
The page is organised into three cards: Users, Projects, and Logger assignments.
The Users card lists every project account in the system, along with its assigned projects and any flags. Each row has actions for editing project assignments, resetting the password, and deleting the user.
| Username | Login name. Lowercase letters, digits, and underscores; up to 32 characters. |
| Role | Always "project" for users created here. |
| Projects | The projects this user can see. A user can be assigned to one or more. |
| Flags | Status indicators (e.g. password-reset required). |
Add user — fill in the inline form at the bottom of the card:
Projects group loggers together. A project account can only see loggers belonging to its assigned projects — this is the primary access-control mechanism in the studio.
| Name | Project identifier (max 40 chars). Used in the user assignment dropdowns and in the logger table. |
| Description | Optional free-text note (max 200 chars). |
| Loggers | Number of loggers currently assigned to this project. |
Add project — fill in the inline form:
This table is the link between hardware and projects. Each row represents one logger that has reported in to the database, along with its assigned project (if any).
| Location | The logger's name / measurement identifier. |
| IP | The IP address the logger was last reachable at — extracted from the latest data transmission. |
| Model | The logger model (e.g. TX1000). |
| Project | The project this logger is currently assigned to. Use the inline dropdown in the row to change the assignment. |
The end-to-end workflow for taking a freshly delivered TX1000 from the box to a project account:
Click the turquoise i button in the bottom-left corner of any page to open the info panel. It contains two items:
| Help Manual | Opens this manual. |
| About | Expands to show the product name, version number, and company. Click again to collapse. |
Click anywhere outside the panel to close it.
This tab covers the hardware side of the Taori system: the TX1000 datalogger, its physical setup, connectivity, and how to deploy it safely in the field. The companion Logger Studio tab covers the web platform used to configure loggers, manage sensors, and access data.
Each TX1000 is assigned to a project. Within the Taori Logger Studio there are two account types:
| Project account | Sees and configures only the loggers belonging to its own project. |
| Admin account | Has access to all loggers across all projects and is responsible for assigning a newly delivered logger to the correct project. |
The TX1000 is a modular LTE datalogger, built within an IP65 rated enclosure secured by an integrated key lock. It contains an LTE modem, a universal logic board, a standard connectivity board, and an integrated MPPT solar charge controller — the charge controller is part of every TX1000.
A solar panel and mounting hardware (e.g. the hanit® pole and brackets) are available as optional add-ons. The 12 V battery is not included with the logger because of European shipping legislation, but the TX1000 is compatible with a wide range of 12 V batteries — Taori is happy to recommend tested options.
| Enclosure | IP65, key-locked |
| Operating temperature | –15 to 50 °C |
| Dimensions | 29.5 × 22 × 8.5 cm |
| Weight | 2.4 kg |
| Power supply | 12 V |
| Modem | Energy-efficient LTE Cat 4 gateway with pre-configured VPN tunnel and multi-network IoT SIM (Europe-wide) |
The logic board hosts the controller, the LTE modem, and the two physical service buttons described in Operating Modes & Buttons. It is not user-serviceable beyond those two buttons.
The default connectivity board provides:
| SDI-12 ports | 12 |
| Analog inputs | 4 |
| Pulse inputs | 2 |
The connectivity board uses push-in spring terminals and is fully replaceable. Custom variants can be specified — contact Taori for a quote.
Every TX1000 ships with a pre-configured IP address and an IoT SIM card. The modem and the connection to the database are also pre-configured at the factory. No manual network or database setup is required at the user side.
After unboxing and powering the logger:
Depending on the configuration set in the Taori Logger Studio, the TX1000 spends most of its life in a low-power sleep state, waking only on the configured measurement and transmission schedule. This is by design and is what gives the logger its long autonomy on solar power.
There are two physical service buttons on the logic board. Both are recessed and can be operated through the housing opening with a small screwdriver or similar narrow tool.
| Left button | Restarts the LTE modem. Use this if the logger is failing to connect to the network or if you need to force the modem to re-register — for example, after moving the device to a new site. |
| Right button | Wakes the logger for 30 minutes for configuration or maintenance. Press this before using the Taori Logger Studio in the field, otherwise the logger may be asleep and unreachable. |
Sensor cables are the most fragile part of any field installation. The most common cause of failure is not the logger but the cabling — specifically corrosion at exposed conductors. Before you start: keep as much insulation on the cable as possible, and only strip the few millimetres needed to seat the conductor in the terminal. The less bare copper, the longer the sensor will live in the field.
The connectivity board uses push-in spring terminals. To insert a wire, press the release tab with a small screwdriver, push the stripped end fully in, then release. Tug the wire gently to confirm a secure connection.
Each terminal is labelled. For digital sensors (e.g. SDI-12), match the three wires to:
| Data | The signal line. |
| Power | The supply line. SDI-12 sensors run at 12 V. For other sensors, the supply voltage on the connectivity board can be switched to 5 V or 3.3 V if required. |
| Ground | The common return. |
For analog sensors there are typically only two wires — follow the polarity given in the sensor's manual. Check the required supply voltage and select 12 V, 5 V, or 3.3 V on the connectivity board accordingly.
The TX1000 housing is rated IP65 and the electronics tolerate moisture well, but a few mounting rules must be respected for long-term reliability.
Always mount the logger upright — with the cable glands facing downward and the lid vertical.
The LTE antenna must be mounted outside the logger case. Keeping it inside the housing will cripple reception and can prevent the logger from connecting at all.
Use the supplied rubber plugs to seal each cable gland around the sensor cables. This keeps moisture out of the electronics and protects the cable jacket from chafing at the entry point. Unused glands must remain plugged — do not leave openings in the housing.
The TX1000 carries two onboard fuses that protect against short circuits on the supply and sensor lines. If a logger goes silent after a wiring change, check the fuses before suspecting a deeper fault.
The logger electronics themselves are quite robust against humidity — the most vulnerable parts of the system are the sensor cables and the exposed conductors at their ends. Treat them as the bottleneck of the installation: keep insulation intact, seal entries, and use an anti-corrosion agent on any exposed copper. See Golden Rule 4.