> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/installation/camera-deployment/power-a-verkada-camera-over-coax.md).

# Power a Verkada Camera over Coax

Learn how to power a Verkada camera over coax (PoC)

Verkada cameras require Power over Ethernet (PoE) in order to function, which requires an Ethernet cable and a PoE switch or power injector. For organizations that have legacy cameras that run on coax cable, swapping out the cabling with Ethernet can be very time-consuming. The solution is Power over Coax (PoC), which functions just as well as standard Ethernet.

![](https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-a538145e0c3b2b1e1c6579a3c9d4045915c01af3%2F475248359b133253c8c5ca5a0a48e5ab04daa693.png?alt=media)

**Example**: Verkada camera running on PoC

![](https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-40243c12ea22f0684011f448c17b851194a8a435%2F7e0aa3a483426e1b2cb3cd3a79d975705c0b0860.jpg?alt=media)

**Equipment in this photo:**

* Netgear PoE/PoE+ switch
* HighWire Powerstar (PoE/PoE+)
* RG59 Coax cable (300 feet)
* Verkada D30

## Caveats to PoC

Each coax run usually needs an adapter on each end. This is because the signal will need to be converted from PoE to PoC, then back to PoE. If the coax installed is already running PoC, then only one adapter is needed at the camera’s end to convert the signal to PoE.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/verkada-cameras/installation/camera-deployment/power-a-verkada-camera-over-coax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.