JeVois Tech Zone - Recent questions and answers in User questions

Answered: For DemoArUco, how do you measure marker size?

Sat, 09 Jan 2021 09:11:19 +0000

You measure the Size " ML " Go indeed include the border !

What are the units of the absolute exposure "absexp" setting for the camera?

Fri, 23 Oct 2020 21:18:44 +0000

Is absolute exposure (absexp) in units of uS (microseconds) or 100uS? I see some cameras use 100uS but I can't confirm if this is true for JeVois.

absexp can be set from 1 to 1259 in JeVois Inventor. I looked at the datasheet for the camera sensor (ov7725 in my case) but I can't relate this back to any numbers I see there such as "Electronic Exposure Up To 510:1". Thanks!

Answered: Jevois-inventor does not load camera, 1.15 firmware, Latest Ubuntu 20 Virtualbox with 1.15

Mon, 14 Sep 2020 21:56:23 +0000

Hum, interesting, probably a bug in VirtualBox for Mac. You did install the extension pack, right?

Can you give us more parameters for your Mac? like OS version and Virtualbox version?

In the meantime, there is no advantage in running the inventor in VirtualBox, you should just run the native MacOS version and remove your USB filters. The workflow then typically is:

- install a USB filter in VirtualBox so that your USB-to-SD adapter gets attached to the virtual machine. Delete the filters you had for JeVois and its serial-over-USB.

- develop code in the linux virtual machine

- flash it to microSD

- insert microSD into JeVois

- start native MacOS JeVois Inventor and connect camera

Answered: what is the best way to locate a red laser pointer spot using jevois ?

Wed, 24 Jun 2020 22:24:44 +0000

Maybe this could help?

https://answers.opencv.org/question/52754/laser-pointer-detect-and-track/

looks like the best way would be to use an optical filter in front of the lens of JeVois. With that, the basic ObjectTracker module should work ok.

Answered: I am not able to add jevois repository and install jevois on ubuntu 18.04

Tue, 12 May 2020 07:48:17 +0000

yes, so sorry, the certificate expired and I had to go to the server physically today to renew it. Please try again, it should work now.

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

Sun, 05 Apr 2020 17:17:09 +0000

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: how to detect a laser pointer spot (650 nm) using jevois ?

Fri, 03 Apr 2020 09:38:59 +0000

You could try coding your own python module to detect your laser spot.

Using cv2.inRange you can detect red blobs in the camera image. Have a look here https://stackoverflow.com/questions/42840526/opencv-python-red-ball-detection-and-tracking and https://www.pyimagesearch.com/2015/09/14/ball-tracking-with-opencv/ to put you on rails.

Answered: I am trying cause my Arduino UNO to trigger the recording of Video through the Save Video Module in Jevois.

Wed, 11 Mar 2020 21:04:11 +0000

You need to remove the "setpar serout" that is in most of your strings. Basically, you should println() this to JeVois:

setmapping2 YUYV 640 480 30.0 JeVois SaveVideo

to setup, then

streamon

to start video streaming, etc

Answered: Jevois doesn't work after Raspberry PI reboots

Mon, 17 Feb 2020 18:11:45 +0000

Looks like jevois is getting confused somehow. Maybe you have some program like modemmanager (which is on Ubuntu) running on your Pi, which sends some modem probes over the USB-to-Serial port of JeVois on boot?

Looks like ModemManager is available on RPi, maybe you have it installed? Can you try sudo apt purge modemmanager and/or inspect your dmesg logs to see whether there is anything about modem, or ttyACM0 or such?

Answered: Darknet YOLO Freezing

Tue, 11 Feb 2020 21:30:08 +0000

Are you moving your camera? If so, you may have some connectivity issues at the mini-USB connector of JeVois. This connector was not designed for mechanical stress. Usually when we run demos, we mount the camera on a tripod and tie the USB cable to the legs of the tripod, so that there will be no mechanical stress or motion at the mini-USB connector. We have cameras running for months non-stop like that. I just confirmed that YOLO (1280x480 YUYV) is running fine and is not running out of memory, etc, it is stable here.

Also see other posts about freezing, in particular: you could also have a bad USB cable (we have had a few of those), or you can use some camera mount with strain relief, available on thingiverse.com (search for "jevois").

Answered: Green light remains on, fan turns on, camera not detected by Windows

Fri, 10 Jan 2020 18:35:07 +0000

If the card is fully inserted and you see no orange flash, maybe there is an issue with your JeVois unit. It is quite rare though as every unit is tested twice at the factory. Please email us at jevoisinc@gmail.com and we will help you.

On rare occasions, also the USB cable may be bad, so if you have another one please try this.

Answered: The global shutter camera returns a blurred image.

Tue, 17 Dec 2019 19:53:33 +0000

