Queclink GL300 User manual

GSM/GPRS/GPS Tracker GL300

@Track Air Interface Protocol

Application Notes: TRACGL300AN001

Revision: 1.02

[email protected]

GL300 @Tracker Air Interface Protocol

Document Title

GL300 @Tracker Air Interface Protocol

Version

1.02

Date

2013-11-26

Status

Release

Document Control ID

TRACGL300AN001

General Notes

Queclink offers this information as a service to its customers, to support application and

engineering efforts that use the products designed by Queclink. The information provided is

based upon requirements specifically provided to Queclink by the customers. Queclink has

not undertaken any independent search for additional relevant information, including any

information that may be in the customer’s possession. Furthermore, system validation of this

product designed by Queclink within a larger electronic system remains the responsibility of

the customer or the customer’s system integrator. All specifications supplied herein are

subject to change.

Copyright

This document contains proprietary technical information which is the property of Queclink

Limited. The copying of this document, distribution to others, and communication of the

contents thereof, are forbidden without express authority. Offenders are liable to the payment

of damages. All rights are reserved in the event of a patent grant or the registration of a utility

model or design. All specification supplied herein are subject to change without notice at any

time.

TRACGL300AN001 - 1 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

Contents

Contents ............................................................................................................................................2

Table Index........................................................................................................................................4

Figure Index......................................................................................................................................5

0. Revision history ............................................................................................................................6

1. Overview.......................................................................................................................................8

1.1. Scope...................................................................................................................................8

1.2. Terms and Abbreviations.....................................................................................................8

2. System Architecture......................................................................................................................9

3. Message Description...................................................................................................................10

3.1. Message Format ................................................................................................................10

3.2. Command and Acknowledgement.....................................................................................12

3.2.1. Quick Start Setting...............................................................................................12

3.2.2. Bearer Setting Information ..................................................................................15

3.2.3. Backend Server Register Information..................................................................16

3.2.4. Global Configuration...........................................................................................18

3.2.5. Non movement detection.....................................................................................21

3.2.6. Time Adjustment..................................................................................................23

3.2.7. Fixed Report Information....................................................................................24

3.2.8. Geo-Fence Information........................................................................................27

3.2.9. Speed Alarm.........................................................................................................29

3.2.10. Function Key Setting...........................................................................................30

3.2.11. Real Time Operation............................................................................................32

3.2.12. White Call List Configuration .............................................................................33

3.2.13. Google link SMS configuration...........................................................................35

3.2.14. Auto unlock SIM-PIN..........................................................................................36

3.2.15. Digital Input Port Settings ...................................................................................37

3.2.16. Protocol watchdog...............................................................................................38

3.2.17. Data transfer between UART and backend server...............................................40

3.2.18. Network Select.....................................................................................................41

3.2.19. Outside Working Hours .......................................................................................42

3.2.20. Temperature Alarm..............................................................................................43

3.2.21. Store Command String.........................................................................................45

3.2.22. User Defined Function.........................................................................................46

3.2.23. Update configuration over the air........................................................................48

3.2.24. Jamming Detection..............................................................................................49

3.3. Report................................................................................................................................52

3.3.1. Position Related Report.......................................................................................52

3.3.2. Device Information Report..................................................................................56

3.3.3. Report for Querying.............................................................................................58

3.3.4. Event Report........................................................................................................70

3.3.5. Buffer Report.......................................................................................................83

TRACGL300AN001 - 2 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

TRACGL300AN001 - 3 -

3.3.6. Report Google Maps hyperlink............................................................................84

3.4. Heartbeat...........................................................................................................................85

3.5. Sever Acknowledgement...................................................................................................85

Appendix: Message Index...............................................................................................................87

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

Table Index

TABLE 1: TERMS AND ABBREVIATIONS .........................................................................................8

TRACGL300AN001 - 4 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

Figure Index

FIGURE 1: SYSTEM ARCHITECTURE................................................................................................9

FIGURE 2: @TRACKER PROTOCOL MESSAGES FLOW...............................................................10

