1.1.1. In RK7 there is a chain of objects that makes printing work: driver -> logical device -> printing purpose -> purpose assignment.
1.2.1. Fiscal printers and modules work with its own protocols (getting raw data) independently from RK7 layouts.
1.2.2. There is special manual on fiscal .
1.3.1. No additional licensing required.
2.1.1. You always use 2 level drivers together: interface (port) and printer. No need to set interface (port) without device that uses that.
2.1.2. There are several network, serial, file interfaces (ports).
2.1.2.1. "IP printer port (integrated)" is the driver for corresponding ucs ethernet UDP printer interface .
2.1.2.2. "Print to TCP/IP printer" is the original supplier TCP printer interface driver.
2.1.2.2.1. This driver can sent data to any TCP socket over the network, including other applications.
2.1.2.2.2. You can set DNS name instead of IP in "Printer address" property.
2.1.2.3. 'Print to file' port made to save printed data to 'File name' text file. Documents will be appended inside given file (not overwrited).
2.1.2.3.1. If you set not valid 'File name', documents will not be saved to default (working) folder.
2.1.2.4. Print to windows printer or port
2.1.2.4.1. This port driver you have to use in case USB printer (or other one) installed in OS windows.
2.1.2.4.2. In driver properties you have to specify windows printer name or windows port name.
2.2.1.1. Windows printer
2.2.1.1.1. "Windows printer" is the only one graphic printer in RK7 (others are not suitable for graphic layouts).
2.2.1.1.2. This driver uses OS print command to print data. It is like "port included" device in RK7. So, no need to search for port driver or try adding to port drivers. Just put p_win.dll driver to the list on cash station.
2.2.1.1.3. This driver encodes all the data coming from any RK7 layout to bitmap image. Because of image output resulting text print quality (brightness, clearness) will be lower than in text mode.
2.2.1.1.4. For text only print normally you have to use 'Print to windows printer or port' port + [printer protocol mode] driver (see 2.1.2.4.), not 'windows printer'. But exceptions possible (for example, if current language characters are not supported by the printer firmware = no character table).
2.2.1.2. Plain text
2.2.1.2.1. Use Plaintex.dll driver with some port, usually with "Print to file" driver.
2.2.1.2.2. This virtual text printer will output only those lines from document layout applied, without any device-related commands.
2.2.1.2.3. This printer used for debug and providing data to external systems, as well as register (save history) function.
2.2.2.1.Choose your printer driver named as model.
2.2.2.2. If no printer named as yours found, try to use another driver with the same emulation type.
2.2.2.3. Assing the driver to logical device.
2.3.1. That is RK7 system "device" object created to be used as link in another objects assignments.
2.4.1. Cash station
2.4.1.1. If you assign logical printer to printing purpose in cash station properties, this printer will be sent to in case printing initiated by given station of some document with selected purpose.
2.4.2. Restaurant
2.4.2.1. If you assign logical printer in restaurant properties to some printing purpose, this will make all RK7 stations in selected restaurant print documents with selected purpose to this device (one and the same printer for restaurant).
2.4.3.1. Service printers to be assigned on restaurant level too, but in this case you have no printing purpose choice (it is hidden), because these documents are all of one preset purpose: "service print".
2.4.3.2. As for service print, you have 2 in 1: printing (service) scheme and logical deivce assignment in document layout properties.
2.4.3.3. If you want to distribute menu items by different places (where they are cooked), you should create (use) one classification for that. Inside this classification ('for service print' by default) you should create categories for each dish preparation place.
2.4.3.4. For each printer (place) you have to create service document (in 'service scheme') and choose category from classification, which to print.
2.4.4.1. You set backup logical printer in order to have printing redirection to that device in case main one cannot do its service print work.
2.5.1. These devices print data using layout and filler data from its memory.
2.5.2. RK7 sends data to fiscal memory before print operation.
2.5.3. In order to print only fiscal document you have to assign empty document layout in RK7 scheme.
2.5.4. Fiscal issues described in.
2.6.1. winprint.exe is a printer host (station), described in.
3.1.1. Find all additional information on documents and layouts in specific manual .
3.2.1. Printing purpose is the final point where device settings meet document settings (see scheme above).
3.2.1.1. To make the system print some document layout in specific cases to specified destinations (or just make it print) you have to assign the layout view to the printing purpose.
3.2.1.2. On the other side, you have to assign logical printer to printing purpose for each cash station (even if it was done on the restaurant level).
3.2.2. There are several ways of layout assignment.
3.2.2.1. Using parameter as shown below.
3.2.2.1.1. Manager station receipt copy (is printed to windows printer installed in current rk7man.exe OS like other manager station reports).
Set in Options->Parameters->Manager station settings->Visualization->'Receipt maket'
3.2.2.1.2. Common shift report (cash station).
3.2.2.2. By means of Printing scheme.
3.2.2.2.1. By means of service scheme.
3.2.2.2.1.1. In this case, you assign logical device to document view (without printing purpose), because in this case printing purpose is predefined = 'service print'. By this "hidden" printing purpose document views are excluded from common printing scheme and put to 'service scheme'. By the way, 'service print' purpose documents are chosen by "hidden" document type 'service print'.
3.2.2.2.2. In common printing scheme.
3.2.2.3. In printing scheme you assign layout view on 3 separate operation-separated printing events.
3.2.2.3.1. Main printer
3.2.2.3.2. Backup printer
3.2.2.3.3. XML printer
3.2.2.3.3.1. This printing event is triggered with Main printing event of this document view if XML layout assigned for it.
3.2.2.3.3.2. If no Main/Backup printer event assigned to given document view, XML printer event is triggered on Print operation independently.
3.2.2.3.3.3. This operation will output XML document formed using "XML layout" mentioned to the printing purpose/logical device or interface specified in "XML printer" view property.
3.2.2.4. In printing scheme you assign layout view(s) on 3 separate operation-separated printing events.
3.2.2.4.1. Main layout
3.2.2.4.2. XML layout
3.2.2.4.3. Macro layout
3.2.2.4.3.1. This layout will be printed to the same purpose (printer) as Main layout, including backup printer assignments.
3.2.2.4.3.2. This type layout(s) view(s) follow Main printing event and being sent to printer right after Main layout
3.2.3. There are several ways of output device (interface) assignment.
3.2.3.1. Logical device on station.
3.2.3.2. Logical interface on station or server.
3.2.3.2.1. Logical interface on cash or print station.
3.2.3.2.2. Logical interface on cash server.
3.2.4. As for printing (data formation and transfer to destination), the process goes like on the following scheme:
4.1.1. RK7 uses Windows codepage for documents (russian = cp1251), not DOS or unicode (and printer usually has DOS one), that is why you have to set up encoding strings in some printer drivers, such as TM200, to DOS codepage (russian = cp866).
4.1.1.1. If you have windows codepage in your printer - delete "decode from" and "decode to" driver properties content. But check that you have one and the same codepage in OS and printer (some languges have several windows CP).
4.1.1.2. As for other languages, you have to prepare "decode from" and "decode to" yourself using your character set tables.
4.1.1.3. To set decoding shown above in RK7, check this (example, decode from "C0" - WIN):
and this (example, decode to "80" - DOS):
4.1.1.4. You set "from-to" pair for each symbol which has different position in character set(s).
4.1.2. Usually you are able to change default printer codepage with specific utility came from manufacturer. In other cases you have to upgrade printer firmware, even by the use of additional tool (hardware).
4.1.3. You are able to check printer codepages of most device by holding "FEED" button on its start (for example, TM200PLUS printer test page you could see below).
4.1.4. If your printer uses windows codepage, remove encoding lines 'decode from' and 'decode to' (delete content) from printer driver settings in RK7.
4.1.5. Some printers have two-byte character settings. You have to choose one-byte mode (dip switch 4 on shown below).
4.1.6. You also have to initiate your printer charset before each print job using driver 'Initial sequence' property (1B7417 for russian cp866 shown below). Find your initial sequence in your printer manual.
4.2.1. In most cases you can't get cash drawer status from printer connected device.
4.3.1. To print image from printer memory you have to upload your logo to printer first of all using supplier utility.
4.3.2. After that you have to add <Logo 1> command to layout.
4.4.1. You can assign other station printers for any purpose if parameter [Enterprise working settings]->[Printing]->[Allow cross-restaurant printing] enabled.
4.4.2. You can redirect receipts (special document type) if set 'anywhere' in parameter 'receipt redirect type'.
4.4.3. Do not forget to set [TCPDNS] to redirected servers in each ini file.
4.5.1. For windows printer it is essential to use monospaced fonts. Find or make monowidth font for your language and charset used in RK7.
4.5.2. You set font in driver parameters
5.1.1. Set full pathway with filename in cash server "Printing" section "Print Log Path" parameter.
5.1.2. Enable "Log All" on each logical device which you need to log (associated with this server stations).
5.2.1. Find out correct settings using changes method.
5.3.1. Set known working configuration.
5.4.1. Device configuration should be done using manufacturer supplied manuals and utilities.