1c compatible equipment. How to connect commercial equipment in six steps? Equipment life cycle

The growth of the business of many companies is often accompanied by an increase in the number and expansion of the fleet of equipment used. As a result, the task of organizing the operational accounting of equipment becomes very relevant for such companies.

To automate the accounting of equipment in medium and large organizations, the application solution "Business Plus: Equipment" is proposed. This software product was developed on the 1C:Enterprise 8 platform and allows you to organize the accounting of production, retail, office and IT equipment.

The program provides the ability to create visual plans for the placement of equipment on the territory of the enterprise, automated inventory of the equipment fleet using bar coding. The life cycle of a unit of account in a program includes commissioning, relocation, maintenance, repair, and decommissioning. The calculation of the total cost of ownership (TCO - Total Cost of Ownership) is provided. Consider the main features of the program.

List of jobs

The system implements the storage of a hierarchical list of jobs - places of use or storage of equipment. The grouping of workplaces reflects their geographical location, for example, city/address/floor/office. A hierarchical list of equipment can be attached to each workplace, reflecting the relationship of accounting objects. The list of cashier workplace equipment may include, for example, Posiflex Cash Drawer, LPOS Keyboard with Magnetic Card Reader, Samsung Monitor 15, Metrologic Barcode Scanner and FELIX Fiscal Recorder.

For each workplace, you can set an arbitrary number of parameters: inventory number, socket number, IP address, mains voltage, etc. Each workplace is assigned a responsible person.

Equipment layout plans

The program contains tools that allow you to create graphical floor plans and indicate the location of specific workplaces on them. You can create a hierarchy of plans, such as building/floor/shop, building/floor/office, etc. Thus, if the plan of the territory of the plant reflects the building of the workshop, then a quick transition to working with the plan of this workshop is possible.

Room plans are closely related to the hierarchy of workplaces and the list of equipment. When selecting a workplace, a list of installed equipment and the location of the workplace on the plan are displayed.

Equipment life cycle

To register operations with equipment, the program uses the documents “Incoming equipment”, “Movement of equipment”, “Transfer for repair”, “Acceptance from repair”, etc. The program allows you to track the life cycle of each accounting unit. In the piece of equipment card, you can view the history of operations and, if necessary, open the corresponding document.

Planning and registration of the fact of equipment maintenance are performed using the document "Maintenance". Two types of service standards have been implemented - “by period” and “by output”. The standard “by period” is used, for example, for a machine that needs to be serviced periodically, every six months. For printer maintenance scheduling, such as after 15,000 pages have been printed, a "by-production" target is applied.

The program provides the ability to store the parameters of equipment models, as well as individual instances of equipment. You can store, for example, parameters such as "warranty period", "serial number", "inventory number", "hard disk capacity", etc.

Implemented accounting "by copies" and "by batches". Accounting "by copies" is used to account for computers, office equipment, furniture, etc. For consumables, an aggregated accounting “by batches” is used.

A flexible report is used to analyze equipment data. The parameters of this report, as well as the design, can be customized. There are preset sets of settings that allow you to generate, for example, a report on balances, a report on movements for a period, a report on total cost of ownership (TCO).

Using barcoding

In the process of inventorying equipment, a reconciliation of accounting and actual data is performed. To facilitate the operation of mass recalculation, the program provides for the use of barcoding technology.

Bar coding is also convenient to use for registration of operations with individual pieces of equipment during transfer for repair and acceptance from repair, re-evaluation, planning and registration of the fact of maintenance, etc. For example, when a failed cash register is received for repair, it is enough to scan its barcode to determine the workplace where it was installed.

Remote data collection on IT equipment

Accounting for IT equipment in the program differs to some extent from accounting for other equipment. Thus, the program allows you to automate the remote collection of data about IT equipment that is on the network. When registering a transaction, the responsible employee must only select the type of movement document. Documents are filled in automatically, so the probability of data errors is minimized.

Differentiation of access rights

The program implements various options for delimiting user access rights when working with data. You can restrict access to equipment lists, for example, by departments. Departments can keep records independently, while the data of all departments is available in the parent organization.

For a situation in which different employees are responsible for accounting for different types of equipment, you can differentiate access rights to data by type of equipment. For example, accounting for commercial equipment can be handled by one employee, and accounting for computers and office equipment by another.

Ease of implementation

Before starting work with the program "Business Plus: Equipment", the lists of those responsible for the equipment, jobs and models of equipment are filled out. Then the equipment is delivered to the workplace and assigned to financially responsible persons.

