0. General

0.1. Software

0.1.1. Mobile waiter notepad software has beed designed for mobile devices.

0.1.2. There are iOS , Android and WinCE versions of MobileWaiter7.

0.2. Hardware

0.2.1. iOS version is designed for iPod touch or iPhone (Apple). iPad mini also possible.

0.2.2. Android OS version fits any smartphone or tablet with 5 inch + screen size. Screen resolution designed for 1270*720px, 1920*1080px. Android 4.4+ necessary.

1. Setup manager station

1.1. Station

1.1.1. To use MobileWaiter7 on PDA (WindowsCE or iOS or Android) as waiter station you are to take some real cash station code for it (PDAs work on behalf of one regular cash station).
1.1.2. Go to service>stations and devices>[your restaurant]>[your cash server] and add new windows cash station (type not “Pocket Station”, but “Cash Station”) to the suitable cash server if you don’t have one yet. If you have at least one cash station there it is no need to create special one for PDA.
1.1.3. Cash station "main" section -> "code" property must be the same as "StationCode=" in tms7.ini file.


1.1.4. So, there must be at least one windows cash station in your cash server, where you are going to put interface (see below).

1.2. Interface

1.2.1. Add “XML interface for windows” to corresponding cash server (not station).
1.2.2. Set "options" -> "port" the same as "ServAddr=" (number after colon) in tms7.ini file.


