Queclink GV58CEU

Queclink GV58CEU
Forum Discussion

Number of units

1460
Online
3639
Total
Features Queclink GV58CEU:
  • 4G/LTE
  • Blackbox
  • BLE enabled
Supported in Wialon:
  • Accelerometer
  • Remote management via GPRS
  • Driver identification
  • Remote management via SMS
  • Communication via TCP
  • Communication via UDP

The following data should also be added to Queclink GV58CEU unit properties section of Wialon GPS tracking software :

Device type: Queclink GV58CEU
Unique ID: imei

Specify the following parameters in configuration software or configuration Queclink GV58CEU for use in Wialon Hosting :

Server port: 22442

3639 units of Queclink GV58CEU device type are connected to Wialon Data Center. This represents 0.15% of all AVL Hardware connected.

Below chart represents the dynamic of connections in the last 30 days:

Parameter name Description Units
dev_type

Queclink device type
*HEX mode only

proto_ver

Queclink protocol version

*HEX mode only

fw_ver

Firmware version
*HEX mode only

battery

Battery level, 0-100

pwr_ext

External power source voltage

adc_mode

Analog Input Mode

adc1

Analog Input 1 voltage

din_status

Digital Input (bit mask)

dout_status

Digital Output (bit mask)

motion_status

17 (0x11) Ignition off Rest: The vehicle is ignition off and motionless.

18 (0x12) Ignition off Motion: The vehicle had been moving before this action was regarded as car-towing event after ignition off.

33 (0x21) Ignition On Rest: The vehicle is ignition on and motionless.

34 (0x22) Ignition On Motion: The device is ignition on and moving.

65 (0x41) Sensor Rest: The vehicle is motionless and no ignition signal is detected.

66 (0x42) Sensor Motion: The vehicle is moving and no ignition signal is detected.

22 (0x16) Tow: The vehicle was towed after ignition off.

26 (0x1A) Fake Tow: The vehicle might have been towed after ignition off.

ibutton

Parameter available only for hex +RESP:GTIDA

Ibutton value

ges_enabled

Only available for hex +RESP:GTGES

The current parking-fence is active or inactive.

  • 0: The current parking-fence is inactive.
  • 1: The current parking-fence is active.

ges_mode

Only available for hex +RESP:GTGES

A numeral to indicate the working mode of the geo-fencing function.

  • 0: Disable auto trigger mode.
  • 21: Automatically set up a Geo-Fence after the ignition is turned off. In this mode, the device will automatically set up a Geo-Fence with the current location as the center point of the Geo-Fence when the ignition is off. It will only send the alarm report when exiting the Geo-Fence zone. The Geo-Fence will be cancelled after the device exits the
  • 22: Manually enable Geo-Fence after the ignition is turned off. In this mode, the device will automatically set up a Geo-Fence with the current location as the center point of the Geo-Fence when the ignition is off. It will only send the alarm report when exiting the Geo-Fence zone. When the device exits this Geo-Fence, it will cancel this Geo-Fence and disable the trigger mode at the same time. If the driver wants to use this trigger mode again, he has to manually set the trigger mode again.


ges_radius

Only available for hex +RESP:GTGES

The radius of the circular Geo-Fence zone. The value range is (50 – 6000000) and the unit is meter.

ges_dt

Only available for hex +RESP:GTGES

The interval of GNSS checking position information against Geo-Fence alarm.

upc_cmd_id

The command ID in the update configuration file. It is always 0 before the
device starts to update the configuration. It indicates the total number of the commands when the result code is 301 or 306. It indicates the ID of the command in wrong format when the result code is 302

upc_result

A numeral to indicate whether the configuration is updated successfully.

  • 100: The update command is starting.
  • 101: The update command is confirmed by the device.
  • 102: The update command is refused by the device.
  • 103: The update process is refused because the battery is low.
  • 200: The device starts to download the package.
  • 201: The device finishes downloading the package successfully.
  • 202: The device fails to download the package.
  • 300: The device starts to update the device configuration
  • 301: The device finishes updating the device configuration successfully.
  • 302: The device fails to update the device configuration.
  • 303: Reserved.
  • 304: <Command Mask>, <GEO ID Mask>, <Stocmd ID Mask> or <Group ID Mask>check fails.
  • 305: The update process is interrupted by abnormal reboot.306: The update process is interrupted by MD5 verification error.

url

The complete URL to download the configuration. It includes the file name.

[x y z]_forward

The factors to calculate the new acceleration in forward direction. The formula to calculate the accelerationin Forward direction Xnew is Xnew = x_forward* X + y_forward * Y + z_forward* Z.

[x y z]_side

The factors to calculate the new acceleration in side direction. The formula to calculate the acceleration in Side direction Ynew is Ynew = x_side * X + y_side * Y + z_side * Z.

[x y z]_vert

The factors to calculate the new acceleration in vertical direction. The formula to calculate the acceleration in Vertical direction Znew is Znew = x_vert * X + y_vert * Y + z_vert * Z.

