DEV Community: QuarkView

Debugging nighttime PoE camera restarts: power, cable and recording checks

QuarkView — Thu, 15 Oct 2026 00:29:25 +0000

A PoE camera can work during the day and restart when its lighting activates. Power is one possible cause; a frozen live view alone does not prove a camera restart.

Capture the symptom

Note the affected channels, failure time and whether other cameras fail together. Check uptime, logs and port counters where available. Compare live view with recorded footage. Keep the original settings and change one variable at a time.

Check power at two levels

Match the exact camera's supported input and maximum demand to the source's per-port capability. Then check the total shared budget. Enough ports does not mean enough power. Include cable loss and lighting, heaters or motors where fitted.

For an illustrative supply-side plan, eight branches requiring 12 W each, including cable losses, need 96 W. Adding an illustrative 20% allowance gives 115.2 W. A source with a 60 W shared budget cannot meet that plan. The allowance is an example, not a standard.

Axis explains typical and maximum camera power. Its measurements describe Axis products; use your own models' specifications.

Isolate cable, port and camera

During an agreed maintenance window, test with a known-good compatible port and a short known-good cable. Do not substitute an unmatched passive PoE injector. If the issue disappears, inspect the original route, connectors, damage and moisture. If the failure follows the camera, review its firmware, settings, temperature and hardware with the manufacturer.

Activate the intended nighttime functions using the manufacturer's instructions. Observe power allocation, link status and uptime with other cameras operating. Avoid changing several settings at once.

Verify recording after the change

Check all channels across a representative night period, including timestamps, playback and export. If backup power is required, include the PoE source and recorder, then test continuity during an agreed outage window. A working live image is not a complete handover test.

Use the QuarkView PoE switch planning guide to compare port capacity, shared power and network layout for your camera system.

NVR storage arithmetic: bitrate, units and mixed camera groups

QuarkView — Thu, 15 Oct 2026 00:23:25 +0000

A camera's resolution does not determine recording storage. Start with the average bitrate of the stream you will actually record, camera count and recording schedule.

Formula and units

Video TB = sum(camera count * average Mbps) * hours/day * days * 0.00045

Mbps means one million bits per second; TB means one trillion bytes. This estimates encoded video only, before audio, recorder overhead and reserve space.

Eight cameras averaging 4 Mbps, recording 24 hours/day for 30 days, use 10.368 TB of video payload. A 4 TB allocation for video holds about 11.57 days with the same assumptions. These are calculations, not measured recorder results.

Mixed camera groups

Four cameras at 4 Mbps plus two at 2 Mbps total 20 Mbps. At 24 hours/day for 14 days, the payload is 3.024 TB. Calculate different recording schedules separately. Use representative busy and nighttime measurements when available.

Adding 20% to that payload gives 3.6288 TB. Reserving 20% of total capacity instead requires 3.024 / 0.8 = 3.78 TB. Neither percentage is a universal manufacturer requirement.

Check assumptions and verify retention

A configured bitrate ceiling is different from an average. Event recording depends on activity and pre/post-event buffers; it does not guarantee a fixed saving. Do not apply another codec discount to a bitrate that already reflects compression.

Check supported drive models, bays, per-drive capacity, redundancy and actual space available for video. Review every channel, playback and export. A one-day sample can refine a forecast; only checking the required recording window after enough time has elapsed verifies retention.

Axis explains bitrate-control methods; its available controls depend on the model.

Use the free QuarkView storage calculator and worksheet to compare drive capacity and recording days for your camera setup.

The camera sees it. Did the SD card save it?

QuarkView — Thu, 08 Oct 2026 15:55:30 +0000

ICSee WiFi camera, shown in the QuarkView camera catalogue.

A live camera image is easy to mistake for a working recording system. You open the app, see the driveway and receive an event notification. Later, when you need the clip, the card may have stopped recording, the event may never have triggered, or the footage may already have been overwritten.

Choosing the card is only part of solving that problem. The useful acceptance test is whether the intended person can find, play and export the required interval.

Begin with the camera, not the card listing

Check the exact camera model and firmware before buying storage. Confirm a usable microSD slot, supported capacity, card family and formatting instructions. Also check whether the camera supports continuous recording or saves only event clips. Wi-Fi, PoE, battery and solar descriptions do not establish those features.

A physically fitting card can still be incompatible. Save needed recordings before initializing a supported card according to the camera manual: formatting erases existing data.

Endurance and speed solve different problems

A card used for occasional file transfers experiences a different workload from a camera repeatedly writing and overwriting footage. High-endurance cards are designed for intensive writing, but the actual rating, operating temperature, warranty conditions and camera recommendations still matter.

Sustained write performance determines whether the card can keep up with the saved stream. Endurance addresses repeated writes over time. Neither a large capacity nor an impressive advertised read speed answers both questions. Follow the camera's required speed class and interface, and purchase through a traceable supplier.

Treat recording time as an estimate

For continuous recording, calculate from usable capacity and the total bitrate actually saved. As an arithmetic example, 128 GB at a constant 4 Mbps produces about 71.11 hours of video payload. That assumes all advertised capacity is available and excludes audio, file overhead, reserved space and gaps. It cannot promise three days of evidence.

Event recording adds another uncertainty: the amount of activity changes. A quiet test day can exaggerate expected retention, while missed triggers mean missing events rather than extra storage efficiency. Observe a busy interval and the oldest playable clip under normal use.

Finish with evidence you can use

During an agreed commissioning window, record a known interval and inspect its timestamp, image detail and event boundaries. Export it with the intended account and play the saved file on the intended computer. Check audio if enabled. Keep the test export outside the camera.