To simplify implementation, the program provides for the use of such built-in technologies of Windows operating systems as Active Directory and WMI (Windows Management Instrumentation). This made it possible to automate the loading of the list of responsible persons, the initial filling in of information about the IT equipment fleet, and the creation of a list of jobs.

Integration and accounting of fixed assets

The program "Business Plus: Equipment" can be used as a separate product. It can also be integrated with the programs "1C: Production Enterprise Management 8" or "1C: Trade Management 8".

The integration increases the convenience of work, all operations are registered in one infobase. Another advantage of integration with 1C:Manufacturing Enterprise Management 8 is the ability to set up the sharing of Business Plus:Equipment with the fixed asset accounting subsystem.

Today, the software product "Business Plus: Equipment" is successfully used by more than ten companies in Chelyabinsk and other cities of Russia. As a result of its implementation, management accounting of equipment has been put in place at enterprises, financial liability has been streamlined, records of repairs and maintenance are being kept, and data collection on IT equipment has been automated. Data on the composition and cost of the equipment fleet also became available for analysis.

The software product "Business Plus: Equipment" received from the company "1C" the certificate "Compatible! 1C: Enterprise.

Continuing the theme of retail automation, let's return to retail equipment. In our previous materials, we analyzed the theory: how to choose the right trading equipment and how it interacts with 1C. This article will be devoted to practice, namely the method of connecting retail equipment to configurations on the 1C:Enterprise platform. We strongly recommend this material for study, since in the future, talking about the features of a particular type of commercial equipment, we will not address in detail the issues of its connection to 1C.

Currently, the range of 1C software can be clearly divided into two parts: configurations based on conventional and managed applications. They are easy to distinguish by their appearance, the internal differences are just as significant, and therefore, despite the continuity, approaches to working with retail equipment in normal and controlled applications differ and will be considered separately. Before continuing reading, we recommend refreshing your knowledge about the principles of interaction between commercial equipment and 1C by reading the article:.

General Application

This type of configuration includes Trade Management 10.3 and Retail 1.0, in the future we will use Retail as an example, although the methods of connecting equipment in any configuration of this type are the same.

First of all, connect all the necessary trading equipment to the PC, switch it to the required mode (for example, RS-232 emulation) and install the necessary drivers for the operating system. After that, you can proceed to connecting equipment directly to the configuration. To successfully complete this task, we need two more things: service processing and a vending machine driver.

As we wrote in the previous article, service processing is an external component of the 1C:Enterprise platform, which is responsible for the interaction of the configuration with the retail equipment driver, which is a dynamic library that is directly responsible for interacting with the equipment and implementing its specified functions.

It’s a little more difficult with drivers, here you first need to establish who exactly is supporting the equipment: 1C or third-party manufacturers. For a regular application, 1C drivers exist only for barcode scanners and are also available on the update service. The rest will have to be found on the manufacturers' websites. Also note that many commercial equipment drivers are paid, for example, ATOL.

What if you do not know where to get the driver? There is a little trick that we will talk about later, but for now you can skip this step and go directly to connecting the equipment. In 1C: Retail we will open Service - Trade equipment - Connection and setup of trade equipment(in other configurations, the path may be slightly different). In the window that opens, we will see all the equipment connected to the workplace, divided into groups.

Please note that the hardware is configured for each computer individually, the binding is done by host name, so if you rename the computer, the hardware will have to be configured again. Information about the equipment connected to different computers is stored in the Trade Equipment information register.

There are two ways to connect the equipment: manually or through an assistant, we recommend using an assistant who will quickly guide you through all the necessary steps, while manual installation requires some experience and knowledge.

Everything is simple here - select the desired type of equipment and click Further. On the next screen, we will see all the service processing equipment loaded for this type of equipment. If the list is empty or the necessary processing is missing, then it must be downloaded by selecting the appropriate item.

To download, specify the directory containing the maintenance processing and click the button Get a list, while all processing will be loaded, and not just for the installed type of equipment, i.e. it is enough to perform this operation once.

After loading, we return to the previous screen and select the necessary processing. The choice depends on the installed drivers for commercial equipment, for example, for a barcode scanner, processing is offered for a driver from 1C and input device drivers from ATOL. Each processing has its own list of supported equipment, from which you should select the desired model. It’s easy with scanners, in fact, this is standard equipment, so let’s take something more complicated, for example, a customer’s display Gigatek DSP-820.

