Intel Realsense D435i

Fixed Intel's bug so the device can be started and stopped

There is a small performance improvement as well, which will be noticeable on SBCs

Also, this only displays depth sensors in the drop-down

Pretty big bug fix that correctly calculates the point-cloud distances into distance scans. You may have noticed that flag objects, such as walls were rounded. This is no longer the case.

Here you can see the wall, corner of the wall, and the edge of the monitor. 

And here's a low scan of just the table in front - where it's flat and no longer curved.

Updated with a huge performance improvement. I didn't realize the Intel sample code was copying the depth data into a managed array on every frame ouch. So I'm referencing the unmanaged memory pointer directly. Should have known better than to copy that bit of code from their sample :D

Should experience a 10 times improvement. I went from 27% cpu to 2% cpu

Like The Navigator, there are variables for the nearest and furthest object detected... just in case this is being used without an NMS skill like the navigator

Thank you so much for making this.  Just installed on the Rock Pi X.  Seems to work well although took me a bit of time to get it working. I have to run it off the USB 3.0 port as I get an error on USB 2.0 but the T265 seems to work on the USB 2.0 port ok

Couple of questions Did you manage to get to work off the USB 2.0 port or do we not have enough bandwidth ? If you can use off usb 2.0 could it work with 2 or more D435i ? If you mount the camera sideways could you set image range vertically instead of horizontally?

The device is usb c which requires usb 3. I’m sure there’s more information about that in the product manual

Ok it works with USB 2.0 with the realsense view app provided by intel.

I guess I could try and  use the USB C port for 1 and the USB 3.0 port for another.

I don’t know how that could be. It’s usb-c which is usb 3. If it’s true, then maybe their app is doing some wizardry that uses a different driver and somehow defies usb-c specifications lol

I googled for you:

they somehow magically use the usb2 channel over usbC and then internally have a different driver that operates at a low speed.

• performance improvement

Is the IMU function of this skill used, or would it work with the less expensive d435?

Although I am currently satisfied with the T265 and Lidar, I am realizing that on a larger robot the Lidar will miss items near the floor, so I might want something mounted lower facing forward instead or to augment the Lidar.

You don’t need to mount it lower, and I wouldn’t recommend doing so. You adjust the area of the image to be detected. Check through live hacks for examples of what’s documented in the manual

there is no imu data stream returned from the device with intel’s sdk. I have tried to get the imu data as well with no success

I believe it will work with the earlier models. I can’t speak on the performance differences between models.

Thanks.  I believe the d435 and d435i are identical except for the IMU as far as specs, but I will confirm.  Not even sure I am going to get one yet, but it intrigues me...

Alan

If you do mount it low, angle it up. I think I read somewhere once about the preferred angle.