TRACGL300AN001 - 5 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

0. Revision history

Revision Date Author Description of change

0.02 2012-10-12 Evan.tu Initial

1.00 2012-10-26

2012-11-12

2012-11-14

2012-11-16

2012-11-19

2012-11-20

2012-11-26

2012-11-28

2012-11-29

2012-12-04

2012-12-15

2013-1-5

2013-1-9

2013-1-15

Evan.Tu

1. Add a new parameter to control whether to drive

the motor in the command “AT+GTFKS”

2. Add a new command “AT+GTMON”

3.Delete the command “AT+GTFFC” protocol

4.Modified the command “AT+GTRTO” protocol

5.Modified the command “AT+GTOWH” protocol

6.Delete the report massage “+RESP:GTANT”

7.Add the report massage “+RESP:GTALS”

8.Add 4 reserved parameter in the command

“AT+GTOWH”

9.Modified the parameter <log enable> is reserved

in the commands “AT+GTQSS 、AT+GTBSI”

10.Modified the report massage “+RESP:GTDOG”

11.Modified the description of NOTE in the

command “AT+GTFRI”

12.Add the report massage “+RESP:GTDAT”

13.Add a parameter <GSM Interval> in the

command “AT+GTNTS”

14.Modified the report massage “+RESP：GTALL”

15.Modified the report massage “+RESP:GTDOG”

16.Modified the decription of the parameter<

Power

key ind

> in command “AT+GTFKS”

17.Add the report massage “+RESP:GTMON”

18.Add the temperature alarm report function

AT+GTTEM and the alarm report massage

+RESP:GTTEM

19.Add a parameter <temperature> in the report

massage +RESP:GTINF

20.Modified the report massage “+RESP:GTMON”

2013-07-24

Evan.Tu

1.Add two new commands “AT + GTCMD” and

“AT + GTUDF”

2.Add two new parameters <SMS ACK Enable>

and <quick link enable> in the command

“AT+GTSRI”

2013-08-28 Evan.Tu 1.Add a new protocol command AT + GTUPC

1.01

2013-08-30 Evan.Tu 1.Delete a protocol command AT + GTMON

1.02 2013-10-17 Evan.Tu 1.Add the report mode 6 in the command

AT+GTQSS

TRACGL300AN001 - 6 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

TRACGL300AN001 - 7 -

2.Add the mode 6 in the command AT+GTFRI

2013-11-14 Evan.Tu 1.Add a new protocol command AT+GTJDC

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

1. Overview

1.1. Scope

The @Track Air Interface Protocol is a digital communication interface based on printable ASCII

characters over SMS or GPRS which is used for all communication between the backend server

and the terminal. The backend server sends a command to the terminal and then the terminal

confirms with an acknowledgement message. If necessary, the terminal also sends report messages

to the backend server.

The purpose of this document is to describe how to build up the backend server based on the

@Track Air Interface Protocol.

1.2. Terms and Abbreviations

Table 1: Terms and abbreviations

Abbreviation Description

APN Access Point Network

ASCII American National Standard Code for Information Interchange

GPRS General Packet Radio Service

GSM Global System for Mobile Communications

HDOP Horizontal Dilution of Precision

ICCID Integrated Circuit Card Identity

IP Internet Protocol

SMS Short Message Service

TCP Transmission Control Protocol

UDP User Datagram Protocol

UTC Coordinated Universal Time

TRACGL300AN001 - 8 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

2. System Architecture

Figure 1: System architecture

The backend server can be accessed by many terminals and should have the following abilities:

 The backend server should be able to access the internet and listen to the connection

originating from the terminal.

 The backend server should be able to support a TCP or UDP connection with the terminal. It

should be able to receive data from the terminal and send data to the terminal.

 The backend server should be able to receive and send SMS.

TRACGL300AN001 - 9 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

3. Message Description

3.1. Message Format

All of the @Track Air Interface Protocol messages are composed of printable ASCII characters.

Each message has the following format:

Message format Message type

