> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_weightstation/troubleshooting.md).

# Troubleshooting

<details>

<summary>"object_gizmo resource is not running"</summary>

Install [object\_gizmo](https://github.com/DemiAutomatic/object_gizmo), keep the folder name `object_gizmo` and start it before `rayn_weightstation`.

</details>

<details>

<summary>"Weigh vehicle" does not appear</summary>

* Your job (and grade) must be listed in the station's jobs.
* With `Config.RequireDuty = true` you must be on duty.
* Make sure an operator spot or a monitor is set for the station.

</details>

<details>

<summary>"There is no vehicle on the scale"</summary>

The vehicle must stand inside the weigh point radius. Increase the radius in **Edit settings** for long vehicles.

</details>

<details>

<summary>Monitor text is too big or too small</summary>

Change `Config.ScreenTextScale` (e.g. `0.8`).

</details>

<details>

<summary>Stations are not saved</summary>

The `data/` folder must be writable, and `data/stations.json` must not be removed.

</details>


---

# 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_weightstation/troubleshooting.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.