We find many repositories in https://osrf.github.io/ovc/software.html can not be open, such as Real-time Semantic Segmentation, Stereo Image Splitter, GPU Accelerated Dense Stereo Disparity Estimation. More about the visual algorithms used in your experiment The Open Vision Computer: An Integrated Sensing and Compute System for Mobile Robots are also not found in http://open.vision.computer.
Thus, we wonder if we could get your visual algorithm to duplicate your experiment (vision-based autonomous navigation of uav) after our hardware is finished?
Looking forward to your reply.

When looking over the imu time stamps recorded for a data set, it looks like the time stamps are not all equally spaced. The IMU ran at 200Hz, so one would expect 0.005s between consecutive imu messages. But that's not what we are seeing.

For the Falcam, the recording was done on an Intel i5 laptop. It was reasonably busy, but not excessively, and I don't recall warnings about message drops from the rosbag record. Drivers and rosbag record were all running on the same host.

These are the timestamp-to-timestamp differences observed for the Falcam, aka ovc 0

Same, but now for the OVC1. Here, the driver was running on the TX2 which was connected via ethernet cable to the recording laptop.

Do you have any explanation as to why we are seeing time stamps like this? Could it be CPU load on the host that is running the driver? The OVC1 data is harder to explain, with what appears to be 400Hz spacing between some data.

Hello,

I am currently working on your OVC3, more specifically "OPEN VISION COMPUTER REV 3A (MARCH 2019)"
I have a board with me.

My plan is to develop an FPGA system to perform my own application, but it looks like OVC3 does not have JTAG connectivity.
When I tried to connect USB-C port to the PC, Vivado's hardware manager did not detect any device.
What are the available options to configure FPGA if I want to load my logic design to OVC3?

I read Trenz's specsheet and manual and found this.

According to this, only boot from SD/flash(eMMC) is possible. (Assuming you are using default firmware in CPLD.)
If that's true, what are the available debug options to probe signals in the FPGA?

I am not asking for specific tutorial for any of these question.
(Though if you can briefly explain me how to do that it would be appreciated.)

Also I want to know how this switch is mapped to the boot mode selection functionality.

Clearly, JTAGEN is for selecting a USB connection to either FPGA/CLPD.
MODE is for SD/eMMC selection.
NOSEQ looks like doing the same functionality that is specified in the above screenshot.
(Selecting JTAG mode when the firmware in the last column is installed I guess?)
But then, what is the USER pin used for?

So my question is...

1. Information on available FPGA configuration options.
2. Information on available debug options.
3. Information on mode switch.

Thank you!

Best regards,
Han-sok

Hi Guys,
I am working on the integration of ROS [ moveit, rviz, etc] with Nvidia IsaaC SDK/ Jetson devices. I was advised to study your project as it uses nvidia hardware.
Could you let me know if your project supports nvidia jetson Xavier AGX/ nvidia jetson NX, nvidia jetson Nano hardware, please?
If it supports - is there a guide how to implement ovc with it? ovc3? ovc4?
Regards & Thanks

Dear sir it seems like the ovc v4 is using Sony imx219 sensor so it is a rolling shutter camera won't it affect running visual odometry algorithms or visual inertial how do you solve the issue of rolling shutter or is my knowledge about this tech and camera very vague.
I hope you will reply
Thank you

Hi,
We want to reproduce the ovc3b but I have some problem on the hardware of ovc3b as following. I need your help.

1. I can not open the kiCAD project of ovc3b. It report that the project file is created by a newer version kiCAD. However, my kiCAD is the newest version.
2. The project lack of libraries. Can you provide all files, including PCB files, schematic diagram and libraries?

Thanks for your responding.

Hi,
We are trying to reproduce the ovc3b these days. The project ovc3b provide us the lens holder PT-LH010M and the CMOS image sensor AR0144CS. However, we still don't know the version of the camera lens. Can you share the information about the camera lens with us?

Waiting for your reply!

Do simple mechanical drawings (dimensions, camera centers, hole placement) exist for either the ovc3a board or perhaps a reference design housing which would have the same information?

I can manually click around and extract this information from the KiCAD project -- is there a better way?

