Versions Compared

Old Version 1

changes.mady.by.user Ekaterina Marchenko

Saved on

compared with

New Version Current

changes.mady.by.user Ekaterina Marchenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Specify other parameters if necessary.

REPORT Field

...

Note

The REPORT field is used to set an active display form. You can use the

...

default forms

...

or create your own ones.

Use the REPORT field to choose a form to display the dishes or the order on the KDS display:

Fig. A list of preset display forms shown.Image Added

A list of preset forms

...

The order is displayed in the form of a dynamic windows window each of which containing contains one order item (— one per dish). It supports the simultaneous delivery mode. I.e. some of the dishes in the order are displayed as inactive and show with a timer for each dish which is linked as regard to the overall preparation time.

Fig. Order displayed using the dishlist.fr3 formImage Added

  • Form dishlist_by_line.fr3

The order is displayed in the form of a dynamic windows window each of which containing contains one order item (— one per dish). The simultaneous delivery mode cannot be applied in this case. I.e. the dishes from the order are displayed with a timer set for each dish individually.

Fig. Order displayed using the dishlist_by_line.fr3Image Added

  • Form dline.fr3

The order is displayed in the form of lines spanning across the display with each KDS line containing one line from the order (for each individual dish and line). It supports the simultaneous delivery mode. I.e. some of the dishes in the order are displayed as inactive and show with a timer for each dish which is linked to as regard to  the overall preparation time.

Fig. Order displayed using the dline.fr3 formImage Added

  • Form dline_by_line.fr3

The order is displayed in the form of lines spanning across the display with each KDS line containing one line from the order (for each individual dish and line). The simultaneous delivery mode cannot be applied in this case. I.e. the dishes from the order are displayed with a timer set for each dish individually.

Fig. Order displayed using the dline_by_line.fr3 display formImage Added

  • Form fullorder.fr3

The order is displayed in the form of a dynamic window which fully shows the order session (for each order) with a timer set for a dish requiring the longest preparation time.

Fig. Order displayed using the fullorder.fr3 display formImage Added

  • Form NotExist.fr3

Auxiliary An auxiliary form. If the layout used in the display form gets deleted (— a file is deleted by mistake from the installation package ) — the NO EXIST message will be displayed when viewing this display form.

  • Form ReadyOrder.fr3

The Take Away Waiter Mode ( waiter mode — the order is displayed in the form of a dynamic window showing the entire order session).

Fig. - Order displayed using the readyorder.fr3 display form

  • Form wfullorder.fr3

Image Added

  • Form wfullorder.fr3

The Being Prepared waiter mode — In the Works waiter mode ( the order is displayed in the form of a dynamic window showing the entire order session).

Fig. Order displayed using the wfullorder.fr3 display formImage Added

SQL Field

...

Note
titleImportant!

The operations algorithm of the KDS client app is set in the SQL settings field. You can choose one of the preset scripts

...

or create

...

your own algorithm.

You In the SQL field, you need to choose the option for the information display rules (what we see on the KDS display) in the SQL.

  • You can set the rules to display only the necessary information using the SQL request.

For instanceexample, to display only the ready dishes, dishes to be delivered, outstanding orders being prepared, etc. As the selection of a dish or an order changes their status, the KDS display will only show those meeting the request's conditions that will be highlighted in a color in accordance with corresponding to their current status. Items not meeting the request's requirements will not be displayed. For this reason at the time of , when selecting the dish or order, they will either be removed from the display, or change their highlight color.

  • Several standard options are offered but the user can generate the necessary request on his/her owntheir own request.

After the dish data is transferred from the cash register station to KDS, the dish and the order get the unprocessed Unprocessed status. It is possible to change the status , i.e. assign a status, at the time of when selecting the dish or order:

Code Block
Status - Unprocessed --->

...



Status - Prepare ---> Status - Prepared

...



Status - Prepare ---> Status - Ready

...



Status - Deliver/Pick Up ---> Status

...

 - Taken out


Standard Scripts Table

Item No

Fig. Options of ready SQL scripts set in the SQL field.

Table — Standard Scripts

Item No.
Script NameScriptDescription

1

Not prepared

SELECT * FROM BaseView WHERE (preptime IS NULL) ORDER BY ID, LineID, IID

  • Not prepared — the display shows the dishes or orders that have been transferred from the cash
registered
  • station and whose status has not yet been changed