onewire[i]_id

It indicates the device ID read from the 1-wire device.

onewire[i]_type

It indicates the type of the 1-wire device

  1. Temperature Sensor
  2. Reserved
  3. HTDZ sensor

onewire[i]_data

Depending on type of 1-wire device

  • onewire_[i]_type = 1: Temperature
  • onewire_[i]_type = 3: First two numbers: Data mask
    • if Data Mask = 00, No data
    • if Data Mask = 01, Second 4 numbers - Humidity
    • if Data Mask = 02, Second 4 numbers - Temperature.
    • if Data Mask = 03, Second 4 numbers - Humidity, Third 4 numbers - Temperature

pwr_int

Internal power voltage

jamming_status

The current jamming status of the device.

  • 1: Quit the jamming state.
  • 2: Enter the jamming state.

crash_counter

A parameter to indicate the crash sequence. It combines the report +RESP:GTCRA and +RESP:GTCRD into one crash event. It rolls from 0x00 to 0xFF.

upd_code

Only available for hex +RESP:GTUPD

Information code.

0x10: Confirm ok. Start to upgrade.

0x11: Baud rate error. UART does not work for CAN100. Stop upgrade.

0x12: The download process is refused because of low power or an incorrect URL.

0x13: Other upgrade commands are being executed. Stop upgrade.

0x14: CAN chipset response is abnormal.

0x15: The backend server cancels this update process.

0x20: Start to download package.

0x21: Package download succeeds.

0x22: Package download fails.

0x30: Start to upgrade.

0x31: Upgrade succeeds. The reserved parameter is used as follows.

upd_retry

Number of retries of updating

wave1_out_id

The ID of the wave shape 1 output

wave1_out_active

The status of the wave shape 1 output.

temp_alarm_id

Only available for hex +RESP:GTTMP

The id of temperature alarm

temp_status

The status of current temperature. 0 means “Outside the predefined temperature range”. 1 means “Inside the predefined temperature range”

temp_device_id

The ID of the temperature sensor

temp_device_data

The current temperature the sensor detects.

roaming_state

A numeral to indicate the roaming status.

  • 0: Home
  • 1: Known Roaming
  • 2: Unknown Roaming
  • 3: Blocking Report

curr_mileage

Current Trip Mileage
*HEX mode only

total_mileage

Total Mileage
*HEX mode only

curr_hourmetercount

Current Trip Hour Meter Count (accumulative ignition time)
*HEX mode only

total_hourmetercount

Total Hour Meter Count (accumulative ignition time)
*HEX mode only

hw_ver

The hardware version of the device.

resp_report_mask

Mask that was set to hex +RSP

ign_dt

Ignition ON interval

igf_dt

Ignition off interval

bat_status

Indicates whether the external power supply is connected

  • 1: Connected
  • 0: Disconnected

iccid

ICCID value

csq_ber

CSQ BER,0-7/99

daylight_saving

Enable/disable daylight saving time.

  • 0: Disable daylight saving time.
  • 1: Enable daylight saving time

time_zone

Time offset from UTC-0

mnc[i]

Mobile network code. It is 3 digits in length and ranges from 000–999.

lac[i]

Location area code in hex format.

cell_id[i]

Cell ID in hex format.

ledon
  • 1 - Cell LED anf GNSS LED turn on as configured
  • 2 - Both LEDs work 10 minutes after tge device is powered on and then will be off.
charging Wheter the backup battery is charging when the main power supply is connected
pwr_s whether the external power supply is connected.
csq_rssi the level of signal strength
id The ID which is currently read
id_reptype
  • The ID is unauthorized or the ID authorization (IDA) function is disabled;
  • The ID is authorized
indx
  • The index of Bluetooth accessory defined in AT+GTBAS which triggers the +RESP:GTBAA message
  • 0xFF for WKF300
acces_type
  • 0 - No bluetooth accessory
  • 1 - Reserved
  • 2 - Beacon temperature sensor
  • 3 - BLE beacon ID device
acbe_model

The model of the bluetooth accessory

alarm_type
  • 0 - the voltage of the Bluetooth accessory is low
  • 1 - the temperature alarm: current temperature value is below
  • 2 - the temperature alarm: current temperature value is upper
  • 3 - the temperature alarm: current temperature value is within the range defined by <low temperature> and <high temperature>
  • 4 - Push button event on WKF300 is detected
bt_name Bluetooth accessory name
bt_mac Bluetooth accessory mac
bt_status
  • 0 - the accessory is not available
  • 1 - the accessory is available
bt_bat_level The voltage of Bluetooth accessory
bt_temp Temperature data fo Bluetooth accessory
can_eng_torgue Engine Torgue
rep_id

