PR110 stations can report input, output, and internal-variable states to one supervisory point, but a remote GSM/GPRS design needs a communications controller between the field devices and the operator display. The IP320 panel can supervise several relays on a wired network; it does not originate modem calls. A five-minute polling cycle also cannot provide prompt alarm notification unless the remote architecture includes event-driven reporting.
Communications mechanism
The term local control here means that each PR110 executes pump logic from its own field inputs. Float switches installed at different elevations provide level states, and the relay starts the transfer pumps without depending on the dispatch station. Loss of the supervisory link must therefore affect visibility, not the basic pumping sequence.
The interface connects a PR110 to an RS-485 network. Through that interface, a supervisory device can read the relay's input and discrete-output states. It can also read or change 64 internal variables, which can represent algorithm states, alarm flags, modes, or setpoints.
That wired capability does not make the operator panel a cellular communications controller. A modem path requires equipment that establishes or accepts the connection, detects failure, retries communication, and presents the remote data to the supervisory application. The field or dispatch architecture therefore needs a PLC or equivalent telemetry controller. PLC100 was identified as one example; SPK207 was identified as a possible alternative to IP320.
Check 1: Local station independence
Check 1: disconnect or disable the supervisory communications path while observing one station. Expect the PR110 to continue interpreting its float inputs and controlling its pump outputs. If pumping stops or becomes dependent on a dispatch command, correct the local control design before selecting modems or IP addressing.
| Reading | Meaning | Next action |
|---|---|---|
| Pump sequence continues locally | The supervisory system is monitoring rather than controlling the essential sequence | Proceed to Check 2 |
| Pump sequence waits for the dispatch station | The communications link is part of the control dependency | Move the required sequence and interlocks into the local relay |
| Inputs change but outputs do not follow the intended logic | The fault is in field sensing, local logic, or output control | Resolve that fault before testing remote communications |
Check 2: Wired network scope
Check 2: identify whether all four stations and the supervisory device can share a physical RS-485 network. Expect a continuous wired path that is electrically suitable for the installation and gives each connected device an unambiguous network identity. Read the supported addressing, cable, termination, biasing, distance, and device-count limits from the manuals for the installed interfaces; no values for those limits are specified here.
If all stations can share the wired segment, the IP320 can exchange data with multiple relays rather than being restricted to one PR110. Configure the panel to read only the required input, output, and internal-variable data from each station. If the stations are geographically separated and no common cable exists, proceed to Check 3. Adding cellular modems to each end does not by itself reproduce a transparent multidrop bus: the communications endpoints still need session control, routing, recovery, and data ownership.
Check 3: Polling and alarm latency
Check 3: compare the proposed polling interval with the required alarm-notification time. A stated polling rate of no more than once every five minutes creates a normal detection delay of up to approximately five minutes for a state that changes immediately after a successful poll, before adding connection and processing delays.
| Requirement | Result | Decision |
|---|---|---|
| Periodic operating status only, with five-minute visibility acceptable | Scheduled polling may satisfy the operational need | Proceed to Check 4 |
| Prompt notification of maximum level or flooding | Five-minute polling leaves an excessive blind interval unless that delay is explicitly accepted | Add event-driven alarm reporting or shorten the validated cycle |
| Alarm must survive a temporary communications failure | A transient event may disappear before the next successful poll | Latch the alarm locally and clear it only through defined logic |
Represent maximum level, flooding, communications health, and other alarm conditions as dedicated internal states where the local program requires derived logic. The 64 accessible internal variables provide a possible data area, but reserve and document each variable deliberately. Reading raw floats alone can miss a short-lived condition after the level returns to normal.
Check 4: Modem session and IP addressing
Check 4: identify which device creates the GSM/GPRS session. Expect a PLC or communications controller to perform this function; the IP320 panel does not dial the remote modems. Without that controller, use the panel with a wired connection only.
A static IP address is not an unconditional requirement. The deciding question is which endpoint must accept an inbound connection and how that endpoint remains reachable. If the dispatch system opens a connection directly to a remote station, the mobile service and network design must provide a stable, reachable endpoint or another documented addressing mechanism. If the remote controller initiates an outbound connection to a known supervisory endpoint, the remote modem may not need its own static address. Confirm addressing, inbound reachability, firewall policy, reconnect behavior, and any carrier translation with the selected communications service rather than treating “static IP” as a modem property.
| Observed design | Static-address decision |
|---|---|
Wired RS-485 only |
No IP address participates in the field link |
| Dispatch initiates an IP session to each remote endpoint | A stable reachable destination or equivalent name/routing service is required |
| Remote controller initiates the session | Use the addressing method required by the receiving endpoint and service |
| No device owns session setup and recovery | The design is incomplete regardless of IP assignment |
Resolving architecture and commissioning procedure
- Keep each pump sequence in its local
PR110. Map the installed float inputs, pump outputs, maximum-level state, and flooding state. - Fit and configure the interface for each relay that must join the
RS-485network. - Assign unique device identities and document every input, output, and internal variable presented to supervision. Read the valid identity range and communication settings from the installed-device manuals.
- For a common wired network, configure the
IP320to poll all four relays. For separated sites usingGSM/GPRS, insert a PLC or telemetry controller that owns connection establishment, polling, retry handling, and data transfer. - Define alarm behavior independently from routine status polling. Latch transient critical alarms locally when they must remain visible after the physical input resets.
- Select the IP arrangement from the actual connection direction. Verify reachable addressing with the communications service before commissioning remote polling.
- Record a communications-failure state for every station so stale values cannot appear as current plant status.
Pitfalls include treating a modem pair as a passive cable replacement, using identical network identities, displaying cached values without an age or failure indication, and relying on five-minute polling for urgent alarms. Changing remote setpoints or modes through the accessible internal variables also turns a monitoring system into a control path; apply permissions and validation appropriate to that expanded function.
FAQ
How do I connect one IP320 panel to four PR110 relays?
Connect the relays through their interfaces on a supported wired RS-485 network, give each relay a unique identity, and configure separate reads for each station. Take cable, termination, addressing, and device-count limits from the installed-device manuals.
How do I monitor PR110 stations through GSM/GPRS?
Add a PLC or telemetry controller that establishes the modem session, polls each remote station, retries failed transfers, and supplies current data to the supervisory display. An IP320 alone does not dial the modems.
How do I verify the four-station monitoring system?
Check each station in turn: expect the correct input, output, alarm, and internal-variable indication; then interrupt its communications path and expect local pump control to continue while the display marks that station's data as failed or stale. Restore the link and expect fresh values to replace the stale indication without clearing a latched critical alarm unintentionally.