...
- Go to Service > Device Signals Processing > MCR Algorithms
- Create an MCR Algorithm of the Masked Input type
- In the Object field, specify the previously bound interface. In our case, this is PDS Interface
- In the Device Types field, select:
- Keyboard
- Magnetic card
- In the Input Mask field, enter a mask. In our case, these are 4 digits — iiii
- In the Scope field, select Interface
- Activate the algorithm and save
- Launch the cash desk and create an order
- Tap the Code from keyboard button and enter the number of an existing card according to the Input Mask
- If the server is running, the card exists and is not expired, information about it will appear on the screen
- To activate a discount or bonus, tap on the picture in the right part of the screen.
FARCARDS
...
Request Repeater
The FARCARDS application is a repeater — it . It receives requests from clients (, for example, from a cash register) desk system, and transfers these requests queries either to the personal card server (— CARDSERV ) — or to an external ( third-party system), and also returns responses to clients from the card server or external system.
A particular feature of FARCARDS is the absence of any built-in mechanisms for storing information about personal cards.
Interaction with an external system is provided by a special interface library implemented according to the FARCARDS specification.
FARCARDS
...
Installation
The installation is performed in the same way as installing the map card server:download
- Download the distribution kit of the repeater current version from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/FARCARDS
...
- Create a directory, for example, UCS\PDS\FARCARDS and copy the contents of the distribution into it
...
- Download the archive with communication libraries from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/netdll.7z and unpack
...
- its contents
...
- into the FARCARDS working directory
FARCARDS
...
Settings
FARCARDS parameters are stored in the FARCARDS.INI configuration file.
General parameters section:
| Code Block |
|---|
[FarServer] |
...
Type = 0 ; repeater operation mode, see below |
...
DLL = RTcp ; the name of the |
...
link library for connecting to CardServ or of the library for communicating with an external system |
...
; Note: in Type=0 mode, the RTcp library cannot be present in the [LinkDLL] section. On startup, FARCARDS checks for this situation and, if necessary, automatically corrects FARCARDS.INI |
...
Log = 0 ; log file detail level (0..3) |
...
Gate = 1 ; parameter number, used in the parameter section of the library specified in the DLL parameter |
...
CloseMins = 5 ; disconnection timeout from CardServ after disconnection of the last client (min), 0 - disconnected immediately. |
...
; Section for listing link libraries |
...
[LinkDLL] |
...
1 = RNB Open |
...
2 = RLocal |
...
3 = pds_netk |
...
; Sections with Link Library Parameters |
...
[RTcp] |
...
Client1 = Remote Resto |
...
Server1 = 127.0.0.1 |
...
Port1 = 2222 |
...
[RNBOpen] |
...
Server = AServ [RLocal] |
...
Port = 1 |
...
[pds_netk] |
...
NetServerName=FarCards |
...
ininame=netk.ini |
There is a "Sub-accounts" the Card Accounts band in print layouts, where you can display all available information on the accounts linked to the card can be displayed. If there are no costsspent amounts, then there is no way to see them.
The following parameters are responsible for displaying expenses spent amounts in the "Customer Information" Client Info window:
| Code Block |
|---|
HasUnitInfo=1 |
...
Show_AccountTypes=1 |
Next, specify in Show_AccountTypes the ID of the expense expenses account, which can be seen in the configurator, in Show_AccountTypes.
FARCARDS
...
Operating Modes
FARCARDS can work in two modes, which are determined by the value of the Type parameter in the [FarServer] section.Mode
Type = 0 Mode
In this mode, FARCARDS connects to the CARDSERV card server and sends all client requests (— for example, from cash servers ) — to it and returns responses.
In fact, this mode has lost its relevance due to the emergence of a more functional distributed PDS configuration (— SYNCARD), as well as the ability of the R-Keeper r_keeper v6 cash server to connect to the card server via the TCP/IP protocol (, starting from version 6.102).
An example of using the Type = 0 mode:there
- There is a restaurant with a working PDS system of personal
...
- cards
...
- There is a second restaurant
...
- , located in a different place
...
- , where you need to use the same cards
...
- When providing TCP/IP communication between restaurants, the second restaurant can use FARCARDS in Type = 0 mode
...
- Access to FARCARDS for cash servers in the second restaurant will be
...
- transparent
...
- , as to a regular CARDSERV,
...
- while FARCARDS via TCP/IP will communicate with the card server in the first restaurant and
...
- retransmit all information exchange
...
- Thus, FARCARS will act as an intermediate link between the cash servers and the card server:
RKCLIENT ⇔ RKSERVER ⇔ FARCARDS ⇔ LAN\WAN ⇔ CARDSERV
An example of setting FARCARDS.INI settings for mode Type = 0:
| Code Block |
|---|
[FarServer] |
...
Type = 0 |
...
DLL=RTcp ; library for |
...
connection with CARDSERV |
...
log = 0 |
...
gate=1 |
...
CloseMins = 5 |
...
; Section for |
...
link libraries |
...
list [LinkDLL] |
...
1=RNB Open |
...
2=RLocal |
...
3=pds_netk |
...
; Parameters section for |
...
connection with a remote |
...
card server: |
...
[RTcp] |
...
Client1 = Far Restaurant ; any unique FARCARDS customer name |
...
Server1 = 192.168.0.99 ; IP address of the remote |
...
card server |
...
Port1 = |
...
3456 ; remote card server port for TCP/IP connection |
...
; Sections with link libraries parameters [RNBOpen] |
...
Server = AServ |
...
[RLocal] |
...
port=1 |
...
[pds_netk] |
...
NetServerName=FarCards (PDS Server name |
...
— interface added to the |
...
cash server) |
...
ininame=netk.ini |
After starting FARCARDS in the Type = 0 mode, the status of the connection to the map card server is displayed in the graphical interface on the Server tab:
Rice. Error connecting to map server
Rice. Connection to the map server was established successfully
If FARCARDS is successfully connected to the map card server, the connection will be displayed in the graphical interface of the map card server on the "Connects" tab (if , in case the CloseMins parameter is non-zero, otherwise, the connection will be short-lived):
Rice. FARCARDS connection status to remote map server
...
Type =
...
1 Mode
In this mode, FARCARDS passes the requests of its clients to the plug-in connected interface library and returns the result of its work to the clients.
In Type=1 mode, FARCARDS acts as a server (, similar to CARDSERV), but the logic for working with personal cards is implemented in the interface library ( and/or in an external system accessed by the interface library).
This mode is usually used to connect the R-Keeper r_keeper cash system with third-party software.
An example of using the Type = 1 mode:
- The customer has his own information system for managing the personal data of employees and/or guests
...
- . It can be either a simple loyalty system or an ERP-class enterprise management system
...
- The customer needs to use the existing system
...
- along with r_keeper cash software
- The specification for the development of the interface library (Extdll.txt) and the FARCARDS distribution kit are transferred to the customer
In the Type=1 mode, only the r_keeper _ 7 POS cash system and the CARDINFO utility can be FARCARDS clients.
In addition to communication the connection with third-party systems, FARCARDS in Type=1 mode is used to connect the R-Keeper r_keeper cash system with other USIES r_keeper software:R-Keeper CRM -
- r_keeper CRM — a customer interaction strategy management system
- Shelter PDS
...
- — a discount system based on Shelter software
- Subscription
...
- — a universal management system
- Premiere
...
- — a cinema automation system
An example of setting FARCARDS.INI settings for mode Type = 1:
| Code Block |
|---|
[FarServer] |
...
Type = 1 |
...
DLL = ExtDLL29.dll ; interface library name |
...
gate=1 |
...
log = 3 |
...
XMLCP=1251 ; setting the code page for XML data |
...
[LinkDLL] |
...
1=RTCP |
...
2=RNB Open |
...
3=pds_netk |
...
; sections with link libraries parameters: |
...
[RNBOpen] |
...
Server = AServ |
...
[RLocal] |
...
port=1 |
...
[pds_netk] |
...
NetServerName=FarCards |
...
ininame=netk.ini |
| Info |
|---|
...
In addition to |
...
editing the FARCARDS.INI configuration file, it may be necessary to set the parameters of the interface library |
...
— see the documentation supplied with the library |
After Starting After starting FARCARDS in Type = 1 mode, the status of the connected interface library is displayed in the graphical interface on the Server tab:
Error loading interface library
Interface library loaded successfully
FARCARDS
...
Launch
Running FARCRDS is possible both as an application and as a service. No security key and/or license required to run FARCARDSNote: is required.
| Info |
|---|
When using the Type =1 mode, FARCARDS launch may depend on third-party components |
...
— see the requirements for the interface library |
The launch mode is determined by the key:
- /DESKTOP
...
- — to launch the repeater as an application
- /INSTALL
...
- — to install the repeater as a service. When installing the card repeater in Windows 7 and higher as a service, the icon will not be displayed in the system tray
- /UNINSTALL
...
- — to remove the installed
...
- repeater service
...
Several repeaters with different settings can be running simultaneously on one computer.
After launch, the repeater icon should appear in the system tray, by . By double-clicking on it, you can open the FARCARDS graphical interface and check the status of the work:
- Server tab
...
- — general information
...
- Chanels
...
- tab
...
- — list of connected clients
...
- DLL
...
- tab — a list of link libraries with parameters and status. If the repeater is launched as an application,
...
- a Shutdown popup menu will be available
...
- on this tab.
Distributed PDS
...
General Information
Distributed PDS is a configuration option for a standard PDS for . It allows the possibility of autonomous operation work of map card servers and periodic data synchronization between servers.
Possible applicationsareas of application:chain
- Chain of restaurants with a single database of personal cards
...
- Geographically dispersed network of public catering points within one enterprise
...
- Off-site autonomous food outlets with personal card service
Benefits of using:no
- No permanent connection between the restaurant and the main
...
- card server is required
...
- All information is duplicated
...
- — in each remote restaurant, a quite up-to-date backup copy of the head base is
...
- created
...
- In case of a breakdown of any database and restoring it from a backup archive, all changes and transactions created since
...
- the backup archive creation will
...
- be sent to the database after synchronization
| Info |
|---|
...
Distributed PDS support has been implemented since the CARDSERV 7.01 card server version |
Scheme of
...
Work
In a distributed PDS configuration, there is always one master (central) map head — central — card server and one or more local (slave) — subordinate — servers.
The main head server, as a rule, is located in the central office, and the local servers are located at remote sites. Synchronization between servers is carried out via the TCP / IP protocol, and it does not matter how the network channel is implemented - : a sufficient condition for synchronization is the ability possibility to connect to the head ( or intermediate ) server by IP address and port.
Standard scheme Scheme of workWork:
Checkout Cash desk ⇔ LAN ⇔
Local CARDSERV ⇔ LAN
⇔
SYNCARD ⇔ WAN (INTERNET) ⇔ Head CARDSERV
Additionally, you can include intermediate map card servers ( in any quantity), for example:
Checkout Cash desk ⇔ LAN
⇔ Local CARDSERV
⇔LAN
⇔ SYNCARD ⇔ WAN (Mobile 3G INTERNET) ⇔ Intermediate CARDSERV
⇔LAN
⇔ SYNCARD ⇔ WAN (ISP INTERNET) ⇔ Head CARDSERV
Distributed PDS
...
Configuration
The distributed PDS configuration includes standard PDS modules (map — card server, map card editor ) — and an additional SYNCARD utility for synchronizing map card servers.
The card server ( CARDSERV ) can operate in four modes:
- Single
- Head
- Local
- Intermediate
...
- — local + head
...
- .
The server operation mode depends on the label tag in the CARD.UDB database. The label tag is put down specified when the SYNCARD synchronizer is connected for the first time - if . If SYNCARD is not used, there are no labels tags in the database (— a single server).Important: Once put down the label
| Note |
|---|
Once specified, the tag remains in the database FOREVER |
Tag Conversion Options!
Label conversion options:Single
- A single server can be made
...
- head, at any time
...
- A single server can be made
...
- local — subordinate — only if its database is empty
...
- A local server can be made
...
- intermediate, i.e. local + head
...
...
- A head server cannot be made Intermediate.
Thus, you can grow the server tree one by one, connecting it a new server as Local local to the running Headhead, intermediate, Intermediate or Local local (then it will become Intermediate) server.
If necessary, you can connect to any of the servers using the PCARDS map card editor.Important:
| Note |
|---|
You can edit data using the PCARDS |
...
card editor only on servers in |
...
single or |
...
head mode. On the |
...
local and Intermediate servers, only viewing data and reports is possible. |
| Info |
|---|
...
You can find out what mode the |
...
card server |
...
works in from the PCARDS application |
...
: go to Help > About > Access: Full, Head, Lower, Transit. The server operation mode is also displayed |
...
at the |
...
card server icon: H |
...
— head, L |
...
— local |
Invalid
...
Actions
The table below describes illegal invalid actions with the map card server database, the consequences to consequences to which they lead, and ways to resolve them:Action to take Consequence Remedy
| Actions | Consequences | Solution |
| Copying the |
...
| card server database from one local restaurant to another and connecting them to one |
...
| common Head server | Complete data desynchronization! |
|
...
|
...
|
...
|
...
|
...
|
| If you try to use a non-empty database that is not local in a local restaurant |
...
| , SYNCARD will not work with it | Error message: "Can |
...
not mark [Local] as Local DB because it is not empty" |
...
|
...
|
...
|
...
|
...
|
...
|
| If you copy an empty database of the |
...
| head server to a local restaurant, SYNCARD will not work with it | Error message: " |
...
Can not mark [Local] as Local DB because it is Head DB" |
|
...
|
...
|
...
|
...
|
...
|
| If you copy the |
...
| local database from the restaurant to the |
...
| head server, SYNCARD will not work with it. In addition, the PCARDS |
...
| card editor will not allow editing data in this database. | Error message: " |
...
Can not mark [Head] as Head DB because [Local] DB is not empty" |
|
...
|
...
|
...
|
...
|
| Info |
|---|
...
*The |
...
card server automatically creates archive copies of the CARD.UDB database once a day |
...
Installing Installing SYNCARD
Before installing SYNCARD, it is assumed that the following conditions are should be met:the
- The working configuration already has a
...
- head or
...
- single card server
...
- There is a connection via TCP/IP
...
- between the local and head or single servers. For example, a VPN with the ability to connect by IP address and port to the computer on which the
...
- head server is running
...
The installation of the SYNCARD synchronization utility is usually performed installed on the same PC where the local map card server is installed or planned to be installed, or on another PC on of the same local network.
To install SYNCARD you need, do the following:install
- Install a local
...
- card server
...
- . if the
...
- card server was installed earlier and has already been used, you must install an empty CARD.UDB database
...
- Download the distribution kit of the SYNCAD current version from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/SYNCARD
...
- . The version history can be
...
- viewed in the HISTORY.TXT file
...
...
- Unpack the contents of the archive, for example, to the \UCS\PDS\SYNCARD directory
...
- Copy the
...
- RTcp.DLL link library to the same directory
...
- . The built of the current versions of
...
- link libraries can be found at FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/netdll.7z
...
| Info |
|---|
...
Considering the note regarding the RLOCAL.DLL library, only RTcp.DLL must be used |
...
for connection between SYNCARD and the local |
...
card server, even if both servers are on the same PC. |
Next, you need to configure edit the main configuration file SYNCARD.INI:
| Code Block |
|---|
[Options] - General |
...
parameters section |
...
Period = 10 |
...
- Synchronization period in minutes — in how many minutes after a successful exchange the next communication session will happen
[Local] - Section of settings for connection with the local card server
DLL = RTcp - DLL for connection with the local card server
Gate = 1 - number of parameters of DLL connection
[Head] - Section of settings for connection with the head card server
DLL = RTcp - DLL for connection with the head card server
Gate = 2 - number of DLL connection parameters
Modem = 0 - a modem usage — more precisely, establishing a connection through a Windows connection: 0 - do not use, 1 - always use, 2 - use only if there is no direct connection
TryLink = 1 - only works if Modem = 2 — number of unsuccessful direct connection attempts before dialing via modem
[Modem] - Section of modem connection settings
PBEntry = 3GMobile - connection name created in Windows
User = - specifying the user for authentication
Psw = - specifying password for authentication
Domain = - specifying the domain for authentication
[Rtcp] - Section for link library parameters
Client1 = SYNCARD - unique client name to connect to the head card server
Server1 = 192.168.0.1 - IP address to connect to the head card server
Port1 = 5555 - port for connecting to the head card server
Client2 = SYNCARD - unique client name to connect to the local card server
Server2 = 127.0.0.1 - IP address to connect to the local card server
Port2 = 4444 - port for connecting to the local card server |
SYNCARD.EXE can be launched with the following keys:
- /INSTALL — to install as a service — recommended
- /UNINSTALL — to remove an installed service
- /DESKTOP — to
...
- launch as an application
After the first launch of SYNCARD, the databases will receive all the necessary tags automatically, and if there is a connection between the servers, the data will be synchronized.
Additional Applications
CARDINFO
...
— Card Information
The CARDINFO application is used to obtain basic information on a personal card without launching a card editor and/or cash station.
It can be used in conjunction along with the PCards card editor or as a standalone application as part of the PDS, no additional license or security key is required.
| Info |
|---|
...
Since CARDINFO 1.10, work with a card reader is supported |
...
, setting is similar to PCARDS |
...
...
Usage with PCards
To share For using CARDINFO along with the map editor you needcard editor, do the following:copy
- Copy the distribution kit of the current version of the application from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/CARDINFO and unpack its contents into the PCards working directory
...
- Create a desktop shortcut
...
- for the
...
- application launch
...
...
- If necessary, connect a card reader, the setting is similar to PCARDS
...
| Info |
|---|
The CARDINFO card reader application uses the same drivers as PCARDS |
...
— if PCARDS is already configured to support the card reader, no additional SYNCARD configuration is required. |
...
Using CARDINFO as a standalone application
To be used use CARDINFO as a separate application as being a part of the PDS, you mustdo the following:copy from ftp ftp
- Copy the distribution kit of the application current version from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/CARDINFO
...
- Unpack the contents of the archive, for example, to the \UCS\PDS\CARDINFO directory
...
- Copy the
...
- link library to the working directory of the application
...
- — it is recommended to use RTCP.DLL
...
- If it is necessary to display the name of discounts, copy the corresponding PCGET.DLL library and the libraries necessary for its operation to the application working directory
...
- — see the description of the PCARDS
...
- settings
...
Create or copy the RKEEPER.INI file and configure the settings
...
— similar to PCARDS
...
:
Code Block [PCards]
...
CSLinkDLL = RTcp - link library name
...
CSLinkGate = 1 - client number
...
, added to link library parameters
...
[RTCP]
...
Client1 = CARDINFO - unique client name to connect to the card server
...
Server1 = 127.0.0.1
...
- card server IP address Port1 = 3030 - TCP port for connecting to the card server- Create
...
- a shortcut on the desktop to launch the application
...
- If necessary, connect a card reader, the setting is similar to that of PCARDS.
Cards List Import
...
The CARDIMP application is used to upload a list of maps cards from a text file in the specified format to the map card server.
The text file format is exactly the same . file format as that for importing a list of cards in the PCards application
To install CARDIMP you need:download , do the following:
- Download the distribution kit of the application current version from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/CARDIMP
...
- Unpack the contents of the archive, for example, to the \UCS\PDS\CARDIMP directory
...
- Copy the
...
- link library to the working directory of the application
...
- — it is recommended to use RTCP.DLL
...
- Create a CARDIMP.INI file and configure the settings:
| Code Block |
|---|
[options] |
...
LinkDLL = RTcp - link library name |
...
[RTcp] |
...
Client1 = - unique name of the client to connect to the |
...
card server |
...
Server1 = |
...
- card server IP address Port1 = - TCP port for connecting to the card server |
The application does not require a security key and/or additional license to run.
The application does not have a user interface and is launched from the console (— command line ) — with the following parameters:
| Code Block |
|---|
Cardimp.exe Login Password FileName |
where
- Login
...
- — username for authorization on the
...
- card server
- Password
...
- — user password for authorization on the
...
- card server
- FileName
...
- — name of the imported file with the list of
...
- cards
Database Maintenance
If the card server database file ( CARD.UDB ) is too large, you can use the DATACUT application to build group old transactions that do not need detailed reporting.
The principle of the application work:transactions
- Transactions in the deleted period that change the balance of funds will be summarized in one transaction for each account
...
- Other transactions of this period will be deleted
...
- All other information in the database will remain unchanged
...
- After creating a new database, the old database is not deleted, but renamed to a BEFORE_CUT_yyyy-mm-dd file, where yyyy-mm-dd is the date before which transactions were deleted
...
| Note |
|---|
The application does not allow deleting transactions in the database for the last 90 days. |
...
| Note |
|---|
When using a distributed PDS |
...
— SYNCARD |
...
, before deleting transactions, all databases of the server tree must be synchronized |
...
— the last synchronization |
...
should happen no more than 90 days ago |
...
. |
To use the application you need:download , do the following:
- Download the distribution kit of the application current version from FTP ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/DATACUT
...
- Unpack the contents of the archive into the working directory of the CARDSERV card server
...
- Stop the CARDSERV card server
...
- Run the application and wait for successful database processing
...
- Start the CARDSERV card server and check the operation.