(no action has been taken towards them) are displayed
  • . As soon as the dish
receives
  • gets the Prepared status it automatically receives the Ready status
.
Note
Important!

Not recommended for use in a standard configuration.


2

Not ready dishes

SELECT * FROM BaseView WHERE (finishcook < 0) ORDER BY ID, LineID, IID

Dishes
  • The display shows the dishes with the Not Ready status, i.e. those transferred from the cash
register
  • station and whose status has not yet been changed, or the dishes with the Prepared status
are displayed.

3

Not ready orders

SELECT * FROM BaseView WHERE (ready < 0) ORDER BY ID, LineID, IID

  • An order with the Not Ready status is displayed
(it
  • . It does not matter whether it contains dishes with the Ready and Not Ready statuses
)
  • . The order will be displayed until it gets the Ready status
.
  • This is an option which will highlight the prepared dishes within an order in purple
(
  • by default
)
  • . As soon as the last dish
receives
  • gets the Ready status giving the Ready status to the entire order, the order will be fully deleted from the display
.

4

Not

taked

taken out dishes

SELECT * FROM BaseView WHERE (ltakeout IS NULL) ORDER BY ID, LineID, IID

  • The display shows the dishes with the Not
Delivered
  • Taken Out status, i.e. dishes with the Not Ready and Ready statuses
(
  • — dishes that have not been prepared and dishes that have been prepared but
have
  • not
been
  • taken away
).

5

Not

taken

taked out orders

SELECT * FROM BaseView WHERE (takeout < 0) ORDER BY ID, LineID, IID

  • The display shows an order with the Not
Delivered status (it
  • Taken Out status.It does not matter whether it has dishes with the
Delivered
  • Taken Out and Not
Delivered
  • Taken Out statuses
)
  • . The order will be displayed until it gets the
Delivered
  • Taken Out status
.
  • This is an option which will highlight the delivered dishes within an order in purple
(
  • by default
)
  • . As soon as the last dish
receives
  • gets the
Delivered
  • Taken Out status giving the
Delivered
  • Taken Out status to the entire order, the order will be fully deleted from the display
.

6

Prepared and not ready dishes

SELECT * FROM BaseView WHERE (preptime IS NOT NULL) AND (finishcook < 0) ORDER BY ID, LineID, IID

  • The display shows the dishes with the Prepared status but without the Ready status. Do not use it in a standard configuration
.

7

Prepared and not ready orders

SELECT * FROM BaseView WHERE (preptime IS NOT NULL) AND (ready < 0) ORDER BY ID, LineID, IID

  • The display shows the
dishes
  • orders with the Prepared status but without the Ready status. Do not use in it a standard configuration
.

8

Prepared and not taked out dishes

SELECT * FROM BaseView WHERE (preptime IS NOT NULL) AND (ltakeout IS NULL) ORDER BY ID, LineID, IID

  • The display shows the dishes with the Prepared status but without the
Delivered
  • Taken Out status. Do not use it in a standard configuration
.

9

Prepared and not

taken

taked out orders

SELECT * FROM BaseView WHERE (preptime IS NOT NULL) AND (takeout < 0) ORDER BY ID, LineID, IID

  • The display shows the
dishes
  • orders with the Prepared status but without the
Delivered
  • Taken Out status. Do not use it in a standard configuration
.

10

Ready dishes and not taked out dishes

SELECT * FROM BaseView WHERE (finishcook > 0) AND (ltakeout IS NULL) ORDER BY ID, LineID, IID

  • The display shows the dishes with the Ready status but without the
Delivered
  • Taken Out status, i.
I.
  • e. only the dishes that have been prepared but
have
  • not
been delivered.
  • taken out

11

Ready dishes and not

taken

taked out orders

SELECT * FROM BaseView WHERE (finishcook > 0) AND (takeout < 0) ORDER BY ID, LineID, IID

  • The display shows the dishes with the Ready status and the dishes with the Delivered status highlighted in purple until the entire order gets the
Delivered
  • Taken Out status
.
  • As soon as the last dish from the order gets the
Delivered
  • Taken Out status, the order will be deleted from the display
.

12

Ready orders and not

taken

taked out dishes

SELECT * FROM BaseView WHERE (ready > 0) AND (ltakeout IS NULL) ORDER BY ID, LineID, IID

  • The display shows the orders with the Ready status containing dishes with the Not
