Balluff MATRIX VISION mvBlueNAOS, Technical Manual

Page: 114 / 292

106
For older versions:
Like on Windows, log files will be generated, if the activation flag for logging called mvDebugFlags.mvd is avail-
able in the same folder as the application (however, using Windows log files will be generated automatically, be-
cause the applications are started from the same folder). By default, on Linux the
mvDebugFlags.mvd will be
installed in the installation's destination folder in the sub-folder "apps" . For example, if the destination folder was
"/home/workspace" , you can locate the mvDebugFlags.mvd like the following way:
user@linux-desktop:~$
// <- Starting the console window, you will be in the home directory: /home/
user@linux-desktop:~$ cd workspace/apps/
// <- Change the directory
user@linux-desktop:/home/workspace/apps$ ls -l
// <- List the directory
insgesamt 144
drwxr-xr-x 9 user user 4096 Mai 21 15:08 Callback
drwxr-xr-x 8 user user 4096 Mai 21 15:08 Callback_C
drwxr-xr-x 9 user user 4096 Mai 21 15:08 CaptureToUserMemory_C
drwxr-xr-x 3 user user 4096 Mai 21 15:03 Common
drwxr-xr-x 11 user user 4096 Mai 21 15:09 ContinuousCapture
drwxr-xr-x 9 user user 4096 Mai 21 15:09 ContinuousCaptureAllDevices
drwxr-xr-x 6 user user 4096 Mai 21 15:09 ContinuousCaptureFLTK
drwxr-xr-x 9 user user 4096 Mai 21 15:09 ContinuousCapture_C
drwxr-xr-x 11 user user 4096 Mai 21 15:09 DigitalIOs
drwxr-xr-x 9 user user 4096 Mai 21 15:09 FirmwareUpgrade
drwxr-xr-x 11 user user 4096 Mai 21 15:09 GenericInterfaceLayout
drwxr-xr-x 11 user user 4096 Mai 21 15:09 GenICamInterfaceLayout
-rw-r--r-- 1 user user 854 Mai 21 15:03 Makefile
-rw-r--r-- 1 user user 7365 Mai 21 15:03 Makefile.samp.inc
-rw-r--r-- 1 user user 20713 Mai 21 15:03 mvDebugFlags.mvd
// <- Log activation flag
drwxr-xr-x 7 user user 4096 Mai 21 15:09 mvDeviceConfigure
drwxr-xr-x 6 user user 4096 Mai 21 15:10 mvIPConfigure
drwxr-xr-x 6 user user 4096 Mai 21 15:11 mvPropView
drwxr-xr-x 9 user user 4096 Mai 21 15:11 SingleCapture
drwxr-xr-x 9 user user 4096 Mai 21 15:11 SingleCaptureStorage
For log file generation you have to execute your app from the folder where mvDebugFlags.mvd is located. E.g. if
you want to start wxPropView:
user@linux-desktop:/home/workspace/apps$ ./mvPropView/x86_64/wxPropView
// <- Start the executable from the folder, where \b mvDebugFlags.mvd is located.
Another possibility would be, to copy the mvDebugFlags.mvd file to the folder of the executable:
user@linux-desktop:/home/workspace/apps$ cp mvDebugFlags.mvd ./mvPropView/x86_64/wxPropView
// <- Copy the log activation flag
user@linux-desktop:/home/workspace/apps$ cd ./mvPropView/x86_64/
// <- Change the directory
user@linux-desktop:/home/workspace/apps/mvPropView/x86_64/$ ./wxPropView
// <- Start the executable
Afterwards, several log files are generated which are listed in
files.mvloglist
. The log files have the file
extension .mvlog. Please send these files to our support team.
1.16.3 General Issues
• The error counter increases (p. 107 )
• Which PC power settings are useful and possibly necessary? (p. 108 )
• Why does updating the device list take so long (p. 109 )
MATRIX VISION GmbH