> For the complete documentation index, see [llms.txt](https://docs.echook.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echook.uk/circuit-schematics/12-and-24v-inputs.md).

# 12 and 24V Inputs

![](https://lh4.googleusercontent.com/3dqEng96hjpyZ2TGc14n3yMBvOySjo-OmNm2KM1m6NvkkP55jNfYTt651rU0modOr0cWeWOQhuywFpl-0hR0gtRoK-O_QZEt2r7qXEDnJOVWC9U_HNJWF7WJr8MN1OHGIE6hJPDr)

Each battery voltage needs to be stepped down so that, in the worst case, the voltage seen at the Arduino does not exceed 5V. To achieve this, a potential divider was chosen to step 30V down to 5V. Each voltage input uses the same component values.

Resistors R1 and R2 above form the potential divider.

C3 is a ceramic capacitor that forms a low-pass filter with R1 and R2 to remove high-frequency components from the voltage signal. On a Greenpower car, the motor produces small high-frequency voltage spikes as the brushes connect and disconnect from the commutator. The low-pass filter removes these from the signal reaching the Arduino.

BattTotalVTP represents the multimeter test point on the back of the PCB, giving easy access to check the voltage output from the potential divider with a multimeter or oscilloscope.

The circuit to the right is identical, but takes the lower battery voltage as an input.


---

# 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://docs.echook.uk/circuit-schematics/12-and-24v-inputs.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.