"ATOL: Driver for data collection terminals" - a software component (driver) designed to work with various models data collection terminals.

Purpose

The data collection terminal is a portable device used mainly for automating trading processes.

• Taking inventory
• Reception and issue of goods in warehouses or in trading floors.
• Order picking, etc.

The terminal can operate autonomously from rechargeable batteries, so you can take it with you to any remote facility (warehouse, trading floor, etc.) to collect data such as barcode quantity, etc.

Depending on the model, the data collection terminal may have: built-in or external barcode scanner internal memory alphanumeric keypad LCD display. Simplicity and reliability in operation, small dimensions and weight make the data collection terminal an invaluable assistant to storekeepers, merchandisers, store managers and other employees involved in accounting and collecting information.

The cycle of work with the data collection terminal:

1. Clear terminal memory
2. Enter product information. To do this, scan the barcode or enter it manually. Additionally, for example, information about the quantity of goods can be entered. Repeat the entry of product data as many times as necessary (until all information is collected).
3. Connect terminal to computer.
4. With the help of the data collection terminal driver, upload the data to the inventory or cash register software.
5. Process data: check stock balances (inventory), fill in the tabular part of the document with selected goods (goods issue), etc.

With the help of a driver, your program can: receive the necessary information from the data collection terminal; configure device parameters; set the format and rules for input data!

Opportunities

Visual Adjustment

"ATOL: Data Collection Terminal Driver" has a visual property page that makes it easier to work with each of the connected devices. Using the properties page, you can easily configure the necessary parameters for working with the data collection terminal (connection port, data transfer rate, etc.) and visually check the work with devices - the client application does not need to program these parameters or create its own user interface to set them up.

The driver provides automatic saving and restoration of settings for working with connected devices.

Finding Connected Equipment

The driver has the ability to search for connected equipment. A convenient and simple dialog has been implemented for searching. With it, you can quickly determine the parameters of data collection terminals connected to a PC.

Connecting multiple terminals to different ports of the same PC

The driver can work with several terminals from one workstation, for which the "logical devices" mechanism is implemented. A logical device is a set of connection parameters with a specific data collection terminal.

Visually, on the driver properties page (or programmatically - using methods and properties), you can create and configure the required number of logical devices and connect to the selected terminal using predefined connection parameters.

Configuring system settings

Through the methods and properties of the driver, you can configure the system parameters of the terminal (date and time, sound, screen backlight, etc.), get information about the type of the connected terminal, the amount of used and free memory, and much more.

Readable barcode settings

The driver allows you to flexibly set the settings for readable barcodes, set the prefix and suffix of the barcode. Immediately on the visual form of the driver, you can check the correctness of the configured parameters by simply clicking on the "Scan" button.

Setting the terminal data format

Using the driver, you can set different logic for the behavior of the terminal when entering data, as well as determine the structure of the input data. For example, you can configure the terminal in such a way that after reading the barcode, the device will display an invitation to enter the quantity (moreover, during the input of the quantity, the device itself will control that it does not go beyond the set range of values).

Such a terminal setting makes the user's work more understandable and convenient and can eliminate a large number of errors.

Working with a terminal connected to a remote PC via a network

The driver supports Microsoft DCOM technology that provides interaction between software components located on different machines on the network. You can configure the driver in such a way that your program will interact with a terminal connected to another computer on the network. In this case, the user will not feel any difference between working with this terminal and a terminal connected locally.

Supported Hardware

Currently, the driver supports the following models of data collection terminals:

• Mobile Logistics v.4»:
• All terminals with a pre-installed system Mobile Logistics Lite»:
• Zebex PDX
• Zebex Z-1050
• Zebex Z-2030
• CipherLab CPT-7XX
• CipherLab CPT-8XXX
… (Keep for updates)

OS Compatibility

Windows 98/ME/NT/2000/XP/2003/Vista/7

Software Compatibility

All Windows development tools supporting OLE Automation technology:

• Delphi · C++ Builder
• Microsoft Visual C++
• Microsoft Visual Basic
• Microsoft Visual Fox Pro
• Applications Microsoft Office with VBA ( Excel Word Access, etc.)
• Navision Axapta
• 1C: Enterprise version 7.5 7.7 8.0 8.1
• and etc.

1C compatible

"ATOL: Data collection terminal driver" is an external component and has been tested for compatibility with the "1C: Enterprise" software system versions 7.7 8.0 8.1 and works with them as:

• ActiveX
• external component.

The presence of the sign "1C-compatible" indicates that this software tested for compatibility with the 1C program system by the specialists of the 1C company. The sign also testifies to the award to the developer - the company "ATOL Technologies" - the status of 1C: Franchisee.

Distribution terms

"ATOL: Data collection terminal driver" is commercial product and copy protected electronic key protection.
Without a security key, the driver will work in demo mode, in which you can write to the TSD and read from it no more than 10 records.

"ATOL: Driver for data collection terminals" is free when working with terminal models using systems:

• "Mobile Logistics"
• ATOL: Moble Logistics Lite

Attention! To use the driver in terminal session multiplayer version required. However, ATOL Group does not guarantee the correct operation of the driver in the terminal session and reserves the right, at its discretion, to refuse consultations in the event of such an organization of the driver.

Static text for products. For example: basic information about the methods and terms of delivery. Shown for all products.
You can change it in the product.tpl file

"ATOL: Driver for data collection terminals" - a software component (driver) designed to work with data collection terminals.

Purpose

"ATOL: Data collection terminal driver" is a software component (driver) designed to work with various models of data collection terminals.

[diagram of device interaction with PC]

The data collection terminal is a portable device used mainly for automating trading processes.

• Taking inventory
• Reception and issue of goods in warehouses or in trading floors.
• Order picking, etc.

The terminal can operate autonomously from rechargeable batteries, so you can take it with you to any remote facility (warehouse, trading floor, etc.) to collect data such as barcode quantity, etc.

Depending on the model, the data collection terminal may have: built-in or external barcode scanner internal memory alphanumeric keypad LCD display. Simplicity and reliability in operation, small dimensions and weight make the data collection terminal an invaluable assistant to storekeepers, merchandisers, store managers and other employees involved in accounting and collecting information.

The cycle of work with the data collection terminal:

