Harvestree LoRaWAN Remote Configuration

← Configuration

Guide for reading and writing settings over LoRaWAN downlink after the device is deployed. First-time setup (ports, calibration, join credentials) is done with Harvestree Toolbox over USB — see Configuration.

Encoding conventions

Value examples (parameter ID is always big-endian; value bytes are little-endian):

Full SET_PARAM fragment for period 1000 s only: 00 02 04 E8 03 00 00 (ID 0x0002, length 4, value LE).

Transport and commands

Other commands on FPort 4 (optional):

RESET (0x04) is available on downlink. FACTORY_RESET (0x05), product/connector tag queries, LoRaWAN network parameters (0x0100–0x01FF), port measurement type changes (0x0006–0x0009 SET), and manufacturer-only parameters (0xF000–0xF0FF) are not available on LoRaWAN downlink — use Harvestree Toolbox over USB or your agreed maintenance procedure.

SET_PARAM rules:

• Every downlink byte after COUNT must belong to a parameter block; no trailing bytes (otherwise STATUS 0xBE, nothing saved).
• All-or-nothing batch: if one parameter in the command is wrong (unknown ID, bad length, out-of-range value, or validation failure at commit), the entire SET is rejected — no parameter from that command is written; the previous configuration stays unchanged. Fix the error and send a new SET (the ACK may include the failing PARAM_ID, 2 bytes big-endian).

ACK format (FPort 2)

• Generic: [CMD:1][STATUS:1][DATA…]
• GET_PARAM success: DATA = [COUNT:1]{[PARAM_ID:2][LEN:1][VALUE:LEN]}×COUNT
• SET_PARAM success (0xAA): usually no DATA — the full batch was saved
• SET_PARAM failure: no DATA or failing PARAM_ID in DATA (2 bytes, big-endian); none of the parameters in that SET were applied

Status codes

Workflow

1. Plan one logical change (for example one period or mode), not a full reconfiguration.
2. Send SET_PARAM on FPort 4 (remember: one bad parameter rejects the whole batch).
3. Read ACK on FPort 2 (0xAA = entire batch saved).
4. Optionally GET_PARAM the same IDs to confirm stored values.
5. Wait for the next measurement or alarm cycle and verify behaviour on air.
6. Record who changed what and when.

flowchart TD
  A[Plan change] --> B[SET_PARAM on FPort 4]
  B --> C{ACK success?}
  C -->|No| D[Read status / GET]
  C -->|Yes| E[Optional GET verify]
  E --> F[Verify uplink]

Examples

SET application mode Monitoring (0) and measurement period 1000 s (0x0003E8):

11 02 00 01 01 00 00 02 04 E8 03 00 00

GET mode and period:

10 02 00 01 00 02

Parameters (downlink)

Application

Alarm timing (Alarm mode)

System alarm thresholds

Alarm type enum (1 byte): 0 none, 1 high, 2 low, 3 in range, 4 out of range. Thresholds use corrected values (same as telemetry). No hysteresis.

Port alarm thresholds

port_index = 0 … 3 (Port 1 … 4), var = 0 … 4 (measurement variable index).

Low/high thresholds: -1e8 … 1e8 (finite). Example — Port 2, variable 0 type: ID 0x0260.

Precautions

• Prefer GET after SET when verifying a change.
• In a multi-parameter SET, one error rejects the entire command — correct and resend; do not assume partial updates were saved.
• Apply one functional change at a time — not several unrelated settings in the same SET.
• Shorter periods increase energy use; for autonomy planning, contact MOIZ or your supplier.