Obstacle avoidance range sensor information wanted...

[Vaklin]

Hi!

I'd like to prepare an ultrasonic altimeter for my H. Something like this one in the RealSense but as a standalone device. I have some spare range sensors, which are good candidates to complete the task. Any information will be welcome, as a pinout, communication protocol, etc.

 

[Thomas111]

Interesting idea

 

[Vaklin]

To bump the topic. Looking for a type of data, which is provided by RealSense. Need to arrange a real "Follow terrain" feature, based on the real-time measured altitude from the copter to the upper level of the obstacles.

 

[DoomMeister]

You may still be able to find information about the RealSense module from the Intel website in their archives. I know it builds a 3D mesh from the LiDAR scan and holds it in its memory.

 

[Vaklin]

Exactly, this is less interesting in my research. I'm accepting that RS works and do the job well. It transmits some data to the FC. The structure of this data is in my scope of interest. In this partial case, I'm looking for sonic radar altitude, measured by the RS.

 

[Vaklin]

Just a question goes through my mind. Will the RS do the tasks without a camera attached? We're talking about H480 with CGO3+. The rest members of the family are not user-friendly enough to do some mods.

 

[DoomMeister]

I think the sonic portion of the RS is only good to about 5 meters.

You raise some interesting questions! The sonic portion is added by Yuneec and is not something that would be covered by information from Intel. I suspect that would be much like the forward facing sensors.

It would be really nice if Yuneec would release some of this type of information used in the H480/H+.

 

[h-elsner]

The RS is connected to the flight controller via UART pin 5 and 6. Thus, I think the camera has nothing to do with it.


br HE

 

[Vaklin]

The camera is the decision-making unit for automated modes. RS should do the same. Simple OBS is FC processed but for sophisticated turnaround maneuvers...

3-5 meters over the terrain is exactly what I'm looking for.

 

[cabinfourus]

Your project has my curiosity on a high. I have thought about doing something like this for a separate drone I am building.

I also do 3D printing, laser cutting, and 3D modeling so I use real sense cameras often. The camera inside the Typhoon H is the R200 if I am correct. Intel doesn't have much support for this camera anymore but I think the SDK is still available. The D4 vision processor is used with the D400 camera to convert to USB. I am not sure but the D4 looks to be the same board inside the Typhoon H module.

Here is the spec sheet and tons of information on the R200.
Sorry for the extra file. I clicked on the wrong one with my first upload.

 

[cabinfourus]

If you don't mind, keep me posted on your project. I'd like to know how well this works out.

 

[Vaklin]

Let me explain a bit more. RS is connected to the FC via MavLink. I don't want to reverse or improve the module itself, just to use data from it. These data fields are the topic of the question.

 

[cabinfourus]

Let me explain a bit more. RS is connected to the FC via MavLink. I don't want to reverse or improve the module itself, just to use data from it. These data fields are the topic of the question.

Okay. I gotcha. You are trying to figure out the RS communications. I have no experience in this area. I wish I did though.