1. Clear terminal memory
2. Enter product information. To do this, scan the barcode or enter it manually. Additionally, for example, information about the quantity of goods can be entered. Repeat the entry of product data as many times as necessary (until all information is collected).
3. Connect terminal to computer.
4. With the help of the data collection terminal driver, upload the data to the inventory or cash register software.
5. Process data: check stock balances (inventory), fill in the tabular part of the document with selected goods (goods issue), etc.

With the help of a driver, your program can: receive the necessary information from the data collection terminal; configure device parameters; set the format and rules for input data!

Opportunities

Working with a terminal connected to a remote PC via a network

The driver supports Microsoft DCOM technology that provides interaction between software components located on different machines on the network. You can configure the driver in such a way that your program will interact with a terminal connected to another computer on the network. In this case, the user will not feel any difference between working with this terminal and a terminal connected locally.

Supported Hardware

Currently, the driver supports the following models of data collection terminals:

• Mobile Logistics v.4»:
• All terminals with a pre-installed system Mobile Logistics Lite»:
• Zebex PDX
• Zebex Z-1050
• Zebex Z-2030
• CipherLab CPT-7XX
• CipherLab CPT-8XXX… (Stay tuned)

OS Compatibility

Windows 98/ME/NT/2000/XP/2003/Vista/7

Software Compatibility

All Windows development tools supporting OLE Automation technology:

• Delphi · C++ Builder
• Microsoft Visual C++
• Microsoft Visual Basic
• Microsoft Visual Fox Pro
• Microsoft Office applications with VBA (Excel Word Access, etc.)
• Navision Axapta
• 1C: Enterprise version 7.5 7.7 8.0 8.1
• and etc.

1C compatible

"ATOL: Data collection terminal driver" is an external component and has been tested for compatibility with the "1C: Enterprise" software system versions 7.7 8.0 8.1 and works with them as:

• ActiveX
• external component.

The presence of the “1C-compatible” sign indicates that this software product has been tested for compatibility with the 1C program system by the specialists of the 1C company. The sign also testifies to the award to the developer - the company "ATOL Technologies" - the status of 1C: Franchisee.

Distribution terms

"ATOL: Driver for data collection terminals" is a commercial product and is protected from copying by an electronic security key.
Without a security key, the driver will work in demo mode, in which you can write to the TSD and read from it no more than 10 records.

"ATOL: Driver for data collection terminals" is free when working with terminal models using systems:

• "Mobile Logistics"
• "ATOL: MobleLogistics Lite"

Attention! To use the driver in a terminal session, a multi-user version is required. However, ATOL Group does not guarantee the correct operation of the driver in the terminal session and reserves the right, at its discretion, to refuse consultations in the event of such an organization of the driver.

Delivery options

ATOL: Data collection terminal driver v.8.x 1 workplace Price: 3500r.

ATOL: Driver for data collection terminals v.8.x 5 jobs Price: 15000r.

ATOL: Driver for data collection terminals v.8.x 10 workstations Price: 23000r.

Static text for products. For example: basic information about the methods and terms of delivery. Shown for all products.
You can change it in the product.tpl file

The driver from Cleverence is a complete set of ready-made, integrated software, which allows you to use TSD with an operating Windows system or Android for inventory, acceptance and shipment of barcoded goods. Package includes: installer special program on TSD, integration components for 1C, TSD program editor, as well as full documentation and a set of additional processing for standard 1C configurations that implement additional advanced driver functionality.

The driver from Cleverens not only allows you to connect the TSD to 1C:Enterprise, it turns it into an effective business automation tool. 4 years of operation and more than 5,000 driver installations have allowed Cleverens specialists to find a solution to most of the issues and small details that arise in the process of implementing bar coding. Experience real use, assembled by the labor of thousands of companies, is now in your store, in your warehouse, in your production.

More about features

Collection of barcodes in the store

The simplest operation is barcode scanning with quantity input. The result can be uploaded to any accounting system document that contains goods and quantities.

If barcodes have not yet been entered in the system, then it is possible to link barcodes to known goods right during scanning. If a product card has not yet been entered, it is still possible to scan a barcode and link it to a new entered card later.

Product information by barcode in the store

Obtaining information about the name, unit of measurement, price and availability of goods, taking into account the characteristics.

The MINIMUM and BASIC licenses display data from the last upload.

Printing to a mobile printer

In the standard delivery of any driver, several methods of carrying out mobile re-evaluation are available, including printing on mobile printers. Mobile printing requires a special additional license for MS-1C-PRINT.

Re-evaluation using a mobile printer is very easy. We scan the goods, if the price on the trading floor is outdated, then we immediately print a new label using a mobile printer with Bluetooth and glue it.

Work completely online

Support online communication with accounting system via Wi-Fi. Allows you to receive up-to-date information about the range, current balances and prices; print documents or price tags. And even create new documents directly from the terminal.

Online work is supported only in PROF

Working with characteristics

Whenever a product is scanned, its characteristics are taken into account. It could be color, size, or something else. Working with characteristics allows you to avoid regrading.

A product may have several characteristics. If products with different characteristics have the same barcode, then mobile device prompts you to select the desired feature from the list.

The driver from Cleverence is a complete set of ready-made, integrated software that allows you to use the TSD with the Windows operating system for inventory, acceptance and shipment of barcoded goods. The package includes: an installer of a special program for TSD, integration components for 1C, an editor for TSD programs, as well as complete documentation and a set of additional processing for standard 1C configurations that implement additional advanced driver functionality.

The driver from Cleverens not only allows you to connect the TSD to 1C:Enterprise, it turns it into an effective business automation tool. 4 years of operation and more than 5,000 driver installations have allowed Cleverens specialists to find a solution to most of the issues and small details that arise in the process of implementing bar coding. The experience of real use, collected by the labor of thousands of companies, is now in your store, in your warehouse, in your production.

The driver package includes:

• Software for data collection terminal (free client Mobile SMARTS);
• An external component for 1C that implements the driver standard commercial equipment;
• Shop equipment driver processing + additional processing for extended driver functions;
• Data collection terminal software configurator (free Mobile SMARTS control panel).

Product details:

Driver Features:

Send your good work in the knowledge base is simple. Use the form below

Students, graduate students, young scientists who use the knowledge base in their studies and work will be very grateful to you.