First of all, let's visit the page http://v8.1c.ru/retail/300/vs_drivers.htm and find out that this model is supported by ATOL (paid) and Scancode (free)

It is quite logical to choose a free driver. Therefore, we go to the Scancode website, in the support section, download the TO driver and install it.

Then in 1C we select Scancode service processing

Clicking Further we will see the previously created devices for our processing, since the required model is not there, then we select Add a new device.

And in the list of supported equipment, select the desired model, here we indicate its name (substituted automatically) and the KKM cash register on which this device will be used.

It is enough to create any device once, after which it can be used to connect similar equipment at other workplaces. The created devices are stored in the Trade Equipment directory and represent, as it is not difficult to see, lists of device model and service processing compliance.

If you use the same equipment model, but in different modifications, then it makes sense to have a duplicate position, clearly reflecting this in the name. For example, Voyager 1250 Barcode Scanner (USB) and Voyager 1250 Barcode Scanner (RS-232), directly specifying the physical interface of the device, instead of the impersonal Barcode Scanner (general). Why is this needed if, from the point of view of 1C, these are absolutely the same devices? And so that you, without getting up from your workplace, simply by looking at the register, can tell exactly what kind of equipment is installed at each workplace.

Finally, by selecting or adding the required device, we proceed directly to its configuration. The setting, as we have already said, is done for each computer separately. Depending on the type of equipment, the number of available options may vary. Below is a typical settings window, let's look at it in more detail.

First of all, check the driver information and driver version. It must be installed and have a compatible version, we will touch on compatibility below, but for now, just make sure that the driver is available and available for the application. If the driver is not installed, then you did something wrong, you may need to register the required library manually, or restart the program if the driver was installed with 1C open.

Above we talked about a little trick. At the bottom of this block there is a link to the latest version of the driver, and if you are using the latest configuration release, the link will also be relevant. So, if you don’t know where to get the MOT driver or didn’t find it on the supplier’s website, you can continue without installing it until now, then go through and download it from this link.

Below are the connection parameters: port and speed. If everything is clear with the port, then in order to find out the speed, refer to the documentation for the device, in the case of this display, the default speed is 19200 bps, and if you leave the value 9600 bps, then instead of letters, the display will show " kryakozyabry".

Now let's talk about compatibility. IT is a dynamic industry, so it may happen that you have more recent driver versions than those listed in the processing compatibility list. How to be in that case?

In most cases the drivers are backward compatible and everything should work. But the situation should not be left to chance. To get started, run a built-in processing test and make sure that the device at least just works.

Then do a test run by performing a full cycle of operations for this device in both modes (RMK and normal). So, for example, with the driver from 1C version 8.0.17.x of the METROLOGIC MS7120 "Orbit" barcode scanner, it works fine, and the METROLOGIC 1250G "Voyager" calls up the selection form with each reading.

If any shortcomings are found in the work, then you should roll back to a compatible version of the driver, but if everything works fine, then leave it as it is. To avoid the annoying message about the driver version mismatch, you can fix the service handling code. Open it with the configurator and find the section responsible for checking the driver version, then replace the version of the compatible driver with your own.

After that, update the maintenance handling in the configuration.

Managed Application

Based on the managed application, new configurations are created, today it is Trade Management 11 and Retail 2.1, which have significant differences from conventional configurations, both externally and internally. But there is also a large degree of continuity. If you know how to work with trading equipment in a regular application, then you can easily figure it out with a managed one.

The main difference is in the unification of the approach, now instead of separate external service processing, the Plug-in Equipment Libraries (PDL) technology is used, which provides a single code base and libraries for working with trading equipment at the platform level. The BPO also includes certified drivers for commercial equipment, which makes it easier to find a compatible version.

All connected equipment is divided into certified, support for all components of the bundle Hardware - Driver Maintenance - Configuration carried out by 1C and equipment supported by the driver manufacturer, whose work with 1C Configurations at the level maintenance driver provided by the manufacturer. There is not much difference between these lists, other than who you will have to contact for support in case of problems, and you should also remember that third-party maintenance drivers are usually paid.

Please note that service processing is not used in a managed application, and the subsystem of the same name is used to work with connected equipment. At the same time, the scheme of interaction with the equipment has not changed dramatically, just the code from the 1C side was unified within the BPO and included in the configuration.

We will not delve into internal differences, those who are interested can deepen their knowledge on the topic of the Connected Equipment Libraries on their own, but let's move on to changes in the user part of the settings.

