Welcome new user! You can search existing questions and answers without registering, but please register to post new questions and receive answers. Note that due to large amounts of spam attempts, your first three posts will be manually moderated, so please be patient.
Because of un-manageable amounts of spam despite our use of CAPTCHAs, email authorization, and other tools, we have discontinued this forum (see the 700k+ registered users with validated email addresses at right?). Please email us any questions or post bug reports and feature requests on GitHub at https://github.com/jevois -- The content below remains available for future reference.

Jevois daemon hangs (solid green) upon Jevois-Inventor startup

0 votes
This problem started last week. I'm using jevois 1.15 and jevois-inventor beta 0.5 on my Ubuntu 18.04 - not VM.

My camera suddenly stopped displaying video on my host computer, but still works in headerless mode. This error arose as I was creating a module's script.cfg file, which I've since deleted. Whenever I try to use Jevois-Inventor (or any other webcam viewer, for that matter) Jevois's LED turn solid green, and the computer doesn't recognise it is connected (I cease being able to communicate with the camera, and I get a notification that a USB device has been disconnected). I get no errors printing in terminal when I use other viewers, but whenever I attempt running Jevois-Inventor from terminal, it prints this error:

"QNetworkReplyHttpImplPrivate::_q_startOperation was called more than once QUrl("http://jevois.org/version")"

and

"Unable to query the parameter info: "Invalid argument""

and

"CameraBin error: "Could not read from resource.""

Similarly, I have not been able to operate the camera in PassThrough mode, and running the daemon on my host computer, despite aligning USB mode of PassThrough with the module I intend to run. Instead, video is streamed from my laptop's webcam.

I should note, I've no problems operating the camera in headerless mode (by issuing commands to the Jevois via serial socket connection, or "jevois-cmd" command). Also to note, other usb camera work fine on my computer.

Has anyone experienced anything similar, or have and sage words of advice?

Thanks!
asked Feb 12, 2020 in User questions by otd (180 points)

2 Answers

0 votes
Maybe your USB host (linux PC) got confused. You may want to check out dmesg on the host. Sometimes after many connect/disconnect cycles the host runs out of USB ports somehow.

Rebooting the host should fix it.
answered Feb 13, 2020 by JeVois (46,580 points)
that's not the problem.  My host has been rebooted many times since the problem started and the port used is consistently /dev/ttyACM0.
strange, can you disconnect the camera, connect it again, and run a dmesg in a terminal of your host? Can you see a UVC device being registered? Something like this:

[...]
[4768736.704777] usb 1-1.3: new high-speed USB device number 13 using xhci_hcd
[4768736.809464] usb 1-1.3: New USB device found, idVendor=1d6b, idProduct=0102
[4768736.809470] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[4768736.809473] usb 1-1.3: Product: JeVois-A33 Smart Camera
[4768736.809476] usb 1-1.3: Manufacturer: JeVois Inc
[4768736.847915] uvcvideo: Found UVC 1.00 device JeVois-A33 Smart Camera (1d6b:0102)
[4768736.849892] input: JeVois-A33 Smart Camera as /devices/pci0000:00/0000:00:1c.6/0000:09:00.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input29
[4768736.851499] cdc_acm 1-1.3:1.2: ttyACM0: USB ACM device
So after I disconnect my camera and then reconnect, it is recognised ok.  Although I'm now just noticing the messages "Entity type for entity [...] was not initialized". Not sure what that means.

This is the output from dmesg upon reconnecting.

[10457.447234] usb 3-2: new high-speed USB device number 8 using xhci_hcd
[10457.595990] usb 3-2: New USB device found, idVendor=1d6b, idProduct=0102
[10457.595993] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10457.595993] usb 3-2: Product: JeVois-A33 Smart Camera
[10457.595994] usb 3-2: Manufacturer: JeVois Inc
[10457.597221] uvcvideo: Found UVC 1.00 device JeVois-A33 Smart Camera (1d6b:0102)
[10457.597574] uvcvideo 3-2:1.0: Entity type for entity Processing 2 was not initialized!
[10457.597575] uvcvideo 3-2:1.0: Entity type for entity Camera 1 was not initialized!
[10457.597632] input: JeVois-A33 Smart Camera: JeVois as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/input/input21
[10457.597888] cdc_acm 3-2:1.2: ttyACM0: USB ACM device
[10457.598124] usb-storage 3-2:1.4: USB Mass Storage device detected
[10457.598229] scsi host6: usb-storage 3-2:1.4
0 votes
If all else fails (and we found that it did), a reflashing of the Jevois sd card should hopefully do the trick.

We never found the source of the ambiguous error, but after reflashing the sd card, adding the same modules and jevois core code changes we had made previously, we found the camera was recognised by webcam viewing software (and jevois inventor) again.
answered Apr 5, 2020 by otd (180 points)
...