Skip to main content

Image Processing with Intel Realsense for Digital Interactive Installations (2/3)

In this second part, I will share how the data between several Realsense devices are merged. First, an overview on how the devices are connected together.


The data flow is as follows

  1. PC 1 and PC 2 gathers detection data from the devices attached to them.
  2. PC 2 has another process that merges the data and sends them to PC 3.
  3. All PCs have knowledge of the device layout and transformation Matrix to transform coordinates into Unity coordinates.* A little more on this later.
  4. PC 2 transfers the transformed coordinates to PC 3 through TCP/IP connection.
As mentioned above, the devices need to know its position in the layout and transforms it detection results into the larger area axes as shown in the figure below.


Each dotted rectangle denotes the view of one Realsense depth camera. Each camera is assigned an identifier (a, b) that reflects its position in the layout.
Both PC 1 and PC 2 holds a settings file that tells them which devices are attached to each PC, mapped to the Realsense device ID, which is unique. With this information, the detected positions from PC 1 and PC 2 are transformed to the top left axes of the total area.

The layout of devices is stored as JSON file on all PCs. The JSON structure is as follows.

{
"devices": [
{
"serial_number": "747612060144",
"pos_x": 0,
"pos_y": 2,
"max_limit_x": 640,
"max_limit_y": 720,
"min_limit_x": 300,
"min_limit_y": 300,
"overlap_x": 0,
"overlap_y": 0
},
{
"serial_number": "811112060489",
"pos_x": 1,
"pos_y": 0,
"max_limit_x": 1280,
"max_limit_y": 720,
"min_limit_x": 0,
"min_limit_y": 0,
"overlap_x": 0,
"overlap_y": 0
}
]
}

The members are

  • serial_number. This is the device's unique serial number as returned by dev.get_info(RS2_CAMERA_INFO_SERIAL_NUMBER) 
  • pos_x and pos_y are the layout identifiers as shown on the device layout figure above.
  • max_limit and min_limit denotes the active areas to perform detection.
  • overlap is currently not used but I plan to consider the case where the devices are not perfectly adjacent.
This concludes the data sharing part. In the next entry, I will share how we use Google's Protocol Buffer to package the detection data when sharing and transmitting from and to the three PCs.

Comments

Post a Comment

Popular posts from this blog

Installing a custom ROM on Android (on the GT-N8013)

It's been a while since my last entry and since it is a new start in 2019, I thought I'd write something about "gone with the old and in with the new". I've had my Samsung Galaxy Note 10.1 (pnotewifi) since 2014, and it's one of the early Galaxy Note tablet series. It has served me well all this years but now it just sits there collecting dust. My old Samsung GT-N8013 I've known a long time about custom Android ROMs like CyanogenMod but has never had the motivation to try them out, until now ! Overview of the process For beginners like me, I didn't have an understanding of the installation process and so it looked complicated and it was one of the reasons I was put off in trying the custom ROM. I just want to say, it's not complicated at all!   Basically you will need to Prepare an SD card and install Android SDK (you need adb ). Install a custom boot loader ( TWRP is the de facto tool at the moment). Use adb to copy custom...
15 comments
Read more

Building a native plugin for Intel Realsense D415 for Unity

Based on a previous post , I decided to write a plugin for the Intel Realsense SDK methods so we can use these methods from within Unity. FYI Intel also has their own Unity wrapper in their Github repository , but for our projects, I needed to perform image processing with OpenCV and passing the results to Unity instead of just the raw image/depth data. There is a plugin called OpenCVForUnity to use OpenCV functions from Unity but previous experiments indicate the image processing inside Unity can take a long time. I hope this post can help someone else who wants to use Intel's cameras or any other devices natively in Unity. Test Environment Windows 10 64bit Unity 2017.2.0f3 x64 bit Realsense SDK from Intel CMake 3.0 or higher Steps Checkout the native plugin code here . Don't worry about the other projects in the same repository. The relevant code is in the link above. Checkout the Unity sample project here . However, instead of master you need to go to the br...
5 comments
Read more

OpenCV native plugin for Unity in IOS

In one of my recent projects, I needed to use OpenCV from within Unity, in IOS. The asset called OpenCVForUnity is overkill because I didn't need the whole OpenCV library, just a few functions. In addition, this asset does not implement the whole OpenCV library so unless you know that what you need is included you may find it lacking when you discover it does not support some functions you need. As my project involves some trial and error and mixing algorithms together I decided to go with a native plugin. Overview In IOS, a native library is built as a bundle . We need to put this bundle inside Unity's Plugins/OSX folder to use it. Therefore, we need to create two projects. An XCode project to build the native plugin. A Unity project to use the plugin. Dependencies Of course, since we need to use OpenCV we will have to install it first. Tutorials on installing OpenCV on IOS are abundant and I will not include them here. Assuming you have installed OpenCV go to t...
2 comments
Read more