Adding a new fiscal printer

From Microinvest

Revision as of 10:23, 16 March 2018 by Marketing (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

[ Microinvest] uses a state-of-the-art fiscal control technology centered in a single library. A single DLL file contains the drivers of all fiscal devices. This monolith structure allows simplicity of operation, flexibility and complete versatility, even with mixed use of devices from different manufacturers in one system.


Adding a new printer

There are situations where a fiscal printer is available but is not described in [ Microinvest]'s programs. In this case, the following may be experimented:

  • Check the exact model of the fiscal device;
  • Find the manufacturer and the model of other devices from the same manufacturer;
  • A similar model is being set up by the same manufacturer;
  • Basic tests are performed to verify that the device is working.

By the above scheme, it is possible to operate successfully with a device outside of the list of supported models, for example, the Datecs FP2000 works seamlessly by setting up the Datecs FP1000. If this is not working, then it is necessary to proceed with expanding the library and create an individual driver for the new device.

Creating and adding a driver

Drivers are complex programming modules for managing certain peripherals. Only highly qualified developers can build such drivers and add them to trading systems. That’s why a procedure for adding a new device to Microinvest products is described.

Adding a new fiscal printer procedure

Adding a new fiscal printer requires a number of different activities:

  1. Collecting information on the device
  2. Ensuring the program protocol for communication between the computer and the fiscal device;
  3. Programming the protocol according to manufacturer's parameters by Microinvest programmers;
  4. Test the connection to the device using a real device and sample tasks;
  5. Build a new library and replace it in an existing version of the program. Or, directly create a new version of the program.

This procedure may take from 1 day to several weeks depending on the complexity of the protocol and system.

Information needed

Fiscal printers work on a complex communication protocol, which is their "language" for data exchange. Therefore, creating an individual driver requires a detailed description of the protocol and the technology of work. Providing a precise protocol is fundamental to all subsequent stages of future driver development for the new system. Typically, the protocol is provided by the device manufacturer at the request of a regional partner in the country concerned.

Testing the new device

Once the data exchange protocol is built up, a device testing procedure follows. In this case, real-time operations with the device are performed, and it checks how it works and how it exchanges data with the application program. In most cases, testing can be performed remotely via the Internet. In rare cases, the presence of the device itself in developers is required. In this case, developers must provide an experimental copy of the fiscal printer for testing and analysis.

Updating the DLL library with devices’ drivers

Once the new driver is ready, a procedure is needed to update the DLL library with the fiscal device drivers. The following sequence is performed:

  1. The new DeviceManager.dll library is copied to the Microinvest Storage Pro Light folder;
  2. Opens a DOS window with administrative rights;
  3. In the Microinvest Warehouse Pro Light folder, the regsvr32 DeviceManager.dll command is executed

Replacing a library should be done by an experienced specialist, otherwise the system will not be able to work properly.


Building and using a fiscal device driver is a complex and responsible task. All partners, equipment manufacturers, programmers and consumers are involved in the right goal. For effective implementation of all necessary actions, quality documentation and a "hot" link for consultation between the units should be provided.

Useful Links

Personal tools