r/accesscontrol • Posted by u/XTIOT_Official

TL;DR

Yes. The XT2010MRZ scans passport MRZ codes and reads 1D/2D barcodes. QR, PDF417, Data Matrix, Aztec – all supported. One scanner for passports, ID cards, boarding passes, and visas.

Why Multi-Format Scanning Matters

Hotels, airports, and banks don't just scan passports. They also need to read:

• Boarding pass QR codes
• Visa PDF417 barcodes
• ID card Data Matrix
• Membership QR codes
• Driver's license PDF417

Separate scanners = cluttered counters, more training, higher costs.

XT2010MRZ does it all in one device.

What Barcodes It Reads

Category	Formats
1D	Code 128, EAN-13, UPC-A/E, Code 39, Codabar,

We recently received a technical question from a customer testing the XTIOT XT6202HD-2 for a retail POS project.

They didn't ask about scan speed or battery life.

Instead, they asked one simple question:

If two USB receivers are connected, will one scan be sent to both receivers at the same time, or do users need to switch between them?

This may sound like a small detail, but for OEM projects, it is very important.

Many products say they support dual receivers, but that doesn't always mean the same thing.

Some products can only send data to one receiver at a time.

Others can send the same barcode to two devices at the same time.

For the XT6202HD-2:

• **The scanner se

One request from an OEM customer recently caught our attention while integrating the XTIOT XT206H3.

The scanner was configured to use USB Virtual COM (V-COM) as its default communication interface.

Then the customer asked an interesting question:

"If an operator performs a factory reset by scanning the reset barcode, will the scanner still remain in USB V-COM mode?"

At first glance, it sounds like a small firmware detail.

But for OEM manufacturers, it can have a significant impact.

Many embedded systems communicate with the scanner through a predefined interface. If a factory reset changes the communication mode back to another default, the host software may no longer d

One feature request keeps coming up in our OEM projects for the XTIOT XT3001AER Bluetooth ring scanner.

It's not about scan speed or decoding performance.

Instead, customers ask:

"Can the scanner switch between Bluetooth HID and Bluetooth SPP?"

At first, it sounds like a small firmware feature.

But in real applications, it can make a big difference.

Some customers use Bluetooth HID because they want the scanner to behave like a standard keyboard. It works well with existing software and usually requires little or no additional development.

Others choose Bluetooth SPP because their application needs structured data, custom commands, acknowledgements, or tighter communic

A software log may show that a UART trigger command was sent, but the barcode scanner still does not start reading. This does not always mean that the command is wrong.

The host TX must connect to the scanner RX. A connection using only the scanner TX is enough for receiving barcode data, but it cannot send commands from the host to the scanner.

The scanner and host also need a common ground. Without it, UART communication may fail even when the TX and RX wires are connected correctly.

The default baud rate of XTIOT barcode scanner modules is 9600. Other baud rates can be set, but the scanner and host must use the same value. If the scanner setting has been changed while the host stil

We recently supported two access control manufacturers integrating the XTIOT XT206M1 into their devices.

The barcode scanner performed as expected during standalone testing.

But once integrated into the customer's hardware, an unexpected issue appeared.

The entire system would occasionally freeze and could only recover after a reboot.

At first, the scanner became the primary suspect.

However, after comparing test results across different platforms, we found that the same scanner operated normally on other host systems.

This reminded us of an important lesson in embedded integration:

A stable barcode scanner does not automatically guarantee a stable system.

Power suppl

We recently supported an access control project using the XTIOT XT206M1.

After deployment, the customer reported that the entire device would occasionally freeze and required a reboot.

The first conclusion was simple: "The scanner must be causing it."

So we started troubleshooting.

We tested the same scanner on different host platforms.

We compared communication logs.

We checked power, interfaces, and firmware behavior.

Interestingly, the issue could not be reproduced on other systems using the same scanner.

That's something we've seen more than once in embedded projects.

When a complete system stops responding, **the last peripheral that communicated with the host is of

We ran into a POS integration issue where the scanner read a 2D barcode correctly, but the software could not find the product.

The problem was not the scanner. The software treated the complete decoded string as one SKU.

