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"
Jump to navigation
Jump to search
Jgullickson (talk | contribs) m |
(→RFID Scanning Rugged Android Devices: Add ECOM RFID) |
||
| (29 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==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: | |
| + | # 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 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]] | 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?== |
| − | TrackAbout | + | 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 300: | Line 73: | ||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| − | | | + | | TC57 |
| Android | | Android | ||
| − | | | + | | 7.0 (Nougat), 8.0 (Oreo) |
| − | | Built in Barcode Scanner and Rugged | + | | Built in Barcode Scanner and Rugged. |
| | | | ||
;CameraScanner | ;CameraScanner | ||
| Line 311: | Line 84: | ||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| − | | | + | | TC72 |
| Android | | Android | ||
| 7.0 (Nougat), 8.0 (Oreo) | | 7.0 (Nougat), 8.0 (Oreo) | ||
| Line 322: | Line 95: | ||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| − | | | + | | TC77 |
| Android | | Android | ||
| 7.0 (Nougat), 8.0 (Oreo) | | 7.0 (Nougat), 8.0 (Oreo) | ||
| Line 333: | Line 106: | ||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| − | | | + | | TC25 |
| Android | | Android | ||
| − | | | + | | 8.0 (Oreo) |
| Built in Barcode Scanner and Rugged. | | Built in Barcode Scanner and Rugged. | ||
| | | | ||
| Line 344: | Line 117: | ||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| − | | | + | | TC26 |
| Android | | Android | ||
| − | | | + | | |
| Built in Barcode Scanner and Rugged. | | Built in Barcode Scanner and Rugged. | ||
| | | | ||
| Line 353: | Line 126: | ||
;HardwareScanner | ;HardwareScanner | ||
:Code39, Code128 | :Code39, Code128 | ||
| + | |||
|- | |- | ||
| Zebra (Motorola) | | Zebra (Motorola) | ||
| Line 377: | Line 151: | ||
|- | |- | ||
| Honeywell | | Honeywell | ||
| − | | | + | | EDA 50 |
| Android | | Android | ||
| − | | | + | | 7.1.1 (Nougat) |
| − | | Built in Camera Scanner | + | | Built in Barcode Scanner and Camera Scanner. |
| | | | ||
;CameraScanner | ;CameraScanner | ||
| + | :Code39, Code128, QRCode | ||
| + | ;Hardware Scanner | ||
:Code39, Code128, QRCode, DataMatrix | :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 | | Android | ||
| − | | | + | | 11.0 |
| − | | Built in Camera Scanner | + | | Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available |
| | | | ||
;CameraScanner | ;CameraScanner | ||
| − | :Code39, Code128, QRCode, DataMatrix | + | :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) | ||
| + | |} | ||
| + | |||
| + | ==RFID Scanning Rugged Android Devices== | ||
| + | {| class="wikitable sortable" border="2" cellpadding="4" | ||
| + | |- | ||
| + | ! 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 | | Android | ||
| − | | | + | | 11.0 |
| − | | Built in | + | | Built in Camera Scanner, Bluetooth 1D barcode and RFID modules available |
| | | | ||
;CameraScanner | ;CameraScanner | ||
| − | :Code39, Code128, QRCode | + | :Code39, Code128, QRCode, DataMatrix, |
| − | ;Hardware Scanner | + | ;Hardware Scanner (Requires Configuration as [[Smartphone_Vendor-Specific_Help#Bluetooth_Barcode_and_RFID_Scanner_Support|Bluetooth HID]] device) |
| − | :Code39, Code128, | + | :Code39, Code128 (Tested, possibly more with Scanner software) |
|} | |} | ||
| − | ==Consumer | + | ==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. | 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= | |
| + | {{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. | ||
| − | == | + | {| 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) | ||
| + | |} | ||
| − | == | + | ==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 445: | Line 273: | ||
| TA Mobile 6 | | TA Mobile 6 | ||
TA Mobile 7 | TA Mobile 7 | ||
| − | + | This printer is currently only functional with the Denso BHT-1200 rugged handheld device. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| − | + | ====Label Printers==== | |
| − | |||
| − | ====Label | ||
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 475: | Line 294: | ||
| [[File:Zebra_ZT400.png]] ZT400 | | [[File:Zebra_ZT400.png]] ZT400 | ||
| Label 4" Printer | | Label 4" Printer | ||
| − | | TA Mobile 6 <sup>2</sup> | + | | TA Mobile 6, TA Mobile 7 <sup>2</sup> |
(Handheld Compatibility)<sup>1</sup> | (Handheld Compatibility)<sup>1</sup> | ||
|- | |- | ||
| Line 481: | Line 300: | ||
| [[File:Zebra_ZT400.png]] ZT410 | | [[File:Zebra_ZT400.png]] ZT410 | ||
| Label 4" Printer | | Label 4" Printer | ||
| − | | TA Mobile 6 <sup>2</sup> | + | | TA Mobile 6, TA Mobile 7 <sup>2</sup> |
(Handheld Compatibility)<sup>1</sup> | (Handheld Compatibility)<sup>1</sup> | ||
|} | |} | ||
<sup>1</sup> This printer is currently only functional with the Denso BHT-1200 rugged handheld device. | <sup>1</sup> This printer is currently only functional with the Denso BHT-1200 rugged handheld device. | ||
| − | <sup>2</sup> Label printing | + | <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:
- 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 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 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. |
| |
| Zebra (Motorola) | TC57 | Android | 7.0 (Nougat), 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Zebra (Motorola) | TC72 | Android | 7.0 (Nougat), 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Zebra (Motorola) | TC77 | Android | 7.0 (Nougat), 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Zebra (Motorola) | TC25 | Android | 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Zebra (Motorola) | TC26 | Android | Built in Barcode Scanner and Rugged. |
| ||
| Zebra (Motorola) | MC3300 | Android | 7.0 (Nougat), 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Zebra (Motorola) | MC9300 | Android | 8.0 (Oreo) | Built in Barcode Scanner and Rugged. |
| |
| Honeywell | EDA 50 | Android | 7.1.1 (Nougat) | Built in Barcode Scanner and Camera Scanner. |
| |
| Urovo | i6310 | Android | 8.1.0 (Oreo) | Built in Barcode Scanner and Camera Scanner. |
|
|
| 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 |
|
RFID Scanning Rugged Android Devices
| Make | Model | Operating System Name | OS Version | Features | Supported Scanner Symbologies |
|---|---|---|---|---|---|
| Motorola | TC20 | Android |
| ||
| Zebra | RFD8500 | Android |
| ||
| 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 |
|
Consumer Android and iOS Devices
For details on the hardware requirements for smartphone, please see the Android or iOS pages.
Certified Printers
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
|
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 |  Microflash 8i
|
Receipt 8" Dot-matrix | TA Mobile 5
TA Mobile 6 |
| DataMax O'Neil |  Microflash MF4Te
|
Receipt 4" Thermal Printer | TA Mobile 5
TA Mobile 6 |
| Toshiba |  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 |  ZT400
|
Label 4" Printer | TA Mobile 6, TA Mobile 7 2
(Handheld Compatibility)1 |
| Zebra | 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.