Zebra MC3300 troubleshooting guide: errors, faults and fixes

Short answer: According to Zebra, this slow flashing indicates a fully discharged battery: it is recharging, but not yet enough to run the mobile computer. Leave it in its cradle or on its cable until the light turns solid orange.

Likely cause

The MC33XX charging light table (quick start guide and integrator guide) associates orange flashing slowly, every 3 seconds, with a completely discharged battery that is charging but not yet sufficiently to power the mobile computer.

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

What to do

1. Leave the mobile computer charging without trying to switch it on.
2. Wait for the light to turn solid orange (normal charging), then switch on the mobile computer.
3. Before first use, the integrator guide says to charge fully, until the light stays green.
4. If the light stays off, see the mobile computer does not charge.

Sources: Charging/notification lights (table 10) (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Charge LED Indicators (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: The MC33XX integrator guide treats this as a charging error: temperature out of range, or a charge of about eight hours that does not complete. Bring the mobile computer back to a temperature between 0 °C and 40 °C, then restart charging.

Likely cause

Charging error according to the light table: temperature too low or too high, or charging that goes on too long without finishing (usually eight hours). The guide states that the mobile computer or accessory may suspend charging to keep the battery within a safe range, and that the light indicates this.

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

What to do

1. Remove the mobile computer from the cradle and let it adjust to the temperature.
2. Check the battery temperature: About phone > Battery information.
3. Restart charging in a room between 0 °C and 40 °C.
4. With an MC32N0 battery, charging takes longer (see MC32N0 batteries).
5. If the light then turns solid red, the battery is at the end of its life: see solid red light.

Sources: Charge LED Indicators (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Charging Temperature (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Charging/notification lights (table 10) (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) (official documentation).

Short answer: Solid red indicates a battery at the end of its useful life, whether it is still charging or already charged, according to the Zebra MC33XX guides. Replace it with a battery compatible with your configuration.

Likely cause

The MC33XX light table gives two cases of solid red: spare battery charging and at the end of its useful life, or charging complete and battery at the end of its useful life. The same state exists on the 4-slot and 20-slot spare battery chargers.

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

What to do

1. Identify the battery: the one in the mobile computer, or a spare battery in a cradle or charger.
2. Take it out of service.
3. Replace it with a battery from the list in the guide: MC33XX PowerPrecision+ 2,740 mAh or 5,200 mAh, or MC32N0 PowerPrecision (see compatible batteries).

Sources: Charging/notification lights (table 10) (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Charge LED Indicators (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · 4-Slot Spare Battery Charger (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: The scan button only starts capture if a scanning application is enabled (Zebra MC33XX guide). With the imager, a red aiming pattern should appear; with the SE965 laser, a red line. If the beam appears but the barcode is not decoded, check that its symbology is enabled in DataWedge.

Likely cause

The quick start guide describes scanning with the imager (SE4750-SR, SE4850-ER) and with the SE965 laser: red beam while the button is pressed, then green scan light and a beep on decoding. The DataWedge documentation points out that each symbology must be ticked in the profile's decoders.

What to do

1. Open a data entry app with an active field.
2. Imager: press and hold the scan button or the trigger; the red aiming pattern comes on. Laser: press and hold the scan button; the red scan line comes on.
3. A successful decode is indicated by the green scan LED and a beep, by default.
4. If the beam does not come on, check that DataWedge is enabled (DataWedge enabled box in its settings).
5. If the beam comes on without decoding, open the DataWedge profile, Configure scanner settings > Decoders, and tick the barcode's symbology.
6. For QR codes and other 2D barcodes, see 2D barcodes.

Sources: Scanning barcodes (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Barcode Input (opens in a new window) – Zebra TechDocs – DataWedge · DataWedge Settings (opens in a new window) – Zebra TechDocs – DataWedge (official documentation).

Short answer: Check your mobile computer's configuration: according to the MC33XX integrator guide, the rotating head model (MC33XX-R) is only available with the SE965 1D laser scanner, and some G and S versions are also fitted with it. Only the SE4750-SR and SE4850-ER imagers are 2D engines.

Likely cause

The configuration table in the integrator guide associates a scan engine with each version: SE965 1D, SE4750-SR 2D or SE4850-ER 2D depending on the model (G, R, S, S45) and the range (Standard, Premium, Premium+).

Configurations listed by Zebra

1. MC33XX-G: SE965 1D or SE4750-SR 2D in Standard; SE965, SE4750-SR or SE4850-ER in Premium and Premium+.
2. MC33XX-R (rotating head): SE965 1D only.
3. MC33XX-S: SE965, SE4750-SR or SE4850-ER; SE4750-SR or SE4850-ER in Premium+.
4. MC33XX-S45: SE4750-SR 2D only.
5. If your mobile computer has a 2D imager, check that the symbology (QR Code, DataMatrix…) is ticked in the DataWedge profile's decoders.

Sources: Configurations (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Barcode Input (opens in a new window) – Zebra TechDocs – DataWedge (official documentation).

Short answer: The beam can come on with the default profile Profile0 without DataWedge knowing which application to send the data to. Zebra recommends associating a DataWedge profile with your software, with Keystroke or Intent output.

Likely cause

The DataWedge FAQ links this symptom to there being no profile associated with the application or to an incorrectly configured input/output; Profile0 then applies by default.

What to do

1. In DataWedge, create a profile dedicated to your software and associate the application with it.
2. Enable the Barcode input and an output: Keystroke for keyboard entry, Intent for an application developed for it.
3. Test again. If the device has just restarted, give DataWedge a few seconds to initialise.

Sources: Frequently Asked Questions (opens in a new window) · DataWedge Profiles (opens in a new window) – Zebra TechDocs – DataWedge (official documentation).

Short answer: If characters are entered incorrectly, the DataWedge documentation advises increasing the inter-character delay of the Keystroke output in steps of 100 ms. According to Zebra, a longer delay can affect the application's performance.

Likely cause

DataWedge's Keystroke output sends the data as keystrokes; a delay between each character can be added for applications that do not accept fast input.

What to do

1. Open the application's DataWedge profile, then Keystroke output.
2. Increase the inter-character delay by 100 ms, test, and repeat if necessary.
3. For a web application or barcodes containing control characters, the Send Characters as Events and Send Control Characters as Events options send these characters as key events.

Source: Keystroke Output (opens in a new window) – Zebra TechDocs – DataWedge (official documentation).

Short answer: According to the MC33XX integrator guide, during a hot swap Wi-Fi and Bluetooth only stay connected for 30 seconds; after that, Wi-Fi is disabled and then re-enabled when the device exits the mode, and Bluetooth is reset. Change the battery quickly and let the mobile computer reconnect.

Likely cause

Section of the integrator guide on backup power and Hot Swap mode: a supercapacitor powers the mobile computer during the replacement; RAM is retained for about five minutes, wireless connections for 30 seconds.

What to do

1. Press the two release buttons, remove the battery and install a charged battery within five minutes to preserve memory.
2. To keep Wi-Fi and Bluetooth without interruption, make the swap in less than 30 seconds.
3. After that, Wi-Fi is re-enabled when the device exits the mode and Bluetooth is reset: wait for it to reconnect before resuming work.
4. Avoid two replacements in quick succession: according to Zebra, the supercapacitor takes about 10 minutes to recharge, and Hot Swap mode only retains data if it is fully charged.

Sources: Backup Power (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Hot Swap Mode (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Replacing the battery (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) (official documentation).

Short answer: The Wi-Fi country determines the channels that can be used. According to Zebra's Wi-Fi Manager documentation, the “AUTO” setting relies on the network's 802.11d country beacon, and countries whose infrastructure does not support it must be selected manually.

Likely cause

The MC33XX supports the 802.11a/b/g/n/ac/d/h/i/k/r/w standards (integrator guide). Not all channels are available in all countries (Wi-Fi Manager).

What to do

1. Check that Wi-Fi is enabled: most Wi-Fi settings can only be changed when Wi-Fi is enabled.
2. Check the Wi-Fi country: in “AUTO”, the mobile computer waits for an 802.11d beacon; if your network does not transmit one, select the country manually.
3. If the fleet is managed, ask the administrator whether a band or a channel mask has been enforced.
4. After a battery change, see loss of Wi-Fi after a battery change.

Sources: Configurations (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Wi-Fi Manager (opens in a new window) – Zebra TechDocs – MX (official documentation).

Short answer: In an MC32N0 cradle, the MC3300 needs the MC33XX charge-only adapter (ADP-MC33-CRDCUP-01), which, according to Zebra, provides charging only, with no communication. To exchange data over USB, use the MC33XX single-slot USB charging cradle, which has a USB port for communication with the computer.

Likely cause

The integrator guide presents the adapter as a backward-compatibility accessory for MC32 cradles: “charge only; no communication”. The MC33XX single-slot USB cradle has a USB port for communication with the host.

What to do

1. To charge only, install the ADP-MC33-CRDCUP-01 adapter in the MC32N0 cradle.
2. To transfer data, place the mobile computer in the MC33XX single-slot USB cradle connected to the computer.
3. For networking, use a 5-slot Ethernet ShareCradle (see Ethernet cradle).

Sources: MC33XX Charge Only Adapter (opens in a new window) · 1-Slot USB Charge Cradle (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: First enable Ethernet in the Quick Access panel, then place the mobile computer in the 5-slot Ethernet ShareCradle: the Ethernet icon should appear in the status bar. The cradle's two green lights indicate the link speed: “1000” for 1 Gbit/s, “100/10” for 100 or 10 Mbit/s.

Likely cause

The integrator guide describes establishing the Ethernet connection, the proxy and static IP address settings (eth0 interface) and the meaning of the cradle lights.

What to do

1. Open the Quick Access panel, tap Ethernet and enable it, then insert the mobile computer into a cradle slot.
2. Tap eth0 to display the connection details.
3. Static IP address: tap eth0, then Disconnect; tap eth0 again, choose Static, enter the IP address (and the gateway, netmask and DNS if required), then CONNECT.
4. Proxy: touch and hold eth0, tap Modify Proxy, choose Manual, enter the host name and port, then MODIFY.
5. If several cradles are daisy-chained, Zebra advises against daisy-chaining when the main connection of the first cradle is at 10 Mbit/s: throughput problems are almost certain.

Sources: Establishing Ethernet Connection (opens in a new window) · Ethernet Settings (opens in a new window) · LED Indicators (opens in a new window) · Daisy-chaining Ethernet Cradles (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: If the light stays off, Zebra cites an incorrectly inserted battery, a cradle or cable that is not powered, or no power source. On the single-slot USB cradle, also remove the lower part of the rubber boot (or the whole boot) before charging.

Likely cause

Light table in the integrator guide: “Off” means that the battery is not charging, that it is not correctly inserted or that the cradle or cable is not powered.

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

What to do

1. Check the power supply to the cradle or USB charging cable; to charge from the mains, the cable must be connected to its power supply unit.
2. Remove the lower part of the rubber boot, or the whole boot, before placing the mobile computer in the single-slot USB cradle.
3. Slide the mobile computer into the cradle slot, or push it into the cable until it reaches the bottom of the holder.
4. Check the battery: pressed in firmly, with both release buttons back in position.
5. Charge between 0 °C and 40 °C. The light turns solid orange, then solid green. Zebra states, from 0 to 90% at room temperature, less than 2.2 h for the 2,740 mAh MC33XX battery and less than 3.8 h for the 5,200 mAh one.
6. A flashing blue light is not related to charging: it indicates that an app notification has been received.

Sources: Charge LED Indicators (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Charging the Battery (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · 1-Slot USB Charge Cradle (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · USB Charge Cable (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Charging/notification lights (table 10) (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) (official documentation).

Short answer: Yes: the MC33XX quick start guide lists the MC32N0 PowerPrecision batteries among the compatible batteries, in 5,200 mAh for the MC33XX-G and in 2,740 or 5,200 mAh for the MC33XX-R and MC33XX-S. They charge more slowly than the MC33XX PowerPrecision+ batteries.

Likely cause

Batteries cited by the quick start guide: MC33XX-G, 5,200 mAh extended batteries MC33XX (PowerPrecision+) and MC32N0 (PowerPrecision); MC33XX-R/S, 2,740 mAh standard and 5,200 mAh extended batteries, MC33XX or MC32N0. The integrator guide gives the charging time for each one.

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

Charging times from 0 to 90% (room temperature, Zebra guide)

1. MC33XX PowerPrecision+ 2,740 mAh: less than 2.2 hours.
2. MC33XX PowerPrecision+ 5,200 mAh: less than 3.8 hours.
3. MC32N0 PowerPrecision 2,740 mAh: less than 3 hours.
4. MC32N0 PowerPrecision 5,200 mAh: less than 5.5 hours.

This is no longer the case on the second-generation MC3300x: its quick start guide states that it is not compatible with the older MC32N0 PowerPrecision batteries.

Sources: Batteries (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Charging the Battery (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Installing the Battery (opens in a new window) – MC3300x Mobile Computer Quick Start Guide (MN-003567-01EN Rev. A) (official documentation).

Short answer: In the single-slot USB cradle, insert the battery bottom first, then pivot the top onto the contact pins, as Zebra instructs. In a 4-slot charger, press gently on the battery to ensure contact: the light then turns solid orange, then green.

Likely cause

The integrator guide gives the same table for the spare slot of the USB cradle and for the 4-slot and 20-slot chargers: off (not charging, battery incorrectly inserted or charger not powered), solid orange (charging), solid green (charging complete), red flashing rapidly (charging error), solid red (end of life).

Caution: The MC33XX integrator guide says to charge batteries between 0 °C and 40 °C and to follow the battery safety guidelines in the MC33XX user guide.

What to do

1. Connect the cradle or charger to its power supply.
2. Single-slot USB cradle: insert the battery bottom first, then fold the top down onto the contact pins.
3. 4-slot charger: insert the battery and press gently on it to ensure contact. On the 20-slot charger, each slot has its own light.
4. Red flashing rapidly: temperature out of range or charging for more than about eight hours; solid red: battery at end of life (see solid red light).

Sources: 1-Slot USB Charge Cradle (opens in a new window) · 4-Slot Spare Battery Charger (opens in a new window) · 20-Slot Spare Battery Charger (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: If an app stops responding, press and hold the power button, tap “Reboot” then “OK” (soft reset). If the mobile computer does not respond at all, press the power button and the 1 and 9 keys simultaneously, then release them when the screen goes off (hard reset).

Likely cause

The MC33XX integrator guide distinguishes four resets: soft reset, hard reset, Enterprise Reset and Factory Reset. The last two erase data; according to Zebra's MX documentation, Enterprise Reset preserves the /enterprise partition, while Factory Reset erases it along with /data and /cache.

Caution: Zebra warns that a hard reset performed with an SD card installed may damage the card or corrupt its data. Enterprise Reset and Factory Reset erase the user's data and apps.

What to do, in order

1. Soft reset (apps that stop responding): press and hold the power button until the menu appears, tap Reboot, then OK. The mobile computer restarts.
2. Hard reset (mobile computer no longer responding): press the power button and the 1 and 9 keys at the same time.
3. Release the keys when the screen goes off: the mobile computer restarts.
4. Enterprise Reset: according to Zebra, it works like a Factory Reset but keeps the /enterprise partition; the mobile computer restarts in Recovery mode.
5. Factory Reset: it erases /data, /cache and /enterprise; removable storage cards are not erased.

The Enterprise Reset and Factory Reset procedures for the MC33XX are in the “Application Deployment” chapter of the integrator guide, which could not be read: only the definitions from the MX documentation are given here.

Sources: Resetting the Device (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Power button menu (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Power Manager (opens in a new window) – Zebra TechDocs – MX (official documentation).

Short answer: Check that the battery is in place and charged: the MC33XX guide says to press it in firmly until both release buttons return to position, then press the power button. An orange light flashing slowly indicates a flat battery that is not yet charged enough to start.

Likely cause

The quick start guide details how to install the battery and how to power on with the power button; the light table indicates a fully discharged battery.

What to do

1. MC33XX-G: loosen the hand strap, align the battery, pivot the bottom into the compartment and press firmly. MC33XX-R/S: same principle, aligning the top of the battery first.
2. Check that both release buttons have returned to their original position, then retighten the hand strap.
3. Press and hold the power button.
4. If nothing happens, put the mobile computer on charge: see orange light flashing slowly.
5. If the mobile computer switches on but stops responding, see reset the MC3300.

Sources: Installing the battery (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Installing the MC33XX-G Battery (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) · Charging/notification lights (table 10) (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) (official documentation).

Short answer: The setup wizard runs at first start-up. According to Zebra, a Google account is only needed on mobile computers with Google services (GMS), and an Internet connection is required to set it up.

Likely cause

The MC33XX integrator guide describes the first start-up Setup Wizard: Google account, Google Wallet for purchases on the Play Store, personal information, backup and restore. The MC33XX is available in an AOSP or GMS version.

What to do

1. First connect the mobile computer to the Internet (Wi-Fi).
2. Follow the wizard: Google account, then personal information and backup options.
3. On an AOSP mobile computer (without Google services), no Google account is required.

Sources: Google Account Setup (opens in a new window) · Configurations (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).

Short answer: According to the DataWedge documentation, the triggers on the MC3300R are assigned by default to barcode scanning and SimulScan: you need to assign a trigger to RFID in Key Programmer, then enable the RFID input (“Enabled”) in the profile. The antenna transmit power sets the range.

Likely cause

The DataWedge 7.3 “RFID Input” page states that RFID input was then only supported on the MC3300R, and that its triggers are reserved by default for barcodes and SimulScan. The MC3330R data sheet gives a nominal range of about 6 m, in the 865–928 MHz band.

What to do

1. Assign a trigger to RFID: Settings > Key Programmer, code SYMBOL_RFID (DataWedge 7.3). Recent versions of DataWedge give the code SYMBOL_TRIGGER_6 for the MC3300R.
2. In the application's DataWedge profile, enable the RFID input (Enabled) and, if required, Hardware trigger with its trigger mode.
3. Increase the antenna transmit power if distant tags are not read: the higher the value, the greater the range (5 to 30 dBm in DataWedge 7.3).
4. With Keystroke output, Zebra requires an inter-character delay of 50 ms.
5. To find a specific tag, the data sheet mentions “Geiger Counter” mode.

The data sheet states that the same RFID SDK is used for the MC3330R, the MC3390R and the RFD2000 and RFD8500 readers.

Sources: RFID Input (DataWedge 7.3) (opens in a new window) – Zebra TechDocs – DataWedge · RFID Input (opens in a new window) – Zebra TechDocs – DataWedge · RFID (opens in a new window) – Product Spec Sheet – MC3330R Integrated UHF RFID Reader (official documentation).

Short answer: The DataWedge “RFID Input” page cites four causes of the RFID reader disconnecting: battery reinsertion, idle timeout, Airplane mode and charging mode. The DataWedge profile must then be re-enabled to restore the connection.

Likely cause

According to Zebra, connections established with RFID readers in the active profile may be lost in these four situations; they are only restored when the profile is re-enabled.

What to do

1. After a battery change, a period of inactivity, leaving Airplane mode or charging, re-enable the relevant DataWedge profile.
2. Check that only one RFID reader is being used: the RFID input only handles one active reader at a time.
3. Try reading again with the trigger assigned to RFID.

Source: RFID Input (opens in a new window) – Zebra TechDocs – DataWedge (official documentation).

Short answer: The head on the MC33XX-R rotates between position detents. Zebra warns: do not try to rotate it beyond these detents, as this could damage the mobile computer.

Likely cause

Warning in the MC33XX quick start guide for the rotating scan configuration.

Caution: “Do not attempt to rotate the device beyond its position detents. This could damage it.” (Zebra quick start guide)

What to do

1. Turn the head to the required detent, without forcing it beyond the position detents.

The MC33XX-R configuration is only available with the SE965 1D laser scanner.

Sources: MC33XX-R features (opens in a new window) – MC33XX mobile computer quick start guide (MN-003143-04FR Rev. A) · Configurations (opens in a new window) – MC33XX Integrator Guide for Android 7.1.2 Nougat (MN-003136-07) (official documentation).