Page History

Debug mode is a special operation mode when the Debug window is open, and is the mode at which you can view the debug window designed for analyzing the progress current status of the Axxon PSIM software operation and for prompt the operational debugging in case if errors occur. Log files are created in this mode—they are stored on the disk for a specific time period. 

Enabling debug mode

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

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

To hide the Debug debug window, select you must reselect the Debug window item in the menu once moremain control panel.

Configuring log file parameters

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

1. The Time of log keeping (hours) parameter means the same as  equals the DebugTime registry key. It specifies the number of hours for keeping the log filesfile. 48 hours by default.
   
2. The Maximum size (MB)  parameter means the same as DebugSize equals the DebugSize registry key. It specifies the number of megabytes provided allocated for log. 100 MB by default.
   
3. The DebugZipDays registry key enables the logs log archiving mode in the .gz format and specifies sets the time period for of their keepingstorage. 2 days days by default.
   

Log files are rewritten when the maximum of when one of the parameters is reachedreaches 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 info displayed information lines ,, displayed every 10 seconds , to 6 (this will reduce reduces the size of the log file), it is necessary to you must add the StatusInfo=0 key.

An The example of the displayed information if when there is the StatusInfo=1 or no keykey 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)

An 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).

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

Example.

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

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

And if DebugZipDays has the value you assign the value to the DebugZipDays parameter in the registry that is equal to the time period in days to keep logs, then logs are not rewritten − they are 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 so as long as it was is specified in the DebugZipDays parameter.