> For the complete documentation index, see [llms.txt](https://tempdocs.zerog.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tempdocs.zerog.one/faq/electronics/motherboards/ldo-voron-leviathan.md).

# LDO Voron Leviathan

Information on the LDO Voron Leviathan can be found on this page.

## GitHub

{% @github-files/github-code-block url="<https://github.com/MotorDynamicsLab/Leviathan>" %}

## Guide

{% embed url="<https://ldomotion.com/#/guide/VORON-Leviathan-V12>" %}

<figure><img src="https://3028713203-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc7rngz4fr0ULXRXV6Dnh%2Fuploads%2F7Cx4QyYXz3X6Xi7Elhz7%2Fldo_leviathan.png?alt=media&amp;token=e3cd2f52-7b2c-43b8-8008-f34eb5807d04" alt=""><figcaption></figcaption></figure>

## Pros

* Fully open source
* TMC5160/TMC2209
* 48v support
* Common STM32F446 MCU
* Dedicated mounting space for a Raspberry Pi 3,4,5 or Zero 2W
* Dedicated power supply and uart port for Raspberry Pi
* Reverse polarity protection for main power supply and HV Stepper supply input
* Dimensions: 170x100mm
* Superior stepper driver cooling (passive)
* Great documentation

## Cons

* Onboard Stepper drivers
* Limited ports

## Ports

* 5x Integrated TMC2209 stepper drivers
* 2x Integrated 48V rated TMC5160 stepper drivers
* 7x motor ports
* 4x Fan ports with flyback protection, 5V/24V selectable voltage, and tachometer inputs
* 4x Thermistor ports with 2k2 ohm pullup resistors
* 1x Dedicated LED strip with flicker free dimming down to 1%
* 1x Neopixel port
* 1x Hotend power output up to 180W
* 1x Hotbed power output up to 240W
* 1x Dedicated Z probe port with selectable voltage and integrated diode
* 3x Endstop ports and a filament sensor port
* Canbus port
* EXP1+EXP2

## Stores

We've added some of the stores to the Sourcing Guide [here](/resources/sourcing-guide.md#ldo-leviathan).


---

# 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://tempdocs.zerog.one/faq/electronics/motherboards/ldo-voron-leviathan.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.