AT+GTXXX=<parameter1>,<parameter2>,…$ Command

+ACK:GTXXX,<parameter1>,<parameter2>,…$ Acknowledgement

+RESP:GTXXX,<parameter1>,<parameter2>,…$ Report

The entire message string ends with character ‘$’.

The characters ‘XXX’ identify the deferent message.

The “<parameter1>,<parameter2>,…” carry the message’s parameters. The number of parameters

is different in different messages. The ASCII character ‘,’ is used to separate the neighbouring

parameter characters. The parameter string may contain the ASCII characters:

‘0’-‘9’, ’a’-‘z’, ’A’-‘Z’.

Detailed descriptions of each message format are located in the specific message sections.

By sending Commands to the terminal, the backend server can either configure and query the

parameters of the terminal or control the terminal to perform specific actions. When the terminal

receives Commands over the air, it will reply with a corresponding Acknowledgement message.

According to the configuration of the parameters, the terminal can send Report messages to the

backend server. Please see the following figure:

Terminal Backend

Server

Command

Acknowledgement

Report

Figure 2: @Tracker protocol messages flow

TRACGL300AN001 - 10 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

When the device receives commands over the air, it supports several commands in one SMS or

GPRS packet without separate symbol between two close commands. But it is necessary to make

sure the total size of the several commands is not longer than 160 if the commands are sent via

SMS. Here is an example to send three commands in one SMS.

AT+GTFRI=gl300,1,1,,,0000,2359,60,60,,,1F,0,,,,,,,,0007$AT+GTGEO=gl300,0,3,101.412248,

21.187891,1000,600,,,,,,,,,0008$AT+GTSPD=gl300,1,5,40,30,60,,,,,,,,,,,,,,,,0009$

It includes three commands (AT+GTFRI, AT+GTGEO and AT+GTSPD) in the above message.

And the terminal will handle the three commands one by one after it received the message via

SMS and it will report the following three acknowledgement message to the backend server one

by one.

+ACK:GTFRI,1A0102,135790246811220,,0007,20100310172830,11F0$

+ACK:GTGEO,1A0102,135790246811220,,0,0008,20100310172900,11F1$

+ACK:GTSPD,1A0102,135790246811220,,0009,20100310172930,11F2$

TRACGL300AN001 - 11 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

3.2. Command and Acknowledgement

3.2.1. Quick Start Setting

The command AT+GTQSS is used to set the GPRS parameter and backend server information in

one command if all these settings are within 160 bytes, otherwise use AT+GTBSI and

AT+GTSRI in two steps.

 AT+GTQSS=

Example:

AT+GTQSS=gl300,cmnet,,,4,,,116.226.44.17,9001,116.226.44.16,9002,+8613812341234,0,1,

,,0001$

Parameter Length (byte) Range/Format Default

Password 4 – 6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

APN <=40

APN user name <=30

APN password <=30

Report mode 1 0 – 6 0

Reserved 0

Buffer enable 1 0|1|2 1

Main server IP/domain

name

<=60

Main server port <=5 0 – 65535 0

Backup server IP <=15 0.0.0.0

Backup server port <=5 0 – 65535 0

SMS gateway <=20

Heartbeat interval <=3 0|5 – 360min 0

SACK enable 1 0|1 0

Reserved 0

Serial number 4 0000 – FFFF

Tail character 1 $ $

 <Password>: The valid character of password is ‘0’-9’, ‘a’-‘z’, ‘A’-‘Z’. The default value is

“gl300”.

 <APN>: Access point name (APN).

 <APN user name>: the GPRS APN user name. If the parameter field is empty, the parameter

will be cleared.

 <APN password>: the GPRS APN password. If the parameter field is empty, the parameter

will be cleared.

 <Report mode>: Supports report modes as following:

 0: Stop reporting.

 1: TCP short-connect preferred mode. The connection is based on TCP protocol. The

TRACGL300AN001 - 12 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

terminal connects to the backend server every time it needs to send data and will shut

down the connection when the terminal finishes sending data. And if it is failed to

