LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Critique my template.....please

I thought I'd ask the capable members to critique my template. The goal is to end up with a generic XY graph. I'm calling the VIT dynamically and passing properties including indicator references that contain the data. The graph simply pulls the data from the indicators. I use a timed loop so I can eventually add a "dt" input parameter. I split the X and Y as my current application for which I need graphs has several indicators from which the user could select an X and a Y. Using the template, the user can open N graphs with different combinations of X and Y.

I think the references could be passed without strict data types and the subsequent variant outputs then cast based upon another input parameter, but that would be for the future. For now, I'm happy just using doubles.

I used a case statement to avoid the feedback node from continually building upon previous data after the maximum X value is reached. The TRUE case is empty.

Currently, this implementation works fine but I'd like some objective eyes to take a look.

Thanks,
Bill


Message Edited by Bill@NGC on 09-01-2007 01:23 PM

0 Kudos
Message 1 of 3
(2,680 Views)
Have a look at the following document.

It describes some issues to be aware of when using VI templates dynamically.

Remarks:

1. How do you intend to react to a quit application action?
2. The graph has no limits (data size), is it handled somewhere else, it could end up taking a lot of memory.

André

Message Edited by andre.buurman@carya on 09-02-2007 08:23 AM

Message Edited by andre.buurman@carya on 09-02-2007 08:25 AM

Regards,
André (CLA, CLED)
0 Kudos
Message 2 of 3
(2,646 Views)
Thanks andre. To answer your questions:


1. How do you intend to react to a quit application action?
If the application quits, any open graphs also quit automatically.
2. The graph has no limits (data size), is it handled somewhere else, it could end up taking a lot of memory.
That's an interesting question. If the X values exceed the graph's range, the case statement will handle that. But there is the possibility that the X values will stop incrementing, so the graph would just keep buffering up redundant data. I'll have to work on that one.

Message Edited by Bill@NGC on 09-02-2007 09:34 AM

0 Kudos
Message 3 of 3
(2,634 Views)