you need to adjust the lens to the viewing distance you need. Note that the lens also has a lock ring. So:

- first unscrew the lens a bit

- then turn the lock ring so that it moves towards the front of the lens

- then screw the lens + ring in until things are in focus

- then hold the lend and just turn the lock ring until it touches the mount of the lens. The lock ring will then prevent the lens from turning due to vibrations and such.

also note that there are two demo modules for the IMU which are not enabled by default:

http://jevois.org/moddoc/DemoIMU/modinfo.html

http://jevois.org/moddoc/DemoDMP/modinfo.html

to enable them, edit JEVOIS:/config/videomappings.cfg and search for DemoIMU and remove the # character in front of the two entries. This is very easy to do if you get JeVois Inventor, then use the 'config' tab to edit that file.

Answered: Trouble Connecting Camera Inventor on Windows

Wed, 04 Dec 2019 02:18:45 +0000

just to close this issue, it looks like it was caused by some problems in the modified module code.

If you send us your code, we can try to further track down the crash and see whether we could add some additional exception handler or such in the JeVois core to avoid a complete crash.

Answered: Uploading jpg's to the camera causes inventor to freeze

Wed, 04 Dec 2019 02:16:02 +0000

following private conversations, looks like the problem was in some helper code added to the module. Posting here just as it might be useful to others.

Remember that JeVois reboots when you eject the virtual USB drive, so the inventor will be greyed-out for 30 seconds or so until jevois has come back online.

if you have more problems, pls send us your code so we can try it here. Usually, the OS on the camera should not crash as we have been careful to catch all kinds of exceptions. But maybe the crash is indeed deep in one of the helpers you are using. Another way which may useful to debug is to run your module on your host computer (linux only), which may give you some more verbose messages when it crashes. Please see here:

http://jevois.org/doc/ProgrammerOrganization.html

and the tutorials.

Answered: Windows: Inventor not recognizing JeVois

Fri, 25 Oct 2019 19:22:44 +0000

Solved!

In Windows Settings i found a Setting for apps to be allowed to have access to the camera, it was OFF.

After turning on, it worked. Don't know why it was off, but now everything is fine!

Anyway, THX for your help!

Answered: Jevois is undetected by Windows PC. Tried Everything Please Help!

Mon, 14 Oct 2019 16:07:44 +0000

please see reply to your other question, @321

The LED should turn solid orange even if there is a driver problem, so most likely either a problem with the USB cable, USB port on your computer, or maybe the camera itself.

Answered: Jevois Camera not detected by Windows

Mon, 14 Oct 2019 16:05:35 +0000

The orange flash is good news, it indicates that the camera correctly boots up, the SD card is correctly inserted, etc. After the LED flashes orange briefly, it should turn solid orange after a few seconds and stay solid orange. If that is not happening, maybe try:

1) maybe your computer is not providing enough power to the USB port. Please try a USB 3.0 port, and have a look there:

http://jevois.org/doc/UserConnect.html

2) we have received a few cases of bad USB cables. Do you have any other mini-USB cable that you could try? Maybe from an external hard-drive?

Otherwise, please email us at jevoisinc@gmail.com and we can arrange a replacement.

Answered: Camera ChArUco calibration errors

Wed, 31 Jul 2019 18:51:41 +0000

It looks like either you are not getting enough detected corners, or they are not good. Maybe the problem is that you are running the ArUco detector in the camera? You should be configuring your camera as a dumb pass-through camera, as follows:

YUYV 1280 720 10.0 YUYV 1280 720 10.0 JeVois PassThrough

or use 640x480 if that is the calibration you want to create. Just to be sure, delete all other video mappings in your videomappings.cfg on the camera, so that this one is the one that will be picked.

Please see section on "Preparing your JeVois Camera" at http://jevois.org/tutorials/UserArUcoCalib.html

You do not want the camera itself to detect the markers and then draw their outlines and then send that video with the outlines to your PC. You want the camera to just send a plain image to the PC. The PC will then detect the markers and draw the green lines and small red squares you see in the screenshot of that tutorial.

Answered: Serial communication with Ubunut 16.04 Host

Tue, 23 Jul 2019 22:36:33 +0000

You probably need to send serial outputs to the serial-over-USB port, adding this to your initscript.cfg, after you have loaded a module with setmapping2:

setpar serout USB

Have a look here for more details: http://jevois.org/doc/UserCli.html

in particular, see section on "Serial communication types": JeVois sends two types of messages: log messages that provide information messages to humans (serlog), and output messages about what it sees and that are intended for machines (serout).

Then, each of these can be directed to either the hardware 4-pin port, or serial-over-USB port, or both, or none.

To select what goes where, you send instructions to JeVois, eg

setpar serout Hard # serout messages to 4-pin port