One of the important innovations is Workplaces. A workplace is a combination of a computer and an infobase user. This allows you to have different sets of pluggable hardware for different users on the same computer. For example, for a cashier we set up a full set of equipment, and for a merchandiser we leave only a barcode scanner and add a TSD.

Workplaces also allow, by ticking the appropriate checkbox, to work with the settings of equipment connected to other computers. This is convenient when you need to centrally change the equipment settings at several workstations at once. For example, you have changed the IP address of the label printing scale, now you do not need to run through all the workstations from where they work with the scales, you can change the settings for them from your computer.

The connection and configuration process itself has changed slightly and has become easier. But there is one subtlety, since the TO drivers are now included in the configuration and are installed automatically, then the program should be run as administrator while setting up the trading equipment, otherwise you may encounter a situation where the application cannot register libraries and you will receive an error.

For a complete list of drivers available in the configuration, click the link Hardware drivers at the top of the form Connecting and configuring equipment.

In addition to satisfying curiosity, this list is also useful in that any driver can be downloaded and then used separately, for example, for configurations based on a regular application, so as not to search for it on the Internet.

Connecting retail equipment has also become easier, there is no connection assistant, but there is no need for it, all you need to choose is the type of equipment, driver and workplace.

After that, you should save the changes and by clicking on the button Tune, specify the connection parameters for this piece of equipment.

It should be noted that the error messages have become more informative, in our case the system already had the 8.0.15.1 driver for Retail 1.0 and we received a strong recommendation to update it to at least 8.0.17.1. Moreover, this can be done literally "without leaving the cash register", choose Functions - Install driver(We remind you that for the success of this operation, 1C must be launched on behalf of the Administrator).

But what about the equipment that is not supported in the configuration? In a normal application, it was enough to get service processing and install the appropriate driver. Nothing has fundamentally changed in the managed application; to connect unsupported equipment, the manufacturer must provide the component using the BPO technology, which must be loaded into the configuration.

For example, let's take a label printer, which is supported by Scancode. A similar component is presented on the support page for this model.

Connecting the component should not cause any difficulties, open the list of drivers and select the option Add new driver from file, point to the downloaded archive.

As you can see - nothing complicated. We hope this material will help you acquire the basic skills of connecting retail equipment to 1C:Enterprise, and in the future we will not focus on this issue, assuming that the reader already has basic knowledge.

• Tags:

New features and changes

Version 1.2.4 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added support for drivers developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.6".
• Added version control for drivers supplied in configuration layouts and a mechanism for updating drivers by the user.
• The exchange with connected equipment in the "1C:KKM Offline" mode and the equipment Web-service has been improved in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.6".
• For the equipment Web service, the ability to send data in batches (price list) with support for a pool of requests has been added.
• Improved exchange mechanisms with KKM Offline ATOL and Shtrikh-M. Implemented:
  • Support for various exchange formats ATOL and Shtrih-M;
  • Hierarchical unloading of goods;
  • Unloading tax rates of goods;
  • Unloading the properties required for the accounting of alcoholic products;
  • Downloading payments by types and types of payments;
  • Loading data of barcodes of excise and special brands of alcoholic products.
  The barcode printing component has been updated to version 8.3.1.1.
  - Fixed memory leaks when generating barcodes.

• Added new driver "ATOL: Customer Display 8.X", version 8.7, developed by "ATOL".
  
• Added a new driver "ATOL: Input Device Driver 8.X", version 8.7, developed by "ATOL".
  The driver supports the operation of two types of equipment "Barcode scanners" and "Magnetic card readers" and was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• Updated driver "Hexagon: Label printers Zebra, Proton, Toshiba-TEC, Datamax-O neil" to version 2.3.2.
  - Added support for Toshiba-TEC and Datamax-O neil label printers.
• Updated "1C: Barcode Scanner (Native)" driver to version 8.1.7.2
  Bugs fixed:
  - 50002661: Error working on Linux with keyboard devices containing non-ASCII characters in their names.
  - 50002662: Keyboard mode bug on Linux: barcodes are not read when the keyboard device is configured correctly.
  - 00065592: In Chrome and Firefox WEB clients bug with missing characters in barcode in keyboard mode. Appears on CipherLab scanners.
• The layout with the "Scancode:Data collection terminals" driver distribution kit is excluded from the library. The driver is installed using the vendor's distribution kit.

Version 1.2.3

