Solar Power and PoE for Off-Grid Networking

A solar power and PoE off-grid networking system uses solar energy to charge a battery, then converts the battery’s DC output into the voltage and connection required by a PoE device. Ethernet data follows a separate path from a switch, router, recorder, wireless bridge or other network source.

This arrangement can power an existing PoE camera, access point or bridge where no mains supply is available. However, compatible connectors are not enough: the battery voltage, converter limits, PoE method, polarity, pinout, device load and network topology must all match.

Trace the solar energy and Ethernet data paths

The easiest way to understand an off-grid PoE installation is to trace power and data separately.

Solar energy path

A typical DC-based energy path is:

PV module: Converts daylight into DC electrical power.
Solar charge controller: Regulates energy from the PV module and manages battery charging.
Battery: Stores energy for use during darkness and periods of limited solar generation.
DC-to-PoE interface: Accepts the available battery-side DC voltage and produces the voltage and pin arrangement required by the powered device.
PoE device: Receives power through the Ethernet cable.

In simplified form:

PV module → charge controller → battery → compatible DC-to-PoE interface → camera or network device

The charge controller is not automatically a PoE source. Similarly, a battery output cannot normally be connected directly to a PoE camera simply because both use DC electricity. A suitable interface must provide the correct output voltage, polarity, pinout and, where required, IEEE detection and negotiation.

Ethernet data path

The data path normally looks like this:

Network source → DC-to-PoE interface → Ethernet cable → powered device

The network source could be:

an Ethernet switch;
a router;
a network video recorder;
a local controller;
a wireless CPE or bridge;
a fibre media converter with an Ethernet output; or
another suitable LAN endpoint.

A basic PoE injector or converter does not create network connectivity. It adds power to an existing Ethernet link. If a remote camera must communicate with a recorder elsewhere, the design still needs a backhaul path, such as a point-to-point wireless bridge, mobile router, fibre connection or wired Ethernet run within its permitted distance.

Keeping these two paths separate during design makes faults easier to diagnose. A device may have sufficient power but no data link, or a valid data connection but insufficient voltage at the far end of the cable.

Separate charging, storage and PoE functions

An off-grid system combines several functions, but each component has a distinct job.

Function	Typical component	What must be checked
Energy generation	PV module	Rated output and compatibility with the controller’s PV input limits
Charge regulation	Solar charge controller	PV voltage, current and power limits; battery profile; protection functions
Energy storage	Battery	Nominal voltage, capacity, discharge limits and permitted charging temperatures
Voltage conversion	DC converter	Input range, output voltage, continuous power and conversion losses
PoE delivery	Injector or PoE interface	Passive or negotiated operation, polarity, pinout and Ethernet capability
Network transport	Switch, router, bridge or recorder	Port speed, topology, addressing and backhaul connection
End load	Camera, access point or other device	PoE standard, voltage range, maximum demand and environmental features

This separation matters when troubleshooting. If a camera disconnects overnight, the cause could be depleted storage, converter undervoltage shutdown, voltage drop, excessive load or loss of network backhaul. Replacing the solar panel will not correct a PoE protocol mismatch, and changing the injector will not fix an undersized battery.

The Maxsol CS12060 solar power system is one example of a solar and storage platform. Its documented configuration includes a 120W monocrystalline panel, a 12.8V 60Ah 768Wh LiFePO4 battery, an MPPT controller and three DC 12V outputs; RS485 is optional. Those nominal ratings do not establish usable delivered energy or a guaranteed runtime. The current configuration should also be checked for controller PV limits, battery charging temperatures and protection behaviour.

Avoid treating the nominal battery figure as energy that can all be delivered to the camera. Available energy is affected by permitted depth of discharge, controller consumption, conversion losses, cable losses, temperature, battery protection thresholds and the actual load profile.

Distinguish passive PoE from IEEE negotiation

“PoE” can describe electrically different systems. The most important distinction is between passive voltage injection and standards-based IEEE PoE.

Passive PoE

A passive injector places a specified DC voltage onto selected Ethernet conductors whenever it is powered. It may not check whether the connected device is compatible before energising the cable.

For a passive PoE connection, confirm:

required device input voltage;
permitted voltage tolerance;
connector polarity;
powered conductor pairs or pinout;
maximum current;
cable and connector suitability;
Ethernet speed support; and
whether power is delivered on spare pairs or data pairs.