setpar serlog USB # serlog messages to serial-over-USB

setpar serout None # serout messages not sent anywhere

setpar serlog All # serlog messages sent to both 4-pin and serial-over-USB

In the code of a module, to send a message to serout, you use sendSerial(), and to send to serlog you use LINFO(), LERROR(), or LFATAL() and note that LFATAL() also throws an exception.

Answered: When i try camera with ffplay,it works, but not with jevois inventor

Wed, 29 May 2019 20:03:33 +0000

Maybe some graphics driver issue? jevois inventor is using Qt which will use OpenGL if available, so maybe there are issues with your OpenGL or graphics drivers.

Answered: USB baud rate

Thu, 09 May 2019 11:46:36 +0000

In general, the baud rate should be set by any app that uses the serial port. This is done with the SetCommState call, but of course the user interface varies from app to app.

None of this has anything to do with whether the serial port is built in, connected via USB, or something else.

Answered: Jevois does not working on Windows 10

Wed, 01 May 2019 22:12:10 +0000

Usually, this means that the host computer cannot provide enough power, or the port is too noisy. Sometimes this happens when you use a tablet, a laptop, or a desktop's "front panel" USB ports, as those often use a plain ribbon cable to connect to the motherboard, while they should use twisted pair cables with precisely matched lengths between data+ and data-. You should try to connect JeVois to ports that are directly attached to the motherboard (usually, in the back of the computer).

Please see http://jevois.org/doc/UserConnect.html for more on power.

Answered: Jevois detected but only shows video for 1 or 2 seconds

Tue, 16 Apr 2019 17:18:26 +0000

Usually, this means that your computer is not able to provide enough power to JeVois.

Thanks for mentioning that you are using a surface pro (tablet), this could be the problem.

Have a look here: http://jevois.org/doc/UserConnect.html

You may need to supplement the current that the tablet can provide, by using a Y cable, and connecting the power end of it either to a battery or a phone charger.

Answered: ModuleNotFoundError: No module named 'zbar'

Wed, 13 Mar 2019 16:18:45 +0000

Yes, I think it's time for you to switch to C++, your life will be much easier since all the libs you want are written in C/C++ anyway.

We will look into it. Right now we just compile some of the zbar source files directly into libjevjoisbase. This is because the zbar distro that came on buildroot at the time did not work for as many types of barcodes. But maybe it works better now. If so, we will get zbar installed system-wide by buildroot (including python bindings) and then we will just link to it as opposed to compiling some of it into libjevjoisbase.

Answered: how to un-distort 90deg fov image with gpu?

Wed, 13 Mar 2019 16:07:47 +0000

yes, following that post that you found, we wrote this module:

http://jevois.org/moddoc/DemoGPU/modinfo.html

which includes a barrel distortion shader (called Dewarp).

source here: http://jevois.org/basedoc/jvpkg_2modules_2JeVois_2DemoGPU_2DemoGPU_8C_source.html

Now, this is C++ only and you should use this component in your module: http://jevois.org/basedoc/classFilterGPU.html

Another approach is to use the CPU and OpenCV in python. A quick search on the web returns lots of results, for example:

https://medium.com/@kennethjiang/calibrate-fisheye-lens-using-opencv-333b05afa0b0

Answered: Can Jevois handle inputs + outputs ?

Tue, 05 Mar 2019 23:50:18 +0000

Yes, that is no problem, you can do both in and out over the serial link, it is bi-directional. See for example in setup() of the following code how we send some commands from the Arduino to JeVois, then we get coordinates data from jevois to Arduino over the same link:

http://jevois.org/tutorials/UserPanTilt.html

note that you have to think about your boot order to make sure the commands will be received (i.e., allow jevois to fully start before you power up your Arduino).

In addition to sending standard jevois commands, you can create custom commands,. Anything that the jevois engine does not recognize will be passed to a function parseSerial() of your module, See

http://jevois.org/doc/ModulePythonTutorial.html

for an example of parseSerial()

Answered: dirt / hair on my ar0135 sensor => how can i fix / clean it ?

Mon, 04 Mar 2019 19:42:27 +0000

Oh, so sorry, this is annoying. We are still working with the factory to make sure this does not happen in the future. From the sensor manufacturer (OnSemi), we receive sensors with a piece of yellow tape on top of it. This is so that it will not get scratched when the pick and place machine takes it out of the tray and places it on the PCB. Then, after the board is soldered, the tape has to be removed. On the samples we have looked at so far, we have found that sometimes indeed there is some dust which was under the yellow tape. In such cases, the sensor should be cleaned before the lens mount is added. But I guess your unit was not cleaned well.