establish a TCP connection with the backend server (including Main Server and

Backup Server), it will try to send data via SMS.

 2: TCP short-connect forced mode. The connection is based on TCP protocol. The

terminal connects to the backend server every time it needs to send data and will shut

down the connection when the terminal finishes sending data. And if it is failed to

establish a TCP connection with the backend server (including Main Server and

Backup Server), it will be stored in the BUFFER (if BUFFER function is enabled,

please refer to <Buffer enable>) or discarded (if the BUFFER function is disabled).

 3: TCP long-connect mode. The connection is based on TCP protocol. The terminal

connects to the backend server and maintains the connection using the heart beat data.

Please note that in this mode the backend server should respond to the heart beat data

from the terminals.

 4: UDP mode. The terminal will send data to the backend server by UDP protocol. It

supports to receive protocol command via UDP. But it is recommended to make sure

the IP address and UDP port of the device can be visited in the internet, and this is

generally realized by heart beat package and the message +RESP:GTPDP.

 5: Force on SMS. Only use the SMS for transmitting.

 6: UDP with fixed local port. Like the UDP mode, the terminal will send data using

UDP protocol. The difference is the terminal will use fixed local port rather than

random port to communicate with the server in this mode. Thus the backend server

could use identical port to communicate with all terminals if the backend server and

the terminals are all in the same VPN network. The port number the device uses is the

same as the port number of the primary server.

 <Reserved>: .Not used at present.Please keep empty

 <Buffer enable>: Enable or disable BUFFER function. Please refer to 3.3.5 for the details

about BUFFER function.

 0: Disable the BUFFER function.

 1: Enable the BUFFER function.

 2: High priority. Enable the buffer report function. Under this working mode, the

device will send all the buffered messages before sending any normal message except

for the SOS message (+RESP:GTSOS).

 <Main server IP/domain name>: The IP address or the domain name of the main server.

 <Main server port>: The port of the main server.

 <Backup server IP>: The IP address of the backup backend server.

 <Backup server port>: The port of the backup server.

 <SMS gateway>: Maximum 20 characters including the optional national code starting with

“+” for SMS messages. Short code (for example: 10086) is also supported.

 <Heartbeat interval>: the interval for the terminal to send heartbeat package message to the

backend server. If set to 0, no heartbeat package is sent.

 <SACK enable>: A numeric to indicate whether the backend server should reply SACK

message to the device.

 0: the backend server does not reply SACK message after receiving a message from

TRACGL300AN001 - 13 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

the device.

 1: the backend server should reply SACK message after receiving a message from the

device.

 <Serial number>: the serial number for the command. It will be invoked in the ACK message

of the command.

 <Tail character>: a character to indicate the end of the command. And it should be “$”.

Note:

If <Report mode> is set as 4 (UDP mode), it is strongly recommended to enable SACK or heart

beat mechanism (<Heartbeat interval> doesn’t equal to 0).

The acknowledgement message of AT+GTQSS command:

 +ACK:GTQSS,

Example:

+ACK:GTQSS,1A0102,135790246811220,,0001,20100310172830,11F0$

Parameter Length (byte) Range/Format Default

Protocol version 6 XX0000 – XXFFFF,

X∈{'A'-'Z','0'-'9'}

Unique ID 15 IMEI

Device name 20

Serial number 4 0000 – FFFF

Send time 14 YYYYMMDDHHMMSS

Count number 4 0000 – FFFF

Tail character 1 $ $

 <Protocol version>: The combination of the device type and the version number of the

applied protocol. The first two characters ‘XX’ indicate the device type. ‘1A’ represents

GL300. The middle two characters are the main version number and the last two characters

are the minimum version number. Both the main version and the minimum version are hex

digital. For example, ‘020A’ means version 2.10.

 <Unique ID>: ID of the device, use the IMEI of the current SIM card inside the terminal.

 <Device name>: Please refer to the parameter <Device name> in the command

AT+GTCFG.

 <Serial number>: The same serial number which is sent to the device with the corresponding

