> 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/logger-card-client-user-manual/store-mission/select-store-sensor/for-b2.md).

# For B2

1. Select the Transport Measuring Point from the “Sensor” list.
2. Change “Name” and “Description” fields if needed.
3. Click “Next>>” to continue.

For B2 this dialog shows two separate alarm levels.

1. The “Card high level” and “Card low level” are read from the Transport Card. The card levels and the alarms triggered by them are NOT stored in the system.
2. The “Sensor high level”, “Sensor low level” and “Alarm filter” are read from the sensor settings in B2 so they appear in the form after the sensor is selected. The alarm filter is a number of consecutive readings beyond an alarm limit that DO NOT generate an alarm event. The system generates mission alarms basing on the sensor levels.

![Table Description automatically generated with medium confidence](/files/62aab014e4d4f2aa66494d22e34352b78b268e07)

The alarm and card levels may differ, but it is a good rule to set them exactly the same.

The alarm state is presented by two icons under the chart.

The “Card alarms” icon shows the status basing on card threshold levels read from the card.

The “Sensor alarms” icon shows the status basing on sensor levels read from B2.

If the user defined multiple fragments, the program would add fragment information to the “Name” section like “First measure (1/4)”. Every fragment can be stored to a different sensor if needed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.boomerang3.com/logger-card-client-user-manual/store-mission/select-store-sensor/for-b2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.