Report ID has different meanings in different messages as listed below.

  • Position related packages (GTTOW, GTDIS, GTIOB, GTSPD, GTSOS, GTRTL, GTDOG, GTIGL,GTHBM, GTVGL)
    • The ID of digital input port which triggers the message +RESP:GTSOS. The range is 1 – 2.
    • The ID of the bound IO which triggers the message +RESP:GTIOB. The value is 0.
    • The ID of the digital input port which triggers the reboot message +RESP:GTDOG. The valid value is 1.
    • The speed level at which the harsh behavior is detected in the message +RESP:GTHBM. 3 indicates high speed, 2 indicates medium speed and 1 indicates low speed.
    • The value of <Virtual Ignition Mode> which indicates the trigger source of the message +RESP:GTVGL.
      2: External power voltage mode (virtual ignition detection)
      3: Reserved
      4: Accelerometer mode (virtual ignition detection)
      7: Combined detection mode (virtual ignition detection)
    • The ID of Digital Input status which triggers the report message +RESP:GTDIS. The rangeis 1 or 2.
    • For other messages, it will always be 0.
  • GTFRI:
    • 1: Fixed time report.
    • 2: Fixed distance report.
    • 3: Fixed mileage report.
    • 4: Fixed time and mileage report.
    • 5: Fixed time or mileage report.
  • GTEPS\GTAIS:
    • The ID of the analog input port which triggers the report message +RESP:GTEPS. The value is 0
    • The ID of the analog input port which triggers the report message +RESP:GTAIS. The value is or 5.
  • GTTMP:
    • The ID of temperature alarm. The range is 0 – 3.
  • GTHUM:
    • The ID of humidity alarm. The range is 0 – 3.
  • GTUDT
    • GEO-Fence / PEO-Fence event triggered report ID. It is in HEX format.

rep_type

Report Type has different meanings in different messages:

  • Position related packages (GTTOW, GTDIS, GTIOB, GTSPD, GTSOS, GTRTL, GTDOG, GTIGL,GTHBM, GTVGL)
    • In the message +RESP:GTDIS generated by a digital input (0: The current logic status of the input port is Disable status; 1: The current logic status of the input is Enable status.)
    • In the message +RESP:GTIOB generated by bound IO (0: The current logic status of the bound IO does not meet the alarm condition; 1: The current logic status of the bound IO meets the alarm condition.)
    • In the speed alarm message +RESP:GTSPD (0: Outside the predefined speed range; 1: Inside the predefined speed range)
    • In the protocol watchdog message +RESP:GTDOG (1: Reboot device message for time based working mode 2: Reboot device message for ignition on working mode 3: Reboot device message for input triggered 4: Reboot device message for network watchdog 5: Reboot device message for EGPRS/LTE watchdog 6: Reboot device message for send failure watchdog 7: Reboot RF message for network watchdog 8: Reboot RF message for EGPRS/LTE watchdog 9: Reboot RF message for send failure watchdog)
    • In the harsh behavior monitoring message +RESP:GTHBM (0: Harsh braking behavior 1: Harsh acceleration behavior)
    • In the (virtual) ignition on/off location messages +RESP:GTIGL and +RESP:GTVGL (0: Ignition on 1: Ignition off)
    • For other messages, it will always be 0.
  • GTFRI\GTERI:
    • 0:Normal fixed report.
    • 1: Corner report which indicates that the device just turns around a corner.
    • 2: FRI report frequency change which indicates the device enters into Geo-Fence or roaming status.
    • 3: Corner report when FRI report frequency changes.
    • 4: Mileage report when fixed report is in mode
    • 5: Reserved.
    • 6: Mileage report when fixed report is in mode 5 and AT+GTFFC works
  • GTEPS\GTAIS:
    • 0: Outside the predefined range.
    • 1: Inside the predefined range.
  • GTTMP:
    • 0 means “Outside the predefined temperature range”.
    • 1 means “Inside the predefined temperature range”.
  • GTVGN:
    • 2: External power voltage mode (virtual ignition detection)
    • 4: Accelerometer mode (virtual ignition detection)
    • 7: Combined detection mode
  • GTGES:
    • 0: The current Parking-Fence is inactive.
    • 1: The current Parking-Fence is active.
  • GTHUM:
    • 0 means outside the predefined humidity range.
    • 1 means inside the predefined humidity range.
  • GTUDT:
    • 0: Timer event triggered.
    • 1: GEO-Fence event triggered.
    • 2: PEO-Fence event triggered.
  • GTDAT
    • 1: Reserved
    • 2: AT+GTDAT from Bluetooth
    • 3: AT+GTDAT from over the air
    • 4: AT+GTDAT triggered by events in AT+GTUDF
  • GTCAN
    • 0: Periodic report.
    • 1: RTO CAN report
    • 2: Ignition event report

gnss_trigger_type

The trigger type of GNSS point has the following meanings.

0: Time point
1: Corner point
2: Distance point
3: Mileage point
4: Optimum point (time & mileage)

mileage

The current total mileage.

card_id

The RFID card ID from the GTERI packet type

More devices from the manufacturer

Contact Wialon and achieve the most ambitious goals with telematics

Fill out a request form to get started with Wialon

Step 1
Step 2
Step 3
First name*
Last name*
Company*
Email*
Phone