Page History

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

...

Enable debug mode

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

1. Shut down Axxon PSIM.
2. Start the Tweaki tweaki.exe utility (see the 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 Debug Mode from None value of the Debug mode parameter from Disabled to Debug 1, Debug 2, Debug 3, or Debug 4 (see the description of modes in The Settings panel of the Windows Axxon PSIM section).
5. Click the OK button.
6. Start Axxon PSIM.
   The Debug window item will appear appears in the Axxon PSIM main control menu.
   
7. Select Debug window in the main control menu to open the Debug debug window. The selected Debug window item will be is marked with a tick.
   

To hide the Debug debug window, select the Debug window item in the main control menu once moreagain.

...

Configure the parameters of log files

You can set log keeping parameters the parameters for log file storage both on the settings panel of the Axxon PSIM setting panel in section in the Tweaki.exe utility (see The Settings panel of the Axxon PSIM section)  and and using some parameters of registry keys:

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

Log files are rewritten overwritten when the maximum of one of the parameters is reached.

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

An example Example of the displayed information if StatusInfo=1 or no key 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 example 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 about information on registry keys in , see Registry keys reference guide.

Example.

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

One week later, the size of the log file is 100 MB. It starts being rewritten In this case, it starts to be overwritten, even though the log is kept has been stored less than it was the specified time. 

And if DebugZipDays has the If you set a value equal to the time period in days to keep logs, then logs are not rewritten − they are archived in the *.gz format and are kept for so long as it was specified in number of days for storing logs to the parameter of the DebugZipDays registry key, then when the maximum size is reached, the logs are not deleted but instead are zipped into a *.gz archive and stored for the number of days specified in the value of the DebugZipDays parameter.