Hosted at http://www.allbest.ru/

Ministry of Education of the Russian Federation state

educational institution

higher professional education

Kazan National Research Institute

them. A.N. Tupolev-KAI

Yelabuga branch

COURSE WORK

BY DISCIPLINE

Microprocessor systems

"Data terminal driver"

Done: student

Borisova T.I. 22575

Checked by: Konyukhov M.I.

Yelabuga 2011

Abbreviations

TSD Data collection terminal.

PC Personal computer.

OS Operating system.

Software Software.

VK External component for the 1C: ENTERPRISE program system v. 7.7.

LU Logical device.

SC Barcode.

About data collection terminals

Data collection terminal (hereinafter referred to as the terminal, TSD) is a portable device designed to automate the inventory, receipt and release of goods in warehouses or trading floors. Having a barcode scanner (built-in or external), alphanumeric keyboard, LCD display, autonomous power supply (accumulators or replaceable batteries), the ability to transfer data to a PC, small dimensions and weight, being simple and reliable in operation, the terminal becomes an invaluable assistant for storekeepers , merchandisers, managers of trading floors and other employees involved in accounting and collecting information.

The cycle of operation of the TSD usually looks like:

Clear TSD memory.

Enter product information.

Make the necessary corrections of the data in the accounting system.

Terminal diagram for HDD

Portable data collection terminals

Supported terminal models

This software supports the following RTD models:

ZEBEX: PDx-10 and PDx-20 series.

OPTICON: PHL, OPL series and model DWT7133. OPTICON terminals must be controlled by the Task-M application developed by Shtrikh-M specifically for these terminals.

Terminals ZEBEX series PDx

ZEBEX terminal software

In EPROM memory TSD ZEBEX PDx series has an operating system called ROM Operation System (ROS). Its main functions are the launch of the TSD, memory management, input-output, task execution.

The ZEBEX RTD package includes a CD with the WinTaskGen program. This program allows you to create tasks and forms for collecting data and upload them to the TSD. WinTaskGen uses its own macro language to write tasks. WinTaskGen help file and WinTaskGen interface in English.

Users of the Data Collection Terminal Driver version A3.0 have the ability to create and upload forms for the Zebex TSD using the built-in form editor. For working with the form editor, see the chapter "Using the form editor".

Connection of ZEBEX terminals

To work with the driver, set the terminal to the following state:

Install the RTD on a communication cradle connected to the PC COM port with a cable, or (if the PDx-10 model without a cradle is used) connect the RTD to the PC COM port with a cable.

Set the exchange parameters (baud rate, parity, number of stop bits, data bit size) on the TSD to the ones you intend to use on the PC.

If the display is blank, turn on the terminal by pressing the button. Ready to operate message will appear on the display. For example, for PDL-20:

PDL-20VER. 1.01

If the terminal is already on, then you need to press the button until the same message appears on the display. OPTICON terminals

This documentation describes the operation of the TSD under the control of the TASK-M application version 3.0.

OPTICON terminal software

General information

Working with TSD Opticon is controlled by an application that can be downloaded from a PC via a special stand or directly via cable. The application is loaded with the help of special software, which is included in the delivery package of the driver. TSD also has its own operating system, which can be loaded into TSD using the same software.

Operating system files have the extension .hex (for OPL-s32)

Application files for TSD have the extension .s2 (for OPL-s32).

The data in the TSD are placed in the form of regular files. Text files in DOS format.

This documentation describes the operation of the TSD under the control of the TASK-M application (“Task Manager”) version 3.0. The original file name of this application for each RTD model:

T3P172.s2 - application for TSD PHL 1700-20.

T3P171.s2 - application for TSD PHL 1700-10.

T3P278.s2 - application for TSD PHL 2700.

T3P138.s2 - application for TSD PHL 1300.

T3DWT.s2 - application for TSD DWT 7133.

T3OPL3.s32 - application for TSD OPL 9723.

T3OPL5.s32 - application for TSD OPL 9725.

T3OP81.s32 - application for TSD OPL 9728-1 MB.

T3OPL8.s32 - application for TSD OPL 9728-512 kB.

T3RFDC.s2 - application for PHL2700RFDC TSD.

Attention! Each TSD model corresponds only to its application and OS.

Usually, the TSD comes with the software already installed in it, but sometimes it becomes necessary to update the built-in application or OS. To do this, below is a description of the sequence of actions for loading software into the TSD using the downloader.

Downloading software to the OPTICON terminal

