<h2>Updated Manual</h2>
<ul>
<li><p>Turns out an out of date manual was on the sd card that was included with the printer. But it was definitely out of date, as it referenced UI items that don't exist, and files that weren't on the SD card.</p>
</li>
<li><p>An updated manual can <a href="https://www.mpminidelta.com/users_manual" rel="noreferrer">be found here</a>
or <a href="https://www.dropbox.com/s/gl5vka5un1mkp2g/mini_delta_manual.pdf?dl=0" rel="noreferrer">possibly out of date here</a></p>
</li>
</ul>
<h2>Resources and sample files</h2>
<ul>
<li>A very helpful <a href="https://www.facebook.com/groups/mpminideltaowners/" rel="noreferrer">Facebook group</a> has a <a href="https://www.facebook.com/groups/mpminideltaowners/files/" rel="noreferrer">bunch of files</a> that are good sample prints. If your manual says you can print a <code>cat.gcode</code> you've got an old manual.</li>
<li>Note: Don't try and just google <code>cat.gcode</code> as I did. The model I found rammed the print head right into the bottom of the printer. The correct model works great (actually called auto00.g on the SD card)</li>
<li>Another great reference site appears to be <a href="https://www.mpminidelta.com/" rel="noreferrer">https://www.mpminidelta.com/</a>, and this <a href="https://www.reddit.com/r/mpminidelta/" rel="noreferrer">reddit</a></li>
</ul>
<h2>Common Problems and Solutions</h2>
<p>The following are some problems I had and their solution</p>
<h3>Can't print custom models</h3>
<p>If you find you can print prebuilt gcodes fine (cat,viking,toothless), but can't seem to print any other models without the print head ramming into the bottom of the printer and going off to the side, you probably haven't setup the autoleveling gcode that's <strong>required</strong>. You can add something like the following line to your software, in a &quot;startup&quot; gcode section. This is detailed in the manual (just search for G29), and <a href="https://www.mpminidelta.com/g29" rel="noreferrer">more info can be found here</a></p>
<pre><code>; auto-levels the build plate with a overall vertical 
; offset of 0.3mm with a center offset of -0.8mm
G29 C-0.8 Z0.3 
</code></pre>
<h3>First layer doesnt stick</h3>
<p>If you find your first layer isn't sticking, or it seems like the plastic is balling up, you need to adjust your startup gcode line mentioned above , so it has a lower Z offset, like Z0.25 for example</p>
<pre><code>G29 Z[offset] ; raises
G29 Z-[offset] ; lowers
</code></pre>
Notes
<ul>
<li>Please try a positive offset value first.</li>
<li>Each printer will require fine tuning in regards to the offset value.</li>
<li>Start with a higher value and decrease as necessary to get good first layer adhesion.</li>
<li>Using a negative offset value may send the nozzle digging into the build plate.</li>
</ul>

CC BY-SA 3.0
2017-08-14T06:38:04.537Z
This is effectively a link-only answer; on its own it does not contain any useful information for someone looking to get started. An answer is supposed to answer the question and, in this case, should help someone get started. You're just pointing the reader to other websites to get the information they need.
Tom van der Zanden
CC BY-SA 3.0
2017-08-14T11:17:44.723Z
There's lots of info here - manual is on sd card, manual is very out of date, where missing files can be found, sample similar files on the internet cause printer to malfunction. That's information - did you know the answer to those questions before you read this answer? True that this ends up being links as well, but I asked and answered the question as it took me about 45 min to get my printer working by googling and trying to find info, and I would've appreciated this answer myself. Thanks!
Brad Parks
CC BY-SA 3.0
2017-09-19T02:11:20.010Z
I agree and don't know what the first guy was tlaking about, unless this answer was majorly upgraded.

