Ensenso XR operation, PointMap

Hi Team,
A customer evaluating Ensenso XR has two questions. Could you please advise?

Q1. According to the manual, is there no need to perform ComputePointMap in XR?

When Triggermode is set to continuous, the DisparityMap value continues to be updated even without ComputeDisparityMap, but PointMap remains null.

So, when I tried to execute ComputePointMap, an error occurred and I was unable to obtain the Pointmap value.

How can I obtain the Pointmap value in Continuous?

Q2. Temporary and Temporary-0001 nodes are created in Execute. What are these and how should I handle them?

Warm regards, Kenzo
Case Number 00207699

Hi Kenzo,

Can you quote a specific passage which implies that no ComputePointMap is required? When I search for PointMap I only find this sentence:

The reprojection of points in cmdComputePointMap is also done on the host PC to save transfer time.

which explains that ComputePointMap is executed on the host, not the device.

Are you talking about the device or the host? The disparity map is constantly updated on the device (visible in NxTreeEdit) and streamed to the host. The host does not automatically update the disparity map. Instead, the received disparity maps are buffered until you call ComputeDisparityMap, which will update the Images/DisparityMap node with the most recently received disparity map. Then you can call ComputePointMap.

So unless you are connecting directly to the device via NxLibRemote, the sequence of operations to obtain a point map are:

For trigger mode Software, the XR behaves like any ordinary stereo camera:

  • Capture (alternatively: Trigger, Retrieve)
  • ComputeDisparityMap
  • ComputePointMap

For trigger mode Continuous, you do not explicitly need to trigger the camera, so the sequence simplifies to:

  • ComputeDisparityMap
  • ComputePointMap

Please note that this last command sequence does not update any image nodes!

If you are connecting directly to the device via NxLibRemote: please do not do that (generally).

Again: are the nodes on the device or the host?

If on the device: you should generally not need to care about the device. You should only interact with the host-side NxLib and only examine the device-side NxLib in NxTreeEdit when sonething is seriously wrong. The command nodes on the device NxLib are created and maintained by the host NxLib.

If on the host: I do not know what application you are using or what commands these nodes are executing, so I cannot tell you how to handle them.

Let me know if that helped or if you have any more questions.

Regards,
Raphael

Hi Raphael,

Customer could solve their issue with your advice.
Thank you so much!

Warm regards, Kenzo