Documentation for Axxon PSIM 2.0. Documentation for other versions of Axxon PSIM is available too.

Previous page Next page


On the page:


Debug mode is the mode at which you can view the debug window designed for analyzing the current status of the Axxon PSIM operation and for the operational debugging if errors occur.

Enabling debug mode

Starting with the 1.0.1.172 hotfix, the Debug 4 mode is enabled by default. In previous versions, Debug mode is disabled by default. To enable the debug mode, do the following:

  1. Shut down Axxon PSIM.
  2. Start the tweaki.exe utility (see Starting and shutting down the tweaki.exe utility).
  3. Select the Axxon PSIM section in the tree located on the left side of the utility dialog window.
  4. Change the value of the Debug mode parameter from Disabled to Debug 1, Debug 2, Debug 3, or Debug 4 (see description of modes in The settings panel of the PSIM section).
  5. Click the OK button.
  6. Start Axxon PSIM.
    As a result, the new Debug window item appears in the Axxon PSIM main control panel.
  7. Select the Debug window item in the main control panel to display the debug window on the monitor screen. The selected Debug window menu item is marked with a checkbox.

To hide the debug window, you must reselect the Debug window item in the main control panel.

Note

The debug mode slows down the system operation and increases the use of system resources. We strongly recommend enabling debug mode for debugging purposes only and disabling it after the configuration is complete.

Note

For more details about working with Debug window, see The Script object. Programming using the JScript language in the The Debug window section.

Configuring log file parameters

You can set the log-keeping parameters both on the Axxon PSIM settings panel in the tweaki.exe utility (see The settings panel of the PSIM section) and using some registry keys:

  1. The Time of log keeping (hours) equals the DebugTime registry key. It specifies the number of hours for keeping the log file. 48 hours by default.
  2. The Maximum size (MB) equals the DebugSize registry key. It specifies the number of megabytes allocated for log. 100 MB by default.
  3. The DebugZipDays registry key enables the log archiving mode in the .gz format and sets the period of their storage. 2 days by default.

Log files are rewritten when one of the parameters reaches the maximum.

When the Debug 4 debug mode is enabled, the video.run log file displays the most detailed information about the file system and memory usage of each camera every 10 seconds. To reduce the number of displayed information lines every 10 seconds to 6 (this reduces the size of the log file), you must add the StatusInfo=0 key.

The example of the displayed information when there is the StatusInfo=1 key or when it is absent:

Uptime: 00:00:12, memory: 423.0 MB
[FS]Health ok.
[FS]Ring cycles count: 0
[FS]Total index in memory size: 62.7 KB
[FS]Total recorders: 4, MemFile: -1, memFile total size: 16.0 MB, last frame skipped time: none, WritingQueueSize: 1500, avg speed: 18.99 MB/sec.
[FS]Total readers: 0 (cached frames: 0)
[FS]Total cameras: 4, internal VMDA detectors: 0, external VMDA detectors: 0. zone detectors: 0.
[FS]Camera 1. Writing queue: 1 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 1, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 2. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 2, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 3. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 3, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 4. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 4, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
Total registered senders: 1
Objects:
VideoFrame: 38(max: 77 at '09-09-22 14:40:13.014')
AudioFrame: 0(max: 5 at '09-09-22 14:40:08.816')
Msg: 73(max: 130 at '09-09-22 14:40:06.733')
Active[1]
SendVideoFrame(local=1,compressed=1) to 'TAG-5509.1': value: 0 (max 0), delay = 46 ms, 09-09-22 14:40:15.548
Inactive[0](no new data for more than 15 seconds)

The example of the displayed information if StatusInfo=0:

Uptime: 00:00:12, memory: 427.0 MB
[FS]Health ok.
[FS]Ring cycles count: 0
[FS]Total index in memory size: 52.9 KB
[FS]Total recorders: 4, MemFile: -1, memFile total size: 16.0 MB, last frame skipped time: none, WritingQueueSize: 1500, avg speed: 7.42 MB/sec.
[FS]Total readers: 0 (cached frames: 0).

For more information about registry keys, see Registry keys reference guide.

Example.

The Time of log keeping is 720 hours (1 month), and the log Maximum size is 100 MB.  

In a week after the log recording starts, the size of the log file is already 100 MB. In this case, it is rewritten, though the log is kept for less than the specified period. 

And if you assign the value to the DebugZipDays parameter in the registry that is equal to the period in days during which logs must be kept, then when the maximum size is reached, logs aren't removed—they are archived in the *.gz format and are kept for as long as it is specified in the DebugZipDays parameter.


  • No labels