# FAQ（Oct/17）

### ※Solution to the Issue of Unable to Save the Cartographer Model

2024/9/21

In the previous configuration, due to formatting issues, the newly saved calibration data could not be properly applied. Even after calibrating the cartographer model, the Z-axis could not home correctly. Additionally, the extruder motor direction has been reversed.

For users who are using the old configuration, please manually adjust the extruder motor direction by **removing the exclamation mark** from the `dir_pin` line in the `[extruder]` section. Here’s what to change:

**Before:**

```
step_pin: EBBCan:gpio18              # Step pin
dir_pin: !EBBCan:gpio19               # Direction pin, "!" indicates logic inversion
```

**After:**

```
step_pin: EBBCan:gpio18              # Step pin
dir_pin: EBBCan:gpio19               # Direction pin
```

To fix the formatting issue, ensure that the section appears as follows, inserting a line before the `[bed_mesh default]` section:

**Before:**

```
#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*# [bed_mesh default]
```

**After:**

```
#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#
#*# [bed_mesh default]
```

Make sure to save the changes and restart the machine to apply the updates.

***

### ※Upgrade Cartographer Software

How to Update Cartographer Software in SIBOOR Kit and Switch Source to GitHub

Here’s the tutorial in English for updating the Cartographer software in the SIBOOR Kit. If you encounter issues like upgrade failures, you can try switching the source to GitHub:

1. **Remove the local repository:**

   ```bash
   rm -rf cartographer-klipper/
   ```

   This step will delete the local Cartographer repository, allowing you to pull the latest version.
2. **Clone the latest repository:**

   ```bash
   cd ~
   git clone https://github.com/Cartographer3D/cartographer-klipper.git
   ```
3. **Set the installation script permissions and execute the installation:**

   ```bash
   chmod +x cartographer-klipper/install.sh
   ./cartographer-klipper/install.sh
   ```
4. **Check the Moonraker configuration file:**

   Open the `moonraker.conf` file, find the `[update_manager cartographer]` section, and check the source for automatic updates. If it is not from GitHub, update it as follows:

   * **Old configuration:**

     ```
     [update_manager cartographer]
     type: git_repo
     path: ~/cartographer-klipper
     channel: dev
     origin: https://gitee.com/NBTP/cartographer-klipper.git
     env: ~/klippy-env/bin/python
     requirements: requirements.txt
     install_script: install.sh
     is_system_service: False
     managed_services: klipper
     info_tags:
       desc=Cartographer Probe (Gitee)
     ```
   * **New configuration:**

     ```
     [update_manager cartographer]
     type: git_repo
     path: ~/cartographer-klipper
     channel: dev
     origin: https://github.com/Cartographer3D/cartographer-klipper.git
     env: ~/klippy-env/bin/python
     requirements: requirements.txt
     install_script: install.sh
     is_system_service: False
     managed_services: klipper
     info_tags:
       desc=Cartographer Probe
     ```
5. **Save and close the file**, then restart the relevant services to apply the changes.

This ensures that the Cartographer software source is pointing to GitHub, potentially resolving upgrade issues.


---

# Agent Instructions: 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:

```
GET https://docs.siboor.com/siboor-trident-june/faq-oct-17.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.