Awesome video Ray. I'm happy to see that it seems to be stable and has been running for a few days.

One quick comment about frame rates though.

So, the frame rate that you're seeing from OpenCV's frame grabber is likely 15 or maybe 30FPS.. The rate that Yolo is actually recognizing frames might be closer to 3 to 4 frames per second. The way it's implemented, Yolo will skip frames if it's not done processing the current one. Once it's done, it adds it's boxes to the current frame that is being displayed.

The nice advantage of this approach is that the normal frame rate for OpenCV isn't affected (much) when Yolo is or isn't running.

The disadvantage is that the boxes that are drawn might be a few frames out of synch with their actual location.

There where no drivers for them in the more resent version of the kernel / Jetpack , time consuming stuff :/

Also batteling problems getting Myrobotlab to se my ttyACMx ports, i am using arduino due's and they work just fine in windows, Myrobotlab runs good on the TX2, only problem is getting it to se the ttyACMx :(

Great work to all off you innvolved in this :)

Btw, i am installing opencv 3.4.0 and YOLO3 (DarkNet) , will that be ok with the new / next version og Myrobotlab ?

So.. the OpenCV service in MyRobotLab (on the nixie release) is JavaCV version 1.4.0 (soon to be 1.4.1) which translates into including OpenCV 3.4.0 (soon to be OpenCV 3.4.1 )

It does have the ability to load machine learning models from various open source platforms. (Caffe, Tensorflow, Darknet, and Torch currently from what I can tell.)

There is no need to install opencv, it's included with MyRobotLab in the OpenCV service.

We currently have an opencv filter for YoloV2 (as this is what was easy to include at the time.) I guess there's not much difference in accuracy between YoloV2 and YoloV3, but I guess the performance is better with V3.