> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-anvandarmanual/dashboard/transporter.md).

# Transporter

Registrering av data under en begränsad tid.

Standardobjekt skickar normalt avläsningar kontinuerligt.

I vissa fall mäts värden bara under en begränsad tid.

Ett sådant fall är transport.

Data från transport kallas **transporter** i Boomerang 3.

### Transportobjekt och transport-MP

För att lagra transportdata måste **transportobjekt** skapas i systemet.

**Transportmätpunkter** måste också tilldelas dem.

Det finns:

* **verkliga transport-MP**
* **virtuella transport-MP**

### Registrera transportdata

Transportmätningar kan registreras på två sätt:

1. **BTiny-transportsensorer**.
2. **Loggerkort**.

#### 1. BTiny-transportsensorer

BTiny-transportsensorer beskrivs på [ICU Scandinavia Transport Solution](https://icuscandinavia.se/transport-solution/).

* De kan registrera temperatur offline eller online.
* Online kräver att sensorn är inom räckhåll för en CloudConnector.
* Avläsningarna skickas till Boomerang 3-servern och lagras i verkliga transport-MP.
* Transportdata kan flyttas från verkliga till virtuella transport-MP vid behov.

<figure><img src="https://3898184682-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCwCdZYMtn8H0BKQBnUbi%2Fuploads%2FSq2p26D82atkkyiAmrr4%2Fimage.png?alt=media&amp;token=e221007c-28ab-4856-a700-ff9f8798cb2a" alt=""><figcaption></figcaption></figure>

BTiny-loggrar är batteridrivna och har minnesbuffert.

De kan logga temperaturer från -196 °C till +120 °C.

#### 2. Loggerkort

Loggerkort beskrivs i [Logger Card-manualen](https://help.boomerang3.com/logger-card-client-user-manual/).

* Loggerkorten registrerar temperatur offline.
* Avläsningarna skickas till Boomerang 3-servern via Logger Card-klientapplikationen.
* De lagras i **virtuella transportmätpunkter**.

<figure><img src="https://3898184682-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCwCdZYMtn8H0BKQBnUbi%2Fuploads%2FBJrS3slqlycyoCzlKMd8%2Fimage.png?alt=media&amp;token=09f68a4b-d25a-4461-baee-fed830be003f" alt=""><figcaption></figcaption></figure>


---

# 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://help.boomerang3.com/boomerang-3-anvandarmanual/dashboard/transporter.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.