Confirm loop overwrite behavior and save important footage promptly elsewhere. If errors recur, preserve accessible evidence, check compatibility and recording settings, then investigate power, temperature and storage status. Try the prescribed initialization and a known-good compatible card after exporting needed footage. Change a single variable at a time.

The SD card selection and recording acceptance guide includes the calculation assumptions, an ordered troubleshooting procedure and a practical handover checklist.

Prepared with AI assistance; calculations and manufacturer references were checked before publication.

Plan Backup Power for Cameras, PoE Equipment and NVR Recording

QuarkView — Thu, 08 Oct 2026 15:48:14 +0000

Front and rear views of the 6708KR PoE recorder listed by QuarkView.

Plan backup power around the full recording path: cameras, their PoE power source, the NVR and any network equipment needed to carry video. Use that path to build a load budget and check recording during a controlled power interruption.

Trace that path before shopping. A camera plugged into the recorder’s own PoE ports has a different power path from a camera supplied by a separate switch. In the second layout, keeping only the NVR alive leaves the cameras without power. Network equipment that carries the video must survive too. A router needed only for internet access may be unnecessary for isolated local recording, but that depends on the actual topology.

Budget the input you will really back up

Consider an explicitly hypothetical installation:

Essential device	Assumed AC load
NVR with storage, excluding camera power	25 W
Populated PoE switch, including its cameras	70 W
Router required for the video path	10 W
Total	105 W

The important detail is the second row. Its 70 W already includes camera power. Adding the individual camera watts again would count the same load twice. An NVR with built-in PoE can create the same mistake: total measured recorder input may already include the cameras.

If you choose an illustrative 25% planning allowance, the calculation becomes 105 × 1.25 = 131.25 W. That is a capacity planning figure, not a battery-runtime forecast. Replace these assumptions with documented demand and measurements from the installation, including night illumination, the installed drives and startup behavior.

Capacity and runtime answer different questions

Check both UPS limits: watts for real power and VA for apparent power. Do not infer watts or backup minutes from a VA label alone. Use the exact model’s official runtime curve or calculator for the intended load and battery configuration.

There is a practical reason to do this. CCTV Camera World publishes roughly 40 minutes at 100 W and 17 minutes at 200 W for one 1000 VA / 600 W UPS at maximum battery health. Those figures describe that particular product. They neither predict our hypothetical system nor apply to every 1000 VA unit. Battery condition and operating circumstances matter too.

Accept the recording, not just the lights

Agree a controlled outage test with the site owner and follow the UPS manufacturer’s procedure while preserving protective earth. Verify battery operation, all required devices and the absence of overload. After restoring power, replay every channel across the interruption and recovery timestamps. Check continuity, time, storage health and resumed recording; export a sample and open it in the intended player.

Test remote access separately if it is required. Backing up your router does not guarantee that the internet provider remains online. Record gaps and unresolved exceptions, and repeat the checks after expanding the system.

The complete camera UPS planning and recording-test guide includes the load worksheet, official source links and the related PoE installation planning steps.

Prepared with AI assistance; calculations and manufacturer references were checked before publication.

Before You Buy a Camera Junction Box, Check What It Actually Supports

QuarkView — Thu, 08 Oct 2026 15:46:37 +0000

YN-BOX-CWB junction box, shown in the QuarkView accessory catalogue.

A camera junction box can make an installation much tidier. It can also become an expensive detour if you choose it before checking the camera base, connectors and wall. The useful question is not whether a box looks large enough. It is whether the complete assembly fits, seals and stays secure in its intended location.

A connection box may not be a camera mount

Start by checking what the product is designed to do. Some boxes provide an approved base for a camera. Others only contain its cable connections and sit beside a separate camera mount. A flat lid or several holes are not enough to tell the difference.

There is a useful contrast in Lorex’s own documentation. Its JB301 guidance describes direct attachment for compatible fixed cameras. Its AJLP-1W instructions instead require installing the camera beside the box. Neither arrangement should be assumed for another manufacturer’s accessory.

That is why a model-specific mounting drawing matters. Compare the fixing-hole count and spacing with your camera base. Check the screw size and whether an adapter is required. Before drilling, present the approved parts together and confirm that the cable exit will not pinch the camera tail.

Measure the connection, not just the cable

A cable that passes through an opening can still have a connector that will not fit inside the box. The camera socket, Ethernet plug and waterproof sleeve form a much larger assembly than the cable alone. Separate power or audio tails also need protected space.

Try the actual components with the lid open. The lid should close without forcing a plug against it or pushing a wire across the gasket. Leave enough cable reserve for someone to inspect the connection later without pulling on the camera. Support the incoming cable independently so its weight does not hang from the socket.

Treat cable entries as part of the installation

Choose the entry direction before fastening the enclosure to the wall. Use the glands, plugs and other fittings approved for the box and cable. A gland must match the cable’s outside diameter, as well as the opening it attaches to. Unused entries need the specified closures.

Outdoors, a weather-resistant camera body does not automatically protect its exposed connections. Follow the sealing instructions at the lid, connector and wall penetration. Where permitted, a downward drip loop helps rain fall away before the cable enters. Do not add drainage holes or block designed vents without model-specific approval.

Finish with evidence

The wall and fasteners must support the complete installation. Loose siding or damaged masonry needs assessment before equipment is mounted. After assembly, verify live view and recorded playback, check that camera adjustment has not twisted the cable, and save photographs with the accessory model.

Our camera junction-box selection and installation guide includes a handover checklist and the manufacturer references behind these distinctions. Use it alongside the instructions for the exact camera and enclosure you plan to install.

Prepared with AI assistance; calculations and manufacturer references were checked before publication.