ATTENTION! This release can be used with 1C:Enterprise version 8.3.6.2237 and higher, with compatibility mode disabled.

New features and changes

Corrective release 1.2.3.5

• Added a new driver "Drimkas: VikiPrint fiscal registrars", version 4.02, developed by "CrystalService".
  
• Updated driver "ATOL: Driver for fiscal registrars 8.X", version 8.7 developed by "ATOL".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• Updated driver "Crystal Service: Pirit fiscal registrars" to version 4.02.
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• Updated driver "1C: Fiscal registrar emulator" to version 1.0.13.
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• Updated driver "1C: Customer Display" to version 1.0.4.1
  - Added support for WEB client Internet Explorer 8.0, 9.0(x86), 10(x86), 11(x86).
  Bugs fixed:
  - 000557621: Error opening COM port when working in Internet Explorer WEB client.
  - 00060158: Incomplete display clearing error when displaying three or more lines.
• Updated "1C: Receipt Printer" driver to version 1.0.6.2
  - Added Linux support. Linux supports COM port and Virtual-COM devices (ttyS, ttyACM, ttyUSB).
  Bugs fixed:
  - 00046295: Alignment error: barcode always aligns to the center, text always aligns to the left.
  - 00059407: Error applying settings incorrectly during "Test" operation.

Corrective release 1.2.3.4

• Bugs fixed:
  - 00057346 - Error uploading TSD data for zero quantity for "Scancode: Data collection terminals" and "Scancity: Data collection terminals" drivers.
  - 00053178 - Error loading sales reports for "1C: KKM Offline" when working in the Google Chrome WEB client.
• Updated "1C: Receipt Printer" driver to version 1.0.4.1:
  Changes:
  - Added support for Internet Explorer versions 8-11, Mozilla Firefox versions 31-39 and Google Chrome 37 and above running under Windows.
• Updated "1C: Customer Display" driver to version 1.0.2.1:
  Changes:
  - Added support for Mozilla Firefox browsers versions 31-39 and Google Chrome 37 and above running under Windows OS.
• Updated "Scancity: TSC Label Printers" driver to version 1.0.0.32:
  Changes:
  - Fixed a bug where the link for downloading the main driver package was not provided.

New features and changes

Version 1.2.3 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added support for drivers developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• The built-in forms for the TAXI interface have been improved in accordance with the internal standards of the 1C company.

Bugs fixed:

• 00011627: Incorrect call of the integration component for SBERBANK acquiring has been fixed.
  In the form for setting up an instance of equipment, you can select the version of the library used.

The composition of supplied drivers has been changed:

• Added new driver "ATOL: Electronic scales 8.X", version 8.7, developed by "ATOL".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4".
• Added a new universal driver "1C: Customer Display (NativeApi)" version 1.0.1, developed by "1C".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5" and supports customer displays connected to COM ports (VirtualCOM) using the following protocols: Epson, Firich/CD5220, DSP800.
  Supports work in thin and thick client in operating environments Windows XP, Windows 7, Windows 8, Linux Ubuntu 12, Linux Fedora 17.
• Updated driver "Shtrih-M: Fiscal registrar driver (Universal)" to version 4.12.
  The driver was developed by Shtrikh-M in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.5".
• Updated "Hexagon: Proton Barcode Scanners" driver to version 1.1:
  Bugs fixed:
  - Fixed connection error - incorrect ID of the connected device was returned.
• Updated driver "1C: Barcode Scanner (NativeApi)" to version 8.1.5.1
  - Added driver support for equipment type "Magnetic card readers";
  
  - Added "COM port timeout" parameter. Defines a timeout when reading a COM port;
  - Supported parameter "Suffix" for devices that emulate a keyboard for Linux OS;
  - Supported "Suffix" parameter for devices working via COM port for Linux OS.
• Updated "1C: Barcode Scanner (COM)" driver to version 8.1.5.1
  - Added "COM port encoding" parameter. Determines in what encoding to accept the character stream when reading the COM port;
  - Added "COM port timeout" parameter. Defines a timeout when reading a COM port.
  Bugs fixed:
  - 30026916: For Linux OS, the sequence of barcode symbols from the COM port arrives in fragments of various lengths depending on the driver settings.
• The layout with the driver distribution kit "Shtrikh-M: Data collection terminals" is excluded from the library. The driver is installed using the vendor's distribution kit.
• The layout with the driver distribution kit "SCALE: Scales with label printing CL5000J" is excluded from the library. The driver is installed using the vendor's distribution kit.
• The layout with the driver distribution kit "Sberbank: Acquiring terminals" is excluded from the library. The driver is installed using the vendor's distribution kit.