I mean it even gives gcode to solve a problem.
user430788
CC BY-SA 3.0
2017-09-19T11:52:04.080Z
In his defense, it has been upgraded as I found more issues that were problematic (gcode being one of them!), but I still thought it was relevant enough to warrant a post ;-)
Brad Parks
CC BY-SA 3.0
2017-08-14T00:36:39.433Z
2017-08-17T19:50:24.103Z
2020-06-18T08:29:41.667Z
Brad Parks
<p>I just got a <a href="https://www.indiegogo.com/projects/monoprice-mini-delta-affordable-starter-3d-printer/x/4856770#/" rel="noreferrer">Monoprice MP Mini Delta</a> from an Indiegogo Campaign, but it came with no printed docs. </p>

<p>How do I get started?</p>

<monoprice-mini-delta>
Monoprice MP Mini Delta - How to get started?
Brad Parks
# Monoprice MP Mini Delta - How to get started?

(Asked by: username_0 on 2017-08-14)

I just got a [Monoprice MP Mini Delta](https://www.indiegogo.com/projects/monoprice-mini-delta-affordable-starter-3d-printer/x/4856770#/) from an Indiegogo Campaign, but it came with no printed docs.

How do I get started?

**Tags:** monoprice-mini-delta


---

## 1 answers

### Answer by username_0 on 2017-08-14. Score: 9 | Accepted answer

## Updated Manual

* Turns out an out of date manual was on the sd card that was included with the printer. But it was definitely out of date, as it referenced UI items that don't exist, and files that weren't on the SD card.
* An updated manual can [be found here](https://www.mpminidelta.com/users_manual)
  or [possibly out of date here](https://www.dropbox.com/s/gl5vka5un1mkp2g/mini_delta_manual.pdf?dl=0)

## Resources and sample files

* A very helpful [Facebook group](https://www.facebook.com/groups/mpminideltaowners/) has a [bunch of files](https://www.facebook.com/groups/mpminideltaowners/files/) that are good sample prints. If your manual says you can print a `cat.gcode` you've got an old manual.
* Note: Don't try and just google `cat.gcode` as I did. The model I found rammed the print head right into the bottom of the printer. The correct model works great (actually called auto00.g on the SD card)
* Another great reference site appears to be <https://www.mpminidelta.com/>, and this [reddit](https://www.reddit.com/r/mpminidelta/)

## Common Problems and Solutions

The following are some problems I had and their solution

### Can't print custom models

If you find you can print prebuilt gcodes fine (cat,viking,toothless), but can't seem to print any other models without the print head ramming into the bottom of the printer and going off to the side, you probably haven't setup the autoleveling gcode that's **required**. You can add something like the following line to your software, in a "startup" gcode section. This is detailed in the manual (just search for G29), and [more info can be found here](https://www.mpminidelta.com/g29)

```
; auto-levels the build plate with a overall vertical 
; offset of 0.3mm with a center offset of -0.8mm
G29 C-0.8 Z0.3 

```

### First layer doesnt stick

If you find your first layer isn't sticking, or it seems like the plastic is balling up, you need to adjust your startup gcode line mentioned above , so it has a lower Z offset, like Z0.25 for example

```
G29 Z[offset] ; raises
G29 Z-[offset] ; lowers

```

Notes

* Please try a positive offset value first.
* Each printer will require fine tuning in regards to the offset value.
* Start with a higher value and decrease as necessary to get good first layer adhesion.
* Using a negative offset value may send the nozzle digging into the build plate.

> **Comments:**
> **username_1**: This is effectively a link-only answer; on its own it does not contain any useful information for someone looking to get started. An answer is supposed to answer the question and, in this case, should help someone get started. You're just pointing the reader to other websites to get the information they need.  
> **username_0**: There's lots of info here - manual is on sd card, manual is very out of date, where missing files can be found, sample similar files on the internet cause printer to malfunction. That's information - did you know the answer to those questions before you read this answer? True that this ends up being links as well, but I asked and answered the question as it took me about 45 min to get my printer working by googling and trying to find info, and I would've appreciated this answer myself. Thanks!  
> **username_2**: I agree and don't know what the first guy was tlaking about, unless this answer was majorly upgraded.  I mean it even gives gcode to solve a problem.  
> **username_0**: In his defense, it has been upgraded as I found more issues that were problematic (gcode being one of them!), but I still thought it was relevant enough to warrant a post ;-)  

---

