Taori Logger Studio v2.0
Help Manual
ProductTaori Logger Studio
Versionv2.0
CompanyTaori UG (haftungsbeschränkt)
Taori Logger Studio // HELP MANUAL
No logger selected
01 Getting Started
Overview

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.

Selecting a Logger

The turquoise dropdown in the top bar is used to select which logger you are working with. Your selection is remembered across pages.

  • 1Click the ↻ refresh button next to the dropdown to scan for available loggers. The status below the dropdown shows how many were found.
  • 2Select a logger from the dropdown. The page reloads automatically and all data on the current page will update to reflect the selected logger.
  • 3The status chip next to the dropdown shows the selected logger's name; its pulsing dot indicates that a logger is currently selected.
The logger selection is stored in your browser's local storage and persists until you select a different logger or clear your browser data.
Navigation

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.

Dark & Light Theme

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.

02 Logger Control
Live Logger Status

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 LoggingWhether the logger is actively recording measurements.
Database ConnectionWhether the logger can reach the database server to upload data.
Timeserver ConnectionWhether the logger's NTP time synchronisation is working.
RTC ConnectionWhether 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.

Database Alerts

This card queries the database monitoring system and displays the latest alert status for two automated checks associated with the selected logger.

Data TransmissionTriggered (CRIT) when no measurement has arrived from the logger for more than 24 hours.
PowerTriggered (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.

Rename Logger
Renaming a logger creates entirely new database records for all connected sensors under the new name. The old records under the previous name are not deleted but will no longer receive new data. Only rename a logger if you are certain this is intended.

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.

Remote Access

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.

All times are in UTC. Make sure to account for your local timezone offset when choosing the wake-up window.
Send Interval

Controls how frequently the logger uploads recorded measurements to the database. A longer interval means fewer uploads and significantly lower power consumption.

15 – 720 minStandard interval range for battery-powered deployments.
1 dayMaximum power saving; suitable for slow-changing environmental parameters.
Real-timeUploads immediately after every measurement. Only use when on mains power.

Select the desired interval and click Apply.

Power Saving Settings

Displays the current power saving configuration retrieved from the logger, including which power-saving modes are active and their current parameter values.

03 Dashboard
Overview

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.

Overview Tab — Health Tiles

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 voltageThe latest supply voltage, shown large and colour-coded: green = healthy, amber = low, red = critical.
Status dotA coloured dot beside the logger name mirrors the battery state, and turns red when the logger has not reported for a while.
Logging / IdleWhether the logger is currently recording measurements.
Last contactHow long ago the logger last reported (e.g. “seen 2 h ago”).
staleA red badge shown when the last contact is older than expected for the logger's send interval — a hint that it may be offline.
AlertsA 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 curveThe logger's battery-voltage curve (with volts on the axis) over the selected time range; hover it to read exact values.
The battery colour thresholds are set to sensible defaults for a 12 V system. If your loggers use a different battery, an administrator can adjust the thresholds in the Dashboard configuration.
Custom Dashboards

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.

  • 1Click the + New tab and give the dashboard a name.
  • 2Click ✎ Edit, pick a Logger and a Parameter, then press Add tile. Repeat to add as many tiles as you like.
  • 3Remove a tile with the beside it in the edit panel.
  • 4Use Rename or Delete dashboard to manage it, and Done to close editing.
Each custom dashboard remembers its own time range. Charts use hourly averages for ranges up to a week and daily averages beyond that, so they stay fast even over long periods.
04 Sensor Configuration
Overview

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.

Sensor Model & the Sensor Database

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.

Define your sensor models and their channels first on the Sensor Database page, then pick the matching model here.
SDI-12 Tab

The logger supports up to 12 SDI-12 ports. The table shows each port's protocol, sensor type, measurement interval, and sensor name.

  • 1Click ↺ Get sensors to query the logger and populate the table with currently connected SDI-12 sensors.
  • 2Click a port box to select it (it will highlight in turquoise).
  • 3Click Edit sensor to open a form where you can update the sensor name and measurement interval for that port.
  • 4Submit the form to apply the changes to the logger.
Analog Tab

The logger supports up to 4 analog ports. These are typically used for 0–10 V or 4–20 mA sensors.

  • 1Click + Add / Edit to open a form. Enter the port number, sensor type, sensor name, and measurement interval.
  • 2Submit to write the sensor configuration to the logger.
  • 3To remove a sensor, click Remove, enter the port number, and confirm.
Pulse Tab

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.

05 Sensor Database
Overview

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.

Sensor Models

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).

  • 1Expand Add / update a sensor model, fill in manufacturer, model and sensor type, and click Save model.
  • 2For SDI-12 you can optionally tick Auto-detection and enter the SDI-12 identity string (the sensor's “I” command response) so matching sensors are recognised automatically.
  • 3Click a row to select a model and edit its channels below.
Channels

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:

ParameterThe measured quantity, e.g. SoilMoisture or Temperature.
UnitThe physical unit, e.g. % or °C.
Raw unitFor analog/pulse sensors: the unit of the raw signal (e.g. mV, counts).
Slope / InterceptConvert 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).
Time-dependent recalibration (a slope/intercept that changes from a certain date onward) is done later in the Data Explorer, not here.
06 Data Explorer
Overview

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.

