> 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/weighing.md).

# Weighing

How operators weigh vehicles and trucks with trailers.

## Live display

With `Config.LiveDisplay = true` the monitor shows the vehicle name and its live weight to everyone nearby. While the vehicle is moving it shows **STOP THE VEHICLE**.

## Operator weighing

1. A vehicle stops inside the weigh point.
2. An allowed job uses **Weigh vehicle** (ox\_target) at the operator spot or monitor.
3. After a short progress bar the operator gets a detailed result:
   * vehicle name and plate
   * vehicle weight
   * trailer name, plate and weight (if attached)
   * cargo weight (trunk + glovebox, ox\_inventory)
   * total weight and limit
4. The same result is shown on the monitor for `Config.ResultTime` seconds – **red** with the exact excess when the vehicle is overweight.

## Trucks with trailers

With `Config.Trailers = true` the truck and its attached trailer are weighed together. It works whether the truck or the trailer is standing on the weigh point.

## Vehicle weight

The vehicle weight is read from `fMass` in the vehicle's handling. If it is missing, `Config.VehicleClassWeights` is used as a fallback.


---

# 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/weighing.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.