> For the complete documentation index, see [llms.txt](https://docs.decharge.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decharge.network/deployment-and-operations/pre-install-checklists/titan-mini-30kw.md).

# Titan Mini (30kW)

Detailed pre-install guide for Titan fast chargers including 3-phase input, grounding, and safety validation.

In addition to the General Requirements mentioned [here](/deployment-and-operations/pre-install-checklists.md), the device specific requirements for DeCharge Titan Mini (30kW) device are as follows:

**Mounting and Foundation**

* Concrete base prepared as per DeCharge installation blueprint
* Safety clearance of at least 0.5 meters on all sides
* Anchor bolts installed and visible
* Canopy or shed installed for protection

**Power Input Requirements**

<table><thead><tr><th width="106.800048828125">Voltage</th><th width="124.20001220703125">Transformer</th><th width="359.4000244140625">Cable Size</th><th>Breaker Size</th></tr></thead><tbody><tr><td>415V</td><td>50 KVA</td><td>35 sq.mm aluminium or 25 sq.mm copper</td><td>72A</td></tr></tbody></table>

* Breaker panel must be within an accessible range
* Neutral wire of 0.5 core must be connected using proper lugs
* Neutral-to-earth voltage must be below 2V

**Earthing**

* Two earthing pits required
* Cabling: 25 x 3 mm tinned copper bus bar or 25 sq.mm single-core copper wire
* Lugs: Ring-type aluminium or copper lugs for grounding points

**Internet Connectivity**

* LAN: Cat6 cabling with proper termination and surge protection
* 4G/5G SIM: Valid SIM with strong signals
* Wi-Fi: High-speed router, no competing devices, good coverage

**Safety Infrastructure**

* Safety bollards installed
* LED lighting in place
* Fire suppression systems if required by local code
* Security arrangements if in a commercial or public location

**Documentation Required**

* Confirmation of grid connection or power availability
* Approved CMS form with device mapping
* Signature of host or location owner
* Photographs of breaker, cables, and mounting area

Please fill out the interest-cum-pre-requisite form if you're interested in installing a 30kW Titan Mini DC Charger at your location:

{% embed url="<https://drive.google.com/file/d/1455ZWxltQoiMk-4vaRjOus-3BTMqGoFF/view?usp=sharing>" %}

Alternatively, you can make a copy of this below document, fill it out, and send it to our email: <chargers@decharge.network>:

{% embed url="<https://docs.google.com/document/d/17Jw4UpsdAUU0RTuNZlAQIaSnWsfC8bjBkfiFVgN-xhs/edit?usp=sharing>" %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decharge.network/deployment-and-operations/pre-install-checklists/titan-mini-30kw.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 `build a script that syncs our docs to a CMS` 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.
