Package Details: ueye-cli 4.96.1-1

Git Clone URL: https://aur.archlinux.org/ueyed.git (read-only, click to copy)
Package Base: ueyed
Description: IDS uEye command line tools
Upstream URL: https://en.ids-imaging.com
Licenses: custom
Submitter: de-vries
Maintainer: de-vries
Last Packager: de-vries
Votes: 5
Popularity: 0.000000
First Submitted: 2015-11-13 14:31 (UTC)
Last Updated: 2023-08-29 14:59 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6

retrakker commented on 2017-03-09 09:34 (UTC)

Hi there. I have a small update to the packagefile in a gist: https://gist.github.com/seichter/9cc31fc6e457630a1442b0edfc934744

j-l commented on 2017-01-03 12:48 (UTC) (edited on 2017-01-03 12:49 (UTC) by j-l)

One shouldn't forget to enable the ueyeusbd.service via systemctl when using the USB connection. This service discovers the ueye. Perhaps the PKGBUILD could echo this to the user after install.

Lindhe commented on 2016-03-08 08:02 (UTC)

Ehm, actually it might be a hardware problem. Like my USB3 port thingy. I spun up a virtual machine with Ubuntu 14.04 and installed the official drivers (as I have done on a physical machine once) and passed through the camera port, and that had the exact same problem... I'll get back if I identify it to actually be a problem with this package.

de-vries commented on 2016-03-07 17:57 (UTC)

Interesting, I only have Ethernet models so I can't test that. Sounds like an upstream problem though, so you could try to contact IDS or your supplier.

Lindhe commented on 2016-03-07 14:49 (UTC) (edited on 2016-03-07 14:49 (UTC) by Lindhe)

For me, the divers crash when running the camera at 60 Hz over USB3.

de-vries commented on 2015-11-13 14:42 (UTC)

For some reason I could only get this to work with an interface named eth0 (did not test eth1), even with the proper settings in /etc/ueye/ueyeethd.conf. So far I have been unable to find out why.

« First ‹ Previous 1 2 3 4 5 6