Version 1.2.2

ATTENTION! This release can be used with 1C:Enterprise version 8.3.6.2041 and higher, with compatibility mode disabled.

New features and changes

Corrective release 1.2.2.3

• Updated "1C: Receipt Printer" driver to version 1.0.3.1:
  Bugs fixed:
  - DSS-00-00048242: The text description of the last error that occurred is not returned.
  - DSS-00-00049454: The cash drawer opening command does not work normally.
  Changes:
  - Added option to automatically open the cash drawer after printing a document. The default value is "True".

New features and changes

Version 1.2.2 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added new asynchronous methods for working with equipment. Synchronous methods are kept for compatibility.
  Supported work in asynchronous mode for all types of equipment. For equipment to work in asynchronous mode, it is necessary to change the configuration code in terms of working with the methods of each type of equipment. The methodology for converting a configuration to asynchronous methods is described in the document "Using the BPO functionality in .htm configurations", sections: "Methodology for converting a configuration to asynchronous methods".
• Added a mechanism for printing cashier's receipts using a software-defined template. The method of using the template printing mechanism is described in the document "Application of the BPO functionality in .htm configurations", sections: "Fiscal registrars" and "Receipt printers".
• Updated barcode printing component to version 8.2.3.1:
  - The returned image format is set to PNG with a depth of 32 bits. This fixed a bug where an incorrect barcode image was returned to the platform.
  - Fixed a bug with incorrectly returned images of barcodes in the client-server version when generating a large number of barcodes in parallel.

The composition of supplied drivers has been changed:

• Added new driver "CAS: Driver for scales with label printing", version 1.0.1, developed by "KAScenter" in NativeApi technology.
  The driver is developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4" and supports the following models of scales with label printing: CAS CL5000J, CAS CL5000, CAS CL3000, CAS LP-1.6, CL-5000D.
• Added new driver "Crystal Service: VikiVision customer display" version 1.0.3. The driver provides connection of displays of the buyer of the brand "VikiVision".
• Added a new driver "Scancity: TSC Label Printers", version 1.0.0, developed by Scancity.
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4".
• Added new driver "Scancode: Driver for TSD CipherLAB 8x00 (NativeApi)", version 1.0.1, developed by "Scancode" in NativeApi technology. The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4".
• Updated "Hexagon: Zebra and Proton Label Printers" driver to version 1.9.9.
  - Added support for Zebra label printers.
• Updated "1C: Receipt Printer" driver to version 1.0.2.1.
  - The driver is prepared to work FireFox, Internet Explorer, Google Chrome in asynchronous mode.

Those "BPO.htm implementation procedure".

Version 1.2.1

ATTENTION! This release can be used with 1C:Enterprise version 8.3.5.1460 and higher, with compatibility mode disabled.

Version 1.2.1 contains functional changes to the subsystem "1C: Library of connected equipment".

• Added support for a new type of equipment "Receipt Printer".
  
• Added support for a new type of equipment "Label printer".
  Drivers developed in accordance with the "Requirements for the Development of Drivers for Connected Equipment, Version 1.4" are supported.
• Added the ability to exchange with "1C: Mobile cash desk" using the universal driver 1C: KKM-Offline in file exchange mode.
• A new protocol for data exchange with equipment "Equipment Web Service" has been added.
  This interaction protocol is implemented on the side of the library using the WEB service "EquipmentService".
  The interaction is carried out in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4".

The composition of supplied drivers has been changed:

• Added a new driver "1C: Receipt printer" version 1.0.1.1, developed in The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4". The driver provides connections for POS receipt printers that support the ESC\POS protocol.
• Added a new universal driver "1C: KKM-Offline" for working with KKM-offline.
  The driver supports uploading settings and a price list with details on the characteristics and packaging of goods, loading a list of sales reports with details on the type of payment and type of payment.
• Added a new driver "Hexagon: Proton Label Printer", version 1.7.6, developed by "Hexagon".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.4".
• Updated driver "Scancode: Data collection terminals" to version 6.0.7.
  - Fixed an error calling a procedure as a function (Appears when working with 1C:Enterprise 8.3.5.1443 and higher).

The procedure for the initial implementation of BPO and updating from BPO versions 1.0.x, BPO 1.1.x to BPO version 1.2 is described in the document those "BPO.htm implementation procedure".

