> 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/expert-center/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md). # Event configuration on Jimi JC series Configure custom event alerts on Jimi JC series dashcams in Navixy using state field value rules with a reference table of supported event codes. Jimi JC devices can send various event codes to the Navixy platform. While the platform has its own notification system with already predefined alerts, you can set up additional custom alerts based on specific event codes from your devices using [state field alert type](/docs/user/guide/events-and-notifications/inputs-and-outputs/state-field-value.md). This feature is particularly useful when you need alerts for events where video recording isn't necessary. For example, count how many particular events happen using the [report on all events](/docs/user/guide/reports/specific-report-details/report-on-all-events.md). ## How to set up event code alerts 1. Navigate to the alert configuration section. 2. Select **State field value** as the alert type. 3. In the settings: * Set `event_code` as the state field. * Enter the desired event code as the expected value. * Configure additional notification preferences as needed. ## Example use case: seat belt unplug alert Let's walk through setting up an alert for when a seat belt is unplugged: 1. Create a new alert. 2. Select **State field value** as the alert type. ![Example use case: Seat belt alert — Setting alert type](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-ae84488e5885b58d2c7b41563b9b484176104ebd%2Fbrowser_KjcUn9UmiH.png?alt=media) 3. In the settings tab: ![Live example: Setting event code 167 for seat belt unplug detection](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-dd61013a2530263a8352a4e5625d9eee55d351ba%2Fimage-20241024-092818.png?alt=media) * State field: `event_code` * Expected value: `167` (seat belt unplugged code) When the device sends a packet with event code 167, the platform triggers the alert and notifies designated personnel. Additionally, check the short video on event code 143 to find out how to create such alerts: {% embed url="" %} ## Event codes table This table provides a list of event codes supported by Jimi JC devices. For your convenience, Navixy presents both: * Decimal codes (used in platform configuration). * Hexadecimal (HEX) codes (as referenced in manufacturer documentation). The definitions provided closely align with the original Jimi JC series documentation, ensuring consistency with manufacturer specifications. Use these codes when configuring state field value alerts in the platform. | HEX Code | Code | Event | | -------- | ---- | ------------------------------- | | 0x01 | 1 | SOS | | 0x0E | 14 | External battery low | | 0x47 | 71 | Fatigue driving | | 0x50 | 80 | Door closed | | 0x51 | 81 | Door opened | | 0x53 | 83 | Fuel stolen | | 0x69 | 105 | File uploading | | 0x70 | 112 | SD card mount | | 0x73 | 115 | Fuel data timeout | | 0x76 | 118 | Temperature data timeout | | 0x80 | 128 | Vibration | | 0x86 | 134 | SD card cannot be recognized | | 0x87 | 135 | Over speed | | 0x88 | 136 | Power removal | | 0x8A | 138 | Oil or electronics connected | | 0x8B | 139 | Oil or electronics disconnected | | 0x8C | 140 | DMS – Eye closed | | 0x8F | 143 | DMS: Distraction | | 0x90 | 144 | Harsh acceleration | | 0x91 | 145 | Harsh deceleration | | 0x92 | 146 | Harsh turning | | 0x93 | 147 | Crash | | 0x94 | 148 | DMS: Missing face | | 0x97 | 151 | DMS: Phone calling | | 0x9A | 154 | DMS: Smoking | | 0xA0 | 160 | DMS: Yawn | | 0xA1 | 161 | DMS: Monitoring shelter | | 0xA2 | 162 | DMS – Calibration fail | | 0xA3 | 163 | DMS: Look down | | 0xA4 | 164 | SD card capacity is not enough | | 0xA5 | 165 | RFID reading | | 0xA6 | 166 | Seat belt plugged | | 0xA7 | 167 | Seat belt unplugged | | 0xCC | 204 | Forward collision warning | | 0xCD | 205 | Lane departure warning | | 0xCE | 206 | Headway monitoring warning | --- # 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/expert-center/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md?ask=&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.