1.2.3. Make sure that there is no other interface assigned to the same port.
1.2.4. Check that this interface is set to the logical one. Do not assign one and the same interface driver to several logical interfaces (see http://support.ucs.ru/en/node/5670).
1.2.5. Set "options" -> "CryptKey" value the same as "ServPWD=" parameter value in tms7.ini file.

2. Files and folders

2.1. Necessary files

2.1.1. What files are there in the distributive? These files are required on TMS7 PC: MobilGuard7.exe (server controller), mwnsettings7.xml (client settings), TMS7.exe (server executable), tms7.ini (server settings) – and two (empty) folders: XMLs and TMP. These files are required on MW7 Windows CE (Mobile) PDA (placed to the folder “UCS” in the root of its filesystem – obligatory): MobWaiterNP7.exe (client executable) and mwnsettings7.xml (this xml should be preloaded normally, that’s why only “.exe” is obligatory, but you have to input TMS7 server IP and port in client application for that). Concerning iOS iPod touch and iPhone devices, you need to upload RkMobWaiter.app with iTunes (the same rules concerning first connection to server and mwnsettings7.xml uploading, see 4.1.2.). In many cases different TMS7 and MW7 versions won't operate together properly. You have to update both server and client at the same time. MobileWaiter7 version you could see in the settings mode of the WinCE application. When you talk about the software described in this manual, both server and client, refer to this version (saved to TMS7 log file on each start). In MW7 distributive there is also \LUpdater\ folder with a Guardant key licensing related application LUpdater.exe.

2.1.2. Where could you get genuine MobileWaiter (7) software? Original and proved to work WinCE PDA software you have to copy from UCS file server /r-keeper/WaiterNotepad/Current/TMS/RK7/ folder. Note that MW7 in the RK7 distibutibe (old and deprecated) is compatible with only this RK7 version (at least no guarantee in case of other RK7 versions). iOS software (client iPod application) you have to download from iTunesStore (RkMobWaiter). TMS7 server take from UCS file server /ftp://ftpint.ucs.ru/dealers/r-keeper/WaiterNotepad/Current/TMS/ folder (one server for WinCE and iOS and Android client types). Pay special attention to compatible versions of TMS7.exe and PDA application (take both Apps at the same time from given here locations only), otherwise you get error "incorrected protocol number". Functionality depends on license, applications are the same. See available functions difference in licensing (3.2.7.).  Android application you have to download from Google play. You are able to download only newest (current) version - so, you must use only newest TMS server as well.

2.1.3. Compatibility Mobile application must be compatible with TMS server. Since you can get from "stores" only newest version of application, you must get newest TMS server from UCS FTP. TMS server must be compatible with RK7 cash server. In TMS server log file you can check compatible RK7 version (minimum).

2.2. Setup files

2.2.1. General information You are to change settings in 2 files (by default, only IP addresses and RK7 objects codes): tms7.ini (for TMS7.exe) and mwnsettings7.xml (for MobWaiterNP7.exe and RkMobWaiter.app). The mwnsettings7.xml you should put near TMS7.exe (in case of firewalled network you might have a problem with this file preloading to PDA or when several TMS7 servers are used to connect to different cash servers on the same network, then put mwnsettings7.xml near MobWaiterNP7.exe also). The tms7.ini you should put near TMS7.exe.

2.2.2. tms7.ini File content format

TruncLogSize = 10000000
QueryRequest = 1
MenuQuery = 1
ModQuery = 1
CommModQuery = 1
PersQuery = 1
TableCheck = 1
TableCheckLine = 1
PrinterConfig = 1
PrinterCommand23 = 1
PrinterCommand23Data = 1
PrinterDispatch = 1
PrecheckPrint = 1
Answer = 1
Socket = 1
NewTableDetaile = 0
SendRecv = 1
CardInfo = 1
RemovePreCheck = 1
RK7CommandLog = 1




Use=1 Settings in tms7.ini file [PAYOFF] section configures payments (for FULL license only) from PDA. To enable payments set "Active=" parameter value to "1", to disable payments set Active=0. If you set Active=1 make sure that both "ReceiptMaketCode=" and "PaymentCode=" parameters are set properly. "PaymentCode=" is a RK7 currency code to pay with (you are able to make paymets by means of PDA with only one cuccency set in this parameter).

"ReceiptMaketCode=" is a RK7 receipt view code from options > printing > printing schemes. If you use compulsory guest types, set DefGuestType= (guest type "Ident" from object properties) in [RK7SERV] section of tms7.ini. Otherwise, "Use guest type" RK7 parameter must not be set to “compulsory property”, then choose “optional property” or “don’t use”. DefGuestType=0 means no guest type will be assigned to the order. In section [LOG] you may enable or disable messages that are being written to TMS7.LOG file. Parameter "Title=" in [TMS] section sets the server system name. You have to change this parameter in case of running two or more TMS7 servers in one windows operation system (servers must have different system names). In this case you must change "Port=" parameter also so that each server has unique port (keep in mind changing corresponding parameter "PORT=" in mwnsettings7.xml <SERV/> tag). [TMS] section "Port" parameter sets main communication port (TCP) to be listened by TMS server. If two or more TMS7 servers in one windows operation system use one Guardant key, you have to set parameters "UseLic=" and "Index=" in [TMS] section. "UseLic=" is a number of PDAs that connect to this server copy, "Index=" is a priority of this server copy in license counting. [TMS] section "KeyPublicNo=" parameter is used in case of several Guardant keys are plugged to one TMS7 server PC. Its value must be end 9 figures from the proper key number taken from LUpdater.exe upper line (without first 2 figures  - because of those 2 figures are random extra info - not key number; see proper key number in driver utility for compare).  This parameter value is simply DECIMAL G.key number (not HEX). If you have only 1 G.key in this OS, no need to set this parameter. [PRECHECKINFO] section "MaketCode=" parameter value is RK7 bill view code (from options > printing > printing schemes). "BySeats=" parameter ="1" value turns on printing bills by seats. "PrecheckStationCode=" parameter value is RK7 cash station code which settings are taken for bill printing (see 1.1.3.). [COMMONMOD] section "Ident=" parameter is fictive mobile waiter common modifier group (which modifiers are available to add to any dish) ident, no RK7 modifier group code or ident must be the same. [SVCNAME] - name of service if you will install it like Windows service (if not set - TMS7 by default) [PRICESCALE] section "Scale=" parameter value is the PriceAmount multiplier (reduces amounts shown and being entered in PDA application; by default =1; do not change without special need). [DRAFTTODO] section "ActiveCourseCode=" (for orders to be immediately cooked), "DraftCourseCode=" and "CookLaterCourseCode=" (for delayed orders) are RK7 course codes (active, draft and delayed) correspondingly which assigned to orders made/changed using PDA application. [ORDERCATEGORY] section "Code=" parameter is the RK7 Order category to be assigned to new orders created from PDA application. [ALTNAME] section "Use=" parameter sets menu item object property name to show as dish name on PDA (it could be "Name", "AltName", "ShortName"). If set dish property is empty, "Name" will be shown for such a menu items (object Name cannot be empty in RK7). [RK7SERV] section parameters "StationID" and "PayStationID" you are to use instead of "StationCode" and "PayStationCode" correspondingly in case you have more than one restaurant in your references. Their values are RK7 cash station Ident(s).

2.2.3. mwnsettings7.xml File content format

<?xml version="1.0" standalone="yes"?>
<RK Ver="7"/>
<PING IP="" WaitTime="10" TryNumber="3"/>
<SERV IP="" PORT="610"/>
<TIMES Sync="2" ST="20" Serv="60" TmpEx="0" Lgf="0"/>
<CAN DD="0" CC="1" QOS="0" CLC="0"/>
<MENU UseNameSearch="1" Cash="1" UpTm="5"/>
<ConPar CWT="50"/>
<LANG Use="15"/>
<GUESTS DefNum="0" DefTab="0"/>
<MSGQ SMN="3"/>
<CHPACK Pack="0"/>
<MMPRCS TC="666"/>
<RK7 EditDraft="1" UseCources="1" Precheck="1" BigMenu="1" />
<ORDFCL T="40" H="234" V="1" CW0="62" CW1="256" CW2="68" CW3="90" TFSZ="22" SFSZ="32" LFSZ="28" QDN="3"/>
<ORDMBTN W="155" H="52" DX="3" DY="3" BW="32" BH="32" BAL="1" TXTW="105" TXTH="22" TXTMH="15" TXTFW="400"/>
<ORDMSBT W="32" H="32" DX="5" DY="5" TH="16" TL="3" USE="1"/>
<BMPCASH SID="100" EID="5000"/>
<Plan Use="1" Scale="0.66666" TH="14" TW="700" TBW="50" TBH="50"/>
<PlanNR Use="1" Scale="0.33333" TH="10" TW="700" TBW="50" TBH="50"/>
<EXTDEV Use="0" CrdFmt="1" COM="7" CHRST="111"/>
<KEYS K1="193" K2="0" K3="195" K4="196" K5="197" K6="13" K7="205"/>
<CHKFM PW="32" QRO="11" SW="8" SAD="2"/>
<CRSS Use="0" TI1="384" TI2="386" TI3="387" TI4="388"/>
<COMBO CReg="2"/>
<FFOOD BegNo="300"/>
<Messages SoundFile="mess.mp3" SoundInterval="5"/>
<TablesView CollButtonTitleHeight="20" CollButtonTitleWidth="46" CollButtonHeight="90" CollButtonWidth="90" CollCount="3" RowHeight="106"/>
<OrderView CourceItemColor="15845119" CourceBckgColor="16773098" ComboItemColor="13038079" ComboBckgColor="15728618" ModOffset="20" ComboOffset="10" NewBckgColor="16313310" PaidBckgColor="8355711" SavedBckgColor="5987327" DraftBckgColor="54741" SumWidth="100" DishTitlePriceWidth="60" DishTitleQNTWidth="40" DishTitleCodeWidth="40" DishListModyHeight="28" DishListDishHeight="28" DishTitleHeighct="22" MenuHeight="204" ButtonLineHeight="44" DishListHeight="148"/>
<MenuView CurValMarkTextColor="16777215" CurValMarkBckgColor="255" LimitMinMarkTextColor="16777215" LimitMinMarkBckgColor="255" LimitMaxMarkTextColor="16777215" LimitMaxMarkBckgColor="255" BtmTxtHeight="20" BtmDY="3" BtmHeight="64" BtmDX="3" BtmWidth="103"/>
<MessagesView RowHeight="54" TextFontHeight="54"/>
<OutgivingView OSO="5"/>
</SETTINGS> Common settings in mwnsettings7.xml Deprecated. To operate offline (open tables and save orders) you have to create (if you don't have one) table with some code (for example: 666) and add a tag <MMPRCS TC="666"/> to mwnsettings7.xml inside <SETTINGS> </SETTINGS> tag (if it's not already there). This also means that if you have taken preset offline mwnsettings7.xml from the distributive it won’t work correctly until there is table 666 in your RK7 database, or till you have corrected the table code inside the tag mentioned to the legacy one. Deprecated. To operate only online remove the tag <MMPRCS/> from mwnsettings7.xml and add <ZCFGTAG tag="TIACXWLN1"/> tag instead. Inside <CAN/> tag CC=“0” parameter value turns off close button, except under settings mode. To change program language set the tag <LANG/> parameter "Use=" value:








































Thai To use bluetooth printer (bixolon SPP-R201BGM for example) inside the tag <EXTDEV/> set parameter Use="4". Check also parameter COM="7" to be correctly set (PDA COM port number). Mind that you have to set proper system language in tag <LANG/> corresponding to printer coding settings in order to print proper symbols. To set bluetooth printer bill format change the tag <CHKFM/> parameters: PW="32" value defines row width (in symbols number); QRO="11" value defines right side "Quant" column offset; SW="7"  value defines "Sum" column width; SAD="2" value defines number of digits in Sum fraction. <GUESTS/> tag DefNum="1" parameter value defines a number of guests by default. If you add this tag to mwnsettings7.xml between tags <MMPRCS/> and </SETTINGS>, the "Guests number" dialog won't appear on PDA. If you set DefNum="0" parameter value to "0" the "Guests number" dialog will appear the same way as without <GUESTS/> tag. <GUESTS/> tag DefTab="1" parameter value defines the default table code to save orders. If you set this parameter value to some number different from "0" the "Table number" dialog won't appear and all orders created on PDA will be saved to this table number. DefTab="0" turns on the "Table number" dialog.
<TIMES /> tag "Sync=" parameter value is the application order list refresh period (in minutes). "ST=" parameter value is the application timeout (in seconds). "Serv=" parameter value is the TMS7 server timeout. <MENU /> tag "Cash=" is the caching boolean, =1 - enabled, =0 - disabled. "UpTm=" is the menu data deterioration period (in minutes), because this reference synchronizes not every <TIMES /> tag "Sync=" time. <RK7 /> tag "Precheck=" value "1" turns on Bill printing from PDA; "EditDraft=" value "1" turns on Draft order activation from PDA; "UseCources=" value "1" turns on Course assignment from PDA. <RK7 /> tag BigMenu="1" turns on showing more than 2500 menu items on application. <Messages /> tag "SoundFile=" parameter made to set sound file name (use low bitrate .mp3 file, around 40 bps; put this file next to server .exe - it will be preloaded with mwnsettings7.xml itself); "SoundInterval=" sets repeat interval.

2.3. Multiserver case

2.3.1. You are able to run several TMS servers in one Windows OS.

2.3.2. You may set them use one (the same) Guardant key or individual (see licensing below).

2.3.3. You have to run each TMS server from individual folder, having separate ini file and client settings (.xml) file.

2.3.4. You have to set different ports for TMS servers to listen and set them in mwnsettings7.xml files correspondigly.

2.3.5. You have to connect TMS servers to different (logical) xml interfaces (in case of connection to one cash server).

3. Licensing

3.1. General information

3.1.1. There are 2 licenses (WinCE) you have to receive to make the software work. First one for WINCE MobWaiterNP7 application (as many license keys as a number of PDAs: 1 license code per 1 device), this license is not necessary for iOS versions. Second one for TMS7 server (one license code in a Guardant key, but generated for a specific device quantity and functionality, both WinCE and iOS).
3.1.2. In case of iOS application you don't need in-application license, only TMS7 server key one.
3.1.3. There are software functionality with payments (FULL) or "mobile manager" and without them (BASIC) "mobile waiter", find the difference in 3.2.7. On license request you have to point which one you want to get and in application settings switch on (FULL) or switch off (BASIC) corresponding "Ext." property (see 4.1.2).

3.1.4. MobileWaiter7 connection and operations are not protected with licensing on RK7 side (if you use XML interface for saving or paying orders with non-UCS software, you have to get 'XML save order' license).

3.2. Server licensing

3.2.1. You are to update your Guardant Stealth II key (protects TMS7) by using (new)LUpdater.exe software (could be taken from RK7 distributive LUpdater folder or from UCS file server: ftp://ftpint.ucs.ru/dealers/r-keeper/WaiterNotepad/iPod/TMS/7/) if you have to (in case you got the key without TMS7 license, with outdated license, etc.).
3.2.2. Start (new)LUpdater.exe and press "Read".

You will see a request in upper line.
3.2.3. The license code you should receive from licensing responsible person of UCS-Moscow (as a response to your request taken from LUpdater upper line).  Additionally in your request you have to mention the quantity of PDA that will be connected to the TMS7 server protected with this key and the functionality required.
3.2.4. The license received you have to enter to the LUpdater lower line and press "Write".

Then press "Close".
3.2.5. Note that there are many different LUpdater applications you may find somewhere, and they are function different ways (for different apllications and even for the same applications different versions). Choose only proper LUpdater (usually distributed in the same folder as server .exe) for your TMS7 licensing.
3.2.6. If you changed TMS7 server to some newer version with updated licensing, you should send a new license request as in 3.2.3., but additionally with your previous license and comment that you've changed version.

3.2.7. FULL license gives you the following functions (on compare with BASIC one): Payment (close order) - only one currency should be chosen (usually national cash). It could be full payment or partial (by cover). Edit saved batch (delete menu items, transfer dish to another cover or order, change course). Split order by covers and pay cover. Activate draft batches, initiate service print. Edit guest marks (cover names), add or delete covers. Close empty order.

3.3. PDA application licensing

3.3.1. This additional license is for WinCE applications only.

3.3.2. You are to generate license on each WinCE/Mobile device.

3.3.3. Start MobWaiterNP7.exe, press certificate button, input 051791 password and press synchronization button (enter settings mode), press “license prolongation” and get the request code there, then send this code to licensing responsible person of UCS-Moscow, input answer code to the field below and press synchronization button.

4. Start and use programs

4.1. First start

4.1.1. Run RK7 cash server = MIDSERV.exe (use /desktop or /install parameter as usually), MobilGuard7.exe (it starts TMS7.exe) or TMS7.exe - to start as desktop, or /INSTALL - to install service, and MobWaiterNP7.exe or iPod application (RkMobWaiter) on PDA. You have to start RK7 cash station also to login with "mobile" user (register him in current common shift - if not yet done). TMS7.exe server will listen to 2 ports: first one that you set in (TCP), and one more that = first one+1 (UDP) - for server status check by client (like "ping").

4.1.2. In PDA application enter settings mode and set server parameters: address, main port (TCP), protocol version (RK7 or RK6), license mode (for RK7). Restart the application after saving changes. Test your network (wireless) connection on client PDA before running MobileWaiter. The main thing is proper IP network, because MobileWaiter uses TCP and UDP over that protocol. We recommend you set fixed IP on client also (it's not a problem if you planned network like good engineer do). You may prefer strongest encryption type for WiFi. You may lock the device OS to connect to only 1 wireless AP if necessary (if you don't use wireless AP "roaming" there). All extended functions won't work on application if "Ext." switcher not turned ON (just inactive or absent buttons; and if license in key not fits this setting applicaton won't work at all).

4.1.3. Login to MW7 with the same user code as to cash station (you have to register this user in current common shift in order to be able to login to MW7 application).

4.1.4. Then you can see interconnection:

4.1.5. For references reload you have to finish session (start new session), session button is username.


4.2. Settings changes

4.2.1. In most cases you have to delete all temporary files both from PDA and server in order to apply new common settings (for example, language changes).
4.2.2. Temporary files are all the files that did not exist before first start and created by MW7 application and server during its uptime.

4.3. Individual settings for users

4.3.1. You are able to use personal settings files in order to change user graphic interface language (for example).

4.3.2. During its uptime application creates copies of mwnsettings7.xml file in its PDA folder (ucs) and gives them names as user code. These files will not be overwritten in case of changing settings in server or client mwnsettings7.xml file. If you want to change user personal settings to server default delete his personal .xml fom PDA.

4.4. Order processing

4.4.1. Create order
4.4.2. Edit order
4.4.3. Close order Payment

5. FastFood mode

5.1. RK7 manager station adds

5.1.1. Add 'Mobile fast food interface' driver to cash server (each cash server which stations are going to accept this type of orders). "DirName" property must be set to one folder for each cash server driver (if other order distribution not necessary). You don't need to create more than 1 "XML interface" for TMS7 server - it is enough to have only 1 TMS (which connects to only 1 cash server) in the restaurant. But given cash server must be always on, and all Mobile users must be registered on it in current common shift as usually.

5.1.2. Add driver file name 'mobfastf.dll' and choose cash server driver(s) in new logical interface.

5.1.3. Create MCR algorithm which calls this (Mobile Fast Food) interface on suitable card read (or some input, keyboard for example). Please, think of input 'parameter' (string) to be unique (not the same as fits other algorithms). You should call only 1 algorithm by some station input at the same time. Read http://support.ucs.ru/en/node/5993 for Algorithm details.

5.2. tms7.ini adds

5.2.1. TMS7 settings must be the same as for Mobile Waiter, but:




VDUID = 150                                              ID VDU

LocalPort = 1113                                        Port on TMS PC (do not change)

RestCode  = 138440006                            Full restaurant code  (as you got VDU license for)

Waiter = MWFF                                          Any tag to identify orders on VDU

ShowComboTitle = 0                                  Show combo packet

5.3. mwnsettings7.xml adds

5.3.1. Related parameters

<RK7 UseCodeNameChoice="1"  UseCodeByDefault="0" UseHorzOrientation="0" FastFoodScanNumber="1" FastFoodDigNumber="8"/>

5.3.2. "FastFoodDigNumber=" - order code symbol quantity (4 to 8) or string length (.xml file will have the same name also).

5.3.3. "FastFoodScanNumber=" enables (=1) or disables (=0) QR code scanner with camera. In second case you will input code from screen keys.

5.4. Transfer files

5.4.1. File format (it follows "SaveOrder" xml-interface query)

<?xml version="1.0" encoding="UTF-8"?>

<Course code="1"/>
<Dish id="1000833" quantity = "1000">

5.4.2. Order files are stored in the folder set in "Dir" parameter of tms7.ini [EXTSAVE] section and are seached by RK7 cash server in the folder set in "DirName" driver property.

5.4.3. Order file is taken by filename which is called by algorithm (see 5.1.3.).

5.4.5. Enhancement of this interface: it could be used to save orders from outside RK7.

5.5. General

5.5.1. This solution makes it easier taking orders in fast food busy hours.

5.5.2. iOS Mobile waiter version only. VDU supported. Minimum versions: VDU – 3.2, RK7 –, TMS – 7.1.10.

5.5.3. You may use numeric order ID tag manually entered or/and QR code with reader device. Customer gets this order ID in any format (on card, paper, verbally, so on).

5.5.4. By default, no additional files to be copied manually - just regular Mobile waiter set.

5.6. VDU

5.6.1. MFF orders go to VDU with station 61.

5.6.2. You may set another color for highlighting orders from MFF. You have to use VDU 'UNITS SETUP' for that.

5.6.3. MFF orders always go after those from cash station(s). When opened from cash station, this order goes to station order list.

5.6.4. If never opened on POS regular station orders are not going to be deleted manually, you may set automatic drop. You have to set 'EndQue Timeout' (minutes) for that.

5.6.5. Overtiming orders will be dropped after new order come (any of).

6. Troubleshooting

6.1. No connection issues

6.1.1. Do xml interface logging. For that go to RK7 manager station: service -> stations and devices -> All -> [your restaurant] -> [your cash server] ; on drivers tab choose xml interface properly created for TMS7 server as in 1.1. Set options -> "outputdir" property (enter legacy pathway to save xml interface incoming and outgoing files). Mind that cash server restart required to start logging after making settings.

6.1.2. Start TMS7 server and MobileWaiter7 application, operate until an error occured, stop all these applications afterwards. The best way is to delete all .xml files from the log folder immediately before an error occured, so that you will have only a very error moment log files.
6.1.3. Compare .xml files from log folder with TMS7.LOG and temporary files from TMP folder (that mentioned in Find all error records related to the problem you've got in these files and guess how to solve it (if you can't guess, ask UCS tech support than).
6.1.4. If you've got "Error: incorrected protocol number" (or "The protocol number ... has to be used for data transmitting") message in TMS7.log, download and change to new (with given protocol number) TMS7.exe (because this error means not suitable to each other server and client versions).

6.1.5. If you've got "Error: Ext lic number exceeded" message in TMS7.log, you should set proper licensing option (see 3.1.3.) or get and save to key suitable license (see 3.2.4.).

6.2. Data management issues

6.2.1. Do xml interface logging according to 6.1.
6.2.2. Follow 4.2.8. of http://support.ucs.ru/en/node/5532 and collect full TMS7 folder at the error moment and interface logs.

6.2.3. Always check TMS7.log in case of any error message on application screen because it may show some improper data.

6.3. Remarks

6.3.1. There are following restrictions in functionality now: This software will not work correctly if your cash server operates under DOS, it is possible to use only windows cash servers. Available functions are different in WinCE and iOS clients. If you want to have extended functions, you'd better use iOS one. System might not work correctly until you have placed your tables to hall plans. It is recommended to set table names and table codes to be the same, and only numeric (if you want be able to choose them on PDA, because you have to input table name there, not code) - for WinCE only.
6.3.2. Several variations of mwnsettings7.xml possible: first allows you working only online, second allows you to work offline; one allows you to make a payment with PDA, another capable only of order saving. In offline mode you have to use only legacy table codes obligatory. Also you can print bills and make payments after that.
6.3.3. In the beginning on PDA (folder “UCS” in the root of its filesystem – obligatory) must be 2 files: MobWaiterNP7.exe and mwnsettings7.xml (this xml should be preloaded normally, that’s why only “.exe” is obligatory). During its uptime application creates other files in its folder and also in Temp folder of your PDA file system (in case of changing settings it’s better to delete all the files created by application).
6.3.4. This manual is actual for TMS7.0.89.
6.3.5. This PDA software work correctly only with RK7.4.21.212 or later. It won't work at all if your RK version older than So, you should take the latest RK7 version to use MW7.

7. Upgrade

7.1. As this MW7 software is additional module for RK7 core system, you do upgrade both.

7.2. In case you do update iOS or Android client, you need to update TMS7 server as well to compatible version.

7.3. In TMS server log you can read minimum RK7 version supported by this server. In case your RK7 core version is lower than specified in tm7.log, you must upgrade the whole system, not only MobileWaiter.

7.4. When you upgrade versions of modules, you should take care of new settings for new versions. You must update settings files (ini, xml), add new parameters, and remove deprecated parameters.