There is a protective piece of glass on top of the chip. So there is little risk of damaging the chip. You should clean the glass with any microfiber cloth that you would normally use to clean glasses, camera lenses, etc. I would try to avoid any chemical at first, but if needed you could also use a small alcohol pad or iPhone wipe, and then wipe out all the alcohol with a microfiber lens cloth.

We have used these here in the lab to clean expensive DSLR cameras and lenses with good success:

https://www.amazon.com/EXTRA-LARGE-Clean-Clear-Microfiber/dp/B01IQH4SMO

Answered: Serial over USB not working with raspberry pi zero

Thu, 28 Feb 2019 19:26:17 +0000

Maybe you need an OTG cable? By default I guess the Pi Zero is a "device" (i.e., you would connect its microUSB to a regular USB port on a host computer). But you want it to operate as "host" here (and JeVois is your "device"), so the OTG cable might be what you need. See, eg,

https://raspberrypi.stackexchange.com/questions/84577/raspberry-pi-zero-w-connect-micro-usb-to-ftdi-to-arduino-board

just a thought but I don't have that hardware right now to test.

The OTG cable should go from microUSB that you plug into your PI Zero to a regular USB (type A) female. Then you would use a Y cable, connect one of the type A male to a power source, the other to your OTG female, and the mini-USB end to JeVois.

Like this: https://www.showmecables.com/micro-usb-2-b-male-to-a-female-6-in?gclid=CjwKCAiAqt7jBRAcEiwAof2uK-SYAzxasWY5hbg_EiiMZRcIuVxs8qRekFJfuDVqAiKWPb8oK2B4vxoChzMQAvD_BwE

Answered: Interfacing with LabView for FIRST robotics

Sun, 10 Feb 2019 03:04:52 +0000

Here is another link from chiefdephi that describes how to set up JeVois for streaming:

https://www.chiefdelphi.com/t/paper-from-zero-to-streaming-for-60/343748

If this does not answer your question, I'd suggest asking in chiefdelphi.com

There are people using JeVois cameras in FRC.

Answered: Which new machine vision module would you like?

Sun, 03 Feb 2019 09:53:48 +0000

Not a machine vision module, but would like to see some ROS support. Possibly rosserial?

https://wiki.ros.org/rosserial

Answered: What could make Inventor 0.5.0 send code as if it were commands?

Thu, 31 Jan 2019 09:38:08 +0000

I cleared __pycache__ for my own code and found that suddenly the problem went away, for all modules. (I tried this after reading another similar issue on this forum)

http://jevois.org/qa/index.php?qa=2586&qa_1=jevois-1-11-err-could-not-write-file-jevois-modules

Answered: camera not recognized in inventor on win10 pro

Wed, 23 Jan 2019 20:24:01 +0000

Maybe an issue with the serial-over-USB driver. Maybe you have installed some drivers for other hardware that is interfering with JeVois. Can you go to your device manager and inspect whether you have an error device, or maybe you need to uninstall some drivers there?

please see here for info:

http://jevois.org/doc/JeVoisInventor.html

section on "troubleshooting for windows"

Answered: stop a module without starting another one

Wed, 23 Jan 2019 20:06:37 +0000

how about just streamoff and no further set mapping? Please also see

http://jevois.org/qa/index.php?qa=2556&qa_1=is-there-an-existing-module-for-low-power-consumption

Answered: New camera lenses

Wed, 23 Jan 2019 19:36:03 +0000

You should unscrew the lens from the shroud, and then you can screw it into the sensor. Note that the base sensor/lens has glue on the lens thread. That is why you should have received en extra sensor with your lenses, and all the extra sensors have been ordered from the factory with no glue.

Please see last photo here: http://jevois.org/doc/Sensors.html

Answered: What module for an overhead people counter

Wed, 23 Jan 2019 19:31:51 +0000

We do not have one pre-built, but, as we say here, "if OpenCV can do it, then JeVois can run it".

So you can look around the web for OpenCV people counter. If you find some tutorials in python, then even easier, you can use JeVois Inventor to write the code. How about this:

https://github.com/LukashenkoEvgeniy/People-Counter

Answered: ArUco blob camera settings not working

Thu, 17 Jan 2019 20:22:07 +0000

Found the answer to this set autoexp to 1 and make sure it is before autogain

Answered: HSV values of moths on sticky trap

Mon, 14 Jan 2019 20:35:05 +0000

If you are using OpenCV in the backend (like we do in all our HSV-related modules), their range is 0...180 and hues as follows:

0=red/do not use because of wraparound, 30=yellow, 45=light green, 60=green, 75=green cyan, 90=cyan, 105=light blue, 120=blue, 135=purple, 150=pink

Usually you would start in the inventor with widening the double-cursor slider to the full range. Then bring one cursor towards the center until you start losing your objects, then back a bit. Finally same for the second cursor. You may want to first also widen the saturation and value sliders too, then try to narrow down all three ranges in sequence.

