
21.7 "Device or resource busy" debug messages
If your application does not work and you see timeout messages please turn on debugging as mentioned
above.
After restarting the application you may see lines similar to these in the terminal window:
{1693166512, 1008, 1879}: media_setup_link(196): Unable to
setup link (Device or resource busy)
{1693166699, 187, 1879}: StartV4L2Acquisition(686): Failed
to enable streaming: 16(Device or resource busy).
Result of start: 0(DMR_NO_ERROR)
This problem usually occurs if more than one application is trying to use the camera's sensor at the same time.
mvIMPACT Acquire makes use of locking files to ensure hat the hardware is only controlled by one
application or thread. Please ensure that all mvIMPACT Acquire applications have been stopped before
starting a new application.
21.8 No mvIMPACT Acquire application is running but still
seeing "Device or resource busy" debug messages
If an application crashes and is unable to clean up its locking files correctly it is possible that subsequent
mvIMPACT Acquire applications will believe that the hardware is still in use. If you are sure that this is not
the case you can remove the locking files by hand and restart your application. The locking files are to be
found in the directory
/tmp/mv/
. It should be safe to remove the whole directory if no mvIMPACT Acquire
application is running:
rm -rf /tmp/mv
Since this directory is part of the RAM disk and not saved on the SD card the easiest way to solve this
problem is to reboot the camera which will erase any locking files and recreate the directory when
needed:
reboot
.
21.9 mvBlueLYNX-X boots but there is no display
If the camera boots and there is no display, the
/media/mmcblk0p1/uEnv.txt
file could be damaged or
misconfigured. However, it is still possible to login to the device using ssh.
To correct this file, you will need
the IP address of the mvBlueLYNX-X and
1.
2.
Please follow these steps:
Connect to the mvBlueLYNX-X:
(A.B.C.D is the current IP address of the
mvBlueLYNX-X)
User:
root
Password:
matrix
1.
Afterwards you can change uEnv.txt via the command line, e.g.
Using an editor like vi or like this:
1.
2.
mvBlueLYNX-X Technical Manual
MATRIX VISION GmbH
22 April 2016 Version - 1.49
207
Summary of Contents for mvBlueLYNX-X
Page 1: ...mvBlueLYNX X Technical Manual 22 April 2016 Version 1 49 Copyright 2017 MATRIX VISION GmbH...
Page 2: ......
Page 10: ...VIII...
Page 11: ...1 mvBlueLYNX X Technical Manual MATRIX VISION GmbH 22 April 2016 Version 1 49 1...
Page 12: ...mvBlueLYNX X Technical Manual 2 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 22: ...mvBlueLYNX X Technical Manual 12 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 24: ...mvBlueLYNX X Technical Manual 14 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 27: ...mvBlueLYNX X Technical Manual MATRIX VISION GmbH 22 April 2016 Version 1 49 17...
Page 28: ...mvBlueLYNX X Technical Manual 18 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 30: ...mvBlueLYNX X Technical Manual 20 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 50: ...mvBlueLYNX X Technical Manual 40 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 108: ...mvBlueLYNX X Technical Manual 98 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 124: ...mvBlueLYNX X Technical Manual 114 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 190: ...mvBlueLYNX X Technical Manual 180 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 214: ...mvBlueLYNX X Technical Manual 204 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 226: ...mvBlueLYNX X Technical Manual 216 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 230: ...mvBlueLYNX X Technical Manual 220 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 236: ...mvBlueLYNX X Technical Manual 226 22 April 2016 Version 1 49 MATRIX VISION GmbH...