TORUS-SN Node Variants Datasheet

TORUS-SN · NODE VARIANTSSN-V1 … V4

Four facility-sensor node classes on one event contract: fixed wireless, programmable SDR, wired optical, and transducer.

PRELIMINARY

doc TORUS-SNV-DS-001
2026-07-05

1Overview

All TORUS-SN nodes share the same seismic/acoustic sensing core, the same event contract (per-source sequence numbers for zero-miss processing), and the same operations integration. They differ in the communications and response layer, which is selected per node to match cost, security event profile, assurance requirements, and AI/HPC data center constraints. A single deployment routinely mixes classes: economical fixed-wireless nodes for the bulk of a campus perimeter, programmable or wired nodes on high-value data hall approaches, and transducer nodes where facility response actuation under safety interlock is authorised.

Hardware design status. Only variant 1 has a complete hardware design (generated schematic, 4-layer PCB, and 3D model, pre-production). Variants 2, 3, and 4 are at design-brief stage: host architecture, block diagram, candidate BOM, and open engineering flags are documented per variant in the repository under hw/variants/, with no schematic or PCB yet. Notably, the SDR variant requires an FPGA/SoC class host (the AD9371's JESD204B interface cannot be serviced by the V1 node's MCU), so it is architected as a carrier board stacked on an unmodified V1 node.

2Variant comparison

#	Variant	Link / RF	Rel. cost	Maturity	Best fit
1	Fixed Wireless	LoRa 433 MHz	Low	FIELDED	Wide, dense campus perimeter rings
2	Programmable Wireless	SDR AD9371 / AD9363 (+LoRa failsafe)	High	R&D	Experimental, R&D, congested-RF facility segments
3	Wired Optical	Optical fibre	Site-dependent	R&D	Highest-assurance, RF-quiet facility segments
4	Transducer	per host node	Add-on	CONCEPT	Authorised, safety-interlocked response points

3Variant 1 · Fixed Wireless (LoRa)

SN-V1 Fixed Wireless

LoRa 433 MHzFIELDED

Lowest cost per node. The default element for the bulk of an AI/HPC data center campus perimeter ring.
LoRa 433 MHz (EU ISM) long-range uplink to the TORUS-MEG gateway via SMA antenna.
Fixed-function radio - no on-site reconfiguration of the RF, which keeps power and cost down.
This is the production TORUS-SN board described in the SN node datasheet.

4Variant 2 · Programmable Wireless (SDR)

SN-V2 Programmable Wireless

SDR AD9371 / AD9363R&D

Software-defined radio front end (Analog Devices AD9371 preferred, AD9363 as a lower-cost option) for reconfigurable waveform, band, and protocol.
Ships with a LoRa failsafe. The LoRa link is a guaranteed fallback and can also serve as the main link; where LoRa alone meets the requirement, variant 1 is the more economical choice and the SDR is not warranted.
Significant per-node cost premium. Justified for experimental and R&D deployments, spectrum work, and facilities with required congested-RF performance.
Higher power draw and compute demand than the fixed variant; power budget and enclosure sized accordingly.

Engineering flag: AD9371/AD9363 carrier board, clocking, and power tree are a distinct design from the fixed node; not yet on the fielded TORUS-SN PCB.

5Variant 3 · Wired Optical

SN-V3 Wired Optical

Optical fibreR&D

Wired optical transport instead of RF - no radio emission and less exposure to RF interference.
Tamper-resistant and RF-quiet, suited to the highest-assurance segments of a data center perimeter or data hall approach where wiring is feasible.
Trades the free-placement advantage of wireless for assurance; used selectively, not across a whole ring.
Under research. Optical transceiver, powering, and mechanical integration are in development.

6Variant 4 · Transducer (Activate / Trigger)

SN-V4 Transducer

response nodeCONCEPT

Transducer node, not a sensor - on a validated cue it actuates a facility response under safety interlock (the response type is deployment-defined and authorised separately).
Mandatory safety interlock. A transducer never actuates straight from a raw cue. It walks a state machine with a compulsory safety-validation stage between activation and trigger.
Every arm, validate, trigger, and abort is logged for post-incident review.

DISARMED → ARMED → VALIDATING →(validation passed)→ TRIGGERED
↴ any state → SAFE → DISARMED (abort). Trigger is refused unless validation has passed.

The interlock is implemented in the operations layer and enforced in code; see the TORUS-CCISRT datasheet and the reference implementation in the torus-ccisrt repository.

7Selection guidance

If the segment needs…	Choose
Lowest cost, wide coverage, standard alarm profile	1 · Fixed Wireless
Reconfigurable RF, congested spectrum, R&D	2 · Programmable SDR
No RF emission, maximum tamper resistance	3 · Wired Optical
An authorised, validated physical response	4 · Transducer

8Trademarks & third-party notice

TORUS is an independent platform. Company names and product model numbers referenced in this document (including but not limited to Analog Devices AD9371 and AD9363, and Semtech LoRa) are used solely for engineering and bill-of-materials identification and imply no affiliation with or endorsement by those companies. Supply of any such third-party product or component to the designers, manufacturers, integrators, or evaluators of the TORUS platform remains at the sole discretion of the respective owning company, organisation, or legal entity. "FOR EVALUATION" is a document-handling marking only and denotes no security classification. All trademarks are the property of their respective owners. Deployments can align with TIA-942 physical-security controls, OCP facility telemetry patterns, and PacketFive northbound API adapters for PSIM, DCIM, BMS, VMS, SIEM, and Redfish. PacketFive Design Services can adapt node variants for other customer requirements.