> For the complete documentation index, see [llms.txt](https://www.projectpanoptes.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.projectpanoptes.org/build/software/pocs-command-line/powerboard.md).

# PowerBoard

## Overview

You can control and monitor the Power Board from the command line using the `pocs power` command. 

For example:

```bash
# Display the status for each power channel (relay)
pocs power status

# Turn off the fans.
pocs power off fans

# Turn on fans by relay index.
pocs power on RELAY_2

# See the current readings for all power channels.
pocs power readings
```

## Commands

### `status`

Get the status of the relays.

```
(conda-pocs)  panoptes@panoptes  pocs power status
[RELAY_0] weather_station..... ON
[RELAY_1] unused1............. OFF
[RELAY_2] fans................ ON
[RELAY_3] unused3............. ON
[RELAY_4] mount............... ON
(conda-pocs)  panoptes@panoptes  
```

### `off/on`

Turn on or off the relay.

```
(conda-pocs)  panoptes@panoptes  pocs power off fans
{'relay': 'fans', 'command': 'turn_off'}

(conda-pocs)  panoptes@panoptes  pocs power status
[RELAY_0] weather_station..... ON
[RELAY_1] unused1............. OFF
[RELAY_2] fans................ OFF
[RELAY_3] unused3............. ON
[RELAY_4] mount............... ON

(conda-pocs)  panoptes@panoptes   pocs power on fans
{'relay': 'fans', 'command': 'turn_on'}

(conda-pocs)  panoptes@panoptes  pocs power status
[RELAY_0] weather_station..... ON
[RELAY_1] unused1............. OFF
[RELAY_2] fans................ ON
[RELAY_3] unused3............. ON
[RELAY_4] mount............... ON
```

### `control`

A different way to control the relays.

```
(conda-pocs)  panoptes@panoptes  pocs power control --relay fans --command turn_off
{'relay': 'fans', 'command': 'turn_off'}
```

### `readings`

Shows a simple bar plot of the most recent power usage statistics for each relay. Probably not actually useful.

```
(conda-pocs)  panoptes@panoptes  pocs power readings
ac_ok............... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ [1]
weather_station..... ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ [0]
unused1............. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ [0]
fans................ ▆▅▆▅▄▆▅▄▅▆▆▄▇▆▄▆█▅▄▅▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ [2]
unused3............. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ [0]
mount............... ▄▂▄▄▄▄▂▁▄▄▂▂▄▄█▅▂▂▂▂▂▂▄▂▄▄▄▂▂▂▂▂▂▅▇▄▄▂▂▂▂▄▂▂▂▂▂▂▄▂ [22]
```

### `restart`

Restart the power (`supervisorctrl`) service. Use if getting errors with the other commands.

```
(conda-pocs)  panoptes@panoptes  pocs power restart
```

## Configuration

The configuration for the power board is stored under the `environment.power` key:

```
(conda-pocs)  panoptes@panoptes  pocs config get environment.power
{
    'arduino_board_name': 'power_board',
    'mean_interval': 5,
    'name': 'Trucker Power',
    'port': '/dev/ttyACM0',
    'record_interval': 60,
    'relays': {
        'RELAY_0': {'default_state': 'on', 'label': 'weather_station'},
        'RELAY_1': {'default_state': 'off', 'label': 'unused1'},
        'RELAY_2': {'default_state': 'on', 'label': 'fans'},
        'RELAY_3': {'default_state': 'off', 'label': 'unused3'},
        'RELAY_4': {'default_state': 'on', 'label': 'mount'}
    }
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.projectpanoptes.org/build/software/pocs-command-line/powerboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.