Solar Power for CCTV Deployment Checklist for NZ Sites

A reliable solar CCTV design starts with evidence, not a panel-and-battery estimate. Before procurement, document every electrical and network load, inspect solar access during the least favourable design month, confirm camera and PoE interfaces, define autonomy and recovery targets, and agree on how the system will be monitored and maintained.

Use the following solar power for CCTV deployment checklist as a pre-design review. It will not predict performance by itself, but it will expose missing information before equipment is purchased, mounted or sent to a remote New Zealand site.

Document camera, recording and backhaul loads

The project load is more than the camera’s headline wattage. It includes everything operating from the solar system during the day and night, including conversion losses and functions that switch on only under particular conditions.

Build a load schedule covering:

• Cameras in normal daytime operation
• Infrared illumination, white light or other night modes
• Pan, tilt and zoom movement
• Heaters, fans, wipers or de-icing functions where fitted
• Microphones, speakers and alarm inputs or outputs
• PoE switches, injectors and DC converters
• Local recorders and storage devices
• Wireless CPE, routers, modems and antennas requiring power
• Environmental sensors and enclosure controls
• Monitoring equipment and auxiliary lighting
• Standby, restart and peak start-up demand

Record measured power where practical. If only a datasheet value is available, identify whether it is typical, maximum or measured under a specific operating mode. A camera listed at a low daytime load may draw substantially more after its infrared LEDs activate, while a radio can vary according to traffic and transmit activity.

Separate day, night and intermittent demand

A single daily watt-hour figure can conceal operational risks. Divide the schedule into at least three categories:

Load category	Evidence to collect	Why it matters
Continuous	Watts, operating voltage and 24-hour duty cycle	Establishes the unavoidable base load
Night-dependent	IR, lighting, heating and seasonal operating hours	Night demand often occurs when there is no solar input
Intermittent	PTZ movement, radio peaks, maintenance access and restarts	Helps identify peak current and converter limitations

Use realistic night length for the design period rather than an annual average. New Zealand’s winter conditions can combine longer nights with lower solar production, so a system assessed only against summer operation may appear stronger than it is.

Define where recording happens

Recording architecture changes both the power requirement and the consequences of a network outage.

For edge recording, confirm:

• Storage medium and recording power draw
• Retention target
• Recording mode, frame rate and resolution
• Behaviour when storage is full
• Recovery after a power interruption
• Whether footage remains accessible if the backhaul fails

For a local NVR or other recorder, include its complete load, storage devices and any supporting switch. For remote or cloud-connected recording, document the required uplink capacity and what happens when the radio or mobile connection is unavailable.

Backhaul traffic should be estimated from actual camera settings rather than nominal port speeds. Include live viewing, recorded footage retrieval, firmware management and periods when multiple cameras transmit simultaneously.

If the architecture is still being selected, the guide to building a solar-powered CCTV system for remote areas provides a broader view of camera, power and communications choices.

Survey shade, mounting and environmental exposure

A desktop solar estimate cannot identify a nearby tree, ridge, building, pole or future structure that blocks the low winter sun. Complete a site survey before finalising panel capacity, battery capacity or mounting hardware.

In New Zealand, the sun tracks through the northern part of the sky. Survey the proposed panel position with particular attention to low-angle winter sunlight and morning or afternoon obstructions. Record photographs, compass direction, panel tilt options and the times when shading begins and ends.

Assess the design month, not just the survey day

Select a design month that reflects the project’s required availability and local seasonal conditions. Document:

• Expected daily solar resource used in the design
• Panel orientation and proposed tilt
• Horizon profile and fixed obstructions
• Seasonal vegetation growth
• Dirt, bird fouling, salt or dust exposure
• The effect of partial shading on the selected panel arrangement
• Any mismatch between the panel location and the camera location
• Cable distance and expected voltage drop between components

Do not assume that “full sun” during a summer inspection represents winter solar access. Where the project has strict continuity requirements, the design inputs should account for periods of poor weather rather than relying solely on monthly averages.

Inspect the mounting environment

The panel, camera, antennas, cabinet and cable entries may face different conditions even when installed on the same pole or structure. Record exposure to:

• Wind and vibration
• Driving rain and water run-off
• Coastal salt
• Dust, mud and agricultural contaminants
• Frost or high enclosure temperatures
• Vegetation and animal interference
• Accidental impact or deliberate tampering
• Flood-prone ground or drainage paths

