Baud rate (9600) is the COM port speed. Relevant for devices connecting to the COM port.
Device identifier is the device number that is sent to the MCR algorithm and can be used to perform different processing depending on the location where a card is read. See Setting Up the MCR Algorithms.
Recoding Setup (chips.bin) (legacy)
Many drivers of identifier input devices support recoding with the use of chips.bin.
The recording technology with the use of chips.bin was developed for r_keeper 6. The chips.bin file is edited by the user with the help of ChipFile.exe. You can download it from the FTP ftp://ftp.ucs.ru/rk7/install/other/CHIPFILE.
The chips.bin file can be automatically loaded from the cash station by the preload program. To do so, add User code recoding file (chips.bin) to the cash station driver list.
After editing, the chips.bin file must be put into base\workmods\chips.udb using WMBRepll. To do so, stop the reference server and then run WMBRepll chips.udb chips.bin. After restarting the reference server and synchronizing with the cash server, preload will take the new version of chips.bin.
Import from chips.bin to r_keeper 7 Data Recoding
r_keeper 7 has the built-in capability of input data recoding that doesn't use third-party lookup tables, such as chips.bin.
You can download the utility at FTP: ftp://ftp.ucs.ru/rk7/install/special/chipsconv/chipsconv.exe.
Run ChipsConv.ехе CHIPS.BIN imp.xml srcformat where:
- <CHIPS.BIN> is the Chips.bin recoding file
- <imp.xml> is the file for import in the XML Import/Export form of the r_keeper 7 manager station
- <srcformat> is an optional format string for source data. By default "%d" is for decimal numbers, which are convenient for recoding after the MCR algorithm. If you need to perform recoding before it, use more intricate formats with prefixes and so on. For eight-digit hexadecimal numbers use "%.8x"
As a result, an XML file will be created containing the imported recordings of the r_keeper 7 format. It can be loaded from the manager station via XML Export/Import.
Main Drivers for Input Devices
PMH43A Mifare Card Reader (usb-com)(pmh43a.dll)
For Windows only. You should install the driver that adds a virtual COM port.
Compatible mode(decimal) - decimal means that the whole card number is sent as a string containing a four-byte number in decimal (can be negative). The format, compatible with r_keeper 6, where the last three bytes of a number are used: the first (the series) is multiplied by 100000 and the number from the last two bytes is added to it.
Use chips.bin — also a format compatible with r_keeper 6.
Hexadecimal means all four bytes in hexadecimal format.
EM9918 RFID Reader (MC_COM.DLL)
Compatible mode (Rkeeper 6) — the format compatible with r_keeper 6 where the last three bytes of the number are used. The first (third) is the series that is multiplied by 100000 and the number from the last two bytes is added to it.
Use chips.bin is also a format compatible with r_keeper 6
Hexadecimal means all five bytes in hexadecimal format.
SIEMENS MC Reader (MC_SMNS.DLL)
Track is the track number for reading. There are three tracks. Other scanning devices read the second track by default.
Keyboard MC Reader (MC_KBD.DLL)
From the keyboard input stream, the driver catches the sequence;XXX…XX<Enter>, where X is 0..9,=. If there are other drivers processing more complex formats, they must be added after this driver.
UCS SRCH 125 (Rev. 3) PS/2(SRC125_3.DLL)
The SRCh 125 driver (firmware 3) displays the number 0..2^30 as a decimal string. If used together with Keyboard MC Reader, this driver must be added after Keyboard MC Reader.
Other Drivers for Input Devices
Guest Call Receiver (guest.dll) — Processing Guest Calls for Waiters
The device sends the button number to the driver. The button number is set for a table in the Button Number property.
Baud rate (9600) — the COM port speed.
ELO and Mouse (ELO.DLL)
For Dos only. Starting from version 10 (installations 184.108.40.206+, 220.127.116.11+), four parameters are added for linear adjustment of incoming coordinates. Adjustment is mostly needed because some touchscreen drivers determine the screen resolution incorrectly. In this case, the screen resolution according to the touchscreen driver should be entered into parameters FixHardHoriz and FixHardVert.
MinDiffClickInterval(4) is the minimal interval (55ms in ticking) between a release and the next closest click (closer than MinDiffClickDistance). Required for eliminating jitter distortion.
MinDiffClickDistance(12) is the minimal distance on the screen (in dots) that allows a quick (less than MinDiffClickInterval) next click. Required for eliminating jitter distortion.
AutoReleaseButton(No) — if Yes, the signal of mouse button release is sent in AutoReleaseDelay after contacting the touchpad, regardless of a real release. If No, signals of releases are sent when they really happen.
AutoReleaseDelay is a delay (55ms in ticking) before sending the release signal if AutoReleaseButton=Yes
FixHardHoriz(0) is an incorrect horizontal resolution (screen width) according to the TouchScreen driver.
FixHardVert(0) is an incorrect vertical resolution (screen height) according to the TouchScreen driver.
FixHardLeft(0) is an incorrect left corner coordinate (received from the TouchScreen driver).
FixHardTop(0) is an incorrect upper corner coordinate (received from the TouchScreen driver).
Chef Keypad (K_99COM.DLL)
PagerMessageType(3) is the pager message type that will be sent to a waiter's pager when called from this keypad.
Message sender code(0) is the code of the employee sending a message to a waiter.
Message() is the message text for a waiter. If empty, a translation of the Cook call waiter text will be sent.