The delivery of the driver includes a program for downloading software to TSD OPTICON. Install the downloader on your PC before starting the download. Everything you need for this after installing the driver on your PC can be found along the path% Installation path (by default "C:\ProgramFiles\Bar-M\TSD 3.0\")%\Application\Opticon\Apploaders\SETUP. After installation, run the downloader (Appload.exe), which is included with the driver.

Before downloading the software to the TSD, connect the TSD or communication cradle to the PC COM port.

In the window that appears, select the SETTINGS main menu item.

Set up PC sharing settings.

Note. The exchange rate on the communication stand is set in its lower part using the switches. See the communication cradle instructions for how to set the baud rate.

When downloading applications through the cradle, you should pay attention to the fact that it is important to correctly set the baud rate with the PC port on the cradle.

For the IRU 1600 stand, set switches 1-8 to the default position (corresponding to 38400 baud): on, off, off, off, off, off, off, off.

For the IRU 1000 stand, switches 1-6 (auto-sensing speed): on, off, off, on, on, on.

For IRU 2700 cradle switches 1-6 (19200 baud rate): on, off, off, off, off, on.

1. For TSD series PHL:

When downloading via cable or via the IRU1000 cradle: While holding down the [S] and buttons, press the PW button with the RTD turned off.

When loading through the IRU2700 cradle: While holding down the [S] and buttons, with the PHL2700 turned off, press the PW button. OS download to PHL 1700 terminals can only be done via cable.

The red light on the terminal will light up. At this time, the old operating system and all files will be deleted in the terminal.

On DWT7133: press all buttons at once and place the RTD on the stand.

On OPL972x: Place the RTD on the stand.

2. In the APPLOAD.EXE program, in the FILES menu, select the DOWNLOADS item.

A file selection dialog will appear.

3.Select the Operation system mask in the dialog and find desired file operating system.

4. After selecting the desired file, click OK.

After the download is completed, the application will be launched on the terminal or, if it is not there, the message: “Not Application”.

1.On TSD series PHL: While holding the and buttons ( and [.] for PHL1300) on the OFF terminal, press the PW button.

On DWT7133 and OPL9723: press all buttons at once and place the RTD on the stand.

On OPL9725: place the RTD on the stand.

The OC system menu appears on the terminal.

2.Select the Download Application item.

3.Select the communication method: By cable (cable), via a stand (cradle) or via IrDA.

In PHL1300 and OPL9725, the communication method is not selectable.

4. In the APPLOAD.EXE program, select the Download item in the FILES menu.

A file selection dialog will appear.

3.Select the Application mask in the dialog and find the required application file.

5. Having selected the required file, press OK.

After the download is completed, the application on the TSD will be launched immediately.

Connecting OPTICON terminals

Before you start, set the exchange parameters at the terminal.

To do this, from the main menu, go to the “Settings” item, then to the “COM-PORT” item, then to the “Method” item and select the method by which data will be exchanged with the PC.

If you are using a communication cradle, then set the baud rate on it to be equal to the baud rate set in the TSD.

Then return to the main menu again. Select item 3 of the main menu "Exchange with PC". The display will show:

TSD in mode

Exchange with PC

Method: xxxxx

Speed: xxxbaud

In this position, the OPTICON RTD is ready to work with this driver.

PDA CONNECTION

The terminal is connected to a PC using a communication stand that combines the functions charger and an interface cable connecting the terminal to the PC.

CRD-20 DB-9 connector and plug

There are two ways to communicate with a PC:

* Data exchange with a PC via the RS-232 interface via a COM port using a communication stand.

* Infrared data exchange through the built-in IrDA communication port of the cradle or PC.

RS-232C interface

The RS-232C interface is designed to connect equipment that transmits or receives data (00D - data terminal equipment, or ADF - data transmission equipment; DTE - Data Terminal Equipment), to the terminal equipment of data channels (DCE; DCE - Data Communication Equipment). An ADF can be a computer, printer, plotter, etc. periphery equipment. The modem usually acts as the DCE. The ultimate purpose of a connection is to connect two ADFs. The complete connection diagram is shown in fig. 2.1; The interface allows you to eliminate the remote communication channel along with a pair of DCE devices by connecting the devices directly using a null modem cable (Fig. 2.2).

Rice. 2.2. RS-232C connection with null modem cable

The standard describes interface control signals, data transfer, electrical interface and connector types. The standard provides asynchronous and synchronous exchange modes, but COM ports support only asynchronous mode.

The RS-232C standard describes single-ended transmitters and receivers - the signal is transmitted relative to a common wire - circuit ground (balanced differential signals are used in other interfaces - for example, RS-422). The interface does not provide galvanic isolation of devices. The logical unit corresponds to the voltage at the input of the receiver in the range from -12 to -3 V. For control signal lines, this state is called ON ("on"), for serial data lines - MARK. Logic zero corresponds to a range from +3 to +12 V. For control signal lines, the state is called OFF (“off”), and for serial data lines - SPACE. The range from -3 to +3 V is the dead zone, which determines the hysteresis of the receiver: the line state will be considered changed only after crossing the threshold (Fig. 2.3). The signal levels at the outputs of the transmitters must be in the ranges from -12 to -5 V and from +5 to +12 V to represent a one and a zero, respectively. The potential difference between the circuit grounds (SG) of the connected devices must be less than 2 V, with a higher potential difference, incorrect perception of signals is possible. The interface assumes the presence of a protective earth for the connected devices if they are both powered by the mains alternating current and have network filters.

ATTENTION

Connection and disconnection of interface cables of self-powered devices must be carried out with the power off. Otherwise, the difference in unbalanced device potentials at the time of switching may be applied to the output or input (which is more dangerous) interface circuits and disable the microcircuits.

The RS-232C standard regulates the types of connectors used.

On ADF equipment (including COM ports), it is customary to install plugs PV-25R or a more compact version - DB-9P. Nine-pin connectors do not have pins for the additional signals required for synchronous mode (most 25-pin connectors do not use these pins).

DB-25S or DB-9S sockets are installed on DCE equipment (modems). This rule assumes that DCE sockets can be connected to ADF sockets directly or through adapter "straight" cables with a socket and plug, in which the contacts are connected "one to one" . Adapter cables can also be adapters from 9 to 25-pin connectors (Fig. 2.4).

If the ADF equipment is connected without modems, then the device connectors (plugs) are connected to each other by a null-modem cable (Zero-modem, or Z-modem), which has sockets at both ends, the contacts of which are connected crosswise according to one of the diagrams shown in Fig. 2.5.

RS-232C interface

Rice. 2.3. Receiving RS-232C Signals

Rice. 2.4. Modem cables

Rice. 2.5. Null modem cable: a - minimal, b - complete

If an outlet is installed on any ADF device, it is almost 100% that it must be connected to another device with a direct cable, similar to a modem connection cable. The socket is usually installed on those devices that have remote connection through the modem is not provided.

In table. 2.1 shows the pin assignment of the COM ports connectors (and any other ADF data transmission equipment). The pins of the DB-25S connector are defined by the EIA/TIA-232-E standard, the DB-9S connector is defined by the EIA/TIA-574 standard. Modems (AKD) have the same name of circuits and contacts, but the roles of signals (input-output) are reversed.

Table 2.1. RS-232C connectors and signals

1 8-bit multicard ribbon cable.

2 Ribbon cable for 16-bit multicards and ports on motherboards.

3 Ribbon cable option for ports on motherboards.

4 Wide ribbon cable to 25-pin connector.

The subset of RS-232C signals related to the asynchronous mode will be considered from the point of view of the PC COM port. For convenience, we will use the mnemonic names adopted in the descriptions of COM ports and most devices (it differs from the faceless designations RS-232 and V.24). Recall that the active state of the signal ("on") and the logical unit of the transmitted data corresponds to the negative potential (below -3 V) of the interface signal, and the state "off" and logical zero - positive (above +3 V). The purpose of the interface signals is given in Table. 2.2. The normal sequence of control signals for the case of connecting a modem to a COM port is illustrated in Fig. 2.6.

Table 2.2. Assignment of RS-232C interface signals

Signal Purpose

PG Protected Ground -- protective ground, connected to the device case and cable screen

SG Signal Ground -- signal (circuit) ground, relative to which signal levels act

TD Transmit Data -- serial data -- transmitter output

RD Receive Data -- serial data -- receiver input

RTS Request To Send -- data transfer request output: "on" state

notifies the modem that the terminal has data to transmit. In half-duplex mode, used for direction control -- the "on" state signals the modem to switch to transmit mode

CIS Clear To Send -- input to allow the terminal to send data. State

"off" disables data transfer. The signal is used for hardware flow control

DSR Data Set Ready - ready signal input from data transmission equipment (the modem is connected to the channel in operating mode and has completed the coordination with the equipment at the opposite end of the channel)

DTR Data Terminal Ready -- signal output of the terminal's readiness for data exchange.

The "on" state keeps the dial-up link in the connected state

DCD Data Carrier Detected -- remote modem carrier detection signal input

Rl Ring Indicator - call indicator input. In a switched channel, the modem signals the acceptance of a call with this signal.

Rice. 2.6. Interface Control Sequence

By setting DTR, the computer indicates a desire to use the modem.

By setting DSR, the modem signals its readiness and connection establishment.

With the RTS signal, the computer requests permission to transmit and declares its readiness to receive data from the modem.

With the CTS signal, the modem notifies that it is ready to receive data from the computer and transfer them to the line.

By removing CTS, the modem signals the impossibility of further reception (for example, the buffer is full) - the computer must suspend data transmission.

With the CTS signal, the modem allows the computer to continue transmitting (to the buffer) Communication via the COM port

The connection of the terminal with the PC via the COM port is carried out via the interface

RS-232C. To connect a terminal to a COM port, do the following:

1. Turn off the PC and terminal.

2. Insert 9-pin DB-9 connector

communication cable

cradles, in 9-pin

PC serial COM port.

Plug in the power adapter as shown in the figure.

If the serial COM port

PC - 25-pin, it is necessary

use an adapter for

COM port (from 9 to 25 pin),

which can be purchased

separately.

3. Turn on the PC.

4. Turn on the terminal.

5. Launch the necessary software with which data will be exchanged.

Communication via IrDA port

Communication of the terminal with the PC via the IrDA interface allows data exchange at a small (about 10-20 cm) distance from the PC. As an IR receiver, a communication stand or the IrDA port built into the PC can be used. This method of communication can be convenient when using the terminal with a laptop.

To use the IrDA protocol, it must be supported by both the client software and the terminal's internal software.

Note: At the time of writing this manual, the ability to communicate via the IrDA interface in the firmware was not supported. This function should appear in the next software versions from the terminal manufacturer.

Procedure for connecting the terminal to a PC via the IrDA interface:

1. Direct the red IrDA elements located on the top of the terminal (see "Device Structure") directly to the IR receiver (IR receiver elements on the communication stand or PC IrDA port).

2. Turn on the infrared communication function on the terminal.

3. Make sure that the distance between the stand and the terminal does not exceed 20 cm.

Installing and using the driver

Description of how the driver works

All operations of a PC with TSD are performed under the control of a program running on a PC.

V this section the schema element "Driver" will be described. This description It is intended, first of all, for programmers who create their own software for working with TSD.

The internal organization of the driver is such that it can be used as Server Automation or an external component for the 1C: Enterprise version 7.7 program system.

Driver protection strategy

The driver can only be used with the Zebex RTD if the security key is present. A security key is not required to work with the Opticon TSD.

This driver can be used as part of any commercial programs if you specify a link to STC "Shtrikh-M".

The latest versions of the software can be found on our Web server:

Installing and registering the driver

Automatic installation

Insert the CD into your CD drive and select the file\Driver\Setup.exe, press Enter.

The driver installation program for your PC will be launched:

The installation program window will appear on the screen. To continue the installation, click the "Next>>" button.

Carefully read the messages displayed by the program. This will help you avoid embarrassing mistakes.

Specify the directory in which you want to place the drivers, test utility, documentation, examples, and other files included in the distribution package.

Choose installation type:

- Complete installation

- Optional installation

To install all components of the TSD driver, select "Full installation".

Specify the program group of the main menu in which to place the link to the test utility. The test utility will be placed in the "Tests" subgroup of the specified group.

Click next to start the installation and wait until all required modules are copied and registered.

If the security key driver has not been installed or has been uninstalled, a prompt to install it will appear on the screen.

It is not usually necessary to configure the security key driver, but if required, click Configure Driver. see also

\Guardant\INSTDRV.txt in the directory specified during installation.

After all the files have been copied to the PC hard drive and the necessary registrations have been made, a window will appear announcing the successful completion of the installation. Click the "OK" button to exit the program.

Note: When installing the driver, the VCL50.BPL library is placed in the Windows system directory.

You can find out the driver version on its properties page. To do this, click on the "About" button on this page.

You can unregister the driver by running: RegSvr32.exe /u Terminals.dll

You can find the location of the driver file by running:

a) run RegEdit.exe