Answered: could you confirm that it is not possible to select video mode over the serial link

Mon, 14 Jan 2019 20:12:07 +0000

There are two ways of selecting a vision module:

- either pick a resolution on a video capture software when running with USB video output

- or send a setmapping2 command when running headless (no host computer grabbing video from jevois)

If your machine vision module supports headless operation with not video out, then you can switch between modules on the fly, you just send the following commands (e.g., so select the ArUco module):

streamoff

setmapping2 YUYV 320 240 30.0 JeVois DemoArUco

streamon

Those commands can be issued at any time, not only in initscript.cfg. To see if a module supports headless operation, please see its doc page, either in the inventor or online. It is indicated near the author name, etc towards top.

In JeVois Inventor 0.5.0 we added a Preferences menu that allows to start the inventor in headless mode. You should proceed as follows:

- check the headless checkbox in preferences

- close the inventor

- disconnect and reconnect jevois

- start the inventor

If you had a setmapping2 in initscript.cfg, that module will be running headless. If you want to switch to another module, send the above commands in the console.

Answered: Detecting moths in pheromone traps

Fri, 11 Jan 2019 19:22:12 +0000

Nice project! Do you have controlled lighting? If so, the moths are dark blobs on a lighter background? Then maybe this module could work:

http://jevois.org/moddoc/ObjectTracker/modinfo.html

If you need several simultaneous bob detection ranges, try http://jevois.org/moddoc/ArUcoBlob/modinfo.html

make sure you use JeVois inventor to easily adjust the double sliders for the HSV ranges.

Otherwise, please upload pictures of your trap somewhere and then link to them here. Maybe a more heavy-duty approach like TensorFlowEasy will be required.

Answered: Why can't I see console output in Inventor?

Wed, 09 Jan 2019 02:06:18 +0000

can you please try to download inventor 0.4.0 again and see whether the color look ok on your machine now? Changed the code that detects Mojave dark mode in the console pane. If it works we will push a new version with this and other improvements.

install old version

Sat, 05 Jan 2019 17:31:03 +0000

Hi guys,

For some reasons, I have to use version 1.9.0. So I cannot set up jevois via the method on the website.

Can I download the *.deb packages (jevois-opencv, jevois-host, jevois-platform, jevoisbase-host, jevoisbase-platform, jevois-sdk, jevois-sdk-dev) from jevois.usc.edu/old and install them via "sudo dpkg -i *.deb? Or is there some instructions on how to do that?

Thanks!

Does the JeVois Inventor work over wireless?

Wed, 02 Jan 2019 10:51:31 +0000

Is it possible to have the interactive debugging with JeVois Inventor work with the Jevois smart camera connected over wireless?

Low Power Mode

Wed, 26 Dec 2018 06:51:21 +0000

Hi, I would like to know if the camera system is able to perform any sort of sleep/hibernation mode when it does not require to run any image processing tasks. As our system only require computer vision processing for certain types of events triggered either via some sort of timer or external interrupt, we would like to explore the possibility of putting the module into low power mode to reduce current consumption rather than disabling power source to the module and having to go through the start up boot sequence every time.

Is there any cmd/code that we can exploit to do this?

Thanks and appreciate any help for this.

Adriel

Setting the system to sleep/hibernate

Tue, 18 Dec 2018 07:11:13 +0000

Hi,

I'm using the camera for a specific event detection and processing. All other times, I actually do not require the system to be powered up and running. Is there a way/cmd to initiate and send the system into hibernation/sleep/low-power mode to save power? This is short of disconnecting the power totally from the camera and having to go through the boot sequence over again everytime the system starts up.

Thanks,

Adriel

Smart camera connected but not recognized by JeVois Inventor?

Fri, 30 Nov 2018 11:15:27 +0000

Hi,

I am on Linux Host machine, I am able to connect via "screen /dev/ttyACM0" and I see video out in OBS Tool. So Camera is working and connected. Nonetheless Jevois Inventor (0.3.0 beta) does not connect. It says "Disconnected / - / -" and stays like this. I have built Jevois Inventor myself, as I am on Arch Linux (and there are only deb packages available).

I have following image on sd card: jevois-image-1.9.0-8G.img