I confirmed from the Intel site that the d435 and d435i are identical specs except for the IMU, so I ordered a d435 to play with.  Interestingly, one of the Amazon listings, and a Tiger Direct listing show a "30 pack" for just a few dollars more than a single unit.  I asked Tigerdirect online to confirm if they are really shipping 30 units and they didn't respond, so for $10 more, I took the chance.  If I get 30 of them, I'll sell them cheap or trade for other robot gear with members here..... (they did say shipping weight is 4.5 lbs and I know the device is only a few ounces so it is possible that they actually did bulk packaging and someone mis-priced it, but it happened at multiple sites (Walmart and a few other sites also had it listed the same way, but out of stock - one even said "bulk pack" which leads me to think I may actually get 30 of them......).

I got my d435 (it was not actually a 30 pack, but had clearly come from one.  Didn't have a box, manual, tripod, etc...  So, I spent more for less.  Should send it back but I am anxious to get using it.  Which leads to the problem.

Downloaded the driver and RealSense Viewer app from Intel.  Plugged it in, tested it, and it works perfectly in the viewer.

Added the plugin to the project, and the camera object can see the RGB camera, but the plugin gives the following error when I attempt to connect (whether or not the RGB camera is connected, also tried in a new project after restarting ARC and only added the plugin with the same results):

Starting Intel RealSense D435... Couldn't resolve requests

No errors showing up in debug, just in the plugin window.

@DJ, I hate to comment just to bounce, but any idea why this works in the viewer and not in ARC.  Should I return it and get the 435i even though the SDK should be identical or can you provide a debug version with enough logging to figure out what is wrong?  I expect to have time on Sunday for some testing if you want me to debug it.

I’m thinking it might be resolution related. I added a todo to have the plug-in robot skill accept a drop down of resolutions in the config menu

its the weekend so no one is working to debug anything for you. But I’m guessing sometime next week there will be an update to the skill for ya to try

Hey can you use the intel program viewer thingy. And tell me what resolutions it supports. There’s ones for the rgb camera and tracking.

Will do tonight.  I think I had it set to 640x480 bit it supports higher and lower. I'll get list tonight or in the morning.

If you want me to test a debug version with extra logging, happy to do so as usual.

Alan

Ya 640x480 is 4:3 which is a square. The 435i uses widescreen 16:9 or something close. So it’s probably an unsupported resolution.

I didn't get a chance to test this weekend, but will after work today.  Thanks.  the resolution thing makes sense.  I was planning on using the RGB camera as the only camera on the bot, so set it to a fairly low res so I wouldn't have an issue with object recognition, but I can stick an EZ-B camera on for that if 16:9 uses too much CPU for object recognition and tracking.

Alan

Updated to allow specifying resolution. Read the manual above for instructions

I got it to work only at the very highest resolution which only supports 6 frames per second, but it was taking 20 seconds or more to detect a distance change in the skill (again, it worked fine in the Intel viewer), so the robot was running into walls.  Most of the resolutions gave the same error as before, without your added text about checking the USB port and supported resolutions.  640x480 gave an error pointing to a particular line of code, but I ran out of troubleshooting time, so I didn't catch it for you.  Will try again tonight.

I'll gather more detailed info for you tonight.  If you want me to try a debug build with extra logging, I am always happy to do that.

when you "test" in the realsense app, are the RGB camera and Sensors both at the same resolution?

I have set them the same and different resolutions, and it works regardless.

Alan

Your tests in the realsense app would need to be the same resolution for both the sensor and rgb. Otherwise, there image and distance detected would be out of sync for mapping in ARC.

What is the resolution and format for both rgb and sensor in realsense app that provide the best cpu usage?

Also, try setting the width & height in the latest version to 0. That will use the auto-size, or the last size used (i.e. from intel realsense viewer)

Will try after work tonight and let you know.

I am sure we'll get this figured out.

Should I run the calibration app that came with the driver download too?   I didn't both since you didn't mention it in the documentation.  Also, there are several profiles in the viewer app for what you are expecting to see (ie, hand signals, far distances close, etc...).  Is there a preferred one and does the device remember it after it is used in the app to when the skill accesses it?

Alan

I don't know anything about a calibration app. That's most likely a question for the intel company that makes the product. You're somewhat exceeding my knowledge of the device haha :)

I have tried everything I could think of, I removed the Intel drivers I had installed and just tried whatever Windows installed.  Still worked in the viewer, but the same issues in ARC.  I tried multiple resolutions.  The only 2 that the RGB and the Stereo have in common are 640x 480 which gives this errors (same as 0x0 no matter what the resolution in the viewer was:

or 1280 x 720 which works but only when set to 6 frames per second and actually only updates the distance about every 20 seconds so the robot drives into walls.

All other resolutions give some variation of:

Here are screen shots of the supported resolutions:

and

I also tried removing the Intel driver and letting Windows find its own driver in case it was a driver issue, with the same results.   If this is not what you see in the viewer, I will return the device and get a 435i.  Otherwise, I am going to go back to Lidar for a while so I can work on navigation scripts that work until we have a 435 skill that actually works.  (that sounded more pissy than I meant.  My mom is in the hospital with Pneumonia,  Thank G-D it is not Covid, but I am stressed).

As always, if you want to provide a debug version with high or highest logging level set to figure out what is causing the issue, I am glad to install and test, although depending on my Mom's condition and if they send her home, I may be offline for a week or so...  They won't let me visit the hospital despite the fact I am fully vaccinated, so at least for the next few days I should be available to test.

I have a question, about the Intel Device. Can it work for outdoors as well? would beinteresting to have an indoor/outdoor sensoe on the robot.

That’s super weird - wonder what they’re doing differently. I’m using their examples in the sdk.

did you set width and height to 0? And same error?

I know you keep asking about a debug version - but you have it already :). the error message that you see is the most verbose there is.

This is why I dislike working with any intel products... discontinued products with discontinued support and incomplete sdk.

One more thing ....

I noticed your screenshots do not have the rgb sensor or depth sensor active. Can your future screenshots include real-world test scenario. Sometimes things can be missed if liberties are taken.

I’d like to know the these things when you get an ideal resolution working with the realsense viewer. Make sure the rgb and depth resolutions & framerate are identical and both sensors are active. Once that’s done, tell me these things...

• the common resolution
• the common frame rate
• the depth format (ie z16)
• the rgb format (ie rgb24)

I'll test again tonight.  Yes, I tried 0x0.  It gave the same error as the 640x480 test (first screen shot in my last message)

There are only 2 common resolutions available. 640x480 and 1280x720.  1280x720 is the only one that kind of works in ARC, but not in a usable way.

Understood. Let me know the frame rate and formats for 640x480

In the latest version, you may be able to use 1280x720 and specify higher skip depth points. try 10 or even 20 and see what your performance is like (or use the recommended performance values). This isn't a long-term solution, but necessary for even slow PCs with low depth resolutions.

*Note: Read about this setting in the manual at the top of this page.

Thanks for the update DJ.  Have a family emergency going on.  I couldn't test last night.  Might be able to this weekend, but then I will probably be unable to do anything for a week or so.

Alan

Sorry to hear that Alan - take care of your fam :)

Thanks DJ.  Family first always. I'll share more (in a different thread) after I know more about what is really going on.   Hearing what my Mom thinks she hears vs what the doctors actually say is not always the same thing, but the situation is not good, just may not be as dire as I first thought.

Updated to latest intel library that apparently includes bug fixes - as they say :)

