Usm gps 2 EN: различия между версиями
Нет описания правки |
|||
| Строка 1: | Строка 1: | ||
[[Usm_gps_2_EN|en]] | [[Usm_gps_2|ru]] | [[Usm_gps_2_EN|en]] | [[Usm_gps_2|ru]] | ||
'''This module is a replacement for the deprecated [[us_gps_EN|us_gps]] module''' | |||
== Description == | |||
'''usm_gps_2''' - A module that can receive information from GPS trackers and monitoring programmes to record the position of personnel and vehicles. Information about the position of these objects and their routes can help in faster solution of emergency situations, as these objects are displayed on the coverage map and you can quickly understand which employee, what is nearby should be sent to solve problems. | |||
The second version of the module differs from the first version in its internal structure. Now for each of GPS protocols runs its own independent "listener", and as a network core uses a powerful asynchronous superserver, capable of processing hundreds of thousands of TCP-connections simultaneously. This makes the module quite stable and reliable. | |||
== Agreement == | |||
'''We do not position this module as a vehicle monitoring system and therefore you should not expect such functionality from the module. Its main purpose is to display the current location of an employee or vehicle, not to monitor mileage, fuel consumption, etc.''' | |||
== Requirements == | |||
Pre-release version (alpha, beta) requires USERSIDE version 3.12.24 or higher. | |||
Release version (RC, release) requires USERSIDE version no lower than 3.13 (still under development). | |||
== Supported GPS tracker protocols == | |||
The following protocols are currently supported. Please note that the list of supported devices may not be complete, as we are not aware of all devices manufactured with support for this or that protocol. It is also important to know that the device model does not necessarily have to be similar to the protocol that is actually flashed in this device. | |||
=== OsmAnd === | |||
Default port: '''5055''' | |||
Supported devices: This protocol is mainly used by mobile applications such as OsmAnd, [https://gpslogger.app/ GpsLogger for Android], SendLocation, Locus Pro Android, Custodium, Traccar and others. | |||
Since this protocol is based on an HTTP request with all data being transmitted through the parameters of this request, it can be used in any application. To transfer coordinates, it is enough to execute an HTTP request: | |||
<code><nowiki>http://module.ip.address:5055/?id={id}&lat={lat}&lon={lon}×tamp={timestamp}&hdop={hdop}&speed={speed}</nowiki></code> | |||
where the following variables are substituted for the required ones: | |||
* {id} - device identifier (IMEI, serial number or any other that allows to identify a particular tracker) | |||
* {lat} - geographic latitude in decimal degree format, for example, 46.488085 | |||
* {lon} - is geographic longitude in decimal degrees, for example, 30.741091. | |||
* {timestamp} - integer timestamp in UNIXTIME format | |||
* {hdop} - the precision reduction coefficient in the horizontal positioning plane (HDOP). A floating point number. The parameter can be left out. | |||
* {speed} is the instantaneous speed in km/h. Floating point number. | |||
For example, for GpsLogger, you should enter the following address in the [https://gpslogger.app/#customurl CustomURL] setting: <code><nowiki>http://module.ip.address:5055/?id=%ser&lat=%lat&lon=%lon×tamp=%timestamp&hdop=%hdop&speed=%spd</nowiki></code>. | |||
=== GT02A === | |||
Default port: '''5022''' | |||
Supported devices: This protocol is implemented in a large number of Chinese devices, so it is impossible to make an exact list of them. However, it is one of the most common protocols found in cheap noname GPS trackers. | |||
Messages of this protocol begin with header <code>hh</code> characters or as HEX: <code>0x68 0x68</code>. | |||
=== GT06 === | |||
Default port: '''5023''' | |||
Supported devices: GT06, GT06N, GT09, Heacent 908, GT03A, GT03B, GS503, ET100, GT100, GT06D, GK301, JM01, JM08, GT02D, IB-GT102, CRX1, JV200, TP06A, BW08, TR06, JI09, Concox GT300, WeTrack 2 | |||
Messages of this protocol begin with header <code>xx</code> characters or as HEX: <code>0x78 0x78</code>. | |||
=== Meiligao === | |||
Default port: '''5009''' | |||
Supported devices: GT30i, GT60, VT300, VT310, VT400, GT30, GT30X, PST-AVL01, PT03, PT60, PT300X, PT30, GT-110P, GT-110K, GT-110M, GT-110ES, GT-110ZS, AVL-011, VT900, P008, GT 30, CT01, CT03, CT04, CT04-R, CT04-X, OCT600, MT01, MT02, PT01, PT03, VT1000, GSY007, T200, iStartek, VT310N | |||
Messages of this protocol begin with header <code>$$</code> characters or as HEX: <code>0x24 0x24 0x24</code>. | |||
=== Autofon v4 === | |||
Default port: '''5079''' | |||
Supported devices: AutoFon 4.4, AutoFon 4.5 | |||
=== Autofon v5 === | |||
Default port: '''5077''' | |||
Supported devices: AutoFon SE, AutoFon SE+, AutoFon D, AutoFon D-Moto, AutoFon Dialog Mayak, AutoFon S, AutoFon GL Mayak | |||
=== Autofon v7 === | |||
Default port: '''5099''' | |||
Supported devices: AutoFon Alpha, AutoFon Alpha XL, AutoFon Alpha 2XL | |||
=== Autofon v9 (Micro-Mayak) === | |||
Default port: '''9109'''' | |||
Supported devices: Autofon Mikro-Mayak, Autofon Mikro-Mayak+. | |||
Starting from module version 2.3 | |||
=== Wialon === | |||
Версия от 14:50, 5 октября 2023
This module is a replacement for the deprecated us_gps module
Description
usm_gps_2 - A module that can receive information from GPS trackers and monitoring programmes to record the position of personnel and vehicles. Information about the position of these objects and their routes can help in faster solution of emergency situations, as these objects are displayed on the coverage map and you can quickly understand which employee, what is nearby should be sent to solve problems.
The second version of the module differs from the first version in its internal structure. Now for each of GPS protocols runs its own independent "listener", and as a network core uses a powerful asynchronous superserver, capable of processing hundreds of thousands of TCP-connections simultaneously. This makes the module quite stable and reliable.
Agreement
We do not position this module as a vehicle monitoring system and therefore you should not expect such functionality from the module. Its main purpose is to display the current location of an employee or vehicle, not to monitor mileage, fuel consumption, etc.
Requirements
Pre-release version (alpha, beta) requires USERSIDE version 3.12.24 or higher.
Release version (RC, release) requires USERSIDE version no lower than 3.13 (still under development).
Supported GPS tracker protocols
The following protocols are currently supported. Please note that the list of supported devices may not be complete, as we are not aware of all devices manufactured with support for this or that protocol. It is also important to know that the device model does not necessarily have to be similar to the protocol that is actually flashed in this device.
OsmAnd
Default port: 5055
Supported devices: This protocol is mainly used by mobile applications such as OsmAnd, GpsLogger for Android, SendLocation, Locus Pro Android, Custodium, Traccar and others.
Since this protocol is based on an HTTP request with all data being transmitted through the parameters of this request, it can be used in any application. To transfer coordinates, it is enough to execute an HTTP request:
http://module.ip.address:5055/?id={id}&lat={lat}&lon={lon}×tamp={timestamp}&hdop={hdop}&speed={speed}
where the following variables are substituted for the required ones:
- {id} - device identifier (IMEI, serial number or any other that allows to identify a particular tracker)
- {lat} - geographic latitude in decimal degree format, for example, 46.488085
- {lon} - is geographic longitude in decimal degrees, for example, 30.741091.
- {timestamp} - integer timestamp in UNIXTIME format
- {hdop} - the precision reduction coefficient in the horizontal positioning plane (HDOP). A floating point number. The parameter can be left out.
- {speed} is the instantaneous speed in km/h. Floating point number.
For example, for GpsLogger, you should enter the following address in the CustomURL setting: http://module.ip.address:5055/?id=%ser&lat=%lat&lon=%lon×tamp=%timestamp&hdop=%hdop&speed=%spd.
GT02A
Default port: 5022
Supported devices: This protocol is implemented in a large number of Chinese devices, so it is impossible to make an exact list of them. However, it is one of the most common protocols found in cheap noname GPS trackers.
Messages of this protocol begin with header hh characters or as HEX: 0x68 0x68.
GT06
Default port: 5023
Supported devices: GT06, GT06N, GT09, Heacent 908, GT03A, GT03B, GS503, ET100, GT100, GT06D, GK301, JM01, JM08, GT02D, IB-GT102, CRX1, JV200, TP06A, BW08, TR06, JI09, Concox GT300, WeTrack 2
Messages of this protocol begin with header xx characters or as HEX: 0x78 0x78.
Meiligao
Default port: 5009
Supported devices: GT30i, GT60, VT300, VT310, VT400, GT30, GT30X, PST-AVL01, PT03, PT60, PT300X, PT30, GT-110P, GT-110K, GT-110M, GT-110ES, GT-110ZS, AVL-011, VT900, P008, GT 30, CT01, CT03, CT04, CT04-R, CT04-X, OCT600, MT01, MT02, PT01, PT03, VT1000, GSY007, T200, iStartek, VT310N
Messages of this protocol begin with header $$ characters or as HEX: 0x24 0x24 0x24.
Autofon v4
Default port: 5079
Supported devices: AutoFon 4.4, AutoFon 4.5
Autofon v5
Default port: 5077
Supported devices: AutoFon SE, AutoFon SE+, AutoFon D, AutoFon D-Moto, AutoFon Dialog Mayak, AutoFon S, AutoFon GL Mayak
Autofon v7
Default port: 5099
Supported devices: AutoFon Alpha, AutoFon Alpha XL, AutoFon Alpha 2XL
Autofon v9 (Micro-Mayak)
Default port: 9109'
Supported devices: Autofon Mikro-Mayak, Autofon Mikro-Mayak+.
Starting from module version 2.3