command. The backend server could use it to distinguish which command the ACK message

is for.

 <Send time>: The local time to send the ACK message.

 <Count number>: The self-increasing count number will be put into every acknowledgment

message and report message. The count is beginning from 0000 and increases by 1 every

time. It will roll back after “FFFF”.

TRACGL300AN001 - 14 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

3.2.2. Bearer Setting Information

The command AT+GTBSI is used to set the GPRS parameter.

 AT+GTBSI=

Example:

AT+GTBSI=gl300,cmnet,,,,,,,0002$

Parameter Length (byte) Range/Format Default

Password 4 – 6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

APN <=40

APN user name <=30

APN password <=30

Reserved 0

Serial number 4 0000 – FFFF

Tail character 1 $ $

The acknowledgement message of AT+GTBSI command:

 +ACK:GTBSI,

Example:

+ACK:GTBSI,1A0102,135790246811220,,0002,20100310172830,11F0$

Parameter Length (byte) Range/Format Default

Protocol version 6 XX0000 – XXFFFF,

X∈{'A'-'Z','0'-'9'}

Unique ID 15 IMEI

Device name 20

Serial number 4 0000 – FFFF

Send time 14 YYYYMMDDHHMMSS

Count number 4 0000 – FFFF

Tail character 1 $ $

TRACGL300AN001 - 15 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

3.2.3. Backend Server Register Information

The command AT+GTSRI is used to configure the backend server information that the terminal

reports to and the report mode that defines the communication method between the backend server

and the terminal.

 AT+GTSRI=

Example:

AT+GTSRI=gl300,4,,,116.226.44.17,9001,116.226.44.16,9002,+8613812341234,0,1,,,,,0003$

Parameter Length (byte) Range/Format Default

Password 4 – 6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

Report mode 1 0 – 5 0

Reserved 0

Buffer enable 1 0|1|2 1

Main server IP/domain

name

<=60

Main server port <=5 0 – 65535 0

Backup server IP <=15 0.0.0.0

Backup server port <=5 0 – 65535 0

SMS gateway <=20

Heartbeat interval <=3 0|5 – 360min 0

SACK enable 1 0|1 0

SMS ACK Enable 1 0|1 0

Quick Link Enable 1 0|1 0

Reserved 0

Serial number 4 0000 – FFFF

Tail character 1 $ $

 <SMS ACK Enable>: This defines whether the ACK confirmation should respond by SMS

when the command was sent by SMS.

 0: the device will send the ACK confirmation with the mode configured by the

<Report Mode>.

 1: the device will send the ACK confirmation by SMS to the phone which sent the

command by SMS.

 <Quick link Enable>: This defines whether the device should establish TCP connection under

certain condition.

 0: disable.

 1: The device should establish TCP connection immediately when a call is coming.

This feature will be valid only when the report mode is set as TCP long connection.

The acknowledgement message of AT+GTSRI command:

 +ACK:GTSRI,

TRACGL300AN001 - 16 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

Example:

+ACK:GTSRI,1A0102,135790246811220,,0003,20100310172830,11F0$

Parameter Length (byte) Range/Format Default

Protocol version 6 XX0000 – XXFFFF,

X∈{'A'-'Z','0'-'9'}

Unique ID 15 IMEI

Device name 20

Serial number 4 0000 – FFFF

Send time 14 YYYYMMDDHHMMSS

Count number 4 0000 – FFFF

Tail character 1 $ $

TRACGL300AN001 - 17 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

3.2.4. Global Configuration

The AT+GTCFG command is used to configure the global parameters.

 AT+GTCFG=

Example:

AT+GTCFG=quectl,123456,,,,,,,,,,,,,,,,,,,,0004$

AT+GTCFG=gl300,,GL300,0,0.0,0,7,0,0,,,,1,1,300,1,0,20491231235959,1,0,,0004$

Parameter Length (byte) Range/Format Default

Password 4 – 6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

New password 4 – 6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’

Device name 20 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’, ‘-’,

‘_’

GL300