b) go to key HKEY_CLASSES_ROOT\CLSID

c) press Ctrl+F

d) type the name of the driver object (AddIn.Terminals and press Enter

e) if the string was not found, then the driver in the system is not

registered

f) press F3 to continue searching

g) above the found subkey is the InprocServer32 subkey

h) the default value of this subkey stores the name of the driver file used by the system when calling the driver as an OLE-Automation server; to browse (after searching) press Tab, Up Arrow, Up Arrow

Setting driver options

To get started, you need to configure the driver. This is easy to do using the test utility that comes with the driver:

Connect TSD to PC.

Run the test utility.

Open the driver's property page (Set properties button).

Click the "Hardware Search" button.

Search for all TSD connected to the PC by pressing the "Search" button.

Note: If ZEBEX TSD is being searched for, it is recommended to use the "Search only ZEBEX TSD" button, which will significantly reduce the search time.

Create the LU structure so that it is convenient for you to work with it:

* button - add new LU;

* button - delete the current LU;

* button - change the name of the current LU;

The current LU is listed in the Current LUN field. You can make the current LU by pressing the button and selecting the required LU from the list that appears.

Set each of the LUs to the required communication parameters.

You can check the correctness of the settings of any LU by the sequence of actions:

* make the current LU configured for this TSD;

