User position update request Sent from client that wants to write position data to the server. If there is any error, the socket is closed. Data is not sent if the position hasn't been updated. Notes: Data is not sent back to the client faster than the interval specified. "_buddies": An FRPOS sentence is sent right away from server for each user with known position with latest known position, and the UTC time when that position was reported. Depending on the value of “username” the following actions are taken: One user: An GPRMC sentence is sent right away from server with latest known position, and the UTC time when that position was reported. Username can be either one user or the buddy list.
Or "_buddies" to get data from all the users buddies. The username in the buddy list to receive position data from. Syntax: $FRRDT,username,interval*XX username Position data is sent as GPRMC sentences from server. Position data messages User position request Used to request position data from another user in requesting users buddy list. Sample sentence: $FRERR,AuthError,You have provided wrong username or password*18
Syntax: $FRERR,err_code,err_message*XX err_code The server can also simply close the connection if some kind of error or time-out condition occur. Will be returned from server on failed login. Syntax: $FRSES,sessionid*XX sessionidĮrror message Error message. Successful login message This message is returned from server on a successful login. This will connect a user to an IMEI number. Sample sentence: $FRLIN,IMEI,1234123412341234,*7A You need to create a device in the GpsGate Web interface for a specific user. Login with hardware IMEI number Syntax: $FRLIN,domain,username,password*XX domain Algorithm to calculate shown in Appendix 1 Login with username and password Syntax: $FRLIN,domain,username,password*XX domain This includes both commands sent from client to server and possible server replies. Login commands This section contains information on login commands. GpsGate Server also supports JSON & XML/SOAP based web services which aren't covered in this document. See Appendix 1 for an example algorithm to calculate the checksum. All sentences should always be followed by a NMEA checksum and carriage return + line feed “\r\n”. The address to is port 30175 (port 80 for HTTP). The protocol can be used with GpsGate Server and.
#Franson gpsgate full#
Full functionality is achieved over TCP/IP. Communication can be made over TCP/IP, UDP and HTTP.
#Franson gpsgate software#
Software and hardware developers are encouraged to use this protocol to integrate with and GpsGate Server. The main purpose is position updates, status messaging, track reports and configuration. Introduction This document describes communication between a GPS tracker client and server. V1.0 and v1.1 (last update November 28th, 2007)Ĭontents Introduction.2 Login commands.4 Login with username and password.4 Login with hardware IMEI number.4 Successful login message.4 Error message.5 Position data messages.5 User position request.5 User position update request.6 Position update - FRPOS.6 Position update - GPRMC.7 Sample scenarios with TCP/IP.7 HTTP position updates.10 GpsGate Server Protocol v1.1 Framework.11 Client version notification.11 Command structure.11 Error handling.13 Interrupted commands.13 Failed to execute command.13 Command not supported.14 Invalid use of protocol.14 Commands.14 _getupdaterules.14 _SendPosition.16 _CreateTrackRecorder.16 _SaveTrackData.17 Appendix 1 - NMEA checksum calculation.19 Appendix 2 - Password algorithm in C#.20
0 kommentar(er)
