> 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/qna/device-related-questions/configuring-coban-family-devices-to-receive-gprs-commands.md).
# Configuring COBAN Family Devices to Receive GPRS Commands
### Question
How can I configure a COBAN family device to receive GPRS commands?
### Answer
COBAN family devices commonly support different commands for controlling their outputs depending on whether the command is sent via SMS or GPRS. Therefore, even if an output command such as stop123456 works correctly via SMS, the equivalent GPRS command may use a different format.
Before using the GPRS commands, the device must be configured to use the appropriate protocol. According to the COBAN protocol documentation, this can be done by sending the following command via SMS:
**protocol123456 18 out**
The documentation specifically recommends configuring Protocol 18 before integrating the device with a server.
If the change is successfully applied, the device should return a confirmation similar to:
***change protocol sucess***
Once Protocol 18 is enabled and the device is connected to the platform, the documented GPRS commands for controlling the oil/power output can be used.
Activate the output / Cut off oil and power:
**\*\*,imei:\,109**
The device should respond with 109 when the command is successfully accepted. The protocol also defines 509 for the execution of the cut-off when the vehicle speed is below 20 km/h.
Deactivate the output / Resume oil and power:
**\*\*,imei:\,110**
A successful command should generate a response containing keyword 110.
In summary: if a COBAN family device responds correctly to output commands via SMS but not through the platform, verify that Protocol 18 has been configured first. After receiving confirmation of the protocol change, commands 109 and 110 can be tested through the active GPRS connection for output cut-off and restoration, respectively.
---
# 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://navixy.com/docs/qna/device-related-questions/configuring-coban-family-devices-to-receive-gprs-commands.md?ask=&goal=
```
`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.