ldd jevois-inventor
       linux-vdso.so.1 (0x00007ffeb92ca000)
       libQt5MultimediaWidgets.so.5 => /usr/lib/libQt5MultimediaWidgets.so.5 (0x00007f64c2e1f000)
       libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f64c27bd000)
       libQt5Multimedia.so.5 => /usr/lib/libQt5Multimedia.so.5 (0x00007f64c26a1000)
       libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f64c2110000)
       libQt5Network.so.5 => /usr/lib/libQt5Network.so.5 (0x00007f64c1f6c000)
       libQt5SerialPort.so.5 => /usr/lib/libQt5SerialPort.so.5 (0x00007f64c1f52000)
       libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f64c1a4e000)
       libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f64c18bf000)
       libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f64c18a5000)
       libc.so.6 => /usr/lib/libc.so.6 (0x00007f64c16e1000)
       libQt5OpenGL.so.5 => /usr/lib/libQt5OpenGL.so.5 (0x00007f64c1688000)
       libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f64c15f5000)
       libm.so.6 => /usr/lib/libm.so.6 (0x00007f64c146e000)
       libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f64c144d000)
       libpulse.so.0 => /usr/lib/libpulse.so.0 (0x00007f64c11fc000)
       libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f64c11c4000)
       libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f64c10e1000)
       libz.so.1 => /usr/lib/libz.so.1 (0x00007f64c0eca000)
       libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f64c0e38000)
       libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f64c0b66000)
       libudev.so.1 => /usr/lib/libudev.so.1 (0x00007f64c0b46000)
       libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007f64c0aba000)
       libicui18n.so.63 => /usr/lib/libicui18n.so.63 (0x00007f64c07dc000)
       libicuuc.so.63 => /usr/lib/libicuuc.so.63 (0x00007f64c060c000)
       libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0 (0x00007f64c0590000)
       libdouble-conversion.so.3.0.0 => /usr/lib/libdouble-conversion.so.3.0.0 (0x00007f64c0579000)
       libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f64c0574000)
       libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f64c0451000)
       /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f64c2f26000)
       libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f64c041e000)
       libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f64c02df000)
       libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f64c00cb000)
       libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f64c000f000)
       libpulsecommon-12.2.so => /usr/lib/pulseaudio/libpulsecommon-12.2.so (0x00007f64bfd8c000)
       libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f64bfd39000)
       libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f64bfa70000)
       libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f64bfa49000)
       librt.so.1 => /usr/lib/librt.so.1 (0x00007f64bfa3f000)
       liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f64bf819000)
       liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007f64bf7fa000)
       libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f64bf6db000)
       libicudata.so.63 => /usr/lib/libicudata.so.63 (0x00007f64bdceb000)
       libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f64bda79000)
       libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f64bda4f000)
       libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007f64bd9d3000)
       libasyncns.so.0 => /usr/lib/libasyncns.so.0 (0x00007f64bd9cb000)
       libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f64bd9b8000)
       libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f64bd796000)
       libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f64bd592000)
       libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f64bd38c000)
       libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x00007f64bd323000)
       libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f64bd11c000)
       libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f64bcef0000)
       libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00007f64bcc45000)
       libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f64bcc2c000)

Hardware serial gives no module output without USB connection

Wed, 28 Nov 2018 21:48:38 +0000

I have a microcontroller connected to the serial output of the JeVois camera. Via this serial line I can send commands to the camera and receive its response.

For the DemoArUco module, when I power up the camera, I receive the boot messages:

INFO: JeVois 1.9.0

INFO: Linux version 3.4.39

INFO: CPU: 1344MHz, 30C, load: 0.24 0.05 0.02 1/57 87

INFO: MemTotal: 238428 kB, MemFree: 170328 kB

INFO: OUT: YUYV 640x300 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:DemoSaliency C++

INF READY JEVOIS 1.9.0

Then I issue a number of commands:

setpar serout None

streamoff

setmapping2 YUYV 320 240 30.0 JeVois DemoArUco

setpar serialdev Hard

setpar serlog Hard

setpar serstyle Detail

setpar serout Hard

streamon

And get the response:

OK

ERR Unsupported command [streamoff]

INF Engine::setFormatInternal: OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:DemoArUco C++

INF Camera::setFormat: Camera set video format to 320x240 YUYV

INF Engine::setFormatInternal: Instantiating dynamic loader for /jevois/modules/JeVois/DemoArUco/DemoArUco.so

OK

INF Engine::setFormatInternal: Module [DemoArUco] loaded, initialized, and ready.

ERR engine:serialdev: Provided value [Hard] rejected because Parameter is frozen

OK

OK

OK

INF Camera::streamOn: 5 buffers of 153600 bytes allocated

INF Gadget::streamOn: 4 buffers of 384000 bytes allocated

OK

INF ArUco::detectMarkers: Loaded camera calibration from /jevois/share/camera/calibration320x240.yaml

And after that I receive the correct output if an ArUco code is in view, e.g.:

D2 U17 4 -284 215 -384 205 -382 178 -281 188

This all works fine as long as i power the camera via the USB of my computer (no jevois software such as jevois-inventor is running on this computer). However, when I power the camera via a power-only USB plug (so no data connection to the computer) I get the same response to the commands, but I receive no output if an ArUco code is in view.

