Integrations
Connect Sentor to the systems already running your site
Sentor sits between the equipment at a site and the people and systems that need to know about it. It reads what your plant, panels and instruments already produce, decides what it means using logic stored on the controller, and acts — switching equipment, raising alarms, notifying people, or reporting upstream into a system you already run.
Step 1
Input
A contact closes, a voltage moves, a current loop shifts, a command arrives.
Step 2
Logic
Scenario logic on the controller decides what it means and whether it warrants action.
Step 3
Action
A relay operates, an output switches, a scenario runs.
Step 4
Report
The event is logged, people are notified, upstream systems are updated.
Every step runs on the controller itself. Integration does not depend on a live connection back to base — the link governs how quickly you hear about something, not whether the site handles it.
1 · Direct I/O
Electrical interfaces
The layer most site equipment already speaks. Anything that produces a contact closure, a voltage, a current loop or a temperature output connects without a gateway, a driver or a protocol conversation — which usually means existing instrumentation is reused rather than replaced.
| Interface | What it connects and how |
|---|---|
| Dry contacts | Eight optically isolated digital inputs read clean contact closures from panels, relays, float switches, limit switches and equipment status contacts. |
| Protected loops | Supervised loops using double 10k end-of-line resistors, so a cut or shorted cable is detected as a fault rather than read as a healthy state. |
| Analogue voltage | 0–1 V, 0–5 V, 0–10 V and 0–30 V on the ST3000. The i7000 reads 0–65 V in a single range at 1 mV resolution, covering 12 V, 24 V and ±48 V supplies on one input without range selection. |
| Current loop | 4–20 mA transducers connect directly — pressure, flow, level, temperature and the rest of the process instrumentation already fitted to most plant. The i7000 resolves to 20 µA. |
| Temperature | Two-wire sensors powered from the input itself, in °C or °F, with no separate supply to run. |
| Relay outputs | Eight single-pole double-throw relays, each presenting a common terminal with normally-open and normally-closed contacts. 1 A maximum switching — 24 VDC/24 VAC where UL approval is required, 48 VDC/32 VAC where it is not. Pulsed and timed operation is supported on the i7000. |
| Analogue outputs | Two 4–20 mA outputs on the i7000, so the controller can drive a control loop or a receiving instrument rather than only switch a contact. |
| Alarm outputs | Dedicated strobe and siren outputs alongside the programmable relays. |
| Sensor power | Approximately 800 mA at 12 VDC from the auxiliary supply for powering field sensors, on a rail that stays up on battery through a mains failure. |
2 · Serial, network and building systems
System interfaces
Where a site has equipment that talks rather than simply switches.
| Interface | What it connects and how |
|---|---|
| RS-232 | Two ports for direct connection to a PC, a modem or serial equipment. |
| RS-485 | Two ports. Links multiple controllers on one site, and carries the LCD keypad terminals up to 1,200 m on four-wire cable. |
| CAN 2.0 | On the i7000, via an 8-pin Phoenix connector — the bus engine and generator controllers use for data a contact closure cannot carry. |
| Ethernet | The ST301 and ST1100 network-enable an ST3000 over LAN or internet. The i7000 carries two 10/100/1000 Mbps ports on the board. |
| Wiegand access control | The ST352A interfaces card, proximity, keychain, fingerprint, palmprint, iris and facial recognition readers, supporting up to 64,000 users. Cardax, Axeze and Variprox readers are named in Sentor’s documentation; most Wiegand readers interface. |
| Clipsal C-Bus | A lighting control interface, so building lighting sits under the same scenario logic as plant and access. |
| X10 | Power-line carrier connection for legacy building control. |
3 · Protocols — confirm with us
Reporting into systems you already operate
These three are supported, and they are the reason a new site can join the monitoring arrangement you already run instead of starting a second one. They sit in their own section deliberately: unlike the interfaces above, they are not covered by figures in the published specification sheets, so we confirm the detail for your configuration rather than let you assume it.
| Interface | What it connects and how |
|---|---|
| Modbus | Supported. The implementation depends on your configuration, so we confirm the detail directly rather than publish a blanket claim. |
| DNP3 | Available for utilities, water, oil and gas, so Sentor sites report into an existing SCADA master. We confirm the conformance level with you when you enquire. |
| SNMP | v1, v2 and v3 for network management integration. The ST9-302 board attaches up to 48 SNMP devices and runs standalone or as a slave to the controller. |
How a site reports back
Communications
Chosen per site. Different sites on the same network can use different methods, and the controller behaves identically either way.
| Interface | What it connects and how |
|---|---|
| Cellular | The ST30G provides always-on multi-band 3G/4G with a static IP address and SSL-encrypted access. |
| Radio | The ST303 RF modem serves sites with no cellular coverage. |
| Satellite, fibre and microwave | Alarms and data travel over whichever bearer reaches the site; the controller is indifferent to which. |
| Landline, voice and DTMF | The ST330 dials out to a computer, telephone or pager, announces the alarm and the device reading in a recorded voice, and accepts keypad responses — so an operator can change the state of a device from any phone. |
Integration scenarios
What this looks like on a real site
Each of these follows the same shape: something happens, Sentor receives it, logic decides, an action follows, and somebody is told.
Fire or security panel raises an alarm
| Trigger | A fire panel, intruder panel or door contact changes state. |
| What Sentor receives | A clean contact closure on a digital input, or a supervised loop where a cut cable must also be detected. |
| Logic applied | The scenario stored on the controller identifies which alarm it is, checks whether the site is armed and whether the condition has persisted, and decides who needs to know. |
| Action | Relay outputs operate, the event is written to the on-board log with a time and date stamp, and notification goes out. |
| Who gets the result | The nominated person for that alarm at that site, by SMS, email, pager or a voice call announcing the alarm and the reading. |
The log entry is captured on site whether or not the site was in contact with anyone at the time, which is what makes it useful for an audit afterwards.
An alarm is announced over the site’s two-way radios
| Trigger | Any monitored alarm condition — fire, intrusion, plant failure, loss of mains — where the people who need to act are out on the site with a handset rather than at a desk. |
| What Sentor receives | The condition arrives on a digital or analogue input like any other. |
| Logic applied | Scenario logic decides that this particular alarm warrants alerting people in the field rather than only back at base, and which announcement applies to it. |
| Action | A relay output operates into the radio system’s alarm or key input. The handsets either receive the pre-recorded announcement held for that alarm — naming the site and what has happened — or sound the radio’s own alert tone, depending on how the interface is set up. |
| Who gets the result | Everyone carrying a handset on that talkgroup, at the moment it happens, rather than after a phone call has been answered and relayed. |
Sentor’s part is the decision and the trigger: it recognises the condition and operates the contact. The transmission is made by the radio equipment, so what the handsets actually hear depends on that system. This is a wiring interface, not a software integration with a particular radio platform — tell us the radio and dispatch equipment on site and we will confirm what the interface needs.
An authorised operator sends a command to the site
| Trigger | Someone needs to act on a site remotely — reset a pump, open a gate, restart equipment, silence an alarm. |
| What Sentor receives | A DTMF keypad response over a phone call through the ST330, an instruction from SitePRO or SentorCloud, or a contact closure from an external system wired to a digital input. |
| Logic applied | The controller checks the programmed conditions before acting — a gate does not open if the interlock says it should not, regardless of who asked. |
| Action | The relevant relay operates: reset a pump, open or close a gate, start or stop equipment, activate a warning light, acknowledge an alarm, or run a predefined site scenario. |
| Who gets the result | The operator gets confirmation, and the action is written to the event log against the time it happened. |
The ST330’s voice-and-keypad path is documented Sentor functionality. Command paths through a third-party dispatch platform depend on that platform offering a contact output or a gateway — ask us and we will confirm what is achievable with your equipment.
Generator and standby power
| Trigger | A generator starts, fails to start, runs, faults, or its supporting systems drift. |
| What Sentor receives | Run and fault contacts on digital inputs; battery voltage, fuel level and temperature on analogue inputs; engine data over CAN 2.0 on the i7000 where the controller supports it. |
| Logic applied | Scenario logic distinguishes an expected start from a failure to start — if mains has failed and the generator has not run within the set period, that is a different event from a routine exercise run. |
| Action | Notification is raised, the sequence is logged, and outputs can operate as configured. |
| Who gets the result | The technician responsible for that site, before the standby supply is needed rather than after it did not arrive. |
Which signals are available depends on what the generator controller exposes. Send us its documentation and we will tell you what can be read.
Transmitter and RF performance at a tower site
| Trigger | Transmit power drifts, reflected power rises, or received signal strength falls. |
| What Sentor receives | Forward and reflected power through the ST505 bi-directional coupler on two analogue inputs; RSSI as an analogue signal. |
| Logic applied | The controller calculates a quadratic each time the transmitter keys up, giving readings accurate to decimal level, and compares them against the thresholds set for that site. |
| Action | An alarm is raised on a VSWR excursion, the trend is logged for compliance reporting, and the transmitter channel can be changed remotely. |
| Who gets the result | The RF technician, with the reading rather than just the fact of a fault — so the visit is planned with the problem already understood. |
The coupler is non-invasive with almost zero insertion loss and screws in line on the coaxial cable. Sentor supplies a calibration utility for commissioning.
Reporting into an existing SCADA or network management system
| Trigger | You already operate a SCADA master or an NMS and do not want a second, parallel monitoring platform. |
| What Sentor receives | Site readings and alarms as normal, from the same inputs. |
| Logic applied | The controller continues to run its own on-site logic; reporting upstream does not replace local decision-making. |
| Action | Data is presented to the upstream system over DNP3 for utilities work, or SNMP for network management. Modbus is supported where the configuration calls for it. |
| Who gets the result | Your existing operators, in the system they already watch. |
These three protocols are stated by Sentor but are not covered in the published specification sheets, so confirm the specific requirement with us before writing them into a tender. We would rather establish it now than have it surface at commissioning.
Named integration
ThinkBoxx
ThinkBoxx states on its own site that its AI-IoT automation platform integrates with Sentor remote control systems, and with Clipsal C-Bus. Their platform adds a cloud dashboard and automation layer over lighting, HVAC, energy, access control, fuel tank and environmental monitoring across a portfolio of sites.
Where Sentor is the controller that senses and switches at the site, that platform is the layer that presents and automates across many of them. The site keeps its own scenario logic either way, which is what allows it to keep working when nothing upstream is reachable.
Before you specify it
The integration claim above is ThinkBoxx’s own, published on their site. Ask us to confirm what it covers for your configuration before you build a requirement around it.
Named integration
Delta Radio Group — two-way radio
Delta Radio Group supply professional two-way radio: analogue, DMR digital, push-to-talk over cellular and LTE, and dispatch. Most of their range is DMR, and their radios are carried in Australia by Radio Industries — the same distributor that supplies Sentor there.
The two meet at the alarm. Sentor recognises a condition at the site and operates a relay into the radio system; the radio system carries the announcement to the handsets. A fire alarm at a pump house can put a spoken message across the talkgroup, or sound the radios’ own alert, at the moment it happens — useful where the people who have to respond are already on site and already carrying a radio.
Most professional radios and dispatch equipment accept a contact input of this kind, so this is not limited to Delta’s range. What differs between models is the wiring and what the radio does with the trigger, which we confirm per site.
Before you specify it
Send us the radio model and the dispatch equipment you run. We will tell you what the interface needs and what the handsets will hear before you build a requirement around it.
What we do not claim
Where the line sits
An interface is not an integration
Sentor can close a contact into another manufacturer’s equipment, and read a contact that equipment provides. That is a wiring interface and it is how most of this is done in practice. It is not a software integration with that manufacturer’s platform, and we do not describe it as one.
Sharing a site is not integration
Plenty of equipment operates at sites where Sentor is installed without any connection to it. Where two systems genuinely exchange signals we will say exactly how; where they simply coexist, we will say that instead.
Ask before you commit
If a tender, a purchase order or a design depends on a specific integration, confirm it with us in writing first. Finding out at commissioning is expensive, and it is entirely avoidable.
Tell us what is already on the site
Send us the equipment list — panels, generators, instruments, access readers, radio systems, the SCADA or NMS you run. We will tell you what connects directly, what needs an interface, and what does not connect at all.