> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/driver-safety/harsh-driving.md).

# Harsh driving

Set harsh-driving thresholds on the GPS device in Navixy. Events generated here power Notifications and Eco-driving reports. Units vary by device family.

Configures device-side detection of harsh acceleration, braking, and cornering. When the device's accelerometer exceeds the configured thresholds, it generates a **Harsh driving** event, which feeds [Notifications](/docs/user/guide/events-and-notifications/safety/harsh-driving.md) and [Eco-driving reports](/docs/user/guide/fleet-management/eco-driving.md).

![](https://2096203889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F446mKak1zDrGv70ahuYZ%2Fuploads%2Fgit-blob-7f8a7cf872b066731a90b5ecfdd68a6fb9f1df93%2Fimage-20240815-214000.png?alt=media)

## Settings

**Enable or disable**, plus thresholds for acceleration, braking, and (usually) cornering. Different devices measure harsh driving differently, by g-force, by speed change, or by force percentage. Your device manual states which method applies. The unit and tuning style differ by device family:

* **G-force thresholds** (g-force is the force felt during acceleration or braking relative to gravity; e.g. about 0.04–3 g, lower = more sensitive), e.g. BCE.
* **Speed-change thresholds**: A km/h change over a detection time, sometimes with a cornering angle (0–180°) and cornering speed, e.g. GoSafe, Concox, Ruptela.
* **Speed-range tables** (different thresholds at low, medium, or high speed) and **vehicle presets** (car, bus, or truck), e.g. some Teltonika/Queclink.
* **Force percentages** (e.g. 25–100%), e.g. Tramigo.
* Some models can additionally use the **motion sensor** alongside GPS.

{% hint style="info" %}
Because units and fields are vendor-specific, the exact controls depend on your device. Tune thresholds to the vehicle type. A sedan accelerates faster than a bus, so the appropriate threshold values differ.
{% endhint %}

## Availability

Appears on devices that support harsh-event detection (not all models do, and some report only a subset of event types).

## Limitations

* Thresholds live here, not in the Eco-driving report, the report only assigns penalties to events the device already generated.
* Events while the vehicle is essentially stopped are ignored.

## See also

* [Harsh driving notifications](/docs/user/guide/events-and-notifications/safety/harsh-driving.md): alert on harsh-driving events.
* [Eco-driving reports](/docs/user/guide/fleet-management/eco-driving.md): analyze driving behavior.


---

# 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://navixy.com/docs/user/guide/devices-and-settings/driver-safety/harsh-driving.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.