VTScada operators need to see UPS status, estimated runtime, and voltage while a standalone UPS keeps the RTU and two switches online long enough for a generator to start. Treat this as three commissioning jobs: size the battery-backed supply for the actual load, expose UPS telemetry through a supported network interface, and prove the generator handoff under load.
What should the operator see in VTScada?
Define the required data before choosing a UPS or network card. The requested screen values are operating status, runtime, and voltage; on-battery status and estimated minutes remaining are examples of values available from some UPS/card combinations. Confirm the exact values and meanings in the selected card’s MIB or register map and the VTScada driver configuration. A displayed voltage is a UPS measurement; it is not a substitute for a power-quality instrument.
Plan the signal path as UPS measurement → network management card or interface → Ethernet network → VTScada driver → tags → operator display. A UPS can be powered correctly while its telemetry path fails. Conversely, a working tag does not prove the UPS can sustain the load or accept generator power.
| Operator symptom | Likely area to check | Commissioning check |
|---|---|---|
| Status, runtime, or voltage is stale or missing | Network path, protocol configuration, card data exposure, driver binding, or tag mapping | Check card reachability, driver diagnostics, and the source value for each mapped tag |
| UPS reports on battery after utility returns | Generator output or UPS input acceptance | Observe the UPS input and operating state during generator transfer |
| Runtime falls short of the requirement | Load, battery condition, or selected UPS capacity | Measure the complete connected load and time a discharge/transfer test |
Check: Write down each operator value, its source in the UPS/card data, and the tag that will display it before selecting the communications method.
How do you size the UPS for the RTU and switches?
Measure the RTU and both switches together in their intended operating state. Include any Power over Ethernet load; a switch’s unloaded draw can materially understate the demand when it supplies powered devices. Use the measured watts and the UPS manufacturer’s runtime data for the intended load, rather than estimating runtime from the VA rating alone. Check both watt and VA limits against the connected equipment and the UPS specifications.
The stated need is a few minutes for a generator start, with five minutes as an approximate requirement. Select a model whose runtime at the measured load gives meaningful margin beyond five minutes when the battery is new; battery aging and a delayed generator start reduce that margin. One field practice is sizing for two hours to cover generator repair rather than only generator start time. That is an operational-resilience choice, not a universal runtime requirement; decide whether the site needs start-ride-through or longer outage coverage.
A suggested CyberPower OR500LCDRM1U example is rated 500 VA / 300 W, with a stated 12 minutes at half load and 3 minutes at full load. Those figures illustrate why runtime must be checked at the actual load. However, that unit is rack-mounted, while the installation needs a standalone UPS for a small room without a rack. It is therefore not a form-factor match, and the supplied runtime figures do not identify a suitable standalone replacement. Compare candidate models’ load/runtime curves and mounting form before ordering.
Check: Record the measured combined watts, any PoE demand, the required ride-through time, and the candidate UPS runtime at that load. Reject candidates that do not meet the form-factor or runtime requirement.
Which UPS form and network interface fit the installation?
Choose a standalone enclosure and confirm the required supply/output voltage against the RTU and switches. Available approaches mentioned for this application include APC or Eaton UPS products with network access, desktop UPS units, DIN-rail DC UPS units, and Phoenix Contact UPS products with EtherNet/IP and/or Modbus. These are alternatives, not interchangeable specifications: verify the exact model, voltage, load capacity, runtime, interface, and supported data before purchase.
Budget for the communications card as well as the UPS. The suggested OR500LCDRM1U example requires a separate RMCARD205 for Ethernet/SNMP. It has six outlets, of which two are surge-only; the RTU and both switches must use battery-backed outlets. Its listed MSRPs were described as totaling about $679, but that rack-mounted example does not resolve the standalone requirement.
APC network management cards are one path; certain cards support Modbus TCP, and AP9630 and AP9640 were identified as supporting Modbus. An AP9613 dry-contact card is another approach when a PLC only needs a discrete indication such as “mains power present.” Dry contact reports limited state, not the status/runtime/voltage set requested for VTScada. Confirm the exact UPS/card compatibility, protocol support, and available data points for the selected combination.
Check: Confirm the selected standalone UPS, its battery-backed outlets, and the exact compatible card/interface against the equipment load and required telemetry before proceeding.
Should VTScada use SNMP or Modbus?
Use the protocol supported by both the selected UPS interface and the installed VTScada configuration. VTScada has an SNMP driver. SNMP is a practical path for UPS telemetry when the card exposes the needed objects; load or consult the card’s MIB and verify that status, runtime, and voltage are available from this exact UPS/card combination.
SNMPv3 may be preferred by a site’s cybersecurity review when the UPS card and network policy support it. Confirm authentication/privacy settings and approval with the site’s cyber assessment process. Modbus TCP can be easier to configure in some SCADA environments and is widely supported in legacy systems, but ease of mapping does not determine security approval. Where a card supports both, choose based on driver support, exposed values, network policy, and maintainability.
| Choice | Use when | Verify before configuring |
|---|---|---|
| SNMP, preferably SNMPv3 when approved and supported | VTScada’s SNMP driver and the card expose the needed UPS objects | Version/security settings, MIB objects, polling access, and tag value/units |
| Modbus TCP | The UPS card supports it and the site accepts the protocol | Register map, data types, scaling, address conventions, and driver compatibility |
| Dry contact to a PLC | A discrete mains-present alarm is sufficient | Contact state, PLC input wiring, alarm logic, and loss-of-comms behavior |
Check: With the UPS and card selected, confirm that the approved protocol returns the required points before creating the final operator display.
How do you bind UPS data to VTScada tags?
Configure the card’s network settings and the VTScada driver connection, then map each displayed tag to a documented UPS value. Keep tag faults separate from binding faults: a tag can exist but point to an invalid or incorrectly scaled source, while a correct mapping can still show bad quality if the driver cannot reach the card.
- Set the card’s network and protocol/security configuration according to the site’s addressing and access policy.
- Use the VTScada SNMP driver or the supported Modbus driver path. For SNMP, identify the relevant MIB objects; for Modbus, use the card’s register map.
- Create or inspect tags for status, runtime, and voltage. Check units, data type, scaling, and state interpretation against the card documentation.
- Review driver diagnostics and tag quality. If a value is absent, test reachability and protocol access first, then verify the object/register mapping before changing the display.
- Show communication quality or stale data distinctly from a valid UPS state so operators do not mistake a telemetry failure for a normal power condition.
Do not infer power quality from UPS status or voltage telemetry. A separate power-monitoring instrument is the appropriate tool when the requirement is detailed power-quality analysis.
Check: Compare each live VTScada value and quality state with the corresponding value shown by the UPS/card interface, and correct any tag-to-source mismatch.
How do you prove the UPS transfers to generator power?
A UPS may continue draining its battery after the generator starts if the generator’s output is outside the UPS input acceptance range. Frequency variation is a known cause to investigate. A runtime test without generator transfer does not prove the ride-through sequence.
- Connect the RTU and both switches to battery-backed outlets, not surge-only outlets, and operate them in the normal load condition.
- Record the measured load and starting battery condition; confirm VTScada is receiving the intended status and runtime values.
- Under an approved commissioning procedure, interrupt utility input and observe the UPS transfer to battery and the operator indication.
- Start the generator and observe whether the UPS accepts generator input and returns to its expected operating state rather than continuing to discharge.
- Time the actual runtime through the handoff and confirm the RTU, switches, network path, and VTScada values remain available.
If the UPS rejects generator power, inspect the generator frequency and voltage during the transfer and compare them with the selected UPS input acceptance specifications. Read those limits from the exact UPS documentation; do not assume a generic tolerance. Resolve the generator/UPS compatibility issue and repeat the complete sequence.
Check: Record a successful utility-loss transfer, generator start, UPS acceptance of generator power, and measured runtime under the installed load.
What should the final VTScada commissioning test prove?
Run the full sequence with the actual standalone UPS, card, RTU, switches, and VTScada tags. Confirm both power continuity and data validity; either can fail independently.
- Verify the operator display shows normal UPS status, a plausible runtime value, voltage, and good tag quality.
- Remove utility power and verify the status changes to the expected battery condition while the RTU, switches, and telemetry remain online.
- Start the generator; confirm the UPS accepts its input, runtime stops declining as expected, and the equipment remains powered.
- Restore utility power and confirm normal status returns. Check that status, runtime, and voltage update rather than remaining stale.
- Document measured load, observed runtime, selected protocol/card, tag mappings, and the successful transfer result for maintenance and future battery checks.
The installation passes only when the devices stay powered through generator handoff and the displayed UPS values recover as live, correctly mapped data.
What happens if the UPS screen values are missing?
What happens if VTScada shows no UPS values?
Check card reachability and driver diagnostics, then confirm protocol access and the MIB object or Modbus register mapping. Distinguish a failed network/driver connection from an incorrect tag binding.
What happens if the UPS has Ethernet but no runtime tag?
Ethernet connectivity does not guarantee that the card exposes estimated runtime. Check the exact card’s MIB or register map and verify support for the selected UPS/card combination before relying on that value.
What happens if the generator starts but the UPS stays on battery?
Check generator voltage and frequency during the transfer against the UPS input acceptance limits. Frequency variation can prevent acceptance, so use the specifications for the exact UPS and repeat the handoff test after correction.
What happens if five minutes is enough for generator start?
Size from the measured RTU and switch load, including PoE, and verify runtime at that load. Choose margin beyond five minutes because battery aging and generator delay can consume the nominal ride-through window.
What happens if the UPS only needs to report mains status?
A dry-contact card wired to a PLC can provide a discrete mains-present indication. It does not provide the full status, runtime, and voltage telemetry requested for VTScada; finish by testing the complete utility-loss and generator-acceptance sequence.