Delivered
  • Taken Out status. I.e. as soon as the dish receives the
Delivered
  • Taken Out status, it will be deleted from the order
.

13

Ready orders and not

taken

taked out orders

SELECT * FROM BaseView WHERE (ready > 0) AND (takeout < 0) ORDER BY ID, LineID, IID

  • The display shows the orders with the Ready and Not
Delivered
  • Taken Out statuses
.
  • All the
delivered
  • taken out dishes within the order are highlighted in purple
.
  • As soon as the last dish receives the
Delivered
  • Taken Out status, the order gets the
Delivered
  • Taken Out status and is deleted from the display
.

14

Prepared dishes

SELECT * FROM BaseView WHERE (preptime IS NOT NULL) ORDER BY ID, LineID, IID

  • Only the dishes with the Prepared status are displayed
.

15

Ready dishes

SELECT * FROM BaseView WHERE (finishcook > 0) ORDER BY ID, LineID, IID

  • Only the dishes with the Ready and
Delivered
  • Taken Out statuses are displayed
(
  • , as the
Delivered
  • Taken Out status suggests that the dish also has the Ready status
).

16

Ready orders

SELECT * FROM BaseView WHERE (ready > 0) ORDER BY ID, LineID, IID

  • Only the orders with the Ready and
Delivered
  • Taken Out statuses are displayed
(
  • , as the
Delivered
  • Taken Out status suggests that the order also has the Ready status
).

17

Taken

Taked out dishes

SELECT * FROM BaseView WHERE (ltakeout IS NOT NULL) ORDER BY ID, LineID, IID

  • Only the dishes with the
Delivered
  • Taken Out status are displayed. I.e. the dishes with the Ready and Not
Delivered
  • Taken Out statuses will not be shown. They will be displayed as soon as they are shown as prepared and delivered on other displays
.

18

Taken

Taked out orders

SELECT * FROM BaseView WHERE (takeout > 0) ORDER BY ID, LineID, IID

  • Only the orders with the
Delivered
  • Taken Out status are displayed. I.e. the orders with the Ready and Not
Delivered
  • Taken Out statuses will not be visible
.
  • They will be displayed as soon as they are shown as prepared and
delivered
  • taken out on other displays
.

19

All

SELECT * FROM BaseView ORDER BY ID, LineID, IID

  • All dishes are
on view
  • displayed and cannot be removed from the display
.

Operation Field

...

In the Operation field, you need to define specify the event that will take place at the time of happen when selecting the dish or the order.

  • Dish and order management suggests that means changing their status will be changed during the work process.

The system uses four statuses. Once the dish is transferred from the cash register station to KDS, the dish and the order are assigned given the Not Processed status.You can make the following changes to the status of the dish and the order at the

time of selectionWhen selecting a dish, you can change the status to the following:

  • Prepare
  • Ready
  • Deliver (TakeOut)

The status can only be changed in the following order:

Not Processed ---> Prepared ---> Ready ---> Picked Up/DeliveredTaken Out

Therefore, it is impossible, for instanceexample, to switch change the status of a dish from Not Processed to Picked Up/Delivereddirectly to Taken Out.

By default defaultm the following colors are used for highlighting each status:

  • Transferred from the cash register – station — white;
  • Prepared – — yellow;
  • Ready – purple ;
  • Delivered/Picked Up – blue .

Fig. List of available operations.

...

  • — purple
  • Taken Out — blue

kds13.pngImage Added

Operations Table

Item No.

Transaction Name

Description

0

opNone

  • Nothing will happen at the time of when selecting the dish or the order.

1

opReadyDish

  • When selected, the dish will receive get the Ready status. If it is the last one in the order, then the entire order will receive get the Ready status. It This operation is used for the cook's display.

2

opReadyOrder

  • When the order is selected, the entire order will get the Ready status. It This operation is used for different displays to show the orders one by one.
  • If it is used in displays showing line by line, then after selecting a window with a dish, all dishes in the order will receive the Ready status (— i.e., will be removed from the display and will be highlighted in another color).

3

opTakeOut

  • If the order is When selected, the entire order will receive the Delivered/Picked Up status provided that Taken Out status, if the entire order has the Ready status. If the order contains unprepared dishes, nothing will change at the time of its selection.
  • It is only used for waiter displays as it is recommended delivering/picking up to take an order through out using them, although it is possible to do it with any other display.

4

