In this article
To set/modify the Kitchen Service configuration
The Kitchen Service Configuration defines the connection configuration for the KDS, for example which Kitchen Service it connects to and various other essential parameters.
When opened for the first time, this function sets default values in the fields. The current server, running the Business Central service tier, and a Business Central KDS Web Service are set as starting values. The default values should cover most of the scenarios.
To set/modify the Kitchen Service configuration
- Go to the How to: Set the Kitchen Service Configuration card.
The General FastTab
| Time Style Settings | An option field to calculate when the time style is supposed to appear on the chits. If you select Percentage of Cook Time, the time style is calculated by percentage of the item cook time. If you select Time Overdue, you decide a fixed time (seconds) that starts ticking after the normal cook time of the chit or line. You specify the percentage and seconds in the Time Style Profile. |
| Default Cook Time | If Time Style Settings is Percentage of Cook Time and items have no cooking time, the KDS will calculate the time style with this default cook time. |
The Connections FastTab
| JSON for KDS Utility | This field contains the related field data, from the How to: Set Up LS Central to Use OAuth page, formatted into a JSON string. It can be copied and pasted to the WS Info field in the KDS Utility. You can also enter the data manually in the fields. |
| Interval to poll Web service from KDS | This value is used by the Standard Kitchen Service to set how frequently it checks if there are new KOTs which need to be sent to the Display Stations. This value must be greater than zero. Recommended values are 2 - 5 seconds. For the WebKDS the interval is set in the WebKDS Admin page by selecting the Time Intervals button. |
The Kitchen Service Settings FastTab
| Debug Logging | Select this check box, if you want the Web Service to log its activities. You can see the results in the KDS WS Log list in the Kitchen Display System menu. The Kitchen Service activities are logged, for example the fetching of the KDS Setup, and the fetching of unsent orders. Some error messages are also logged, for example if an error occurs when KDS sends to printers. The activity for theExpeditor Bump Printing is also logged in case it has to be debugged. |
| Log KDS Order Status Updates | Turn on this toggle switch, if you want the Web Service to log the KOT statuses coming from the Kitchen Service. For example, when a bump occurs. You can see the result in the Kitchen Order Status Log list in the Kitchen Display System menu. |
The Kitchen Service Settings FastTab
| Debug level | Here you can choose how much information is logged in the log files that are located in the C:\ProgramData\LS Retail\Kitchen\Log\ folder. The possible values are:
For normal operation the Error or Main setting should be sufficient. |
| Save Order Files in Debug Folder | Save Order files in C:\ProgramData\LS Retail\Kitchen\Debug folder on the server, where the Standard Kitchen Service runs. When Debug level is Verbose, and this field is checked, the KDS will save the orderfiles in this folder. Every time something new is sent from the POS, a new version of the order is saved. The files are in pairs: First file is the state right after the KDS receives the order. The second file is saved when the KDS has processed the order so it can be sent to the printers/displaystations. |
| Max Number of Files in debug Folder | The maximum number of files in the Debug folder. Value 0 means that there is no limit. Suggested value is 500, but it is up to the user. The files can quickly pile up in the Debug folder, which affects the performance of the file system on the server running the KDS. This parameter limits the number of files in the folder. |
| Days to keep debug files in folder | The number of days until the log files are deleted from the C:\ProgramData\LS Retail\Kitchen\Log\ folder. |
| Hours to keep order files in folder | The number of hours to keep the order alive in the KDS. The orders/KOTs are stored in XML files in the C:\ProgramData\LS Retail\Kitchen\Work\ folder, as well as in memory. If, by any chance, the order is still "alive" in the system after the X number of hours, it is removed forcefully, as it is not sensible to keep it in the system for hours. |
| Log KDS data (no. of days) | The KDS stores data about the KOT activity in an SQL log table. To minimize space taken up by that table, all data older than X days is deleted once every day. |
| No. of log files (rotating) | When a log files reaches the maximum size, it is closed and a new one is started. To limit the number of log files, the number of log files to create is set here. |
| Log file size in Bytes | The maximum size of the log files. When maximum is reached, a new file is started. The default size is 5 MB. |
| Log KDS Printing only to KDS logfile | Check this to write the output only to the Kitchen Service logfile instead of to the printer (for debugging purposes). Note: that no printing occurs when this is checked! |
| Log KDS Order Status Updates | Check this to log the status of the KOTs in the KDS. To open up the loglist, in the BC backoffice, search for the Kitchen Order Status Log page |
Web KDS WebService Connections
See Connection Configuration for more details.
Command action buttons
There are three command actions on this page:
| Refresh WS Info | This command creates, or refreshes, the OData information for the KDSodataAPI web service in the Web Services List. It also refreshes the information in the JSON information field. This applies only for the Standard/Legacy KDS. |
| Reset KDS Configuration | This action resets the values in the page to default values. It also recalculates the JSON data. |
| Reset KDS Related Tables and Info | Cleans up all KDS related data in the system. All transactions must be posted/voided before this can be done. See Starting Over in Hospitality – Resetting KDS Tables and Information for detailed information. Note: Use this action with care, because you will lose all KOT related data in the LS Central system. |