> For the complete documentation index, see [llms.txt](https://docs.kemperconnect.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kemperconnect.de/asset-types/vacufil/history.md).

# history

The History tab displays performance trends for the VacuFil 125 mobile extraction system, showing differential pressure, system state, and cleaning events over time.

## Accessing History

Navigate to the device detail page and select the "History" tab.

## Performance History Chart

### Chart title

Performance History (24 Hours)

### Chart subtitle

Filter pressure and system state over time

### Data series

| Series                    | Description             |
| ------------------------- | ----------------------- |
| **Differential Pressure** | Filter pressure in Pa   |
| **System State**          | Running/Off (area fill) |
| **Cleaning Cycles**       | Filter cleaning events  |

### Chart legend

| Element          | Description                  |
| ---------------- | ---------------------------- |
| Pressure line    | Filter differential pressure |
| State area       | System operating state       |
| Cleaning markers | Automatic cleaning events    |

## Time range

Default 24-hour view with options:

* 24 hours (detailed)
* 7 days (hourly)
* 30 days (daily)

### Data resolution

| Range    | Resolution            |
| -------- | --------------------- |
| 24 hours | 5–15 minute intervals |
| 7 days   | Hourly aggregates     |
| 30 days  | Daily aggregates      |

## Reading the chart

### Differential pressure line

The pressure trend reveals:

* Rising trend: Filter loading
* Sudden drop: Cleaning cycle occurred
* Sawtooth pattern: Normal with periodic cleaning
* Consistently high: Filter may need attention

### System state area

* Shaded when running
* Clear when off
* Correlates with usage

### Cleaning events

* Markers show cleaning cycles
* Normal operation includes periodic cleaning
* Frequency indicates filter utilization

## Chart interaction

### Hover details

* Exact pressure value
* Timestamp
* State information

### Legend toggle

* Show/hide series
* Focus on specific data

## Historical patterns

### Normal operation

* Pressure rises during use
* Cleaning brings pressure down
* Regular sawtooth pattern

### Heavy use

* More frequent cleaning cycles
* Faster pressure rise
* Higher average pressure

### Potential issues

* Pressure not dropping after cleaning
* Very high sustained pressure
* Irregular patterns

## Use cases

### Filter monitoring

* Track filter condition
* Predict replacement needs
* Optimize cleaning

### Usage analysis

* Operating time patterns
* Identify peak usage
* Plan maintenance windows

### Troubleshooting

* Correlate issues with pressure
* Identify anomalies
* Document performance

## Related documentation

* [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status
* [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Fault codes
* [Service](file:///monitoring/service/overview.md) - Maintenance


---

# 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://docs.kemperconnect.de/asset-types/vacufil/history.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.