opReadyAndTakeOut

  • If the order is When selected, the entire order will get the Ready and Delivered/Picked Up status.Taken Out status
  • It is used for the cook's display, when a dish is prepared and delivered right away (in bars, for instance)taken out at once, f.ex., in bars. In this case, no action should be taken at the time of delivering the order special action is needed for taking out the order, which saves time.

5

opTakeOutDish

  • When the dish is selected, it receives the Delivered/Picked Up status provided that Taken Out status, if the dish already has the Ready status. If it is the last one in the order then , the entire order will receive the Delivered/Picked Up status.Taken Out status
  • This operation It is used for the waiter's display.

6

opSendMessage

  • If When the order is selected, the waiter will get a message informing that the order is ready.
  • It is not recommended for use, as it is not topical outdated and requires complex settings (, i.e. cannot be set as a task).

7

opReadyDishOnly

  • When selected, the dish will receive get the Ready status.
  • If it is the last one in the order, then only this dish will get the Ready status while the entire order will keep is the Not Ready status.
  • Such an order cannot be delivered.taken out
  • It is not recommended for use, as it was made for a special project.

8

opPrepareDish

  • If When selected, the dish is selected it will get the Prepared status. This is an internal (, i.e. intermediate ) status which is used before ReadyDish.
  • It is not recommended for use in a standard configuration.
  • It is used only for the three-stage option: cook (Prepared), order assembler (Ready), and waiter (Delivered/Picked UpTaken Out), for instanceexample, when using the substitution editor.
  • In a standard configuration, when a dish is assigned gets the Ready status, the dish always gets Prepared status automatically.

9

opCustom

  • Enables you to take perform several actions on a one station. When you select selecting this operation, you get an additional opportunity to set configure the operations for this display form (— preparation, readiness, delivery).
  • Based Depending on the settings, a single display can be used to prepare, cook and deliver a dish.
  • You can take between perform from one and to three actions depending on the enterprise's needs. But the status check procedure required for upgrading the status remains standard.

The additional fields used for the opCustom operation are shown in the figure below.Fig. Setting additional fields at the time of selecting an opCustom event.:

Image Added

Screen Name

...

Field

In the Screen Name field, you should specify You should state the name of the display form to be shown on the KDS display in the Screen Name..

  • The name and ordinal number of the newly created form are inserted by default.

Fig. Setting the display form nameImage Added

Print Groups Field

...

In the Print Groups field, you need to select the service print groups to be shown on in this display form. Dishes from other service print groups will not be shown on in this display form.

  • If none of the groups are selected, ALL groups will be shown.

Fig. Setting the visible print groups for the selected display

...

Image Added

Other Settings of Screen Settings Section

View and set configure other parameters in the Screen Settings section as if required.

Table 1 — Other Screen Settings Parameters

.
Item No
ParameterDescription

1

Auto mark first record if record count more then one screen

  • Under When this setting is used, if the orders fully fill the display form's first page, the next dish which is to appear on the second page will be shown the last on the first page as . This happens bacuse the very first dish on the first page will be automatically deleted if the display is assigned the opReadyDish event, or this first dish will be transferred into given the status corresponding to the event assigned for this display.

2

History screen

  • Under When this setting is used and provided that if the request has been re-written in a reverse order, the display will show all the orders under an event illustrating with an assigned event from all displays (for . For example, you can display all the deleted (, i.e. prepared ) dishes).
  • For the dishlist.fr3 and dline.fr3 forms and their varieties, this setting is used to show different dish statuses (— ready, picked up)taken out. If this setting is not used for these forms, their displays will only show dishes with the Not Ready status and nothing will appear on the screen when choosing another SQL.

3

Way of marking

  • Select one of three options for numbering KDS windows.

An example of how windows can be numberedwindow numbering options:

Fig. Window numbering options

