LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Sensor Mapping Express VI's performance degrades over time

Solved!
Go to solution

I was attempting to do a 3d visualization of some sensor data. I made a model and managed to use it with the 3d Picture Tool Sensor Mapping Express VI. Initially, it appeared to work flawlessly and I began to augment the scene with further objects to enhance the user experience. Unfortunately, I believe I am doing something wrong at this stage. When I add the sensor map object to the other objects, something like a memory leak occurs. I begin to encounter performance degradation almost immediately.

 

I am not sure how I should add to best add in the Sensor Map Object reference to the scene as an object. Normally, I establish these child relationships first, before doing anything to the objects, beyond creating, moving, and anchoring them. Since the Sensor Map output reference is only available AFTER the express vi run. My compromise solution, presently, is to have a case statement of controlled by the"First Call" constant. So far, performace seems to be much better.

 

Does anyone have a better solution? Am I even handling these objects the way the community does it?

 

EDIT: Included the vi and the stl files.

Message Edited by Sean-user on 10-28-2009 04:12 PM
Message Edited by Sean-user on 10-28-2009 04:12 PM
Message Edited by Sean-user on 10-28-2009 04:16 PM
Download All
0 Kudos
Message 1 of 3
(3,548 Views)

I can't run your example code becasue it is missing "make wireframe.vi" I removed that component and this example work just fine for me, I think the first call architetuer in that case is agood choice.

 

 

Message 2 of 3
(3,514 Views)
Solution
Accepted by Sean-user

I agree with Hunter, your current solution is simple and effective, and I can't really visualize a much better way to accomplish the same task.

 

Just as a side-note, the easiest and simplest way to force execution order is to use the error terminals on the functions and VIs in your block diagram. Here'a VI snippet with an example of that based on the VI you posted. (If you paste the image into your block diagram, you can make edits to the code)

 

 

test for forum_modified.png

 

 

Since you expressed some interest in documentation related to 3D picture controls, I did some searching and found a few articles you might be interested in. There's nothing terribly complex, but these should be a good starting point. The first link is a URL to the search thread, so you can get an idea of where/what I'm searching.You'll get more hits if you search from ni.com rather than ni.com/support.

 

http://search.ni.com/nisearch/app/main/p/q/3d%20picture/

 

 

 

Creating a 3D Scene with the 3D Picture Control

 

Configuring a 3D Scene Window

 

Using the 3D Picture Control 'Create Height Field VI' to convert a 2D image into a 3D textured heigh...

 

Using Lighting and Fog Effects in 3d Picture Control

 

3D Picture Control - Create a Moving Texture Using a Series of Images

 

Changing Set Rotation and Background of 3D Picture Control

 

 

Caleb Harris

National Instruments | http://www.ni.com/support
Message 3 of 3
(3,505 Views)