* press the "Check connection" button;

– in the “Result” field, the type of TSD should be displayed, for example, “Terminal PDL-20 version 1.01 ID: _”.

In the course of work, to “switch” the driver from one piece of equipment to another, simply select the appropriate LU (on the driver properties page, the “Current device” field). For the utility to work with the TSD, you need to occupy the port - check the box (there is a checkmark) “The device is on”. If the device is not turned on, then work with the equipment will not be carried out.

Test utility TestTerminals.exe

Purpose and capabilities of the utility

The utility is designed to familiarize developers with the principles of using the driver and allows you to:

Set up the driver.

Read data stored in the TSD memory

Load data into TSD memory.

Download tasks to the memory of the ZEBEX TSD and applications to the OPTICON TSD.

Delete data in the TSD memory.

Visually adjust the TSD parameters (including the form format).

The main window of the utility

After starting the utility, the main window of the utility will appear on the screen:

Files and tasks tab:

Logical Device Setup window

The window is opened by pressing the button "Logical devices" or selecting the menu item "Properties/Logical devices" on the main form of the utility.

Logical devices

A logical device is a set of driver properties that has a unique number and an optional name. There can be from 1 to 99 such sets (devices) at the same time. This allows, once having configured several sets of properties, to quickly apply the necessary parameters simply by switching devices. The device number is assigned automatically when it is created and cannot be changed. The device name can be changed at any time.

The current device is the device whose properties are currently available for reading and editing. All driver methods work with the properties of this particular device. To change the properties of another device, it must first be made current.

The logical device index is the serial number of the device in the list of existing logical devices in the driver. That is, when a new logical device is created, it is assigned the minimum free number, and the indices are recalculated so that the numbers are in order. When a logical device is removed from the “middle” of the list of devices, the numbers of the remaining devices do not change, but the indices change in such a way that again a continuous series of values ​​is obtained.

For example, there were three logical units, numbered 1, 2, and 3, with indices 0, 1, and 2, respectively; after deleting the logical device with number 2, a “hole” will appear, i.e. you can make logical device number 1 or 3 current, but not 2. However, the device index number 3 has changed from "2" to "1". When creating a new logical device, it will be assigned number 2 and index 1 (for device No. 3, the index will change from 1 to 2). Such “gaps in numbers” create certain problems when working with devices, for this reason the concept of a logical device index was introduced.

Driver Programming

Data types

This chapter uses types to describe data:

Driver connection

Different programming languages ​​use different syntax, we will give here only an example for "1C: TRADE AND WAREHOUSE" v. 7.7.

The name of the driver object is "AddIn.Terminals".

An example of a global configuration module 1C: ENTERPRISE:

Variable Trm Export; // Global var. to work with the driver

Variable Result; // Service variable

. . . // Section of the description of global procedures

Result = LoadExternalComponent("Terminals.dll");

// Initialize global. variable if the component is found

If Result = 1 Then Trm = CreateObject("AddIn.Terminals");

Otherwise Report("External component not found.");

EndIf;

//After that, access to the properties and methods of the driver is possible
// in all modules:

// Call the driver method

If Trm.AddDevice()< 0

// Property access

Then Report("Error:" + String(Trm.ResultDescription));

EndIf;

Driver Methods

Almost all driver methods are functions, that is, they return a value. Many of them return the code of the error that occurred while executing the given method (the error code is also stored in the ResultCode property, and its description is in the ResultDescription). When called, methods can use or modify properties:

* - as a result of the method execution, the values ​​of the specified properties are updated. As already mentioned, each method also enters the error code in the ResultCode property, and its description in ResultDescription.

Methods for working with logical devices

AddDevice()

AddDevice()

Return type: Integer / Integer.

Method for creating a new logical device (number and index are assigned automatically, and the name of the new device is set to "Untitled"). Returns the error code.

Actions performed:

If DeviceCount = 99, then -7 is returned and the LU creation process is aborted.

A new LU is created (all properties that have property type "L" take on the current values).

DeviceCount is incremented by one.

The new LU is assigned the minimum of the unoccupied numbers.

Indexes are recalculated:

LUs are sorted in ascending order of numbers;

The LU with the minimum number is assigned index 0, the next _ 1,..., the LU with the maximum number - index (DeviceCount - 1).

The created LU becomes the current one.

See also: CurrentDeviceNumber , CurrentDeviceIndex , DeviceCount , and CurrentDeviceName properties.

DeleteDevice()

DeleteDevice()

Return type: Integer / Integer.

Returns the error code.

The method is designed to remove the current logical device. It must be remembered that you cannot delete all devices (there must be at least one), so when you try to delete the last logical device, the method returns -8. Be careful - it is impossible to undo the deletion.

See also: CurrentDeviceNumber , CurrentDeviceIndex , and DeviceCount properties.

Methods for reading data from the memory of the TSD

BeginReport()

ReportStart()

Return type: Integer / Integer.

Returns the error code.

The report start method reads all data from the terminal memory into the PC memory (driver buffer). The number of the form from which the data is read is given in FormNumber.

See also: DeviceEnabled, ShowProgress , Field1…Field16 properties and EndReport and GetRecord methods.

BeginReportKey()

StartReportByKey()

A type return value: Integer / Integer.

Returns the error code.

