Impact Acquire SDK GUI Applications
|
Using Windows, it is possible to access the log files generated by Balluff via the Help menu. Sending us the log files will speed up support cases.
The options are to
You can access the log files in Linux via /opt/ImpactAcquire/data/logs
.
You can also extract the directory using the following command
env | grep MVIMPACT_ACQUIRE_DATA_DIR
or move into the directory directly via
cd $MVIMPACT_ACQUIRE_DATA_DIR/logs
For older versions:
Like on Windows, log files will be generated if the activation flag for logging called mvDebugFlags.mvd is available in the same folder as the application (however, using Windows log files will be generated automatically, because 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 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 DeviceConfigure drwxr-xr-x 6 user user 4096 Mai 21 15:10 IPConfigure drwxr-xr-x 6 user user 4096 Mai 21 15:11 ImpactControlCenter 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 ImpactControlCenter:
user@linux-desktop:/home/workspace/apps$ ./ImpactControlCenter/x86_64/ImpactControlCenter // <- 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 ./ImpactControlCenter/x86_64/ImpactControlCenter // <- Copy the log activation flag user@linux-desktop:/home/workspace/apps$ cd ./ImpactControlCenter/x86_64/ // <- Change the directory user@linux-desktop:/home/workspace/apps/ImpactControlCenter/x86_64/$ ./ImpactControlCenter // <- 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.
If you have used the install script, you can access the log files via /~/ImpactAcquire/data/logs
.
You can also extract the directory using the following command
printenv | grep MVIMPACT_ACQUIRE_DATA_DIR
or move into the directory directly via
cd $MVIMPACT_ACQUIRE_DATA_DIR/logs
Another possibility would be to copy the mvDebugFlags.mvd file to the folder of the executable:
user@apple-mac:~/ImpactAcquire/apps$ cp mvDebugFlags.mvd ../bin/
(Copy the log activation flag)user@apple-mac:~/ImpactAcquire/apps$ cd ../bin/
(Change the directory)user@apple-mac:~/ImpactAcquire/bin$ ImpactControlCenter.app/Contents/MacOS/ImpactControlCenter
(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.