Skip to content

Commit

Permalink
Update Cura documentation and instructions (#16)
Browse files Browse the repository at this point in the history
Co-authored-by: Anna <16231288+HumbleDeer@users.noreply.github.com>
Co-authored-by: Stefan Dej <meteyou@gmail.com>
  • Loading branch information
HumbleDeer and meteyou authored Jun 5, 2024
1 parent faf22a4 commit 648fb46
Show file tree
Hide file tree
Showing 3 changed files with 25 additions and 8 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed .gitbook/assets/image (26).png
Binary file not shown.
33 changes: 25 additions & 8 deletions overview/slicer/cura.md
Original file line number Diff line number Diff line change
@@ -1,26 +1,43 @@
# Cura

### Thumbnail
## Thumbnail

{% hint style="info" %}
If you're using the Moonraker Connection plugin for Cura, you can skip these steps. This plugin includes a feature for the generation of thumbnails.
{% endhint %}

<figure><img src="../../.gitbook/assets/image (12).png" alt=""><figcaption></figcaption></figure>

You have to add a Post Processing Script to add "G-code thumbnails" in Cura. To add these scripts, click on `Extensions > Post Processing > Modify Gcode`. Then click on `Add a script`, chose `Create Thumbnail` and fill in the size `32x32`. Add again the same script with the size `400x400`.
You have to add a Post Processing Script to add "G-code thumbnails" in Cura. To add these scripts, click on `Extensions > Post Processing > Modify Gcode`. Then click on `Add a script`, choose `Create Thumbnail` and fill in the size `32x32`. Add again the same script with the size `400x400`.

{% hint style="warning" %}
Important is, that the size is square! If you don't use a square resolution, Cura will squeeze the thumbnail.
It is important for this size to be a square, with equal size on both length and width. If you don't use a square resolution, Cura will squeeze the thumbnail.
{% endhint %}

<figure><img src="../../.gitbook/assets/image (36).png" alt=""><figcaption></figcaption></figure>

### Direct G-code upload
## Direct G-code upload

Install the [Moonraker Connection](https://marketplace.ultimaker.com/app/cura/plugins/emtrax/MoonrakerConnection) plugin by [Emtrax](https://github.com/emtrax-ltd) using the Ultimaker Marketplace.

Next, configure the plugin's parameters in Cura:

Install the OctoPrint-Connection plugin in Cura’s Marketplace. In Cura go to `Settings > Printer > Manage Printers` and find the Button `Connect OctoPrint`. Add your printer and type anything in the `API Key` field.
1. Navigate to `Settings > Printer > Manage Printers`
2. Select the printer profile you wish to connect to Moonraker
3. Click `Connect Moonraker`.
4. Configure the fields as appropriate for your printer. The most important ones are listed below.
- Connection > **Address (URL):**
The address you've been using to access Mainsail, prefixed by `http://`.
e.g. `http://myprinter.local/`
- Monitor > **Camera > URL**
The address of the camera stream on the network, prefixed by `http://`.
e.g. `http://myprinter.local/webcam/stream`

<figure><img src="../../.gitbook/assets/image (26).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../.gitbook/assets/cura_moonraker-connection_configuration-window.jpg" alt="Moonraker Connection configuration window in Cura"><figcaption>Moonraker Connection configuration window in Cura</figcaption></figure>

### Best practise G-codes
## Best practise G-codes

In Cura, there is a straightforward solution to add custom G-codes. Pedro Lamas has developed an excellent script that you can use as post-processing to add everything necessary.
In Cura, there is a straightforward solution to add custom G-codes. Pedro Lamas has developed an excellent post-processing script for including the necessary custom G-codes.

Follow the guide here to use this script: [https://github.com/pedrolamas/klipper-preprocessor](https://github.com/pedrolamas/klipper-preprocessor)

Expand Down

0 comments on commit 648fb46

Please sign in to comment.