What do I need to do to get this working without a connection to my computer?

It seems related to the problem mentioned here, but it gives no solution.

jevois-daemon -> Floating point exception (core dumped)

Sat, 24 Nov 2018 11:06:35 +0000

I executed jevois-daemon, but it isn't work..

erroe : Floating point exception (core dumped)

asdasd@ubuntu:~$ jevois-daemon
INF Engine::onParamChange: Using [stdio] hardware (4-pin connector) serial port
INF Engine::onParamChange: No USB serial port used
ERR VideoMapping::videoMappingsFromStream: In file /jevois/config/videomappings.cfg:518: No .so|.py found for JeVois/FaceDetector -- SKIPPING.
INF Engine::postInit: Loaded 60 vision processing modes.
INF Engine::postInit: Initalizing Python...
INF Engine::postInit: Starting camera device /dev/video0
INF Camera::Camera: [10] V4L2 camera /dev/video0 card JeVois-A33 Smart Camera bus usb-0000:02:03.0-1
INF Engine::postInit: Using display for video output
Floating point exception (core dumped)

how can I execute jevois-daemon properly?

Thank you

A Question about videomapping

Sat, 24 Nov 2018 04:02:24 +0000

Hello,

I'd like to create and use a new SaveVideo module 640x480 size.

so, I wrote 'NONE 0 0 0 YUYV 640 480 30.0 Jevois SaveVideo' in jevois/config/videomappings.cfg.

and I execute 'jevois-add-videomapping NONE 0 0 0 YUYV 640 480 30.0 Jevois SaveVideo'.

As a result, I saw it on the listmappings

But, it didn't work properly

When I ran the SaveVideo module that I had written, the video introducing jevois was displayed and later the result was that I filmed running another module.

help me please

Thank you

I want use new videomapping

Fri, 23 Nov 2018 07:32:06 +0000

I'd like to use SaveVideo module in a different size.

so, I wrote NONE 0 0 0 YUYV 640 480 30.0 JeVois SaveVideo in jevois/config/videomappings.cfg

then, I excuted sudo jevois-add-videomapping NONE 0 0 0 YUYV 640 480 30.0 JeVois SaveVideo

and checked listmappings

AVAILABLE VIDEO MAPPINGS:

