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"
Lsilverman (talk | contribs) |
|||
| Line 211: | Line 211: | ||
<sup>2</sup> These are the scanner symbologies tested by TrackAbout and that pertains only to TAMobile 6. There might be other scanner symbologies enabled on the device by default. | <sup>2</sup> These are the scanner symbologies tested by TrackAbout and that pertains only to TAMobile 6. There might be other scanner symbologies enabled on the device by default. | ||
| + | |||
| + | ==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. This applies to new but also older devices. | ||
| + | |||
| + | Certification consist of testing the device, this takes between 4 and 8 hours, TrackAbout charges 4 hours of labor. If the test passes, the device is certified. If it fails, developement is likely needed and additional cost will likely incur. | ||
| + | |||
| + | ===Certification charges=== | ||
| + | Unless the device is a replacement of a popular device, the customer requesting certification will be responsible for the cost. Typical charge for the initial certification test is 4 hours at the current labor rate. | ||
| + | |||
| + | If the initial test fail and the device requires development work, certification for a new device takes in average 16 hours of QA and Dev combined time, but can also be more, depending on the issue. This cost will be passed to the customer, an initial estimate will be sent before the work starts. | ||
| + | |||
| + | ===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 help responsible for any issues related to non-certified device. | ||
| + | |||
| + | ===How to request device certification=== | ||
| + | Contact the [[Contact Us|Support team]] | ||
| + | |||
| + | ===How long does it take?=== | ||
| + | *Testing takes between two and 10 days. Contact Support to get a better estimate at the time you need the evaluation performed. If all tests succeed, the device is then certified and added to our Support Wiki page. | ||
| + | *If any test fails, the device might need to be sent to our developers to work and certify the device. The time involved here can vary quite a bit depending on the issue (OS, scanner, SDK, manufacturer, printer, etc...). | ||
==Minimum Hardware Requirements for Rugged Devices== | ==Minimum Hardware Requirements for Rugged Devices== | ||
Revision as of 14:46, 28 June 2016
Certified Rugged Handhelds
Windows Mobile and Windows CE devices
For applications other than 1D or linear barcodes, please contact TrackAbout Support.
Clients intending to purchase or utilize new devices should contact TrackAbout for their specific needs.
Click on column headings to sort.
| Make | Model | Operating System Name | OS Version | TA Mobile 5 (App Forge) | TA Mobile 6 (CF.NET) | Symbologies 2 |
|---|---|---|---|---|---|---|
| Denso | BHT-1200 (B12QXC and BHT-1261QWBG-CE) | Microsoft Windows CE | 6.00.0000 | Yes | Code 128 | |
| Denso | BHT-710BWB | Microsoft Windows CE | 5.00.0000 | Yes | Code 128 | |
| Honeywell | Dolphin 9700 | Windows Mobile 6.5 Professional | 5.2.21875 | Yes | Yes | Code 39 Code 128 Codabar |
| Honeywell | Dolphin 9900ni "ni" models | Windows Mobile 6.1 (Intrinsically safe) 1 | Yes (ScanWedge enabled) | Yes (ScanWedge disabled) | Code 128 | |
| Honeywell | Dolphin 99EX | Windows CE Embedded Handheld 6.5 Classic | 5.2.23152 | Yes (ScanWedge enabled) | Yes (ScanWedge disabled) | Code 128 |
| Honeywell | Dolphin 7800 | Windows CE Embedded Handheld 6.5 Classic | 5.2.29049 | Yes (ScanWedge enabled) | Yes (ScanWedge disabled) | Code 128 |
| Intermec | CN70 also available in nonincentive certified (Div. 2) | Windows Embedded Handheld 6.5 Classic CE | 5.2.23152 | Yes | Code 128 | |
| Intermec | CN50 | Windows Mobile 6.1 Professional | 5.2.21051 | Yes | Code 128 | |
| Intermec | CN51 | Windows Embedded Handheld 6.5 Professional | 5.2.29153 | Yes | Code 128 Code 39 | |
| Intermec | CK70 | Windows Embedded Handheld 6.5 Professional | (To Be Updated) | Yes | Code 128 Code 39 Data Matrix | |
| Intermec | CK70 | Windows Embedded Handheld 6.5 Professional | (To Be Updated) | Yes | Code 128 Code 39 Data Matrix | |
| Motorola | MC32N0 (MC3200) | Windows Embedded Ver. 7 (CE7) | 7.00.2848 | No | Yes But requires patches | Code 128 |
| Motorola | MC3090 (discontinued) | Microsoft Windows CE | 5.00.1400 | Yes | No | Code 128 |
| Motorola | MC75 (discontinued) | Windows Mobile 6.5 Classic | 5.02.21840 | Yes | Yes (Beep issue) | Code 128 |
| Motorola | MC3190 (discontinued) | Microsoft Windows Mobile | 5.02.20962 | Yes | Yes | Code 128 |
| Motorola | MC67 (cellular) | Microsoft Embedded Handheld 6.5 Professional | 5.2.29128 | Yes | Yes | Code 128 |
| Motorola | MC65 (discontinued) | Windows Mobile 6.5 Professional | 5.02.23145 | Yes | Yes | Code 128 |
| Motorola | MC55 (no cellular) | Windows Mobile 6.5 Classic | 5.2.23121 | Yes | Yes | Code 128 |
| Motorola | MC75 (discontinued) | Windows Mobile 6 Professional | 5.02.1947 | Yes | Yes | Code 128 |
| Psion | WorkAbout Pro | Microsoft Windows CE | 5.00.0000 | Yes | Yes | Code 128 |
| Psion | WorkAbout Pro | Windows Mobile 6.1 Professional | 5.02.1621 | Yes | Yes | Code 128 |
| Psion | WorkAbout Pro3 | Microsoft Windows CE | 5.00.0000 | Yes | Yes | Code 128 |
| Psion | WorkAbout Pro4 | Microsoft Windows CE | 6.00.0000 | Yes | Code 128 Code 39 |
1 Intrinsically safe or Non-Incendive Equipment : Certified for use in specified hazardous locations by UL (Class I, Division 2) UL Web Site , ensuring worker safety
2 These are the scanner symbologies tested by TrackAbout and that pertains only to TAMobile 6. There might be other scanner symbologies enabled on the device by default.
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. This applies to new but also older devices.
Certification consist of testing the device, this takes between 4 and 8 hours, TrackAbout charges 4 hours of labor. If the test passes, the device is certified. If it fails, developement is likely needed and additional cost will likely incur.
Certification charges
Unless the device is a replacement of a popular device, the customer requesting certification will be responsible for the cost. Typical charge for the initial certification test is 4 hours at the current labor rate.
If the initial test fail and the device requires development work, certification for a new device takes in average 16 hours of QA and Dev combined time, but can also be more, depending on the issue. This cost will be passed to the customer, an initial estimate will be sent before the work starts.
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 help responsible for any issues related to non-certified device.
How to request device certification
Contact the Support team
How long does it take?
- Testing takes between two and 10 days. Contact Support to get a better estimate at the time you need the evaluation performed. If all tests succeed, the device is then certified and added to our Support Wiki page.
- If any test fails, the device might need to be sent to our developers to work and certify the device. The time involved here can vary quite a bit depending on the issue (OS, scanner, SDK, manufacturer, printer, etc...).
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 Rugged Smartphones
| Make | Model | Operating System Name | OS Version | Features | Supported Scanner Symbologies |
|---|---|---|---|---|---|
| Motorola | TC55 | Android | 4.1.2 | Built in Barcode Scanner and Rugged |
|
| Honeywell | Dolphin CT50 | Android | 4.4.4 | Built in Camera Scanner (Imager), (Scanner does not work yet) |
|
Consumer and Other Android and iOS Devices
For details on the hardware requirements for smartphone, please see the Android or iOS pages.
iPhones 5S and later all have great scanning performance.
For Android smartphones, we recommend Samsung Galaxy S6 (or later) phones for the best scanning performance.
Certified Printers
Proof of Delivery Receipt - Mobile Printers
Below are the TrackAbout certified mobile printer for TA Mobile 5 and TA Mobile 6 Proof of Delivery (POD) Receipt.
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.
1 This printer is currently only functional with the Denso BHT-1200 rugged handheld device.
Label Mobile 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.
1 This printer is currently only functional with the Denso BHT-1200 rugged handheld device.
2 Label printing from TAMobile 6 require custom software