Map

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.

Select Logger & Data Filter

Click a logger card in the right panel to select it. Once selected, the data filter form unlocks.

SourceRaw (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.
CumulativeFor a Calibrated source only: show a running sum instead of individual values (useful for pulse totals such as rainfall).
MeasurementOpen the dropdown and tick one or more parameters to overlay several series on the same chart.
Data Quality Grading

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.

  • 1Pick the logger, the measurement, and the From / To range you want to grade.
  • 2Click Grading, choose a grade (with an optional note), and click Set.
  • 3Existing graded periods are listed below — edit (✎) or delete (✕) them there. Where periods overlap, the most recent grade wins.
Calibration

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.

  • 1Select the logger, the measurement, and the start date (From).
  • 2Click Calibration and enter Slope and Intercept. Leave “From onward” ticked for an open-ended period, or untick it to limit the change to the From / To range.
  • 3Click Set, then switch the Source to Calibrated to see the result. Existing periods can be edited or removed in the list below.
Calibration applies to Raw signals only. The Calibrated source lists only measurements that actually have a real calibration (a sensor-model curve or a period you set here).
Time Range

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.

Preview

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:

TableDisplays raw rows with timestamp, field name, and value.
ChartPlots 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.

Download CSV

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.

Add Logger Location

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.

  • 1Select the logger from the dropdown (only loggers without coordinates are listed).
  • 2Enter Latitude and Longitude in WGS84 decimal degrees (e.g. 47.9569 / 7.8381).
  • 3Enter the Logger Model and Project name.
  • 4Optionally upload a Station Photo by clicking the photo drop area.
  • 5Click Save. The logger will appear on the map after the next page refresh.
Station Photos

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.

07 Data Processing
Overview

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.

Select Logger

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.

Source & Time Range

Pick the input SourceRaw 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.

Calculations — Aggregation

Aggregate an existing parameter over a fixed time window and save the result as a new dataset in the database.

ParameterThe parameter to aggregate (from the selected logger's measurements).
FunctionMean, Sum, Min, Max, Median, Count, First, Last, or Standard Deviation.
EveryThe time window size (e.g. every 1 hour).
Output nameName for the resulting time series (e.g. AirTemp_hourly_mean).
Output unitUnit tag for the new time series.
The result is saved alongside the original data so it never overwrites the original mapped values.
Calculations — Formula

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.

08 Administration
Overview

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.

Users

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.

UsernameLogin name. Lowercase letters, digits, and underscores; up to 32 characters.
RoleAlways "project" for users created here.
ProjectsThe projects this user can see. A user can be assigned to one or more.
FlagsStatus indicators (e.g. password-reset required).

Add user — fill in the inline form at the bottom of the card:

  • 1Enter a Username (max 32 chars).
  • 2Enter an initial Password — minimum 10 characters with a mix of letters, digits, and symbols. Share it with the user through a secure channel.
  • 3Select one or more Projects in the multi-select list (hold Ctrl / Cmd to pick more than one).
  • 4Click Create user. The new account appears in the table immediately.
Use the Reset password action in the user's row to set a new password — a modal opens where you can type the new password and confirm. The user is not notified automatically; share the new password through a secure channel.
Projects

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.

NameProject identifier (max 40 chars). Used in the user assignment dropdowns and in the logger table.
DescriptionOptional free-text note (max 200 chars).
LoggersNumber of loggers currently assigned to this project.

Add project — fill in the inline form:

  • 1Enter a Project name.
  • 2Optionally add a Description.
  • 3Click Create project.
Deleting a project does not delete its loggers, but any user accounts that had access only to that project will lose access to those loggers until they are re-assigned to another project.
Logger assignments

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).

LocationThe logger's name / measurement identifier.
IPThe IP address the logger was last reachable at — extracted from the latest data transmission.
ModelThe logger model (e.g. TX1000).
ProjectThe project this logger is currently assigned to. Use the inline dropdown in the row to change the assignment.
A pink banner appears at the top of the page whenever there are unassigned loggers. These are loggers that have reported data to the database but have not yet been linked to a project — they are visible only to the admin until they are assigned. This is the typical state of a newly delivered logger after its first data transmission.
Onboarding a new logger

The end-to-end workflow for taking a freshly delivered TX1000 from the box to a project account:

  • 1Power on the logger in the field. See the Hardware tab for first-time setup details.
  • 2Wait for the logger to send its first data transmission. The unassigned-loggers banner on this page will then show one new entry.
  • 3Open Logger assignments and pick the appropriate project from the dropdown in the new logger's row.
  • 4If the project does not exist yet, create it in the Projects card first.
  • 5If a new account is needed for that project, create it in the Users card with the project ticked in the multi-select.
09 Info Panel
Accessing the Info Panel

Click the turquoise i button in the bottom-left corner of any page to open the info panel. It contains two items:

Help ManualOpens this manual.
AboutExpands to show the product name, version number, and company. Click again to collapse.

Click anywhere outside the panel to close it.

01 Introduction
About this manual

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.

Projects, project accounts & admin

Each TX1000 is assigned to a project. Within the Taori Logger Studio there are two account types:

Project accountSees and configures only the loggers belonging to its own project.
Admin accountHas access to all loggers across all projects and is responsible for assigning a newly delivered logger to the correct project.
The admin workflow for assigning loggers to projects is described under Administration in the Logger Studio tab.
02 The Four Golden Rules in Data Logging
The TX1000 is engineered to withstand challenging environments and a wide range of application errors. A few things, however, remain the user's responsibility and cannot be solved by design. If you only read one section of this manual, read this one.
1
Always disconnect the logger from power before working on it.
Whether you are wiring sensors, swapping cables, or doing any other work inside the housing — disconnect the power supply (battery and/or solar) first and verify before you touch anything. Working on a live board risks a short circuit that can damage the logger and the sensor.
2
Keep cable insulation as intact as possible.
When the wires of a powered sensor touch each other (for example, power and data), the sensor can be permanently destroyed. Strip only as much insulation as needed to seat the conductor in the spring terminal. Trim long pigtails and avoid bare copper outside the connector.
3
Match the cable colours to Data, Power, and Ground.
Always check the sensor's manual for the correct cable colour assignments (Data, Power, Ground). Colour codes vary by manufacturer — do not assume "red = power". Incorrect wiring can damage both the sensor and the logger. For analog sensors with only two wires, follow the manufacturer's polarity instructions.
4
Protect against corrosion on the sensor side.
Corrosion caused by humidity typically affects the sensors and their cabling, while the logger electronics inside the IP65 enclosure tolerate moisture well. Use an anti-corrosion agent (e.g. Taori SensorProtect) on exposed sensor wires, and seal the cable entries into the enclosure with the supplied rubber plugs.
03 Technical Specifications
TX1000 — at a glance

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.

Datalogger
EnclosureIP65, key-locked
Operating temperature–15 to 50 °C
Dimensions29.5 × 22 × 8.5 cm
Weight2.4 kg
Power supply12 V
ModemEnergy-efficient LTE Cat 4 gateway with pre-configured VPN tunnel and multi-network IoT SIM (Europe-wide)
Logic board

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.

Connectivity board

The default connectivity board provides:

SDI-12 ports12
Analog inputs4
Pulse inputs2

The connectivity board uses push-in spring terminals and is fully replaceable. Custom variants can be specified — contact Taori for a quote.

04 Connectivity & First-Time Setup
Pre-configured network access

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.

Bringing a new logger online

After unboxing and powering the logger:

  • 1Connect the 12 V power supply (battery and/or solar). The logger boots automatically.
  • 2Wait for the logger to send its first data transmission to the central database. This is required: the actively assigned IP address is only visible to Taori once the logger has reported in.
  • 3Once the first datapoint is received, the logger can be reached over the VPN tunnel for active configuration and remote service through the Taori Logger Studio.
  • 4The admin then assigns the new logger to the correct project via the Administration page in the Logger Studio. From that point on, the project account can see and configure the logger like any of its other devices.
Until the first transmission arrives, the logger is not reachable remotely. Do not start in-field configuration before the logger has appeared in the database — see the Administration section under the Logger Studio tab for the exact admin steps.
05 Operating Modes & Service Buttons
Sleep state

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.

The two service buttons

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 buttonRestarts 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 buttonWakes 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.
06 Connecting Sensors
Cables come first

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.

Power off — always. Disconnect the logger from power before doing any work inside the housing. Working on a live system can short-circuit the logger or destroy the sensor. The TX1000 has two onboard fuses that protect against short circuits, but the fuses are a backup, not a license to work hot.
Push-in spring terminals

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.

Wire assignment

Each terminal is labelled. For digital sensors (e.g. SDI-12), match the three wires to:

DataThe signal line.
PowerThe 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.
GroundThe 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.

Do not rely on cable colour alone. Manufacturers use very different conventions, and a wrong assignment can permanently damage the sensor or the logger. Always cross-check against the sensor's datasheet before powering up.
07 Field Deployment
Overview

The TX1000 housing is rated IP65 and the electronics tolerate moisture well, but a few mounting rules must be respected for long-term reliability.

Orientation

Always mount the logger upright — with the cable glands facing downward and the lid vertical.

Never lay the logger flat when deployed: water can pool on the lid and eventually find its way past the seal.
Antenna

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.

Cable entries & sealing

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.

Fuses

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.

Moisture in general

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.