map_suite_gps_tracking_server_supported_devices
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
map_suite_gps_tracking_server_supported_devices [2015/09/17 03:44] admin [Xexun TK102 and TK102-2] |
map_suite_gps_tracking_server_supported_devices [2015/09/17 05:24] (current) admin |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Certified GPS Tracking Devices ===== | ===== Certified GPS Tracking Devices ===== | ||
| + | <div gps_tracking_devices> | ||
| + | <div floatleft> | ||
| {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Xexun_TK102.jpg}} | {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Xexun_TK102.jpg}} | ||
| + | </div> | ||
| ==== Xexun TK102 and TK102-2 ==== | ==== Xexun TK102 and TK102-2 ==== | ||
| Ultraportable personal tracking device with auto reporting and monitoring via SMS or GPRS. | Ultraportable personal tracking device with auto reporting and monitoring via SMS or GPRS. | ||
| Line 21: | Line 23: | ||
| * Move | * Move | ||
| * Vibration | * Vibration | ||
| - | + | <div floatleft> | |
| - | <div float_left> | + | |
| {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Xexun_TK103.jpg}} | {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Xexun_TK103.jpg}} | ||
| </div> | </div> | ||
| Line 42: | Line 43: | ||
| * Vibration | * Vibration | ||
| + | <div floatleft> | ||
| {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_OBDtrac.jpg}} | {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_OBDtrac.jpg}} | ||
| + | </div> | ||
| ==== Orion OBDtrac ==== | ==== Orion OBDtrac ==== | ||
| Line 54: | Line 56: | ||
| [[http://deviceerrorlog.cygnustrack.com/?q=Orion|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=Orion|Debug Communications Log]] | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_CT-24.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_CT-24.jpg}} | ||
| + | </div> | ||
| ==== SANAV CT-24 ==== | ==== SANAV CT-24 ==== | ||
| Line 71: | Line 74: | ||
| * PanicAlert | * PanicAlert | ||
| + | <div floatleft> | ||
| {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_CT-58.jpg}} | {{ gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_CT-58.jpg}} | ||
| + | </div> | ||
| ==== SANAV CT-58 ==== | ==== SANAV CT-58 ==== | ||
| Line 88: | Line 92: | ||
| * PanicAlert | * PanicAlert | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_GC-101.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_GC-101.jpg}} | ||
| + | </div> | ||
| ==== SANAV GC-101 ==== | ==== SANAV GC-101 ==== | ||
| Line 105: | Line 110: | ||
| * PanicAlert | * PanicAlert | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_GX-101.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Sanav_GX-101.jpg}} | ||
| + | </div> | ||
| ==== SANAV GX-101 ==== | ==== SANAV GX-101 ==== | ||
| Line 122: | Line 128: | ||
| * PanicAlert | * PanicAlert | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_CalAmp_LMU.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_CalAmp_LMU.jpg}} | ||
| + | </div> | ||
| ==== CalAmp LMU-2000, 3000 and 4000 Series ==== | ==== CalAmp LMU-2000, 3000 and 4000 Series ==== | ||
| Line 131: | Line 137: | ||
| [[http://www.calamp.com/|Manufacturer website]] | [[http://www.calamp.com/|Manufacturer website]] | ||
| - | **Listener address:** 184.73.199.2<br> | + | **Listener address:** 184.73.199.2 \\ |
| - | **Port:** UDP 1893<br> | + | **Port:** UDP 1893 \\ |
| [[http://deviceerrorlog.cygnustrack.com/?q=CalAmp|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=CalAmp|Debug Communications Log]] | ||
| Line 158: | Line 164: | ||
| * VehicleAlarm | * VehicleAlarm | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_DCT_Antares.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_DCT_Antares.jpg}} | ||
| + | </div> | ||
| ==== DCT Antares ==== | ==== DCT Antares ==== | ||
| Line 166: | Line 173: | ||
| [[http://www.digitalcomtech.com/|Manufacturer website]] | [[http://www.digitalcomtech.com/|Manufacturer website]] | ||
| - | **Listener address:** 184.73.199.2<br> | + | **Listener address:** 184.73.199.2 \\ |
| - | **Port:** TCP 1899<br> | + | **Port:** TCP 1899 \\ |
| [[http://deviceerrorlog.cygnustrack.com/?q=DCTAntares|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=DCTAntares|Debug Communications Log]] | ||
| Line 174: | Line 181: | ||
| * Panic | * Panic | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Enfora_MT-GL.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Enfora_MT-GL.jpg}} | ||
| + | </div> | ||
| ==== Enfora MT-GL ==== | ==== Enfora MT-GL ==== | ||
| Line 182: | Line 190: | ||
| [[http://www.enfora.com/|Manufacturer website]] | [[http://www.enfora.com/|Manufacturer website]] | ||
| - | **Listener address:** 184.73.199.2<br> | + | **Listener address:** 184.73.199.2 \\ |
| - | **Port:** UDP 1890<br> | + | **Port:** UDP 1890 \\ |
| [[http://deviceerrorlog.cygnustrack.com/?q=Enfora|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=Enfora|Debug Communications Log]] | ||
| Line 192: | Line 200: | ||
| * TrailerDetached | * TrailerDetached | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Falcom_Stepp_II.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Falcom_Stepp_II.jpg}} | ||
| + | </div> | ||
| ==== Falcom Stepp II ==== | ==== Falcom Stepp II ==== | ||
| Line 200: | Line 209: | ||
| [[http://www.falcom.de/|Manufacturer website]] | [[http://www.falcom.de/|Manufacturer website]] | ||
| - | **Listener address:** 184.73.199.2<br> | + | **Listener address:** 184.73.199.2 \\ |
| - | **Port:** TCP 1896<br> | + | **Port:** TCP 1896 \\ |
| [[http://deviceerrorlog.cygnustrack.com/?q=Falcom|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=Falcom|Debug Communications Log]] | ||
| Line 208: | Line 217: | ||
| * Panic | * Panic | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Meiligao_VT310.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Meiligao_VT310.jpg}} | ||
| + | </div> | ||
| ==== Meiligao VT310 ==== | ==== Meiligao VT310 ==== | ||
| Line 217: | Line 227: | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_EasyTrac.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_EasyTrac.jpg}} | ||
| + | </div> | ||
| ==== Orion EasyTrac ==== | ==== Orion EasyTrac ==== | ||
| Line 225: | Line 236: | ||
| [[http://www.oriontech.com.tw/|Manufacturer website]] | [[http://www.oriontech.com.tw/|Manufacturer website]] | ||
| - | **Listener address:** 184.73.199.2<br> | + | **Listener address:** 184.73.199.2 \\ |
| - | **Port:** TCP 1865<br> | + | **Port:** TCP 1865 \\ |
| [[http://deviceerrorlog.cygnustrack.com/?q=Orion|Debug Communications Log]] | [[http://deviceerrorlog.cygnustrack.com/?q=Orion|Debug Communications Log]] | ||
| Line 246: | Line 257: | ||
| * GeoFenceOutGroupNumber | * GeoFenceOutGroupNumber | ||
| + | <div floatleft> | ||
| {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_SpeedTrac.jpg}} | {{gpstrackingserver:Map_Suite_GPS_Tracking_Server_-_Device_-_Orion_SpeedTrac.jpg}} | ||
| + | </div> | ||
| ==== Orion SpeedTrac ==== | ==== Orion SpeedTrac ==== | ||
| Line 283: | Line 295: | ||
| If you aren't development-inclined or don't have the programming resources, ThinkGeo's professional services team can help you integrate your custom hardware into your Map Suite GPS Tracking Server solution. We'll tailor your installation to work with your devices and customize their interaction with the system to meet your specific needs. If you need professional device integration with the GPS Tracking Server, simply [[http://thinkgeo.com/contact-us.aspx|let us know]]. | If you aren't development-inclined or don't have the programming resources, ThinkGeo's professional services team can help you integrate your custom hardware into your Map Suite GPS Tracking Server solution. We'll tailor your installation to work with your devices and customize their interaction with the system to meet your specific needs. If you need professional device integration with the GPS Tracking Server, simply [[http://thinkgeo.com/contact-us.aspx|let us know]]. | ||
| + | </div> | ||
map_suite_gps_tracking_server_supported_devices.1442461497.txt.gz · Last modified: 2015/09/17 03:44 by admin