ODO enable 1 0|1 0

ODO mileage <=9 0.0 – 4294967.0Km 0.0

GPS on need 1 0|1|2|3 1

GPS fix delay 2 5 – 60sec 5

Report items mask <=4 0000 – 007F 001F

Gsm report 1 0|1|2|3 0

Reserved 0

Event mask 4 0000-3FFF 0FFF

EPB mode 1 0|1 0

LED on 1 0|1|2 1

Info report enable 1 0|1 1

Info report interval <=5 30 – 86400sec 300

Location by call 1 0|1 1

Expiry enable 1 0|1 0

Expiry time 14 YYYYMMDDHHMMSS 204912312

35959

Agps mode 1 0|1 0

Sleep enable 1 0|1 0

Reserved 0

Serial number 4 0000 – FFFF

Tail character 1 $ $

 <New password>: Set to change the current password.

 <Device name>: the name of the device, which appears in each uplink message.

 <ODO enable>: Enable or disable the odograph function to calculate the total mileage. The

current mileage is included in the message GTINF.

 0: Disable the ODO mileage function.

 1: Enable the ODO mileage function.

 <ODO mileage>: The value of the current total mileage.

TRACGL300AN001 - 18 -

Queclink

Confidential

GL300 @Tracker Air Interface Protocol

 <GPS on need>: Whether to close GPS chip after retrieving GPS position information.

 0: Never close GPS chip

 1: Close GPS chip after retrieving GPS information every time.

 2: Never close GPS chip only in ignition on state or movement state.

 3: Never open GPS chip.

 <GPS fix delay>: This is the time to wait after GPS fixing succeed. After GPS fixing succeed,

the device will wait for a period of time (defined by <GPS fix delay>) and then get the result

of GPS fixing because maybe it is not accurate to get the position immediately after GPS

fixing succeed. (e.g. if <GPS fix delay> is set as 7, we will wait for 7 seconds after GPS

fixing succeed and then get the position as the result). The range of the parameter is 5 – 60,

and the default value is 5. Unit: second.

 <Report items mask>: Bitwise report mask to configure the composition of all the uplink

message. Each bit represents a field in the uplink message. If some bit is set as 1, the

corresponding field will be filled if it is included in the uplink message. Otherwise, the field

will be empty.

Bit0(0001): <speed>

Bit1(0002): <azimuth>

Bit2(0004): <altitude>

Bit3(0008): GSM LAI and CI, including <mcc>, <mnc>, <lac>, <cellid>

Bit4(0010): <send time>

Bit5(0020): <Device name>

 <Event mask>: A Hex value to configure which event reports can be sent to the backend

server: Each bit corresponds to a report message. And if the bit is set as 1, the corresponding

report message can be sent to the backend server. Otherwise, it can not be sent to the backend

server. Here is the mapping between each bit and each report message.

bit0(0001): +RESP:GTPNA

bit1(0002): +RESP:GTPFA

bit2(0004): +RESP:GTEPN

bti3(0008): +RESP:GTEPF

bit4(0010): Reserved

bit5(0020): +RESP:GTBPL

Bit6(0040): +RESP:GTBTC

Bit7(0080): +RESP:GTSTC

bit8(0100): +RESP:GTSTT

bit9(0200): Reserved

bit10(0400): +RESP:GTPDP

bit11(0800): +RESP:GTPNL

bit12(1000): +RESP:GTIGN and +RESP:GTIGF

bit13(2000): +RESP:GTIGL

 <Gsm report>: If GPS fixing for the report message +RESP:GTSOS, +RESP:GTRTL,

+RESP:GTLBC and +RESP:GTFRI were failed and the parameter <Gsm report> was set as

1, the terminal reports the message +RESP:GTGSM, including the information of the service

cell and the neighbour cells after those messages.

 0: Not allow the cells’ information report after failed to get GPS position.

TRACGL300AN001 - 19 -

Queclink

Confidential

Page is loading ...

Queclink GL300 User manual

Queclink GL300 User manual

Related papers

Other documents