kds17.pngImage Added

  • markByGenValues — by a A unique value within the display (if . If #1 is cast off reset it can be assigned to the next order)
  • By RK markByOrderNumber — by an order number
  • By RK7 package number

...

  • from r_keeper 7
  • markByPacketNumber — by a package number from r_keeper 7
Note

Since KDS version 1.3.0.4, a new Mark Whole Order by Order Caption Click option is available, which can only be used with the activated "Way of Marking: markByGenValues" or "MarkByOrderNumber". Allows you to perform a

...

configured dish by dish operation for the entire order by

...

tapping the order header

...

Table 2 — Other Screen Settings Parameters

.
Item No
ParameterDescription

4

Barcode Scanner port

  • The scanner port is indicated if the technology for casting off reseting an order by scanning a barcode is used ( a special barcode is used) — . This parameter is custom made.
  • DO NOT use it in a standard configuration!

5

Barcode prefix

  • Used The parameter is used for printing the barcode (exclude , excluding the ' RK7 blank ' prefix from the code) — . This parameter is custom made.
  • DO NOT use it in a standard configuration!

6

Mark first record by F1/Done

  • If you press When pressing F1 ( on the old keyboard ) or Cancel (Reset on the new keyboard) then , the operation selected for this display form for the first item on the display will be performed.
  • Example: the first order in the list will be cancelled reset for the DishList display in ReadyDish.

7

Confirmation on mark record

  • It is used for the cook's display.
Under
  • If this setting is used, when selecting a dish or an order, a
message
  • window will
pop up
  • appear enabling you to choose an operation for this display
(
  • as planned
)
  • , cancel the operation, or send a message to the waiter
,
  • : msg for waiter
, (
  • to the station, to the mobile waiter, pager, etc.
).
Note
Important!

The message will be sent

independent

independentl of the display form, service principle, operation and location in the order area. I.e. if you selected the Msg for Waiter item, the dispatched message will contain the text from

RK

r_keeper settings, for

instance

example, Ready Table #XX, or

Kitchen Paging Waiter

Cook call waiter.


A view of the The dialog box:

Fig. An additional request for confirming the action and sending the message to the waiter.

Image Added

  • If When using ARM, if this setting is on then when using ARM, the next setting should also be activated (— Use ARM-compatible confirmation window ).

Fig. ARM controller settings

Fig. Dialog box for confirmation

  • — should also be activated

Image Added

  • There is a prompt note under each button for what to press on the cook's keyboard, as ARM does not support sensory input ( TS).
    Image Added
  • Only a picture which is not a fully-fledged client is displayed.

Table 3 — Other Screen Settings Parameters

Item No
.
ParameterDescription

8

Use ARM-compatible confirmation window

  • Use ARM-compatible confirmation windows.
Used
  • This parameter is used only jointly with the Confirmation on Mark Record setting
.

9

Send a message to the waiter when Ready dish (RK6 only)

  • Sending a message informing that one of the
dished
  • dishes in the order is ready. Can only be used for the ReadyDish event and
RK6.
  • r_keeper 6

10

Move marked record to top

  • The order window will move to the top of the list on the display when an operation with an order or a dish in the order is performed
.

11

Show some last operation

  • Used
at the time of adjustment
  • during debugging process in order to view what operations were performed with the dish (log)
.
  • Not supported by ARM
.
  • It makes
is
  • possible to set how many last operations should be displayed and their viewing rules
.

An example of using the Show Some Last Operation parameter:

Fig. Selecting the number of displayed last operations

Fig. Log Parameters

Image Added

An example of the log parameters:
Image Added

  • When such settings are used, Under these settings five log lines will be displayed. The next operation will be shown as the last in the list while the first line will be deleted from the list.

Fig. A view of the set operation log on the display.

Table 4 — Other Screen Settings Parameters

.
Item No
ParameterDescription

12

Group By: Print Group(True)/Order Number(False)

  • Under When this setting is used, the images will either be grouped by print groups, or by the order number (for instance. For example, the orders from the bars and the kitchen will either be shown in one window, or in different ones). Similar to the Joint By Order setting.

13

Sound file or beep theme

  • When specifying the sound file in this field (, for instanceexample, C:\WINDOWS\Media\ringin.wav), an alarm will go off as soon as sound signal will be played when a new order appears on the KDS display (— the order numbering is tracked with the last number entered into the memorybeing memorized, and the next ordinal consequtive order will appear on the display accompanied by an alarm).a sound signal

14

Duration of sound

  • This field can be used to set configure the duration of the alarm in case sound signal if it is used.

15

Use letter enumerateThe

  • In this field, the need for using
letters (
  • letter labels as special
identifiers)
  • identifier, for the order is indicated
in this field (
  • — whether the is a need to use letters A, B, C, D
).

16

Static letter number

  • If the Use Letter Enumerate setting is active, the need to save the Letters in the database is specified in this field.
  • When an order is saved, its Letter is analyzed and when the orders are shown on different displays, it comes under is marked by the same Letter (without . Without this setting only the numbering is used).

17

Zoom

  • In this field, you can specify the scale of the display form to be shown on the station's display (. It is set individually).

18

Join By Order

  • Combining dishes from different service print groups into one order at KDS
.
Under
  • When this setting is used, if the dishes from different service print groups are entered into the cash
register at
  • station during the same session,
then
  • the KDS display will show all the dishes in this session
will be displayed
  • in the same order, only
provided
  • in case that REPORT - fullorder.fr3 has been
installed
  • set. Within this order, the dishes will be grouped by service print groups
.
  • Without this setting but under the same conditions, on the KDS display such an order will be split into several orders depending on the number of service print groups
on the KDS display
  • .
An example

Examples of how an order is displayed using the Join By Order parameter:

Fig.
  • With the Join by Oder setting
Fig.
  • Image Added
  • Without the Join by Order setting
    Image Added

19

Group Combo DishUsing this parameter, you can

This parameter allows to show combo dishes on the display.

If the Show Combo Dish As Line parameter is

selected

enabled, the dishes will be shown as a line

; if

. If the parameter

if not selected

is disabled, the dishes will be shown vertically.

Examples of how orders are displayed using the Show Combo Dish As Line parameter:

Fig. With the Show Combo Dish As Line parameter on

Fig. With the Show Combo Dish As Line parameter off

Note: For the combo dishes to be displayed in the proper format you need to use the manager station directory, go to Settings ⇒ Parameters ⇒ Installation ⇒ Communication with other systems ⇒

Note

For the combo dishes to be displayed in the proper format, in the manager station, go to Options > Parameters > Installation > Link with other systems > KDS and VDU, and

set

select Components Only in the Value property

as Components Only

.

If this setting is skipped

then

, not all data on combo dishes will be transmitted through the xml interface leading to misdisplayed information on KDS displays.


Table 5 — Other Screen Settings Parameters

.
Item No
ParameterDescription

20

Join By Order + OneKDSCheck (RK6)

  • If
the RK6 cash register
  • r_keeper 6 cash station uses the OneKdsCheck=ON server setting
(
  • specified in Rkeeper6.ini at the cash server
)
  • , then whether this setting is present or not does not affect how the order is displayed
at
  • in KDS. All dishes within one session will be displayed in one order without being grouped by service print groups, i.e. in the same order as at the cash
register (
  • station — can be used for
meal
  • dish course
modelling
  • emulator, if the courses are entered as dishes
).
  • The OneKdsCheck=ON setting is available
for cash register versions starting
  • since cash station version 6.97.1.
Under
  • When this setting is used, the order in the Order Control is formed as one order and its sequence of dishes fully corresponds to the
sequence of dishes
  • one entered at the cash
register
  • station. I.e. a single order is generated for the session
as opposed to
  • and not several orders grouped by service print groups.
Important!
Note

When such an order is

generated

created, it is

allocated

given the first service print group

(

— the print group with a minimal cipher

) from the RK6 Editor (you

— from r_keeper 6 Editor. You can see the cipher in streams.db

)

. It is necessary to tick this service print group

on

at the KDS server, otherwise this service print group will be

cast off

reset and the order will fail to reach the KDS server.

Example: The service print group has a minimal cipher of 1 and is called Print. The dishes within the order have service print groups with ciphers 3 (Kitchen), 8 (Bar), and 10 (Hot Kitchen). For the dishes to be shown on KDS displays it is necessary to tick all four groups.

Fig. An example of KDS server settings


  • When the KDS display is set using the F2 key only the actual service print groups that use the dishes (Bar, Kitchen, Hot Kitchen) need to When configuring the KDS display in the window called by the F2 key, only the actual service print groups that use the dishes should be ticked. It is not essential obligatory to tick the Print group. You can either tick it or not. But if the Print group uses is used by the dishes for this display, you should tick it as well.

...

  • Image Added

  • When using the Join By Order and OneKdsCheck=ON setting, the order on the display will be the same as entered at the cash

    register (

    station — with the same dish sequence

    ) (order 1) and with

    — and when the OneKdsCheck=OFF

    (order 2).

...

  • setting is used.
    It is also

...

  • necessary to

...

  • make the following setting in the FSVDU.ini

...

  • file:

    Code Block
    PackLines=OFF

    In this case the dishes will not be packed

    .

...

  • .

...

  • When working with Ipod devices, it is necessary to set specify KDSSolid=1 in tms2.ini in section , section [TMS] (starting with — since TMS version5.39) to rule out dishes being grouped , to disable dish grouping by print service groups. This setting only operates jointly with the OneKdsCheck=ON r_keeper server keeper setting (see first order). If the setting is OneKdsCheck=OFF setting is used, the Ipod will send the orders classified by service print groups and in to different windows.

Fig. An example of an order sent from an Ipod

General Settings Section

It is necessary to specify configure the main settings in on the second tab of the General Settings tab.
Fig. The General Settings windowImage Added

DataBase Settings Field

...

Image AddedFig. Connecting to the KDS database
Table 1

...

— General Settings Parameters

.
Item No
ParameterDescription

1

RK Version

  • The operational RK (The used r_keeper version is specified — either 6 or 7) version is installed

2

Station Name

  • The KDS station name is set (specified — manually for win. For ARM, keep the field empty for ARM).

3

Alarm Time (minutes)

  • The time in minutes (until the nominal cooking time countdown starts) after which the timer's highlight color will change to the color set below (Alarm Time Color).

4

Alarm Time Color

  • The color in which the timer will be highlighted (in this example . In our example, the color code is 255.128.0)

Example:

Fig. Setting the Alarm Time Color parameterImage Added

Table 2

...

— General Settings Parameters

...

.
Item No
ParameterDescription

5

RS-232 Port

  • Not used.

6

RS-232 Baud

  • Not used.

7

Use Scheduler

  • If the function is activated (ticked) — its box is ticked — automatical switching over the display forms can be automatically rotated after is possible during certain periods of time.
  • The main display form is set in the Main Report field, while the additional form is set in the Second Report field.
  • The duration of the periods for rotating changing over the main and additional display forms is set specified in the Second Report Time field according with to the specified format.

Example:

Fig. An example of the Use Scheduler parameter settingImage Added

Table 3

...

— General Settings Parameters

...

Parameter

Description




8

Refresh Screens (milliseconds)

  • Refresh time – — should be preferably kept as it is

9

Refresh data (milliseconds)

  • Refresh time – — should be preferably kept as it is

10

Time to delay command (seconds)

  • Delay time for performing the operation for changing the dish /or the order status. I.e. the operation can still be rejected within this time frame.

11

Localization

  • Localizing the operation confirmation window (starting from , since version 1.3.0.7)

Additional KDS

...

Client Settings

Changing

...

Field Colors in Display Form

Here an is an example There is a description of how to change from blue to another color in the example.
Open the display form in the report designer (by pressing the D key), find and change the following part of the set algorithm in the form code after ScreenNumberOnBeforePrint(Sender: TfrxComponent):

Code Block
begin

...


    if screenNumber.Color=

...

clBlue then begin
    ScreenNumber.Color:=$0000DDDD;

...


end;

with $0000DDDD - rgb as the where $0000DDDD is for the RGB color, you can specify a color other than blue.Fig. An example of changing the field's color.

Additional KDS

...

Server Settings

  • Specifying the service print groups on in the KDS server settings does not affect how they are displayed on at the KDS stations and how orders are formed on in KDS. They are required only for the process of selecting the already formed orders At KDS in KDS for the server. I.e. if some of the orders are not required at the server they can be cast off reset this way (to reduce , thus reducing the load on the server).
  • If the Preparation Control function is not activated in the RK6 r_keeper 6 Editor for the service print feedflow, the service print groups will still be visible in the KDS display settings (ScreenOptions) and at the KDS server (Options), but in this case no orders will be sent to KDS from the cash register!

...

  • station.

FSVDU.INI

...

Parameters

The following FSVDU.INI parameters have been added for RK7 in server settings starting from to the KDS server settings for r_keeper 7, since KDS version 1.3.1.2::

Code Block
UseOrderNameAsTable – It should be switched on if new persons are welcome to join a party at a table. In this case the table's full number is transmitted as OrderName

...



AutoChangeMainWaiter – Updating the

...

 orders when changing the main waiter.

The following FSVDU.INI parameters have been added to KDS sever settings starting since version 1.3.2:

Code Block
DelayTimeSec – The possibility of delaying sending a message on the readiness of a dish (in seconds)

...



DelayedPrintGroups - Listing print groups separated by a coma, similar to the PrintGroups client settings.

...