0 - OUT: NONE 0x0 @ 0fps CAM: YUYV 1280x1024 @ 15fps MOD: JeVois:DemoARtoolkit C++
1 - OUT: NONE 0x0 @ 0fps CAM: YUYV 640x480 @ 30fps MOD: JeVois:SaveVideo C++
2 - OUT: NONE 0x0 @ 0fps CAM: YUYV 640x480 @ 30fps MOD: JeVois:DemoARtoolkit C++
3 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:DemoARtoolkit C++
4 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:ObjectTracker C++
5 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:FirstVision C++
6 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:FirstPython Python
7 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:SaveVideo C++
8 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:SaveVideo C++
9 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:RoadNavigation C++
10 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:DemoArUco C++
11 - OUT: NONE 0x0 @ 0fps CAM: YUYV 320x240 @ 15fps MOD: JeVois:PythonObject6D Python
12 - OUT: NONE 0x0 @ 0fps CAM: YUYV 176x144 @ 120fps MOD: JeVois:FirstVision C++
13 - OUT: NONE 0x0 @ 0fps CAM: YUYV 176x144 @ 120fps MOD: JeVois:SaveVideo C++
14 - OUT: NONE 0x0 @ 0fps CAM: YUYV 176x144 @ 120fps MOD: JeVois:FirstPython Python
15 - OUT: 0�� 32767x3 @ 0fps CAM: \s+ 640x480 @ 60fps MOD: JeVois:SaveVideo C++
16 - OUT: YUYV 1280x1092 @ 7fps CAM: YUYV 1280x1024 @ 7fps MOD: JeVois:TensorFlowEasy C++
17 - OUT: YUYV 1280x480 @ 15fps CAM: YUYV 640x480 @ 15fps MOD: JeVois:DarknetYOLO C++
18 - OUT: YUYV 960x240 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:DemoNeon C++
19 - OUT: YUYV 880x480 @ 10fps CAM: YUYV 640x480 @ 10fps MOD: JeVois:DarknetSaliency C++
20 - OUT: YUYV 640x546 @ 20fps CAM: YUYV 640x480 @ 20fps MOD: JeVois:MarkersCombo C++
21 - OUT: YUYV 640x500 @ 20fps CAM: YUYV 640x480 @ 20fps MOD: JeVois:DemoArUco C++
22 - OUT: YUYV 640x480 @ 60fps CAM: YUYV 640x480 @ 60fps MOD: JeVois:SaveVideo C++
23 - OUT: YUYV 640x480 @ 30fps CAM: YUYV 640x480 @ 30fps MOD: JeVois:SaveVideo C++
24 - OUT: YUYV 640x480 @ 29fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:JeVoisIntro C++
25 - OUT: YUYV 640x480 @ 15fps CAM: YUYV 640x480 @ 15fps MOD: JeVois:PythonTest Python
26 - OUT: YUYV 640x480 @ 7.5fps CAM: YUYV 640x480 @ 7.5fps MOD: JeVois:DiceCounter C++
27 - OUT: YUYV 640x360 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:JeVoisIntro C++
28 - OUT: YUYV 640x312 @ 50fps CAM: YUYV 320x240 @ 50fps MOD: JeVois:DemoSalGistFaceObj C++
29 - OUT: YUYV 640x300 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:DemoSaliency C++
30 - OUT: YUYV 640x290 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:FirstVision C++
31 - OUT: YUYV 640x252 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:FirstPython Python
32 - OUT: YUYV 640x240 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:ColorFiltering C++
33 - OUT: YUYV 544x240 @ 15fps CAM: YUYV 320x240 @ 15fps MOD: JeVois:DarknetSingle C++
34 - OUT: YUYV 512x240 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:TensorFlowSaliency C++
35 - OUT: YUYV 464x240 @ 15fps CAM: YUYV 320x240 @ 15fps MOD: JeVois:TensorFlowSingle C++
36 - OUT: YUYV 352x288 @ 30fps CAM: YUYV 352x288 @ 30fps MOD: JeVois:PythonSandbox Python
37 - OUT: YUYV 320x308 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:TensorFlowEasy C++
38 - OUT: YUYV 320x290 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:FirstVision C++
39 - OUT: YUYV 320x288 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:SaliencySURF C++
40 - OUT: YUYV 320x286 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:DemoQRcode C++
41 - OUT: YUYV 320x266 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:ArUcoBlob C++
42 - OUT: YUYV 320x262 @ 15fps CAM: YUYV 320x240 @ 15fps MOD: JeVois:PythonObject6D Python
43 - OUT: YUYV 320x260 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:DemoArUco C++
44 - OUT: YUYV 320x258 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:DemoARtoolkit C++
45 - OUT: YUYV 320x256 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:RoadNavigation C++
46 - OUT: YUYV 320x254 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:ObjectTracker C++
47 - OUT: YUYV 320x252 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:ObjectDetect C++
48 - OUT: YUYV 320x240 @ 60fps CAM: YUYV 320x240 @ 60fps MOD: JeVois:SaveVideo C++
49 - OUT: YUYV 320x120 @ 30fps CAM: YUYV 160x120 @ 30fps MOD: JeVois:DemoBackgroundSubtract C++
50 - OUT: YUYV 176x144 @ 120fps CAM: YUYV 176x144 @ 120fps MOD: JeVois:SaveVideo C++
51 - OUT: YUYV 64x192 @ 25fps CAM: YUYV 320x240 @ 25fps MOD: JeVois:SalientRegions C++
52 - OUT: GREY 640x480 @ 29fps CAM: YUYV 640x480 @ 29fps MOD: JeVois:EdgeDetection C++
53 - OUT: GREY 640x480 @ 20fps CAM: YUYV 640x480 @ 20fps MOD: JeVois:PythonOpenCV Python
54 - OUT: GREY 320x960 @ 45fps CAM: YUYV 320x240 @ 45fps MOD: JeVois:EdgeDetectionX4 C++
55 - OUT: GREY 320x240 @ 59fps CAM: YUYV 320x240 @ 59fps MOD: JeVois:EdgeDetection C++
56 - OUT: GREY 320x240 @ 30fps CAM: YUYV 320x240 @ 30fps MOD: JeVois:SuperPixelSeg C++
57 - OUT: GREY 176x288 @ 100fps CAM: YUYV 176x144 @ 100fps MOD: JeVois:OpticalFlow C++
58 - OUT: GREY 176x144 @ 120fps CAM: YUYV 176x144 @ 120fps MOD: JeVois:DemoEyeTracker C++
59 - OUT: GREY 160x495 @ 60fps CAM: YUYV 160x120 @ 60fps MOD: JeVois:DemoCPUGPU C++
60 - OUT: GREY 128x117 @ 5fps CAM: YUYV 160x120 @ 5fps MOD: JeVois:DenseSift C++

I executed jevois-daemon --videomapping=1, but it didn't work properly

Window running other modules is displayed and video displayed in window is stored.

help me, please

With the macos mojave the jevois-inventor program crashes

Fri, 16 Nov 2018 18:06:24 +0000

Hi,

when I connect the camera I get the following message:

Malformed JeVois software version from JeVois Smart Camera

Why?

Thanks and regards,

jeffry