The report start method reads data from the terminal's memory into the PC's memory (driver's buffer), selecting only those records whose field, whose number is contained in SearchFieldNumber, contains a value equal to the current value of the KeySearch property. The number of the form from which the data is read is specified in FormNumber. The driver buffer must be cleared before the method is executed, otherwise the method returns -10 and the report will not be received. If the ShowProgress property contains TRUE, then when reading data from the TSD, a window with a progress bar will be displayed on the PC screen. To execute the method necessary condition: DeviceEnabled = TRUE.

See also: DeviceEnabled, SearchFieldNumber, KeySearch, ShowProgress , Field1…Field16 properties and EndReport and GetRecord methods.

BeginReportLimit()

StartReportToLimit()

Return type: Integer / Integer.

Returns the error code.

The report start method reads data records from the terminal memory into the PC memory (driver buffer). Records are read from MinRecNumber to MaxRecNumber. The number of the form from which the data is read is given in FormNumber.

The driver buffer must be cleared before executing the method, otherwise the method returns -10 and the report will not be received.

If the ShowProgress property contains TRUE, then when reading data from the TSD, a window with a progress bar will be displayed on the PC screen.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: DeviceEnabled, MinRecNumber, MaxRecNumber, ShowProgress , Field1…Field16 properties and EndReport and GetRecord methods.

EndReport()

EndReport()

Return type: Integer / Integer.

Returns the error code.

The method finishes working with the report data and clears the driver's internal buffer.

See also: BeginReport and GetRecord methods.

GetRecord()

GetRecord()

Return type: Integer / Integer.

Returns the error code.

The command to receive the next record of the report from the buffer of the driver. The logic of the driver is as follows: all fields of the next record are placed in the corresponding properties in text form. The first field is in the property Field1 , the second is in Field2 ... the sixteenth is in Field16 . If there are less than 16 fields in the form, then Fieldx properties where x is greater than the actual number of fields in the current form should be ignored.

The data structure of the fields (purpose, type) depends on the settings of the terminal form. You can quickly and visually customize the form using the form editor, accessible from the visual properties page (“Form editor” button).

When trying to get a record before the beginning of the report (BeginReport) or after it is closed by the EndReport method, GetRecord will return an error -10.

See also: Field1 ... Field16 properties and BeginReport and EndReport methods.

GetField(Param: integer)

GetField (FieldNumber: Integer)

Return type: WideString / String.

Returns the Param number field.

The command to get the field with the number specified as a function parameter from the next report record from the driver buffer

See also: Field1 ... Field16 properties and GetRecord, BeginReport and EndReport methods.

GetHeader()

GetTitle()

Return type: WideString / String.

Returns the title of the read form from the internal file buffer.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property and GetRecord method.

SaveToFile(Param1: WideString)

WriteToFile(Parameter: String)

Return type: Integer / Integer.

Returns the error code.

The method writes the data from the form with the number FormNumber to a file named Param1(Parameter). For the file format, see the description of LoadFromFile.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property, LoadFromFile method.

DownLoadFile(TFile: WideString; PCFile: WideString)

Returns the error code.

Only for TSD OPTICON.

Downloads the contents of a file from the TSD named Tfile to a file named PCFile.

See also: UploadFile method.

Methods for writing data to the memory of the TSD

BeginDownLoadTable()

StartLoadingTable()

Return type: Integer / Integer.

Returns the error code.

Preparing the driver's internal buffer for loading data into the PDx. The buffer is formed by adding rows with the AddInTable command.

The driver's internal buffer must be cleared, otherwise the method will return a -10 error and the operation will fail.

See also: AddInTable , ClearTable , and DownLoadTable methods.

AddInTable(Param1: WideStr)

AddToTable(Parameter: String)

Return type: Integer / Integer.

Returns the error code.

The method adds the string Param1(Parameter) to the buffer when generating a table for loading into PDx.

The table for loading is formed according to the following algorithm:

1Field_1Record

2Field_1Record

xField_1Record

1Field_2Record

xField_2Record

1Field_yRecord

xField_yRecord

where x is the number of fields in the record;

y - number of records;

DownLoadTable()

LoadTable()

Return type: Integer / Integer.

Returns the error code.

The method loads data from the internal buffer into the TSD form with the number FormNumber. Old data in the form of TSD is deleted. After executing this method, the driver buffer is cleared.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property.

AddToTable()

LoadToTable()

Return type: Integer / Integer.

Returns the error code.

The method adds data from the internal buffer to the TSD form with the number FormNumber. The old data in the form of TSD is retained. After executing this method, the driver buffer is cleared.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property.

ClearTableBuffer()

ClearTableBuffer()

Return type: Integer / Integer.

Returns the error code.

Clears the driver's internal buffer when generating a table for loading into the TSD.

See also: FormNumber property.

LoadFromFile(Param1: WideString)

LoadFromFile(Parameter: String)

Return type: Integer / Integer.

Returns the error code.

Used only for ZEBEX TSD.

Writes data from a file (*.ULD) to the TSD form with the FormNumber number.

The data in the file must be in a special format:

1st line: Form title;

The following lines are records whose fields are separated by spaces;

This format (*.ULD file) is used in the WinTaskGen program supplied with the ZEBEX terminal when working with data, as well as in the LoadFromFile and SaveToFile methods of this driver.

See also: FormNumber property, LoadFromFile and SaveToFile methods.

UploadFile(FileName: WideString)

UploadFile (FileName:string)

Return type: Integer / Integer.

Returns the error code.

Only for TSD OPTICON.

Uploads a file from a PC named FileName to the TSD.

See also: Download File method.

Additional Methods

GetRecordCount()

GetNumber of Records()

Return type: Integer / Integer.

Returns the number of records in the form.

The command to get the number of records in the form, the number of which is specified in the FormNumber property.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property.

GetFieldCount()

GetNumberFields()

Return type: Byte/ Unsigned integer.

Returns the number of fields in a form entry.

The command to get the number of fields in the form entry whose number is specified in FormNumber.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property.

GetFormName()

GetFormName()

Return type: WideString / String.

Returns the name of the form.

The command to get the name of the form whose number is specified in FormNumber.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: FormNumber property.

clear()

clear()

Return type: Integer / Integer.

Returns the error code.

This method erases all data in the form (the form number is given in FormNumber) of the terminal. After this command, all data in the terminal's memory is irretrievably lost.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

See also: DeviceEnabled property.

LoadTask(Param1: WideStr)

LoadTask(Parameter: String)

Return type: Integer / Integer.

Returns the error code.

For Zebex: Load task from file named Param1(Parameter). The file format is *.TSL. The task file is a software for ZEBEX RTD developed in the WINTASKGEN environment that is supplied with the ZEBEX RTD (on CD).

For OPTICON: Not supported. Downloading applications is carried out using special software. You can also load the application file into the TSD memory and then use the appropriate command in the TSD application.

Before calling the method, you must delete all data in all forms of the TSD.

To execute the method, the necessary condition is: DeviceEnabled = TRUE.

LoadFormFromFile(Param1: WideString)

LoadFormFromFile(Parameter: String)

Return type: Integer / Integer.

Returns the error code.

Loads a form from a file named Param1(Parameter). The file format is (*.TSF) or, for TASK-M applications version 3.0: (*.OTF).

Development of *.TSF forms can be done using the “Form Editor” on the properties page of this driver or in the WINTASKGEN environment that comes with the ZEBEX DSD (on CD). *.OTF forms are developed by the task editor available on the driver properties page.

DeleteFormSetting()
DeleteForm()

Return type: Integer / Integer.

Returns the error code.

Only for TSD OPTICON.

Deleting settings and form data with FormNumber.

EraseFile(FileName: WideString)

DeleteForm(FileName: String)

Return type: Integer / Integer.

Returns the error code.

Only for TSD OPTICON.

Deleting a file named FileName in the OPTICON TSD.

SetTime(TimeString: WideString)

SetTime(Time: String)

Return type: Integer / Integer.

Returns the error code.

Sets the time in TSD. The format of the sent string: HH/MM/SS.

H - hours, M - minutes, S - seconds. For example, “09/11/00” is 9 hours, 11 minutes, 0 seconds.

SetDate(DateString: WideString)

SetDate (Date: String)

Return type: Integer / Integer.

Returns the error code.

Only for TSD OPTICON (TASK-M from version 3.0)

Sets the date in the TSD. The format of the sent string: MM/DD/YY.

GetTime() : WideString

GetTime() : String

Returns a string containing the time received from the TSD.

Only for TSD OPTICON (TASK-M from version 3.0)

The format of the received time: HH/MM/SS, as in the SetTime method.

GetDate() : WideString

GetDate() : String

Return type: WideString /String.

Returns a string received from the TSD containing the date.

Only for TSD OPTICON (TASK-M from version 3.0)

The format of the received date: MM/DD/YY, as in the SetDate method.

ShowProperties () driver utility editor given

The method displays a visual property page through which you can:

add, modify and delete LU

configure communication settings with equipment

check the connection with the equipment

search for the COM port to which the equipment is connected

This method cannot be called if the driver is used as an external component for 1C:ENTERPRISE programs. In this case, the property page can be displayed by selecting the menu item "Service / Parameters ...", on the "Settings of the data collection terminal" tab.

By clicking on the properties page of the "Check connection" button:

The type and number of the TSD is requested (if DeviceEnabled = FALSE for the current LU, then the driver temporarily occupies the port).

If the operation was not successful, the "Result:" field displays a description of the error.

If the data is successfully received, then a string is displayed in the "Result:" field, for example: "Terminal PDL-20 version 1.01 ID: _".

By pressing the button "Search for equipment" The standard window for searching for equipment is displayed on the screen:

"Search" starts the search (on all available ports of this PC, the driver tries to request the ID of the TSD). For each port, the search is conducted until the first correct answer. The "Search result" field contains records only about the successful finding of equipment.

"Search for Zebex RTD Only" starts a search (on all available ports on this PC, the driver attempts to query the RTD ID) for only the Zebex RTD. The presence of this operation is due to the fact that the search for only TSD ZEBEX is carried out much faster than TSD OPTICON.

"Abort" - interrupts the search.

"Close" - closes the search window. The search results do not affect the properties of the driver's LU in any way.

By pressing the "System parameters" button on the properties page, if there is a connection with the TSD, the window " System settings terminal":

Clicking the "Barcode Settings" button on the properties page opens the "Decoder Modes" window:

By clicking on the properties page of the button "Terminal task settings tools" the "Development tools" window opens:

Here you can select one of the built-in editors available in the driver for developing forms or tasks. Moreover, the task editor can only be used for TSD running "Task-m" starting from version 3.0.

For information on how to use the "Form Editor", see the "Using the Form Editor" chapter.

For information on how to use the Task Editor, see the Creating Forms Using the Task Editor chapter.

Clicking on the "About" button on the properties page opens the "About" window:

If an Internet browser is installed on the system, then click on www.shtrih-m.ru to open the www page "Shtrih-M". If you have an email system installed on your system, click [email protected] to create a letter to the service technical support and [email protected] to create a letter to the information service "Shtrikh-M".

Driver Properties

1 - There are two types of access to the property: RW - the property is available for writing and reading, R - the property is available only for reading.

Similar Documents

Windows NT 5 architecture. Execution priorities program code. Description of the MIDI data format. Installing the driver in the system. Choice of software development tools. Handling WDM Driver Model Requests. Using the DirectKS library.

term paper, added 06/24/2009


Increasing the speed of the operating system. Development of drivers for data storage facilities, device operation control by PnP commands. Creating, configuring, and installing a class driver virtual disk, its structure and properties.

term paper, added 06/18/2009


Windows NT I/O architecture. Internal organization of the USB bus. Essential characteristic WDM driver model. Entry points of the developed driver, placement of code in memory, installation of the driver in the system. Implementation of driver code in C language.

term paper, added 09/27/2014


Using the kernel-mode driver and control application to create system threads. Imitation of data processing and organization of delays. Driver development in C++. Test stand configuration. Accuracy of changing delays and timer operation.

term paper, added 06/24/2009


Mechanisms of interaction between the kernel-mode driver and custom application: multilayer driver architecture, data hiding algorithm, interaction between driver and application, user interface of the file access filtering program.

term paper, added 06/23/2009


Development of a Linux driver that monitors allocation and deallocation by processes virtual memory and allocating physical pages on page faults. Compiling the driver and working with it. Experimental verification of driver performance.

term paper, added 06/18/2009


DBMS access technologies. Data source management. Typical driver settings. Ways to create tables. Launch and content of the script ( text file with commands). Automated tools for managing the database structure.

presentation, added 08/19/2013


Installation " Microsoft SQL SERVER 2012". Creation of a data file, transaction log, tables, queries and filters, charts and triggers, tabular forms and reports. Connecting a data file to a project. Creation of simple and complex ribbon forms to work with them.

term paper, added 12/13/2013


Representation of information in the form of databases using tables, forms, queries, reports. The essence of queries and their functions. Application of forms and reports. Purpose and use Email global network. Description of the Compass-3D system interface.

test, added 12/23/2014


The structure of the mandatory information included in the database of a computer company. Create tables with help from Microsoft Access, containing information about computers, customers, payment. Development of forms for performing calculations, viewing and editing data.