EN | CZ
About companyProductsShopTechnical support
Moravian Instruments
Main page
About company
Software download
Documents download
Products
The Control Web System
VisionLab Machine Vision Software
DataCam Cameras and DataLight Lighting Units
DataLab industrial input/output system
Scientific cameras
Price list
Services
Custom-made Solutions
Technical support
Control Web Examples

Main pageNews

Improved debugging window in Control Web 9.
 The use of debugging outputs is one of the simplest and at the same time most effective ways to detect and understand errors in a program. It allows the developer to monitor what is really happening in the application “at runtime” and verify whether the program behaves as expected.

The Log window has been completely redesigned in Control Web 9. Messages are no longer displayed in separate tabs (error, debug, messages, and system), but by selecting in the tree on the left side of the window it is possible to display either all messages or only one group. It is now possible to view all messages in one table. This makes it possible, for example, to see debug messages in the context of communication error messages or messages about establishing communication with a remote application.

The messages are displayed in a clear table. It is possible to search or filter messages in the message window according to a specified mask.

Saving to files

In previous versions, events were saved into the files 'cw_dbg'/'cw_msg'/'cw_sys.log'. If the file size was exceeded, Control Web renamed the file extension to 'lo$' (overwriting the existing file) and created a new one. If the maximum file size was set too small, it was not possible to monitor what happened in the application a long time ago. If the user wanted to preserve a longer history of information about the application runtime and set a larger maximum file size, the writing could unnecessarily slow down the application.

In the new version of the Control Web system, debugging messages are stored in several files. The user can set the size of one file and the number of files to be kept. The files thus have a “reasonable” size and it is still possible to view a longer history.

The file size can represent one hour or one day (parameter log_file_fragmentation). The number of files kept on disk can be set using the parameter log_file_history (set by years, months, days, and optionally hours). Everything can be easily configured in the application data editor.

Older records can be displayed in files on disk or during application runtime directly in the Log Window by selecting from the tree. There is one item in the tree for each created file.

The file name begins with cw_msg_, cw_dbg_, cw_err_, followed by the year, month, day, and optionally hour.

The files are text-based and can be viewed in any text editor. The file format is CSV.

The CSV (Comma-Separated Values) format is a simple text format designed for storing and exchanging tabular data. Each line in a CSV file represents one record (for example, a row in a table), and the individual values in a line are separated by a comma or another delimiter, most often a semicolon. This format is widely supported – it can be easily opened in spreadsheet applications such as Microsoft Excel or Google Sheets, as well as in database and programming tools.

              Sep=;
              UTC; Color; Application; Message
              2025-10-15 13:44:45.717; 0x0; "test panel"; "Z06 Valve VT-125 opened"
              2025-10-15 13:44:50.719; 0x0; "test panel"; "Communication failure with PLC 15"
              2025-10-15 13:45:00.720; 0x0; "test panel"; "Z17 Valve VT-346 opened"
              2025-10-15 13:45:01.721; 0x0; "test panel"; "Z06 Pump C16 failure"
              2025-10-15 13:45:16.723; 0x0; "test panel"; "Z06 Maximum level exceeded in tank Z-45"
            
 
 | About company | Products | Technical support | Software download | Documents download | 
Moravian Instruments, Masarykova 1148, Zlin 4, CZ-76302, Czech Republic