> 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/ja/insutru/camera-deployment/power-a-verkada-camera-over-coax.md).

# 同軸ケーブルでVerkadaカメラに電力を供給する

同軸ケーブル給電（PoC）でVerkadaカメラに電力を供給する方法を学びます

Verkadaカメラは動作するためにPower over Ethernet (PoE)が必要であり、そのためにはEthernetケーブルとPoEスイッチまたは電源インジェクターが必要です。同軸ケーブルで動作する旧式のカメラを使用している組織では、配線をEthernetに交換するのに非常に時間がかかる場合があります。解決策はPower over Coax (PoC)で、標準のEthernetと同様に機能します。

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

**例**: PoCで動作するVerkadaカメラ

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

**この写真の機器：**

* Netgear PoE/PoE+スイッチ
* HighWire Powerstar（PoE/PoE+）
* RG59同軸ケーブル（300フィート）
* Verkada D30

## PoCの注意点

各同軸配線には通常、両端にアダプターが必要です。これは、信号をPoEからPoCに変換し、その後PoEに戻す必要があるためです。設置済みの同軸がすでにPoCで動作している場合は、カメラ側で信号をPoEに変換するためのアダプターは1つだけで済みます。


---

# 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/ja/insutru/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.