Confirm that the mounting structure and fixings will suit the assessed site conditions. Product enclosure ratings alone do not establish that the complete installation is weatherproof; glands, cable loops, vents, connectors and installer-made penetrations all affect the result.

The Maxsol CS12060 120W, 60Ah, 768Wh solar system documents a 120W monocrystalline panel, 12.8V 60Ah 768Wh LiFePO4 battery, MPPT controller and three DC12V outputs. These specifications can be compared with a project’s load and interface requirements, but they do not establish universal runtime or suitability for a particular New Zealand site.

Confirm voltage, PoE and data interfaces

Voltage matching is not enough to prove compatibility. The camera, converter, switch and radio must agree on electrical range, PoE method, polarity, pinout and data interface.

For every powered device, record:

• Nominal and permitted input-voltage range
• Maximum continuous power
• Peak or start-up power
• DC connector type and polarity
• PoE voltage and power requirement
• Whether IEEE PoE negotiation is required
• Passive PoE pinout, if applicable
• Ethernet speed and duplex requirements
• Number of powered and data ports
• Earthing and surge-protection requirements
• Maximum cable length and conductor size

Do not treat all PoE as interchangeable

“PoE” may refer to standards-based negotiation or a passive voltage placed directly on selected conductors. A passive converter with the correct output voltage can still be incompatible if the camera expects IEEE negotiation, a different polarity or another pin assignment.

The POE24V DC-to-PoE converter accepts 12–36V DC and provides adjustable 12–57V PoE output, Gigabit Ethernet and an LCD voltage display. Its documented continuous load when converting 12V to 48V is no more than 30W. These facts do not establish IEEE PoE negotiation, so the project team must verify protocol, voltage, polarity, pinout and camera demand before specifying it.

Allow for cable voltage drop on DC runs, especially where a low-voltage source is some distance from the load. Measure voltage at the powered device under maximum expected demand rather than only at the battery or controller terminals.

Verify the complete data path

Confirm whether each camera uses copper Ethernet, fibre, Wi-Fi, point-to-point wireless or mobile backhaul. Check:

• Port count at each network node
• Required Ethernet speed
• VLAN and addressing requirements
• Camera multicast or discovery behaviour
• Management access
• Expected bitrate in both directions
• Latency tolerance
• Failover behaviour
• Local recording during a link outage
• Surge isolation between outdoor network segments

Where wireless is proposed, complete a path survey rather than relying on a model’s distance label. Terrain, vegetation, mounting height, interference, channel width, alignment and local noise can all affect throughput.

For example, the CPE295 5.8GHz directional wireless CPE documents a 2×2 14dBi directional MIMO antenna, one Gigabit LAN port, IEEE 802.3af/at or 9–48V DC power support, and 6.5W full-load consumption. Its range and rate labels are not guarantees of site throughput. Confirm line of sight, link budget, channel conditions and the capacity required by the actual camera configuration.

Set autonomy, recovery and load-priority objectives

Autonomy is the period the system is expected to operate with little or no useful solar charging. It should be a written project objective, not an assumption made after the battery has been chosen.

Agree on:

• Required hours or days of autonomy
• Whether all loads must remain active
• Minimum acceptable camera coverage
• Maximum tolerated recording gap
• Battery reserve or low-voltage threshold
• Recovery expectations after poor weather
• Whether remote intervention is available
• Conditions that justify an auxiliary charging source

A project may prioritise recording over live backhaul, or a critical camera over supplementary cameras. Establish those rules during design so the controller or network equipment can implement them predictably.

Distinguish autonomy from recovery

A battery may support the load through a low-solar period but remain partly discharged when normal weather returns. Recovery describes whether the available panel energy can run the daytime load and replace the consumed battery energy within the required period.

This is why increasing battery capacity alone does not necessarily solve an energy shortage. A larger battery can provide more stored energy, but it can also take longer to recharge if panel input is limited.

Document the assumptions used for:

• Usable battery energy
• Low-temperature and high-temperature conditions
• Battery and controller losses
• DC conversion losses
• Cable losses
• Panel derating assumptions
• Existing daytime load during recharge
• Consecutive low-solar days

For the calculation method, use the separate guide to sizing an off-grid solar power system for CCTV. Keep the resulting worksheet with the project records so procurement and commissioning teams can compare the installed system against the original assumptions.