To use the features provided by the plug-in library in configuration, you must follow the instructions in the document"Using BPO functionality in .htm configurations".

Version 1.1.7

ATTENTION! This release can be used with 1C:Enterprise version 8.3.5.1443 and higher, with compatibility mode disabled.

New features and changes

Version 1.1.7 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added common asynchronous methods for connecting and disconnecting equipment. Synchronous methods are kept for compatibility.
• The asynchronous operation of the following types of equipment is supported: barcode scanner, magnetic card reader, POS printer offline, scales with label printing.
  For barcode scanners and magnetic card readers to work in asynchronous mode, it is necessary to change the configuration code in terms of connecting and disconnecting equipment.
  To support work with offline printers and scales with label printing in asynchronous mode, it is necessary to change to asynchronous methods of working with these types of equipment in the configuration code. For these types of hardware to work in the web client, you also need to install the extension to work with files in the browser.
  The methodology for converting a configuration to asynchronous methods is described in the document "Using the BPO functionality in .htm configurations", sections: "Methodology for converting a configuration to asynchronous methods", "Barcode scanner", "Magnetic card reader", "KKM-offline", "Scales with label printing.
• Errors reported:
  - 30013422: Uploading and downloading to KKM offline does not work in the web client (Google Chrome)
• Driver "1C: Barcode Scanner (NativeApi)" version 8.1.1.1 is prepared for Google Chrome to work in asynchronous mode.
  Reported bugs:
  - 10142713: The test window is shown minimized in the web client (Google Chrome).
  - 10142681: Error localizing driver setup form interface in web client (Google Chrome).

The composition of supplied drivers has been changed:

• Added a new driver "Crystal Service: Pirit fiscal registrars", version 2.01, developed by "Crystal Service".
  
• The driver "INPAS-UNIPOS: Acquiring system driver" has been updated to version 1.1.1.2.
  - Fixed error setting the value of the "Currency code" parameter. Previously, it was not possible to set a currency code other than the default value (810).
• Added support by the current ATOL driver for the following customer display models:
  OMRON DP75-21, NCR 597X, Barcode-miniPOSII PRO, Posiflex PD-201/PD-309/PD-320.
• Updated driver "1C-Rarus: Driver for fiscal registrars MEBIUS" to version 1.1.1.5.
  - Fixed a bug in the "OpenCash Drawer" method. Previously, the cash drawer was not opened.
  - Fixed a bug in the "Connect" method. Previously, when executing the method on some FR models with an open shift, an error message was printed on the receipt tape.

Version 1.1.6

ATTENTION! This release can be used with 1C:Enterprise version 8.3.5.1119 and higher, with compatibility mode disabled.

New features and changes

Version 1.1.6 contains functional changes to the subsystem "1C: Library of connected equipment".

• Added new driver "GAZPROMBANK: Acquiring system driver", version 1.0, developed by "Gazcardservice".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2"..
• Added new driver "USC-EFTPOS: Acquiring system driver", version 1.0.2, developed by Shtrikh-M.
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• Added new driver "INPAS-UNIPOS: Acquiring system driver", version 1.1.1.1, developed by 1C-Rarus.
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• Added new driver "1C-Rarus: Driver for fiscal registrars MEBIUS", version 1.1.1.4, developed by "1C-Rarus".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• Added new driver "Shtrih-M: Fiscal registrar driver (Universal)", version 4.11, developed by "Shtrikh-M".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• The layout with the distribution kit of drivers for fiscal registrars Shtrikh-M version 4.X is excluded from the library. The installation is performed using the supplier's distribution kit.
• The layout with the general distribution of ATOL drivers version 6.X is excluded from the library. The installation is performed using the supplier's distribution kit.
• Updated "1C: Barcode Scanner (COM)" driver to version 8.1.0.4
  Fixed driver bugs:
  
  
• Updated driver "1C: Barcode scanner (NativeApi)" to version 8.1.0.4
  Added new features:
  - Support for USB-scanners operating in keyboard emulation mode under Linux OS.
  Fixed driver bugs:
  - 10131526: Application freeze/multiple repetition of a character entered from the keyboard in case of simultaneous operation of the "1C: Barcode Scanner (COM)" and "1C: Barcode Scanner (NativeApi)" components through the "Keyboard" port.
  - 30009911: Crash when some CipherLab scanners work in virtual COM port mode.
  - 30008098: Incorrect definition in the "Test" window of the COM port from which the barcode was read when working under Linux OS.
  - 30008099: Platform crash after closing the "Test" window when working under Linux OS.
  - 30009836: Displaying the driver settings form in Russian, regardless of the specified regional setting of the infobase.