If such a document were created, where should it live in the repository?

We are facing an issue with the RGB sensor. In indoor environments, the colors in the images are ok, as shown by the following picture.

However, when we take the sensor outside, pictures look like these:

Yellow and green boxes are indistinguishable. This issue seems to be more than just white balancing the image.

Another example during data collection:

In the documentation, there are specific channel gains for each Bayer color channel. I tried modifying this, but I was not able to solve the problem.

Any hints are appreciated! Thanks!

Brought about by this suggestion: #61 (comment)

I'm debating working on using JSON in #61 or another PR. Here's some sample code that I think I'll be basing the implementation off of:

#include <jsoncpp/json/json.h>
#include <iostream>
#include <sstream>

int main() {
  Json::Value root;

  root["name"] = "my_name";
  Json::StreamWriterBuilder builder;
  builder["indentation"] = "";
  std::string output = Json::writeString(builder, root);

  std::cout << output << std::endl;
  std::stringstream ss(output);

  Json::CharReaderBuilder rbuilder;
  Json::Value root_read;
  std::string errs;
  Json::parseFromStream(rbuilder, ss, &root_read, &errs);

  std::cout << errs << std::endl;
  std::cout << root_read["name"] << std::endl;
}

Output:

$ ./a.out
{"name":"my_name"}

"my_name"

Still not sure if I should change the serialization (struct vs an actual library). I could just replace the whole host -> client message with a length field followed by the JSON string. Something about it doesn't feel right but it would work... 🤷

@luca-della-vedova thougths?

First of all, I would like to thank the whole team for the great work done on this project.
I intend to reproduce the OVC4, I would like to get some feedback on the project.

• Do you consider this version mature enough to be used in the specified conditions (six picam synchronized with an IMU)?
• Have you noticed any particular issues during development or things you would like to see addressed in future releases (I am very curious to understand what drives your design preferences in each version)?
• It seems you are using the Argus sdk from Nvidia to fetch the image frames, did you observe any latency? (I had this kind of trouble with a Jetson TX2 & Argus in the past)
• How difficult would it be to modify the project to integrate a camera such as the OV9281 1MP from Arducam?

Hello,

I recently cloned the OVC3b module with great success. However, when I connect the module to my laptop with USB-C, the image rate is lower than what I get on the OVC (15-20Hz instead of 33Hz). Have you ever experienced such a result? I would like to avoid compressing the image to avoid additional latency.

I really appreciate the effort put into this project.
Thank you !

Hi,
The model you used in the ovc3b camera board TE0820-03-3BE21FA is no longer available. I want to know if it can be replaced with 4DE21FA without changing the circuit (because our PCB board has been made, only this chip is missing.)

Cheers,
Jingjing

Hello,

We are getting the following error from the OVC1 when we are trying to launch the driver:

We have not seen this error before. Do you have any idea on what would be causing it?

Best,
Steven

Hi
What would be the recommended method to attach an IMU to this board? Before this version, your designs usually includes some IMU integration. But in OVC5 it's unclear.
Another question:
Is the OVC5 in early stages or near to finish?
Thanks.

Documenting the issue so I don't forget to look into it.

OVC3 is currently configured to use jumbo frames in its ethernet interface:

ubuntu@arm:~$ cat /etc/dhcp/dhcpd.conf | grep -n 13500
45:  option interface-mtu 13500;

This can cause some instabilities: the interface stops sending data in an unpredictable way. Commenting this line solves the issue.

Hi there,

Are there any plans for osrf to have a manufacturing partner to build/sell/distribute this project? Alternatively, is anyone here looking into manufacturing these?

Cheers,

• mounting holes for the XU5 are 180 degrees off
• DIP switch footprint is slightly too narrow, and the DIP switch interferes with the XU5 module if it's mounted currently (just needs to move ~2mm further away, and it will be fine)

Hello! I'm sorry to leave this as an issue, but it seems like it might be the best place for others to find information if they are searching later, rather than resorting to email.

Are there any ROS bags available for download with captured data from the OVC2? I'm extremely interested in exploring this platform. I've looked through the OSRF website and other standard places, but I can't seem to find more info.