Define low-energy behaviour

Load shedding should preserve the most important security function. A typical priority plan might distinguish between:

1. Essential recording and critical cameras
2. Communications needed for alarms or health monitoring
3. Secondary cameras
4. Continuous live viewing
5. Non-essential lighting or auxiliary equipment

The correct order depends on the site’s operational purpose. Confirm whether devices can restart automatically and whether repeated low-voltage cycling could corrupt storage, reset settings or leave a network device offline.

Plan monitoring, maintenance and physical access

A solar CCTV site should reveal declining energy performance before the cameras stop. Define what will be measured, where the data will be viewed and who is responsible for responding.

Useful monitoring points include:

• Battery voltage and, where available, state of charge
• Solar charging current or daily energy input
• Load current or daily energy consumption
• Controller warnings and low-voltage events
• Camera and recorder availability
• Storage health and retention
• Link uptime, signal quality and throughput
• Cabinet temperature
• Door or tamper status
• Device restart history

A voltage reading alone may not provide a reliable picture of remaining battery energy. Establish how the selected battery system reports state and what thresholds will trigger investigation.

Design for safe, practical maintenance

Remote does not always mean inaccessible, but access may be expensive or weather-dependent. Record:

• How technicians will reach the panel, camera, antenna and enclosure
• Whether elevated work or specialised equipment is required
• Isolation points for the panel, battery and loads
• Space for test instruments and replacement components
• Labelling and cable identification
• Battery removal path
• Spare fuse and connector requirements
• Vegetation-control responsibilities
• Panel-cleaning and inspection intervals
• Access permissions and site contact details

Place serviceable equipment where it can be inspected without disturbing antenna alignment or camera aim. Allow room for cable bend radii, drip loops, glands and ventilation. A crowded enclosure makes fault-finding harder and can expose connectors to strain.

The maintenance plan should be based on actual exposure. A coastal installation may need different inspection attention from a sheltered inland site, while sites near trees may require regular shade and vegetation checks.

Commission with measured energy and network evidence

Commissioning should show that the installed system matches the design record. A camera image on a laptop proves basic connectivity, but not energy balance, night operation, recording continuity or recovery behaviour.

Collect measurements under known conditions and retain them as a baseline.

Energy commissioning record

Record at minimum:

• Panel open-circuit and operating voltage where appropriate
• Charging voltage and current under stated solar conditions
• Battery voltage before and after testing
• Total load current in daytime mode
• Total load current with all night functions active
• Voltage at each critical load
• Converter input and output voltage
• Peak load during start-up or PTZ movement
• Controller settings and low-voltage thresholds
• Polarity, fuse sizes and cable identification

Check the system after dark or deliberately activate night modes. Confirm that infrared lighting, heaters and any auxiliary illumination are included in the measured load.

Where practical, observe at least one representative charge-and-discharge cycle. Short commissioning windows cannot prove long-term solar performance, so state what was measured and what remains an operating assumption.

Network commissioning record

Capture:

• Camera IP addresses and port assignments
• Switch, router and radio configuration backups
• Measured camera bitrate
• Packet loss, latency and usable throughput
• Wireless signal and noise indicators
• Link performance with all cameras streaming
• Recording continuity during a backhaul interruption
• Remote management and alarm delivery
• Automatic restart after controlled power loss
• Date and time synchronisation
• Retrieval of recorded footage

For directional wireless links, document mounting height, antenna alignment, channel selection and both ends of the path. Do not accept association speed alone as evidence of usable CCTV throughput.

Complete the handover pack

The final project file should include:

• Site and shade survey
• Load schedule
• Solar and autonomy calculations
• Interface and compatibility matrix
• Wiring and network diagrams
• Equipment settings
• Commissioning measurements
• Photographs of cable entries, labels and mounting
• Monitoring thresholds
• Maintenance schedule
• Known limitations and unverified assumptions

The most common pre-deployment failures are incomplete night-load data, unverified PoE interfaces, optimistic winter solar assumptions, no recovery target and no plan for diagnosing a remote outage. Closing these gaps before procurement is usually easier than changing power and network architecture after installation.

As a practical next step, compare the linked Maxsol architecture examples with the project’s required port count, measured load, transmission distance, input and output power, environmental exposure, and management requirements. Treat each device as a separate compatibility decision rather than assuming the products form a tested bundle.