A passive output set to the wrong voltage or pin arrangement can fail to start the device and may risk damage. A label such as “24V PoE” is not sufficient on its own because different passive systems can use different polarities and pinouts.

Negotiated IEEE PoE

IEEE PoE power sourcing equipment detects a compatible powered device before applying full operating power. Depending on the applicable standard and equipment, it may also classify or negotiate the available power.

Common device documentation may refer to IEEE 802.3af, 802.3at or 802.3bt. The source and powered device must support a compatible method and sufficient power level. A converter with an adjustable output voltage is not automatically compliant with any of these standards.

Characteristic	Passive PoE	Negotiated IEEE PoE
Device detection	Often absent	Expected as part of standards-based operation
Output behaviour	Voltage may be continuously present	Power is applied after detection
Main compatibility checks	Voltage, polarity, pinout and load	IEEE standard, power class, load and implementation
Adjustable voltage	May be provided	Does not by itself prove compliance
Risk of connecting an unknown device	Higher without full documentation	Reduced when both ends correctly implement the same standard

Before connecting an existing PoE camera, check its datasheet and label for exact wording. “PoE supported” is less useful than a stated IEEE standard or a clearly documented passive input range and pinout.

The Maxsol POE24V DC-to-PoE converter accepts 12–36V DC and provides an 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, and conversion efficiency of up to 94% is a maximum rather than a guaranteed design value. The available facts do not establish IEEE powered-device detection or negotiation, so voltage, polarity, pinout and protocol compatibility must be verified.

The linked solar system and converter are selection examples, not a tested compatible bundle.

Match battery and converter operating voltages

Voltage compatibility must be checked across the complete operating range, not only at the nominal values printed on the product names.

A battery described as 12V does not remain at exactly 12V. Its terminal voltage changes with state of charge, charging conditions, load and battery management behaviour. The converter must continue operating across the battery system’s actual minimum and maximum voltage.

Check the following interfaces:

PV module to charge controller

Confirm the controller’s maximum PV open-circuit voltage, current and input power. These limits should be checked against the selected module and expected configuration. Do not add or substitute panels based only on their wattage.

Charge controller to battery

The controller must use a charging profile suitable for the battery chemistry and system voltage. For LiFePO4 batteries, confirm permitted charging temperatures and how low-temperature protection is implemented. Do not assume every controller, battery management system or enclosure handles cold-weather charging in the same way.

Battery to DC-to-PoE converter

Verify that the converter input range covers:

the battery’s highest charging voltage;
its normal operating range;
its low-voltage region before protection disconnects; and
any brief voltage drop caused by load changes or cable resistance.

If the converter drops out before the battery reaches its intended low-voltage threshold, some stored energy may be inaccessible to the load. If its maximum input is below the battery’s charging voltage, the design is unsuitable even if their nominal voltages appear to match.

Converter to powered device

Set or select an output that the device explicitly supports. Also verify polarity and pinout before connecting the Ethernet cable. A voltage display helps an installer see the configured output, but it does not confirm what reaches the device after cable loss, nor does it verify PoE protocol compliance.

Long cable runs deserve particular attention. Voltage drop increases with current and conductor resistance. Poor terminations, underspecified cable, copper-clad aluminium conductors or damaged connectors can make the problem worse. Measure voltage at the load under operating conditions where practical rather than relying solely on an unloaded reading at the source.

Budget continuous and startup demand

An off-grid design must cover energy over time and instantaneous power at the same time. These are related but different requirements.

Energy, measured in watt-hours, affects how long the battery can support the load.
Power, measured in watts, determines whether the converter, wiring and battery can run the load at a particular moment.

Use the device’s maximum specified input demand rather than relying only on a typical consumption figure. Cameras may consume more when infrared illumination, heaters, wipers or motors operate. Wireless equipment can also show higher demand during startup or periods of heavy transmission.

Hypothetical load example

The following figures are hypothetical assumptions for illustrating the method; they are not measured Maxsol product performance.

Assume a camera normally requires 9W but can reach 15W when infrared lighting is active. Assume the network bridge requires 6W and the supporting electronics require another 2W.

The normal load would be:

9W + 6W + 2W = 17W

The higher operating condition would be:

15W + 6W + 2W = 23W

The converter must support at least the higher simultaneous demand, allowing for its own limits, conversion losses and reasonable engineering margin. The battery and cabling must also supply the corresponding input current at the lowest expected operating voltage.