Version 1.1.5

ATTENTION! This release can be used with 1C:Enterprise version 8.3.5.1098 and higher, with compatibility mode disabled.

New features and changes

Version 1.1.5 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added new driver "ATOL: Fiscal registrar driver 8.X", version 8.2, developed by "ATOL".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".

Version 1.1.4

ATTENTION! This release can be used with 1C:Enterprise version 8.3.5.1068 and higher, with compatibility mode disabled.

New features and changes

Version 1.1.4 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added new driver "Hexagon: Proton barcode scanners", version 1.0, developed by "HEXAGON".
  The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2". The driver supports barcode scanners of the Proton model line.

Version 1.1.3

ATTENTION! This release can be used with 1C:Enterprise version 8.3.4.496 and higher, with compatibility mode disabled.

New features and changes

Corrective release 1.1.3

• Bugs fixed:
  - 00027876: Error with access rights to workplaces when updating external components at system startup.
  - 00028754: Events from input device drivers named "Barcode" and "TracksData" are not handled.

Version 1.1.2

ATTENTION! This release can be used with 1C:Enterprise version 8.3.4.465 and higher.

New features and changes

Version 1.1.2 contains functional changes to the subsystem "1C: Library of connected equipment".

• Added new driver "ATOL: Driver for data collection terminals under MobileLogistics", version 8.2, developed by "ATOL". The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• The driver "1C-Rarus: Felix fiscal registrar driver" has been updated to version 1.2. Added support for fiscal registrars Felix 80K. The driver was developed by 1C-Rarus in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".

Version 1.1.1

ATTENTION! This release can be used with 1C:Enterprise version 8.3.4.437 and higher.

New features and changes

Version 1.1.1 contains functional changes in the subsystem "1C: Library of connected equipment".

• Added the ability to connect new drivers developed according to the "1C: Compatible" standard. The opportunity is provided:
  • Loading into the infobase a driver file supplied as an external component archive, prepared in accordance with the requirements set forth in the document "Technology for creating external components";
  • Loading the driver distribution file into the infobase;
  • Possibility using a driver pre-installed on local computers.

  Drivers must be developed in accordance with the requirements set out in the documents "Technology for creating external components" and "Requirements for the development of drivers for connected equipment, version 1.2":

• Added the ability for the library to work in modality rejection mode. Added non-modal methods for working with equipment. Modal methods are kept for compatibility, and can be removed if necessary ( see document for details"Procedure for implementing BPO.htm").
• Adaptation of screen forms for the Taxi interface has been completed.
• The work of the library in OS Linux is supported.

The composition of supplied drivers has been changed:

• Added a new version of the driver "1C: Barcode Scanner" version 8.1.0, developed in NativeApi technologies. (For details, see the document "Technology for creating external components".) The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2".
• Added a new driver "CAS: Driver for electronic scales for simple weighing", version 1.0.4, developed by "KAScenter" in NativeApi technology. The driver was developed in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2" and supports the following models of electronic scales: CAS AD, CAS AD-H, CAS ED, CAS ED-H, CAS MWP, CAS MWP-H, CAS SW , CAS DB-H, CAS DB-II, CAS PDS, CAS AP-M, CAS AP-EX, CAS ER Junior.
• Added new driver "HEXAGON: Driver for data collection terminal", version 1.1. The driver was developed by "HEXAGON" in accordance with the document "Requirements for the development of drivers for connected equipment, version 1.2". The driver supports the following models of data collection terminals with "Goods 5" software loaded: Proton PMC-2100, Proton PMC-1100, Proton PMC-1200, Proton PMC-8100.
• Drivers "INPAS: AcquiringTerminals" and "SoftCase: AcquiringTerminals" are no longer supported. Layouts with drivers are not supplied as part of the library, driver handlers are left for ensuring the operability of acquiring systems previously installed at the workplace.

The procedure for the initial implementation of BPO and updating from BPO versions 1.0.x to BPO version 1.1 is described in the document those "BPO.htm implementation procedure".

To use the features provided by the plug-in library in configuration, you must follow the instructions in the document"Using BPO functionality in .htm configurations".

Full configuration distribution

The distribution package of the library is available for download for registered ITS users.