Tracing and identification of a factory warehouse developed by Honeywell d6110

Recently, we have developed a two-dimensional scanning PDA project using Honeywell d6110, which is easy to use.

It is the product material code, corresponding to the intermediate code, and then the intermediate code generates various product codes according to the needs of different OEM brands and carries the serial number.

The repository is required to scan the bar code, record the flow, and generate a Summary of the quantity of materials for CRM.

First, advertise for yourself and paste some images.

When the advertisement is complete, the people who pay attention to me will surely return.

Honeywell d6xxxx series machines are usually Windows Mobile 6.5 systems. It is easy for other developers to follow.

I want to talk about the SDK provided by Honeywell.

1. Comment: in principle, for a large first-line brand, the SDK should look comfortable and organized in the new cloud flow (here I like Moto again), but I found many flaws in the Honeywell documentation.

I will not talk about the specific flaws. If the overall percentage is set, give 80 points (Moto can give 95 points ).

2. Programmers face the same pitfalls as me:

Like everyone else, get the development prototype, log on to the official website, download the SDK, and the latest version r812 on the Internet. According to the SDK, wm6.5.3 dtk is also required (flaws, in fact, 6.1 is enough, not 6.5.3)

After the installation is complete, you are most concerned about, of course, the decode scan bar code section. This is unique.

3. According to the inertial thinking, everyone will carefully read the SDK documentation. In this document, the decoding wizard is to use decodecomponet, which looks pretty good. There is a demo in samples.

As a result, I fell into two major pitfalls. This is two flaws.

A. Follow the steps to add the decodecomponet control. You cannot find the path. At least I am not at all in vs2008 + sdk812.

Correct Path: C: \ Program Files \ Honeywell \ SDK for Windows Embedded handheld \ assemblies_cf3 \ HSM. Embedded. decoding. decodecomponent. dll

B. I spent a lot of effort and finally found the damn control. The toolbox is finally displayed. So it's not natural to run that demo.

I went and fell into the trap again. In addition, it is too deep.

When you open the decodecomponent demo, it is displayed that the interface control is incorrect, the property is incorrect, my God, and their own items are all incorrect !!!!

I am studying, and studying. Finally, dx, Let's guess how to solve this problem ?????

Install sdk7 and change the control to sdk7. Open the sdk8 demo !!!!

The upgrade is understandable. Please, we have a strict attitude towards a large company. Upgrade the demo and do not mislead programmers.

4. In the end, I gave up decodecomponet. I found that although simple functions are powerful. But it was not flexible enough. I switched to decodeassembly, and it was a great deal.

In the end, I don't quite understand a small problem. Now that there is a linearcode type, why should we classify the EAN/UPC barcode into retailcode independently ??? Not understanding ......

Tracing and identification of a factory warehouse developed by Honeywell d6110