ATIS 0300107-2012 Processing Data in ANSI MH10 8 3 Formatted High Capacity AIDC Media.pdf

《ATIS 0300107-2012 Processing Data in ANSI MH10 8 3 Formatted High Capacity AIDC Media.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300107-2012 Processing Data in ANSI MH10 8 3 Formatted High Capacity AIDC Media.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0300107 ATIS Standard on - PROCESSING DATA IN ANSI MH10.8.3 FORMATTED HIGH CAPACITY AIDC MEDIA As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees a

2、nd forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from design and innovati

3、on through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership

4、 Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit. Notice of Disclaimer . 6.2

5、.4 Recommendations to reader suppliers This guideline recommends that reader suppliers clearly provide technical information in their manuals and/or on their web sites in support of the proposed solution in this guideline. 6.3 Other Connection Methods The next subsections outline two methods of sett

6、ing-up/programming a reader to process the data from high capacity AIDC media conforming to MH10.8.3 formatting which allows applications to handle the special characters. ATIS-0300107 9 6.3.1 USB port & keyboard emulation The reader is plugged directly into a USB port on the computer. In this confi

7、guration, the imager emulates a keyboard. Data from the reader is passed to an application in the same manner as data from a keyboard. The non-printable characters are not passed or substituted in different ways depending on language settings of the PC operating system and application. In this mode,

8、 a driver is needed for the reader. Applications designed for keyboard entry do not need any reprogramming or middleware to accept data from the reader. 6.3.2 Native/POS mode Native mode (also referred to as Point of Service/Sales mode“ POS mode or “Human Interface Device mode” HID mode) can be used

9、 in combination e.g. with a USB or Bluetooth connection. In this configuration, the reader passes the data directly to the computer, without emulating a keyboard and without any processing. All non-printable characters are passed unmodified, there is no driver needed and there are no dependencies fr

10、om language settings of the application or operating system. However data from the reader in native mode is not visible in the applications of the computer without some programming of the application or middleware. This mode is not supported by all readers. Suppliers for the PC operating system or t

11、he reader provide Application Programming Interfaces (APIs) which can provide functionality for this native mode/POS mode. 7 Bibliography References included here are informative to aid the user but are essential for implementing the recommendations in this guideline. ISO/IEC 15434, Information tech

12、nology Automatic identification and data capture techniques Syntax for high-capacity ADC media ATIS-0300107 10 Appendix A Keyboard Buffer and Interfaces The KEYBOARD BUFFER is used on personal desktop computers, workstations and laptop computers. The keyboard buffer is a memory bank or reserved area

13、 that holds information typed on the keyboard before the central processing unit is ready to accept it. Characters may be passed through this buffer by a reader sending data through a USB port, serial port or a reader connected through the keyboard connection itself on a PC. AIDC readers, depending

14、on manufacturing and model, may pass control characters used in high capacity AIDC media differently. Also, keyboards for different countries may pass these control characters differently. There are some options for processing the characters in the keyboard buffer. Either commercially available soft

15、ware can be used or low level programming can be developed. The details of using a keyboard buffer is beyond the scope of this guideline and this approach is not recommended, as the “Recommended Methods” in section 6 eliminate the need for this level of knowledge and development expertise. Below is

16、a brief description of the interfaces and discusses some of the requirements if the application developer prefers not to use one of the “Recommended Methods” in section 6. WEDGE The wedge interface uses an adaptor, which allows both the keyboard and reader to be connected to a single PS2 port on a c

17、omputer. Having both the keyboard and reader tied to the PS2 port allows data to be fed directly into an application from either device as if it were being typed on a keyboard. USB port The reader is plugged directly into a USB port on the computer. In this configuration, the imager emulates a USB k

18、eyboard. Data from the reader is passed to an application in the same manner as data from a keyboard. Having the reader tied to the USB port allows data to be entered either by keyboard or reader into an application. The USB port may be programmed to emulate a keyboard by sending the input from the

19、USB port to the keyboard buffer. The output from the USB device must be captured and processed at communication port and before it reaches the keyboard buffer in order to avoid sending control characters which an application cannot process correctly. The RS, GS and EOT characters from an ANS MH10.8.

20、3 formatted data stream from an AIDC reader can disrupt an application if not handled correctly. If it is desired to use the USB port without using one of the Recommended Methods in section 6, the developer will need to do have a thorough understanding of how the USB port sends data to the computer,

21、 as well as a need to understand how each AIDC reader sends the data through the USB. The details of developing this process are beyond the scope of this guideline. RS232 The RS232 interface requires the application read the serial port to capture data from the reader. This type of configuration doe

22、s not allow data to be directly entered into an Excel or Word type application. The benefit of RS232 is that it supports the full ASCII character set and is not limited to only those characters available through a keyboard interface. Processing of control characters from a reader is dependent on how

23、 the manufacturer of the reader has implemented those characters in a particular reader model. This implementation may also vary between models from the same manufacturers. If it is desired to use the RS232 serial port for processing reader output and not use one of the Recommended Methods in sectio

24、n 6, contact the manufacturer for an application development kit for the reader(s) needed for the application. BLUETOOTH The Bluetooth interface uses a Bluetooth adapter, which allows “wireless” connection. This type of configuration allows data to be directly entered into an application. An understanding of how the reader passes data with the control characters to the Bluetooth device is necessary.