Self-Service Kiosk or r_keeper_SelfServiceTerminal_7 is a system enabling the customer to independently select dishes and pay for the order using a bank card. It can also be called a kiosk, a self-service terminal, and a self-service cash register.
To ensure that the r_keeper_SelfServiceTerminal_7 operates properly you need the following components:
| Processor (CPU) | Minimum (no videos played) Processor Type: Intel Atom Dual Core CPU Speed: 1.6 GHz or higher 1.8 GHz or higher recommended
| |
|---|---|---|
| Video Adapter (VGA) | The video adapter should support Direct X versions 9.0c and up. The minimal video memory (inbuilt and allocated): 256Mb Minimal resolution: 1024х768 | |
| Random Access Memory (RAM) | 1 GB minimum It is recommended using 2 GB and more | |
| Disk Space | A minimum of 20 GB free disk space | |
| Local Area Network | Ethernet (10/100/1000 BaseT) | |
| Interfaces | You need a free USB port to connect the Guardant security key.
|
The SB Pilot bank card authorization driver is given as an example |
This product is available at FTP: ftp://ftp.ucs.ru/rk7/INSTALL/RK7_Kiosk/
r_keeper_SelfServiceTerminal_7 demands a license starting with version 1.0.1.6 . There are two types of licenses for this product:
The license will be linked to a virtual key generated by r_keeper 7 cash server which is to be licensed for at least zero stations.
You can generate a license for zero stations only if you have a master license. |
The virtual key is requested from the license server and is stored in an encrypted form in the HKLV\SOFTWARE\UCS\SelfService (x86) or in the HKLM\SOFTWAREWow6432Node\UCS\SelfService (x64) register section. |
License Verification Mechanism:
The LicReq.exe app is used to generate a license request code. The app is launched from the SelfOrderService.exe working directory.
LicReq.exe should be launched on behalf of the administrator or a user with a right to make records in the register. |
To generate a request code, take the following steps:
Set up the cash server connection in the SelfOrderService.ini configuration file. It is enough to fill in the CashServer parameter in the [XMLIntf] section.
[XMLIntf] ; the cash server's XML interface address. CashServer=127.0.0.1:8787 |
Before generating a license, obtain a master license for this kiosk type (with or without the payment option) and enter the respective type of kiosk operation in SelfOrderService.ini |
It is recommended to use a separate cash server that will be launched on the same computer as the kiosk. |
XML Interface
To ensure the interaction between the Kiosk and r_keeper 7 cash server, you need to add and configure the XML interface:
Starting version 0.7.0, an r_keeper_SelfServiceTerminal_7 (RKeeperKiosk.exe) client interacts with the cash server directly using the HTTP protocol. Take the following steps to set up the protocol:
Specify the <user>...</user> и <password>...</password> parameters in the \App\settings.xml kiosk client configuration file in the <xmlinterface>...<xmlinterface> section:
<xmlinterface> <host>127.0.0.1</host> <port>5252</port> <user>HTTPUSER</user> <password>1</password> |
The kiosk's hardware is supported only by r_keeper 7 cash register and/or third-party bank card authorization software — none of the kiosk's modules needs to directly interact with the peripheral equipment.
You need to add a new printing station before setting up the equipment:
To set up the equipment, take the following steps:
Since SelfOrderService version 1.0.1.12 and RKeeperKiosk version 0.0.3.14, there is a new operation mode — order without payment (Type = 3).
This mode requires another license, see the Licensing section.
The operation principle is similar to the end of the queue technology (ordering from the queue). In the order without payment mode, after saving the order the kiosk forms files in a special XML format to be further processed by the r_keeper 7 cash server.
This mode allows running the kiosk on any computer without using any specialized equipment, such as a fiscal register, PIN pad, card reader, etc.
If the order without payment mode is used, add the Mobile Fast Food Interface to the cash server to enable order processing:
Enter and configure the Type, OrderQueueAddress, PrinterPurposeIdent, and OrderNumAsCode parameters in the SelfOrderService.ini configuration file.
The value of the DirName parameter should be coordinated with the OrderQueueAddress parameter value in SelfOrderService.ini, the kiosk server's configuration file. |
If necessary, fill in the LogName parameter of the interface properties, for example, for debugging or information collection purposes.
This mode operates based on the license without order payment function.
The working principle is the same as for Order without Payment but with the use of Entrance Card technology.
When entering, the guest gets an identification card which can be used to make several orders on different self-service kiosk terminals, for example, at the restaurant, the play area, or the cinema. When leaving, the visitor goes to the cash desk and pays for all the orders with a single payment.
You need to edit SelfOrderService.ini to set up this operation mode.
[XMLIntf] TwoStepsAuth = 0 — do not use two step authorization [Settings] Type = 4 — kiosk operation mode Oder without Payment with Entrance Card technology |
This mode operates based on the license supporting the order payment function.
The settings for this operation mode match those for the Pay and Print Using r_keeper Station and Order without Payment.
Type = 5 — Pay with a Card or at Cash Desk operation mode.
When the order is saved at the kiosk and is later paid for at the cash desk it is recommended to use two cash servers — a kiosk at one cash server and a cash register on the other cash server, otherwise, the order could get doubled at the VDU.
Settings:
OrderQueueAddress=\\PC-QA-10\mobileff — address for sending the orders in the Order without payment mode.
[VDU] sectionUseVDUSpecialUnitNum=1 |
This parameter is needed to ensure that the kiosk order does not get doubled in VDU after payment at the cash desk.
[Settings] Section Type3NumLength=4 |
The length of the order number, printed on the slip. The order number on the slip is used to pay for the order at the cash desk.
<vdu> UseVDUSpecialUnitNum>true</UseVDUSpecialUnitNum> </vdu> To ensure that the order does not get doubled in VDU after the payment at the cash desk. |
<cashPay> <orderNumLength>4</orderNumLength> </cashPay> The length of the order number printed in the slip. The order number on the slip is used to pay for the order at the cash desk. |
The order number should have four digits:
Settings in SelfOrderService.ini:
[Settings] Type3NumLength=3 OrderPrefix=1 Settings in Settings.xml: <server> <cashPay> <orderNumLength>3</orderNumLength> <orderPrefix>1</orderPrefix> </cashPay> </server> |
The orderPrefix is the new setting here: a non-negative integer within the range between 0 and 9. In the settings example above the value equals 1.
Different prefixes should be specified for kiosks working with one cash server. Then numbers from different kiosks will not overlap when paying at the cash desk.
If over ten kiosks operate with one server, the overlapping issue will appear again.
Another obligatory condition for launching r_keeper_SelfServiceTerminal_7 is preparing the menu to be displayed at the kiosk. The r_keeper_SelfServiceTerminal_7 will not run until you configure the menu tree.
Go to Menu > Menu Tree and create catalogs (selector pages) and sub-catalogs to be displayed on the kiosk screen.
The menu tree should have three levels. |
These selectors are then filled with sub-catalogs — second-level selectors. For example, the Juice, Mineral Water, and Alcohol, etc. selectors are added to the Beverages selector, while the second-level selectors are filled with menu dishes. Only dishes can be added to the second-level selectors. You cannot add combo dishes and sub-catalogs there.
Once the tree is created, all catalogs — first level selectors — should be moved to the Initial Choice catalog which is the tree root.
The obligatory condition is that the first and second-level selectors should only be selector pages and not menu items. |
To assign pictures to the dishes in the menu tree, specify the path to the dish picture catalog in the r_keeper 7 manager station. To do this, go to Options > Parameters > Installation > Large images path.
The pictures for the dishes are set up in the Self-Service/Web-Orders item of the dish properties. If there is no such item, go to Options > Parameters > Options usage and enable the Self-Service/Web-Orders parameter.
The self-service kiosk communicates with the cash server through the kiosk server.
The kiosk server supports only one kiosk client. |
SelfOrderService.exe is the main file executed by the kiosk server, and its configuration file is SelfOrderService.ini
Launch SelfOrderService.exe only as administrator! |
Before launching the kiosk server, edit its configuration file. The parameter values specified below should match the r_keeper 7 data:
StationIdent — the identifier of the cash station which will generate orders TableIdent — the identifier of the table for which the orders will be formed WaiterIdent — the identifier of the employee generating the orders MaketIdent — the identifier of the receipt print layout DelReceipMaketIdent — the identifier for undoing the receipt DefaultSelectorIdent — the identifier of the kiosk menu selector in the menu tree Ordertype — a list of order type identifiers available for the kiosk VoidIdent — the identifier of the reason for deleting a dish from the receipt |
A kiosk client is a user interaction interface featuring dish selection, order payment, and manager's functions. The kiosk client's executive files are placed in the \Арр subdirectory.
RKeeperKiosk.exe is the kiosk client's main executive file. It is launched automatically when the SelfOrderService.exe server is launched. The kiosk parameters are stored in two configuration files: configuration.xmlandsettings.xml.
The configuration.xml file contains the main parameters such as functionality, design, etc.
The settings.xml file contains server and debugging parameters.
The versions.txt file contains information about the build current version: server_version — client_version—"*theme"_current_file version.
Check the following parameters in the XML interface section of the settings.xml configuration file (they are added automatically from SelfOrderService.ini after the kiosk's first launch):
Host — cash server address Port — cash server HTTP Port, is entered in the HTTP Server block of the cash server's properties User — the user created for the kiosk's communication with the cash server via the HTTP protocol (http_user) Password — user password StationIdent — cash station identifier TableIdent — table identifier WaiterIdent — waiter identifier MaketIdent — receipt layout identifier DelReceiptMaketIdent — receipt deletion reason identifier |
A manager functions section has been added to the kiosk interface starting with r_keeper_SelfServiceTerminal_7 version 1.0.1.13:
Two-step authentication is used to enter the manager section: in addition to the employee's code and password, you should enter a temporary password, generated automatically and sent to the specified e-mail address.
To set up this function, launch the LicReq.exe app as administrator and log in as a dealer.
Go to the Email Configuration tab and fill in the SMTP server connection parameters, specify the receiver and sender addresses, and be sure to set the Use EHLO!! parameter.
Click Test settings to verify the operability — a testing letter with a temporary password will be sent to the specified e-mail address.
Every time the kiosk is launched, the hash of the current shift is being checked — ShiftHash в SelfOrderService.ini. If there is no hash or it does not match the current date, the hash gets re-generated, and a new temporary password is automatically sent to the specified e-mail address. |
A button for resending the password is added to the manager station authentication window when the <resendShiftPassword>true</resendShiftPassword> parameter is set in the kiosk's configuration file \App\configuration.xml. |
To enter the manager section an employee should have the Close Common Shift and Close Cash Shift rights.
To enter the manager section, do the following:
The kiosk supports graphic file viewing for menu items. The files should be located in the \App\Assets\Dishes subdirectory.
The self-service kiosk only supports the JPEG, PNG, and JPG formats. The BMP format is not supported. |
The current localized version of the system interface is available for automatic downloading from the localize.ucs.ru server starting with SelfOrderService version 1.0.1.71.
See the localization settings parameters in the [LNG] section of the SelfOrderService.ini configuration file.
The Windows user's account used to launch the self-service kiosk should be authorized to view, delete or make records in the branch of the HKLM\SOFTWARE\Wow6432Node\UCS\SelfService (x64) or HKLM\SOFWARE\UCS\SelfService (x86) registers. |
To launch the kiosk, do the following:
To ensure an automatic software launch:
To exit the kiosk, close the SelfOrderService.exe kiosk server — a system tray icon, which will automatically close RKeeperKiosk.exe.
Starting with RKeeperKiosk version 0.8.4., event statuses for which you can enable or disable the kiosk blocking have been added to the configuration.xml configuration file:
<deviceState> <!-- Shift duration has exceeded 24 hours --> <shift24Out lock="true"/> <!-- Paper low --> <paperLow lock="true"/> <!-- Out of paper --> <paperOut lock="true"/> <!-- Printer error --> <paperOther lock="true"/> <!-- Fiscal memory device almost full --> <EKLZNearEnd lock="true"/> <!-- Fiscal shift has exceeded 24 hours --> <fisc24Out lock="true"/> <!-- Fiscal data recorder unavailable --> <fiscAvailableLock lock="true"/> <!-- Unsent receipts intact --> <OFDUnsendedDocsLock lock="true"/> </deviceState> |
You can launch the r_keeper_SelfServiceTerminal_7 in a demo mode. No license is required.
There is no need to launch the cash server in this mode. The kiosk client part, RKeeperKiosk.exe, does not use the kiosk server SelfOrderService.exe but operates with preset text data — a set of XML files.
A test data set is not included in a software distribution kit. If the test data is available, it should be copied to the \App\TestData client subdirectory. r_keeper_SelfServiceTerminal_7 will not start in a demo mode without it. The menu item pictures for the test data set are copied into the \App\assets\dishes standard directory. |
To switch on the demo mode, set the true value for the <demo>...</demo> parameter in the settings.xml configuration file of the RKeeperKiosk.exe app.
<app><!-- Demo mode --><!-- The demo mode has an option of recording the mouse status (up, down, and move). Calling the record panel (shift + "~"). You can also save the status in a file and play from the file. --> <demo>true</demo> </app><!-- Managing the Screen Resolution |
This section will be filled on an as-needed basisб as all the main parameters are described in the .INI and XML files.
settings.xml
OrderNumLength — the length of the order number printed on the slip. The order number from the slip is used for paying for the respective order at the cash desk.
SelfOrderService.ini
Type30OrderNum — this parameter shows the next order number. There is no need to change this value manually as it is done automatically.
A User Guide for r_keeper_SelfServiceTerminal_7 in Russian is available at FTP: ftp://ftp.ucs.ru/books.