1.16 Troubleshooting
105
-2145
DMR_ACQUISITION_
←
-
ENGINE_BUSY
An error returned when the
user application attempts to
start the acquisition engine
at a time, where it is already
running.
2.5.3
[-2145]
-2146
DMR_BUSY
An error returned when the
user application attempts to
perform any operation that
currently
for
any
reason
cannot be started because
something else already run-
ning.
The log-output will provide
additional information. 2.
←
-
32.0
[-2146]
-2147
DMR_OUT_OF_MEMORY
An
error
returned
when
for any reason internal re-
sources (memory, handles,
...) cannot be allocated.
The log-output will provide
additional information. 2.
←
-
32.0
[-2147]
-2199
DMR_LAST_VALID_
←
-
ERROR_CODE
Defines the last valid error
code value for device and
device manager related er-
rors.
[-2199]
1.16.2
Accessing log files
If you need support using our products, you can shorten response times by sending us your log files. Accessing the
log files is different in Windows and Linux:
1.16.2.1
Windows
Since
mvIMPACT Acquire 2.11.9
You can access the log files in Windows using
wxPropView
(p.
). The way to do this is described in
"Accessing
Log Files"
in the
"mvIMPACT Acquire SDK GUI Applications"
manual.
1.16.2.2
Linux
Since
mvIMPACT Acquire 2.24.0
You can access the log files in Linux via
/opt/mvIMPACT_Acquire/data/logs
.
You can also extract the directory using the following command
env | grep MVIMPACT_ACQUIRE_DATA_DIR
or change the directory directly via
cd $MVIMPACT_ACQUIRE_DATA_DIR/logs
MATRIX VISION GmbH
Summary of Contents for MATRIX VISION mvBlueNAOS
Page 1: ...mvBlueNAOS Technical Manual English Version 2 14...
Page 2: ......
Page 8: ......
Page 22: ...14 MATRIX VISION GmbH...
Page 183: ...1 18 Use Cases 175 Figure 2 Sample settings MATRIX VISION GmbH...
Page 286: ...278 Test setup front side MATRIX VISION GmbH...
Page 292: ...284 MATRIX VISION GmbH...