Do not use a converter’s maximum efficiency figure as the fixed value in a guaranteed runtime calculation. Efficiency varies with input voltage, output voltage and load. Likewise, a 768Wh nominal battery should not be treated as 768Wh delivered to the camera.

For a detailed port-level assessment, use a separate PoE power budget calculation for security cameras. That process is particularly important when a system powers more than one device or includes a PoE switch.

Solar generation and storage must then be assessed against the total daily energy requirement, seasonal conditions, expected periods of poor weather and permissible depth of discharge. The off-grid solar sizing guide for CCTV systems covers that broader exercise. A design that works during favourable summer conditions should not automatically be assumed to meet a year-round requirement in the UK.

Review a compatible architecture checklist

Use this checklist before purchasing components or connecting an existing PoE camera.

Powered-device compatibility

Identify the camera or network device’s exact model and hardware version.
Confirm whether it requires passive PoE or an IEEE standard.
Record its accepted voltage range, polarity and powered pinout.
Check maximum demand, not just typical consumption.
Account for infrared lighting, heaters, motors and other optional functions.
Confirm whether it needs Gigabit Ethernet or can operate at a lower link speed.

DC-to-PoE interface

Confirm that its input range covers the battery’s full operating range.
Check that its output can be set to the device’s supported voltage.
Verify continuous output power at the intended input and output voltages.
Establish whether PoE is passive or negotiated.
Verify polarity and conductor pairing.
Confirm the required Ethernet speed and data pass-through.
Allow for conversion losses rather than assuming loss-free operation.

Battery and charging system

Confirm battery chemistry, nominal voltage and charge-controller compatibility.
Check charge and discharge current limits.
Verify charging-temperature restrictions and protection behaviour.
Treat nominal watt-hours as a rating, not guaranteed usable energy.
Include controller, converter and communications equipment in the load.
Confirm the controller’s PV voltage, current and power limits from the current datasheet.

Network architecture

Identify the source of Ethernet data.
Decide whether backhaul will use cable, fibre, wireless bridging or a mobile connection.
Check cable distance, type, conductor material and outdoor rating.
Plan IP addressing, recording destination and remote management.
Consider what happens if the network link fails while local power remains available.
Decide whether local recording is required as a fallback.

Outdoor installation

Select an enclosure appropriate to the environmental exposure.
Protect entries against water and provide suitable cable glands.
Manage condensation and internal temperature.
Provide appropriate overcurrent, isolation, surge and earthing measures for the installation.
Keep battery, controller and converter installation requirements accessible for inspection.
Avoid placing connectors under mechanical strain.

Commissioning checks

Measure battery and converter input voltage before connecting the load.
Confirm the converter’s output voltage and polarity.
Test the network link before adding PoE where the equipment permits.
Connect the powered device only after confirming protocol and pin compatibility.
Observe startup and maximum-feature operation, not only idle behaviour.
Check voltage at the device end of the cable under load.
Record settings, cable routes and protection devices for future maintenance.

Common mistakes to avoid

Several apparently minor assumptions can undermine an otherwise sound design:

Assuming all PoE is interchangeable: Passive and IEEE PoE are not equivalent.
Treating adjustable output as proof of compliance: Voltage adjustment does not establish detection, negotiation or standards support.
Connecting a camera directly to a battery: Matching nominal voltage does not confirm polarity, pinout or permissible operating range.
Forgetting the data source: Solar power keeps equipment energised but does not provide Ethernet connectivity.
Using average load only: Night-time features or startup demand may exceed the assumed figure.
Equating nominal capacity with usable runtime: Battery and conversion limits reduce delivered energy.
Ignoring cable voltage drop: A correct source voltage does not guarantee adequate voltage at the remote device.
Designing around maximum efficiency: “Up to” efficiency is not a guaranteed value for every load and voltage combination.
Assuming two products form a compatible system: Every electrical and protocol interface still needs verification.

Practical next step

Start with the powered device: document its PoE protocol, maximum load, voltage, polarity, pinout and Ethernet requirements. Then trace backwards through the converter, battery, controller and PV source while designing the network backhaul separately.

When comparing the linked Maxsol models, check them against the required port count, continuous and startup load, cable distance, operating voltages, installation environment and management needs. Confirm the current datasheets and supplied configuration before treating any components as a compatible off-grid system.