AOVX GL100 on TrackeraX
The AOVX GL100 is an asset tracker with Bluetooth and 4G LTE. It has an internal battery. In TrackeraX it connects over the jt808 protocol on port 6015 and accepts 23 commands from the platform.
[ How to connect it to TrackeraX ]
- Insert a SIM card with mobile data and set the APN of your carrier on the device.
- Set the server to the domain of your TrackeraX platform and the port 6015 (jt808 protocol).
- Create the device in TrackeraX with its IMEI or identifier and choose the AOVX GL100 model.
- Wait for the first position and turn the parameters above into sensors and alerts.
The exact commands to set the APN and server depend on the firmware: check the manufacturer's manual or ask our support team.
[ Hardware and connectivity ]
- Internal battery
- Bluetooth
- 4G LTE
[ Commands you can send from TrackeraX ]
Available from the web platform and the apps. The custom command sends any text the device firmware accepts.
- Output controloutputControl
- Engine stopengineStop
- Engine resumeengineResume
- Arm alarmalarmArm
- Disarm alarmalarmDisarm
- Dismiss alarmalarmDismiss
- Reboot devicerebootDevice
- Request positionpositionSingle
- Reporting intervalpositionPeriodic
- Stop reportingpositionStop
- Text messagemessage
- Voice messagevoiceMessage
- Driver identificationgetDriver
- Start live videovideoStart
- Stop live videovideoStop
- videoPropertiesvideoProperties
- parameterQueryparameterQuery
- mediaSearchmediaSearch
- mediaUploadmediaUpload
- ptzRotateptzRotate
- ptzFocusptzFocus
- ptzIrisptzIris
- ptzWiperptzWiper
- aiAdasaiAdas
- aiDmsaiDms
- aiTpmsaiTpms
- aiBsdaiBsd
- List recordingsvideoRecordingList
- Download recordingvideoFileDownload
- Play recordingvideoPlaybackStart
- Playback controlvideoPlaybackControl
- Alarm attachmentsalarmAttachments
- Request photorequestPhoto
- Custom commandcustom
[ Data reported by the jt808 protocol ]
Parameters the server decodes from this protocol. In TrackeraX you turn them into sensors, alerts and reports. Each model reports the ones its firmware and wiring allow.
- Audio fileaudio
- Battery voltagebattery
- Battery levelbatteryLevel
- Blockedblocked
- Cardcard
- Chargingcharge
- Coolant temperaturecoolantTemp
- Device temperaturedeviceTemp
- Doordoor
- Driver ID (RFID / iButton)driverUniqueId
- Fault codes (DTC)dtcs
- Engine loadengineLoad
- Fuelfuel
- Fuel consumptionfuelConsumption
- Fuel levelfuelLevel
- Fuel usedfuelUsed
- G-sensorgSensor
- Geofencegeofence
- HDOPhdop
- Heart rateheartRate
- Humidityhumidity
- SIM ICCIDiccid
- Ignitionignition
- Photoimage
- Digital inputsinput
- Locklock
- Motionmotion
- OBD odometerobdOdometer
- OBD speedobdSpeed
- Odometerodometer
- External powerpower
- RPMrpm
- GSM signalrssi
- Satellitessat
- Visible satellitessatVisible
- Stepssteps
- Throttlethrottle
- Trip odometertripOdometer
- Firmware versionversionFw
- Video filevideo
- VINvin
Numbered inputs and sensors
- Analog inputs (adc1, adc2…)
- IO elements (io1, io2…)
- Temperature sensors (temp1, temp2…)
[ Alarms the protocol can report ]
- Accidentaccident
- Doordoor
- Fatigue drivingfatigueDriving
- Faultfault
- Fuel leakfuelLeak
- Geofencegeofence
- Geofence entrygeofenceEnter
- Geofence exitgeofenceExit
- GPS antenna cutgpsAntennaCut
- Harsh accelerationhardAcceleration
- Harsh brakinghardBraking
- Harsh corneringhardCornering
- High RPMhighRpm
- Idlingidle
- Jammingjamming
- Lane changelaneChange
- Low batterylowBattery
- Low powerlowPower
- Movementmovement
- Overspeedoverspeed
- Parkingparking
- Power cutpowerCut
- Power offpowerOff
- Power restoredpowerRestored
- Removalremoving
- SOSsos
- Tamperingtampering
- Temperaturetemperature
- Towingtow
- Vibrationvibration
[ Protocol-specific attributes ]
abnormalDrivingAlarm · abnormalDrivingDegree · adasAlarm · adasAlarmId · adasAlarmLevel · adasAlarmSerial · adasAlarmStatus · adasAlarmType · adasAltitude · adasDateTime · adasDeviationType · adasFrontDistance · adasFrontVehicleSpeed · adasLatitude · adasLongitude · adasRaw · adasRawLength · adasRoadSignData · adasRoadSignType · adasSpeed · adasVehicleStatus · airPressure · airTemp · alarmAreaEntering · alarmAreaId · alarmAreaType · alarmAttachments · alarmIdentifier · alarmJimi · alarmMask · alarmPhotoSaveFlag · alarmPhotoSwitch · alarmSerial · alarmSmsSwitch · alarmSupplement · alarmTerminalId · alarmThresholdType · alcohol · answerPolicy · apn and 179 more
[ Other AOVX models ]
[ Other devices on the jt808 protocol ]
AOVX GL100 FAQ
Which port does the AOVX GL100 use to connect to TrackeraX?
The AOVX GL100 uses the jt808 protocol and connects to port 6015 on your TrackeraX server. Just set your platform domain and that port on the device.
What data does the AOVX GL100 send to the platform?
TrackeraX reads 44 parameters of the jt808 protocol on this device, for example: Audio file, Battery voltage, Battery level, Blocked, Card. Each one can become a sensor or an alert.
Can I send commands to the AOVX GL100 from TrackeraX?
Yes. From the map or the device page you can send 33 command types to the AOVX GL100, including: Output control, Engine stop, Engine resume, Arm alarm, Disarm alarm.
Which alarms does the AOVX GL100 report?
TrackeraX recognizes these jt808 alarms: Accident, Door, Fatigue driving, Fault, Fuel leak. Any of them can become an email, push or webhook notification.
How do I add the AOVX GL100 to my platform?
Insert a data SIM, set the APN, point the device to your platform domain on port 6015 and create it in TrackeraX with its IMEI, choosing the AOVX GL100 model.
Try the AOVX GL100 on your own platform
Open the live demo or check the plans: white label, your domain, your apps.
Brands, logos and product images belong to their respective owners.