A GS1 2D barcode may contain several data fields in one symbol. Application Identifiers tell the software what each field means—for example:

• 01: GTIN
• 10: batch or lot number
• 17: expiration date
• 21: serial number

The scanner’s job is to decode the symbol and transmit the data. The POS host still needs to identify the barcode format, separate the fields and use the GTIN for product lookup. GS1’s retail guidance also assigns interpretation and trans

Over the past year, we've noticed an interesting trend.

More and more OEM customers are asking for 1280 x 800 barcode scanner modules before discussing almost anything else.

At first, we thought they simply wanted a higher-resolution sensor.

But after working on different projects, we realized something else.

The requirement usually isn't about image quality. It's about application flexibility.

The same scanner may need to read:

• Printed labels
• Mobile phone screens
• Small QR codes
• Low-contrast barcodes
• Different working distances

Instead of designing a different scanner for every application, many equipment manufacturers prefer **one module that can handle a wider rang

We recently supported a smart locker manufacturer evaluating the XTIOT XT728M for one of their projects.

The customer wasn't asking for the lowest-cost scanner.

Their biggest concern was what happens when the first scan fails.

Unlike a staffed counter, a smart locker has no operator to help the user.

If the barcode isn't read immediately, people often move their phone away, change the angle, or try again.

Every failed first attempt creates hesitation and slows down the pickup process.

In self-service applications, decoding speed is important—but first-pass read performance is even more important.

A scanner that reads correctly on the first attempt can significantly imp

We recently completed a passport scanning project in Europe using the XTIOT XT6201MRZ handheld scanner.

At first, the customer focused on MRZ reading speed.

But during field testing, a different challenge appeared.

Not every passport presents the same scanning conditions.

Some passports were brand new with glossy pages.

Others had worn surfaces, protective covers, or slight wrinkles after years of use.

The MRZ was still there—but the optical conditions were very different.

In real-world applications, operators don't have time to adjust the document angle for every passenger.

They simply expect the scanner to capture the MRZ quickly and continue with the next person.

We recently supported an EMS manufacturer integrating the XTIOT XT206M embedded barcode scanner into one of their OEM projects.

The barcode wasn't difficult to read.

The real challenge was that the scanner had to fit into a product we would never see.

Unlike equipment manufacturers building their own machines, EMS companies build products for many different customers.

Every project has different mechanical layouts, cable routing, mounting positions, and available space.

A scanner that works perfectly in one device may require a completely different installation in the next.

That's why, in OEM projects, **mechanical integration is often more important than decoding perfo

We recently worked with an overseas manufacturing plant that wanted to reduce cycle time at manual workstations.

At first, everyone focused on scanner speed.

But after reviewing the workflow, we found a different bottleneck.

The operator wasn't waiting for the scanner. The operator was constantly reaching for it.

That repeated motion—pick up, scan, put down—happened hundreds of times every shift.

Instead of looking for a "faster" scanner, the customer chose the XTIOT XT3001EBR Ring Scanner.

Because the scanner stays on the operator's finger, both hands remain available for assembly while scanning becomes part of the natural workflow.

Sometimes, improving productivity i

We recently worked with a global tire manufacturer on an automated tire identification project.

The customer needed to read the code on every tire as it moved through production.

At the beginning of the project, everyone focused on the barcode itself.

Could the scanner decode the code reliably on a curved rubber surface?

After reviewing the application, we discovered that decoding wasn't actually the biggest challenge.

One camera simply couldn't see enough.

The tire was too large, and the required installation distance was fixed by the production equipment.

A single camera could only capture part of the inspection area.

Even though the code was readable, **it wasn't alway

We recently worked with a customer who needed to scan 6 mm barcodes for their production process.

At first, everyone focused on the barcode size.

Could the scanner reliably decode such a small code?

After testing, both the XTIOT XT6201C wired scanner and the XT6202GHD wireless scanner performed well with the customer's samples.

But the customer had another requirement.

The scanned data had to be entered into a system using the Turkish keyboard layout.

At first glance, barcode scanners simply output text.

In reality, keyboard language and character mapping can become an integration challenge.

If the scanner's output doesn't match the operating system's keyboard