Warning
WARNING: The TrackAbout MetaWiki has been deprecated and is no longer being updated.

Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.

Difference between revisions of "TrackAbout Certified Devices"

From TrackAbout MetaWiki
Jump to navigation Jump to search
 
(98 intermediate revisions by 17 users not shown)
Line 1: Line 1:
 +
==Certified Device Policy==
 +
TrackAbout maintains a limited list of TrackAbout-certified and supported devices by specific manufacturers.
  
−
==Certified Rugged Handhelds==
+
Decisions about which manufacturers and devices to support is carefully considered. TrackAbout cannot support all mobile devices, due to hardware incompatibilities and variance in operating system supported features.
−
Windows Mobile and Windows CE devices
 
  
−
''Click on column headings to sort.''
+
See [[Smartphone Hardware Purchasing Recommendations]] for information about consumer-grade Android and iOS devices.
  
 +
See [[#Rugged Android RFID Devices]] below.
 +
 +
See [[Certified Rugged Windows Devices (Legacy)]] for older TAMobile 6 and 5 certified devices.
 +
 +
==How to get a device certified by TrackAbout==
 +
If a customer wants to use a non-certified device, TrackAbout needs to test and certify the device.
 +
 +
Generally, TrackAbout prefers customers to use already-certified devices whenever possible. However, we do understand that not all of our certified devices are available in all regions of the world.
 +
 +
Customers must provide test devices to TrackAbout for certification at customer's cost. It's best for TrackAbout to be able to keep at least one test device indefinitely to maintain compatibility and be able to offer support should the customer have device-specific issues.
 +
 +
The certification process:
 +
# Research device specifications - A TrackAbout engineer will evaluate the specs and capabilities of the device as advertised by the manufacturer. A particular area of focus is determining whether the device uses custom barcode or RFID scanning hardware. Scanning hardware usually requires software work by TrackAbout. It is necessary to integrate the manufacturer's software development kit (SDK) in order to fully enable the scanning function within TrackAbout's apps. Sometimes, the manufacturer provides a "data wedge" app which can send scans to the TrackAbout app, and integration is not required. This evaluation needs to take place.
 +
# If no custom hardware is present and no custom integration is required, TrackAbout will perform a certification. The customer will be responsible for the cost at the current labor rate. Testing takes between two and ten days and will have a minimum labor charge of 4 hours, possibly more depending on the complexity of the evaluation.
 +
# If custom integration is required, a negotiation regarding the labor requirements and scheduling of the work must take place, taking into account TrackAbout's other development priorities, and the size of the customer opportunity. '''For custom integration and certification, TrackAbout will require two devices, one for development and one for the QA team.''' Certification for a new device can take from 40-80 hours of software development and QA time. An initial estimate will be provided and a statement of work agreed to before the work may start. The timeframe of the work will also need to be negotiated.
 +
 +
==Why do devices sometimes require additional software development to be certified?==
 +
The TrackAbout application accepts barcode and RFID scans on many different screens and in many different ways. For maximum scanning speed and the lowest possible employee frustration, TrackAbout prefers to deeply integrate with the scanning engine of the device.
 +
 +
Simpler apps might show a text box on the screen to receive a scan. When the label is scanned, the scan engine fills the text box by quickly typing the characters into the field.
 +
 +
The TrackAbout app records whether tags are typed or scanned. TrackAbout's app treats typed tag numbers differently than scanned tag numbers. Typing a tag indicates a tag might be unscannable or damaged. An employee typing a tag may mistype it, creating exceptions on the record that are only seen later. Evidence that a tag was typed can later help someone understand why a record looks wrong.
 +
 +
Supporting rapid, repeated scanning requires deeper integration than the "here's a textbox and press OK" model.
 +
 +
In order to provide the best possible user experience, TrackAbout therefore has to talk directly to the scanning hardware (or the manufacturer's code library for the scanning hardware), and this takes custom development.
 +
 +
==What if I want to use a non-certified device?==
 +
If a customer decides to use a non-certified device, TrackAbout Support will be limited and cannot be held responsible for any issues related to the user of the non-certified device.
 +
 +
==How to request device certification==
 +
Contact the [[Contact Us|Support team]]
 +
 +
==For how long will you support a certified device?==
 +
TrackAbout will usually support certified devices until one of the following happens:
 +
* The device manufacturer no longer supports it
 +
* The operating system gets too old and can no longer be supported by our application as documented on our [[Smartphone Hardware Purchasing Recommendations]] page.
 +
 +
==Where should I procure hardware in my country?==
 +
In North America (USA, Canada and Mexico), TrackAbout recommends working with [https://www.supplychainservices.com/ Supply Chain Services]
 +
 +
Outside North America, please ask the [[Contact Us|Support Team]].
 +
 +
TrackAbout recommends not buying second-hand hardware from gray markets such as eBay. Generally, used hardware has a limited lifetime remaining due to aging of the batteries and the operating system.
 +
 +
==Barcode Scanning Rugged Android Devices==
 
{| class="wikitable sortable" border="2" cellpadding="4"
 
{| class="wikitable sortable" border="2" cellpadding="4"
 
|-
 
|-
Line 11: Line 58:
 
! Operating System Name  
 
! Operating System Name  
 
! OS Version  
 
! OS Version  
−
! TA Mobile 5 (App Forge)
+
! Features
−
! TA Mobile 6 (CF.NET)
+
! Supported Scanner Symbologies
 
|-
 
|-
−
| Denso
+
| Motorola
−
| BHT-1261WBG-CE
+
| TC56
−
| Microsoft Windows CE
+
| Android
−
| 6.00.0000
+
| 6.0 (Marshmallow)
 +
| Built in Barcode Scanner and Rugged.  Limited Certification.  Not tested for printing.
 
|  
 
|  
−
| Yes
+
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Denso
+
| Zebra (Motorola)
−
| BHT-710BWB
+
| TC57
−
| Microsoft Windows CE
+
| Android
−
| 5.00.0000
+
| 7.0 (Nougat), 8.0 (Oreo)
 +
| Built in Barcode Scanner and Rugged.  
 
|  
 
|  
−
|Yes
+
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Honeywell
+
| Zebra (Motorola)
−
| Dolphin 9700
+
| TC72
−
| Windows Mobile 6.5 Professional
+
| Android
−
| 5.2.21875
+
| 7.0 (Nougat), 8.0 (Oreo)
−
|Yes
+
| Built in Barcode Scanner and Rugged.
−
|Yes
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Honeywell
+
| Zebra (Motorola)
−
| Dolphin 9900ni [http://www.honeywellaidc.com/CatalogDocuments/non-incendive-offering-dolphin-99ex-series.pdf "ni" models]
+
| TC77
−
| Windows Mobile 6.1 (Intrinsically safe) <sup>1</sup>
+
| Android
−
|
+
| 7.0 (Nougat), 8.0 (Oreo)
−
| Yes (ScanWedge enabled)
+
| Built in Barcode Scanner and Rugged.
−
| Yes
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Honeywell
+
| Zebra (Motorola)
−
| Dolphin 99EX
+
| TC25
−
| Windows CE Embedded Handheld 6.5 Classic
+
| Android
−
| 5.2.23152
+
| 8.0 (Oreo)
−
| Yes (ScanWedge enabled)
+
| Built in Barcode Scanner and Rugged.  
−
| Yes
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Honeywell
+
| Zebra (Motorola)
−
| Dolphin 7800
+
| TC26
−
| Windows CE Embedded Handheld 6.5 Classic
+
| Android
−
| 5.2.29049
 
−
| Yes (ScanWedge enabled)
 
−
| Yes
 
−
|-
 
−
| Intermec
 
−
| CN70 also available in nonincentive certified (Div. 2)
 
−
| Windows Embedded Handheld 6.5 Classic CE
 
−
| 5.2.23152
 
 
|
 
|
−
| Yes
+
| Built in Barcode Scanner and Rugged.
 +
|
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 +
 
 
|-
 
|-
−
| Intermec
+
| Zebra (Motorola)
−
| CN50
+
| MC3300
−
| Windows Mobile 6.1 Professional
+
| Android
−
| 5.2.21051
+
| 7.0 (Nougat), 8.0 (Oreo)
−
|
+
| Built in Barcode Scanner and Rugged.
−
|Yes
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Motorola  
+
| Zebra (Motorola)
−
| MC3190
+
| MC9300
−
| Microsoft Windows CE
+
| Android
−
| 6.00.3122
+
| 8.0 (Oreo)
−
| Yes
+
| Built in Barcode Scanner and Rugged.  
−
| Yes
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix
 +
;HardwareScanner
 +
:Code39, Code128
 
|-
 
|-
−
| Motorola
+
| Honeywell
−
| MC3090
+
| EDA 50
−
| Microsoft Windows CE
+
| Android
−
| 5.00.1400
+
| 7.1.1 (Nougat)
−
| Yes
+
| Built in Barcode Scanner and Camera Scanner.
 
|  
 
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode
 +
;Hardware Scanner
 +
:Code39, Code128, QRCode, DataMatrix
 
|-
 
|-
−
| Motorola
+
| Urovo
−
| MC75
+
| i6310
−
| Windows Mobile 6.5 Classic
+
| Android
−
| 5.02.21840
+
| 8.1.0 (Oreo)
−
| Yes
+
| Built in Barcode Scanner and Camera Scanner.
−
| Yes (Beep issue)
+
|  
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix,
 +
;Hardware Scanner (Requires Configuration)
 +
:Code39, Code128, QRCode, DataMatrix (Tested, possibly more with Scanner software)
 +
|
 
|-
 
|-
−
| Motorola
+
| ECOM
−
| MC3190
+
| Smart-EX 02 with Ident-EX 01 with 1D Barcode module
−
| Microsoft Windows Mobile
+
| Android
−
| 5.02.20962
+
| 11.0
−
| Yes
+
| Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available
−
| Yes
+
|  
−
|-
+
;CameraScanner
−
| Motorola
+
:Code39, Code128, QRCode, DataMatrix,
−
| MC67
+
;Hardware Scanner (Requires Configuration as [[Smartphone_Vendor-Specific_Help#Bluetooth_Barcode_and_RFID_Scanner_Support|Bluetooth HID]] device)
−
| Microsoft Embedded Handheld 6.5 Professional
+
:Code39, Code128 (Tested, possibly more with Scanner software)
−
| 5.2.29128
 
−
|Yes
 
−
|Yes
 
−
|-
 
−
| Motorola
 
−
| MC65
 
−
| Windows Mobile 6.5 Professional
 
−
| 5.02.23145
 
−
|Yes
 
−
|Yes
 
−
|-
 
−
|Motorola
 
−
|MC55
 
−
|Windows Mobile 6.5 Classic
 
−
| 5.2.23121
 
−
| Yes
 
−
| Yes
 
−
|-
 
−
| Motorola
 
−
| MC75
 
−
| Windows Mobile 6 Professional
 
−
| 5.02.1947
 
−
| Yes
 
−
| Yes
 
−
|-
 
−
| Psion
 
−
| WorkAbout Pro
 
−
| Microsoft Windows CE
 
−
| 5.00.0000
 
−
| Yes
 
−
| Yes
 
−
|-
 
−
| Psion
 
−
| WorkAbout Pro
 
−
| Windows Mobile 6.1 Professional
 
−
| 5.02.1621
 
−
| Yes
 
−
| Yes
 
−
|-
 
−
| Psion
 
−
| WorkAbout Pro3
 
−
| Microsoft Windows CE
 
−
| 5.00.0000
 
−
| Yes
 
−
| Yes
 
−
|-
 
−
| Motorola
 
−
| MC3200
 
−
| Microsoft Windows Mobile Embedded 7
 
−
| 7.00.2824
 
−
| Not Tested
 
−
| '''FAILED''' See below
 
 
|}
 
|}
  
−
<sup>1</sup> Intrinsically safe or Non-Incendive Equipment :&nbsp;Certified for use in specified hazardous locations by UL (Class I, Division 2) [http://www.ul.com UL Web Site] , ensuring worker safety
+
==RFID Scanning Rugged Android Devices==
−
 
 
−
IP rating: [https://en.wikipedia.org/wiki/IP_Code Link IP protection, IP Code, International Protection Marking, also sometimes interpreted as Ingress Protection Marking]
 
−
 
 
−
==Minimum Hardware Requirements for Rugged Devices==
 
−
TrackAbout customers are not required to use a certified device, but please check with us first.  This needs to be evaluated on a case by case basis for the specific device in question.  The following list is the minimum requirements for a device we will consider certifying.
 
−
* Windows Mobile 6, Windows Embedded Handheld 6.5, or Windows CE 5/6
 
−
* CPU - 600 MHz, 1 GHz recommended
 
−
* RAM - 256 MB, 512 MB recommended
 
−
* Storage/ROM/Flash - 128 MB, 1 GB recommended.
 
−
* Screen - 240x320(minimum), 320x480 or higher recommended.
 
−
* Barcode scanner (TrackAbout supplied barcodes are Code128)
 
−
* Wifi or Cellular data connection recommended
 
−
 
 
−
==Featured Smartphones==
 
 
{| class="wikitable sortable" border="2" cellpadding="4"
 
{| class="wikitable sortable" border="2" cellpadding="4"
 
|-
 
|-
Line 177: Line 193:
 
! OS Version  
 
! OS Version  
 
! Features
 
! Features
 +
! Supported Scanner Symbologies
 
|-
 
|-
 
| Motorola
 
| Motorola
−
| TC55
+
| TC20
 
| Android
 
| Android
−
| 4.1.2
+
|  
−
| Built in Barcode Scanner and Rugged
+
|
 +
|
 +
:RFID
 +
|-
 +
| Zebra
 +
| RFD8500
 +
| Android
 +
|
 +
|
 +
|
 +
:RFID
 +
|-
 +
| ECOM
 +
| Smart-EX 02 with Ident-EX 01 with RFID module
 +
| Android
 +
| 11.0
 +
| Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available
 +
|
 +
;CameraScanner
 +
:Code39, Code128, QRCode, DataMatrix,
 +
;Hardware Scanner (Requires Configuration as [[Smartphone_Vendor-Specific_Help#Bluetooth_Barcode_and_RFID_Scanner_Support|Bluetooth HID]] device)
 +
:Code39, Code128 (Tested, possibly more with Scanner software)
 
|}
 
|}
  
−
For details on the hardware requirements for smartphone, please see the [[Smartphone_App#Android_Version_Compatibility|Android]] or [[Smartphone_App#Operating_System|iOS]] pages.
+
==Consumer Android and iOS Devices==
 +
For details on the hardware requirements for smartphone, please see the [[Smartphone_App#Hardware_requirements|Android]] or [[Smartphone_App#Supported_iPhones|iOS]] pages.
  
−
==Certified Printers==
+
=Certified Printers=
−
<span style="color:red">Important Note</span>.
+
{{warning|Before ordering a printer, please contact TrackAbout Support to confirm that the printer will work with your TrackAbout versions and mobile devices.}}
−
Before ordering a printer, please contact TrackAbout Support to confirm that the printer will work with your TrackAbout versions and mobile devices.
 
  
−
====Proof of Delivery Receipt - Mobile Printers====
+
==Mobile Receipt Printers==
−
Below are the TrackAbout certified mobile printer for TA Mobile 5 and TA Mobile 6 Proof of Delivery (POD) Receipt.
+
Below are the TrackAbout certified mobile printers for Proof of Delivery (POD) receipt printing.
 +
 
 +
{| class="wikitable sortable" border="2" cellpadding="4"
 +
|-
 +
! Manufacturer
 +
! Model
 +
! Type
 +
! Supported Software
 +
|-
 +
| [[Pairing_a_Zebra_ZQ520_for_use_with_TAM6_and_TAM7|Zebra ZQ520]]
 +
| [[File:ZQ520.jpg|120px]] ZQ520
 +
| Receipt 4" Thermal Printer
 +
| TA Mobile 6 (Only Supported on Denso mobile devices)
 +
TA Mobile 7 (Only supported on Android)
 +
|}
  
−
If there are any new printers which you would like to have certified, it will require new code and is a big, costly job. Reach out to your TrackAbout Support representative to get an estimate of cost for the printer you'd like to use.
+
==End-of-Life Mobile Printers==
 +
The following printers are no longer in production and are not recommended.
  
 
{| class="wikitable sortable" border="2" cellpadding="4"
 
{| class="wikitable sortable" border="2" cellpadding="4"
Line 203: Line 256:
 
! Supported Software
 
! Supported Software
 
|-
 
|-
−
| DataMax O'Neil
+
| [[Pairing an O'Neil Printer With TAMobile6 Handheld|Datamax O'Neil]]
 
| [[File:mf8i.png|120px|link=Microflash 8I]] Microflash 8i
 
| [[File:mf8i.png|120px|link=Microflash 8I]] Microflash 8i
 
| Receipt 8" Dot-matrix
 
| Receipt 8" Dot-matrix
Line 209: Line 262:
 
TA Mobile 6
 
TA Mobile 6
 
|-  
 
|-  
−
| DataMax O'Neil
+
| [[Pairing an O'Neil Printer With TAMobile6 Handheld|DataMax O'Neil]]
−
| [[File:mf4t.png|120px|link=Microflash 4T]] Microflash 4T and Microflash 4 Te
+
| [[File:mf4t.png|120px|link=Microflash 4T]] Microflash MF4Te
 
| Receipt 4" Thermal Printer
 
| Receipt 4" Thermal Printer
 
| TA Mobile 5
 
| TA Mobile 5
 
TA Mobile 6
 
TA Mobile 6
 +
|-
 +
| [[Troubleshooting_Mobile_Printers#Pairing_the_Toshiba_EP4DL_Printer_.284_inch.29|Toshiba]]
 +
| [[File:toshiba-b-ep4dl.jpg|120px]] B-EP4DL
 +
| Receipt 4" Printer
 +
| TA Mobile 6
 +
TA Mobile 7
 +
This printer is currently only functional with the Denso BHT-1200 rugged handheld device.
 
|}
 
|}
  
−
====Label Mobile Printers====
+
====Label Printers====
 
The printers listed below are used for very specific environment and should not be ordered without receiving confirmation from TrackAbout that the application will support the device.
 
The printers listed below are used for very specific environment and should not be ordered without receiving confirmation from TrackAbout that the application will support the device.
  
Line 225: Line 285:
 
! Type
 
! Type
 
! Software version
 
! Software version
−
|-
 
−
| Toshiba
 
−
| B-EP4
 
−
| Receipt Printer
 
−
| TA Mobile 6 (custom)
 
 
|-
 
|-
 
| Zebra
 
| Zebra
 
| RZ400
 
| RZ400
 
| RF & Desktop Label Printer
 
| RF & Desktop Label Printer
−
| TA Mobile 6 (custom)
+
| TA Mobile 6  
 +
|-
 +
| Zebra
 +
| [[File:Zebra_ZT400.png]] ZT400
 +
| Label 4" Printer
 +
| TA Mobile 6, TA Mobile 7 <sup>2</sup>
 +
(Handheld Compatibility)<sup>1</sup>
 +
|-
 +
| Zebra
 +
| [[File:Zebra_ZT400.png]] ZT410
 +
| Label 4" Printer
 +
| TA Mobile 6, TA Mobile 7 <sup>2</sup>
 +
(Handheld Compatibility)<sup>1</sup>
 
|}
 
|}
 +
<sup>1</sup> This printer is currently only functional with the Denso BHT-1200 rugged handheld device.
 +
 +
<sup>2</sup> Label printing requires TrackAbout Support to set up label formatting.

Latest revision as of 17:49, 10 January 2023

Certified Device Policy

TrackAbout maintains a limited list of TrackAbout-certified and supported devices by specific manufacturers.

Decisions about which manufacturers and devices to support is carefully considered. TrackAbout cannot support all mobile devices, due to hardware incompatibilities and variance in operating system supported features.

See Smartphone Hardware Purchasing Recommendations for information about consumer-grade Android and iOS devices.

See #Rugged Android RFID Devices below.

See Certified Rugged Windows Devices (Legacy) for older TAMobile 6 and 5 certified devices.

How to get a device certified by TrackAbout

If a customer wants to use a non-certified device, TrackAbout needs to test and certify the device.

Generally, TrackAbout prefers customers to use already-certified devices whenever possible. However, we do understand that not all of our certified devices are available in all regions of the world.

Customers must provide test devices to TrackAbout for certification at customer's cost. It's best for TrackAbout to be able to keep at least one test device indefinitely to maintain compatibility and be able to offer support should the customer have device-specific issues.

The certification process:

  1. Research device specifications - A TrackAbout engineer will evaluate the specs and capabilities of the device as advertised by the manufacturer. A particular area of focus is determining whether the device uses custom barcode or RFID scanning hardware. Scanning hardware usually requires software work by TrackAbout. It is necessary to integrate the manufacturer's software development kit (SDK) in order to fully enable the scanning function within TrackAbout's apps. Sometimes, the manufacturer provides a "data wedge" app which can send scans to the TrackAbout app, and integration is not required. This evaluation needs to take place.
  2. If no custom hardware is present and no custom integration is required, TrackAbout will perform a certification. The customer will be responsible for the cost at the current labor rate. Testing takes between two and ten days and will have a minimum labor charge of 4 hours, possibly more depending on the complexity of the evaluation.
  3. If custom integration is required, a negotiation regarding the labor requirements and scheduling of the work must take place, taking into account TrackAbout's other development priorities, and the size of the customer opportunity. For custom integration and certification, TrackAbout will require two devices, one for development and one for the QA team. Certification for a new device can take from 40-80 hours of software development and QA time. An initial estimate will be provided and a statement of work agreed to before the work may start. The timeframe of the work will also need to be negotiated.

Why do devices sometimes require additional software development to be certified?

The TrackAbout application accepts barcode and RFID scans on many different screens and in many different ways. For maximum scanning speed and the lowest possible employee frustration, TrackAbout prefers to deeply integrate with the scanning engine of the device.

Simpler apps might show a text box on the screen to receive a scan. When the label is scanned, the scan engine fills the text box by quickly typing the characters into the field.

The TrackAbout app records whether tags are typed or scanned. TrackAbout's app treats typed tag numbers differently than scanned tag numbers. Typing a tag indicates a tag might be unscannable or damaged. An employee typing a tag may mistype it, creating exceptions on the record that are only seen later. Evidence that a tag was typed can later help someone understand why a record looks wrong.

Supporting rapid, repeated scanning requires deeper integration than the "here's a textbox and press OK" model.

In order to provide the best possible user experience, TrackAbout therefore has to talk directly to the scanning hardware (or the manufacturer's code library for the scanning hardware), and this takes custom development.

What if I want to use a non-certified device?

If a customer decides to use a non-certified device, TrackAbout Support will be limited and cannot be held responsible for any issues related to the user of the non-certified device.

How to request device certification

Contact the Support team

For how long will you support a certified device?

TrackAbout will usually support certified devices until one of the following happens:

Where should I procure hardware in my country?

In North America (USA, Canada and Mexico), TrackAbout recommends working with Supply Chain Services

Outside North America, please ask the Support Team.

TrackAbout recommends not buying second-hand hardware from gray markets such as eBay. Generally, used hardware has a limited lifetime remaining due to aging of the batteries and the operating system.

Barcode Scanning Rugged Android Devices

Make Model Operating System Name OS Version Features Supported Scanner Symbologies
Motorola TC56 Android 6.0 (Marshmallow) Built in Barcode Scanner and Rugged. Limited Certification. Not tested for printing.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) TC57 Android 7.0 (Nougat), 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) TC72 Android 7.0 (Nougat), 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) TC77 Android 7.0 (Nougat), 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) TC25 Android 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) TC26 Android Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) MC3300 Android 7.0 (Nougat), 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Zebra (Motorola) MC9300 Android 8.0 (Oreo) Built in Barcode Scanner and Rugged.
CameraScanner
Code39, Code128, QRCode, DataMatrix
HardwareScanner
Code39, Code128
Honeywell EDA 50 Android 7.1.1 (Nougat) Built in Barcode Scanner and Camera Scanner.
CameraScanner
Code39, Code128, QRCode
Hardware Scanner
Code39, Code128, QRCode, DataMatrix
Urovo i6310 Android 8.1.0 (Oreo) Built in Barcode Scanner and Camera Scanner.
CameraScanner
Code39, Code128, QRCode, DataMatrix,
Hardware Scanner (Requires Configuration)
Code39, Code128, QRCode, DataMatrix (Tested, possibly more with Scanner software)
ECOM Smart-EX 02 with Ident-EX 01 with 1D Barcode module Android 11.0 Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available
CameraScanner
Code39, Code128, QRCode, DataMatrix,
Hardware Scanner (Requires Configuration as Bluetooth HID device)
Code39, Code128 (Tested, possibly more with Scanner software)

RFID Scanning Rugged Android Devices

Make Model Operating System Name OS Version Features Supported Scanner Symbologies
Motorola TC20 Android
RFID
Zebra RFD8500 Android
RFID
ECOM Smart-EX 02 with Ident-EX 01 with RFID module Android 11.0 Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available
CameraScanner
Code39, Code128, QRCode, DataMatrix,
Hardware Scanner (Requires Configuration as Bluetooth HID device)
Code39, Code128 (Tested, possibly more with Scanner software)

Consumer Android and iOS Devices

For details on the hardware requirements for smartphone, please see the Android or iOS pages.

Certified Printers

Warning
WARNING: Before ordering a printer, please contact TrackAbout Support to confirm that the printer will work with your TrackAbout versions and mobile devices.


Mobile Receipt Printers

Below are the TrackAbout certified mobile printers for Proof of Delivery (POD) receipt printing.

Manufacturer Model Type Supported Software
Zebra ZQ520 ZQ520.jpg ZQ520 Receipt 4" Thermal Printer TA Mobile 6 (Only Supported on Denso mobile devices)

TA Mobile 7 (Only supported on Android)

End-of-Life Mobile Printers

The following printers are no longer in production and are not recommended.

Manufacturer Model Type Supported Software
Datamax O'Neil Mf8i.png Microflash 8i Receipt 8" Dot-matrix TA Mobile 5

TA Mobile 6

DataMax O'Neil Mf4t.png Microflash MF4Te Receipt 4" Thermal Printer TA Mobile 5

TA Mobile 6

Toshiba Toshiba-b-ep4dl.jpg B-EP4DL Receipt 4" Printer TA Mobile 6

TA Mobile 7 This printer is currently only functional with the Denso BHT-1200 rugged handheld device.

Label Printers

The printers listed below are used for very specific environment and should not be ordered without receiving confirmation from TrackAbout that the application will support the device.

Manufacturer Model Type Software version
Zebra RZ400 RF & Desktop Label Printer TA Mobile 6
Zebra Zebra ZT400.png ZT400 Label 4" Printer TA Mobile 6, TA Mobile 7 2

(Handheld Compatibility)1

Zebra Zebra ZT400.png ZT410 Label 4" Printer TA Mobile 6, TA Mobile 7 2

(Handheld Compatibility)1

1 This printer is currently only functional with the Denso BHT-1200 rugged handheld device.

2 Label printing requires TrackAbout Support to set up label formatting.

Retrieved from "https://meta.trackabout.com/w/index.php?title=TrackAbout_Certified_Devices&oldid=8752"