DAMM, really may just need to find one, I was always curious about this one.

v18 - hides error that Intel driver sometimes raises when stopping sensor

v19 updated

• default resolution values are 640x480x6fps to match the latest firmware settings

• fix for the offset value that wasn't being calculated correctly

Thanks, regarding the question if could be possible for the RS 435 to stop feeding the NMS, and use it for other purposes (like an arm cam), what do you think?

I can quickly change this robot skill so the depth data is not pushed to NMS.  How would you access the data from the sensor? There are 307,200 data points at 640x480 resolution. That would be a vast array. Do you have any ideas about how you would like to access the data?

For now I was taking about that  basic option to disable the NMS feed to use it as also as a CAM only.

One idea to take advantage of  the depth information (outside the NMS) is to use it for example in the arm to have  better precision  to manipulate and recognize objects. Datapoints volume could be manipulated in a similar way as is in the current skill with the image gap selection.  Thanks

I understand to make it not send to NMS. However, I am struggling to figure out a way to present 307,200 data points to the user. Can you give me an example of how it can be used? Would you want to know furthest distance and closest distance of each frame? Or how can I make the data available to you?

I am intrigued by this product as they sell an outdoor waterproof style as well. I am planning on buying one but want to verify that it works ok within ARC. @TechGuru did you get it working ok? Can it be used as a standalone product without having to go through NMS. I'd like to manipulate the variables in different ways.