LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Get your questions answered by LabVIEW developers.

Another question: Assuming this was a success, can we expect more to come?

To quote myself from earlier in the thread (speaking with Brian Tyler):

I assure you that the more involved people would love it if we had a place where we could regularly deposit such questions whenever they come up, and know that the developers are listening and could eventually answer. Using the email address from any of your blogs would probably work for that, but I was thinking of a more public\organized place. Another board on this site?
Brian said you were probably the person to ask.

___________________
Try to take over the world!
Message 61 of 129
(3,433 Views)
Hi  Forum,

We're building a sequencer into an existing Labview 5.0 Vi to automate our testing and processing. Our main Vi calls various non-LV programs from disk and runs tests and processes results from various samples for X amount of time. We have been doing this manually.
 
Automating will be accomplished based on following table events. In this table, we can have an unlimited amount of instructions to follow. We'd use this table to control everything in the main Vi. We are basically tied to using the LV5 version of this Vi.
 
Description:
Let's say that we want to insert an  "event " (one row can consist of up to 120 scalar values in 6 discrete arrays) somewhere into the middle of the table.  It would not be efficient to have to completely redo the whole table each time we want to add or delete an event in the middle of the table (i.e. split table into 2 subsets, then insert a new row or delete an old one).   We need to be able to update,  insert, replace  or  delete an entry anywhere in the table also.

LV 6/ 7 has array blocks for editing an entire row: replace, delete or insert, which is perfect for what we want to do. For our situation editing in rows works.
 
An "arrayeditor.vi " for our sequencer was designed and tested with LV6 /7 and does the required complete row replace, delete, and insert as needed. This Vi was put together using "Replace Array Subset",  "Insert into Array", and "Delete from Array" functions. 
 
The primary functional app we have, without the sequencer feature is based on LV5.0. Up till now we've had to perform the steps that we are doing in the "table" manually. We can't try to use different versions of LV to try to patch things together.  
 
Saving the test LV6 .0 "arrayeditor.vi" to LV5 format doesn't work, because these particular array  editing functions of LV6/7 don't exist in LV5.
 
We do not want to upgrade the app to LV6 or LV7, because  the main app works perfectly and FAST in LV5. The overall app/project size in LV5 is small too when you consider the size of the runtime engines in anything the later LV's offer.  When we've tested LV6/LV7 versions, we've found such to be way too large for our needs. We have limited memory restrictions in the computer board running the main app.
 
We've checked out two previous forum postings that talked about array building or editing, and looked at the very old LV5.0 tutorial example of replacing a line/row of data, and seen that one utilizes a strategy of splitting an array into 2 subsets or uses a table and functions from later LV versions that don't exist in LV5.0.  These posted examples really don't completely emulate/duplicate the LV6/7 equivalents mentioned above:
http://forums.ni.com/ni/board/message?board.id=170&message.id=39731&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=22518&requireLogin=False
What we need are one to one LV5.0 equivalents of the LV6/7 functions of these three array editor blocks:  "Replace Array Subset", "Insert into Array", and "Delete from Array" for entire rows. 

These 3 functional blocks are the exact ones that we've verified will solve our problem.  If we knew exactly what was "inside", specifically the procedures followed within these blocks we could emulate/build such using components from LV5.0 functions.

Does anyone have the the actual block diagrams of what is in the function for the three  blocks "Replace Array Subset", "Insert into Array", and "Delete from Array" for entire rows in LV6/7?
 
If  we could get that, we would be happy to do up LV5 equivalents and post for folks to use.
 
Lastly, does anyone know how to remove all the extras from the LV6/7 runtime modules that are never used - to strip these down to bare minimums for JUST what is needed for a particular app?

THANKS.Charlott
0 Kudos
Message 62 of 129
(3,567 Views)
Please read the subject of this thread in the very first post. Your question is completely off topic.
Message 63 of 129
(3,566 Views)
Is there any future (or current) technology for scripting or macro expansion for labview.  Other languages allow a future which then allows for the development of programs to write programs.  I am also interested in the development of a labview modeling language, I know that labview is almost a modeling language itself but a higher level of architecture would be nice for the planning stages much like UML provides for OO languages.  A data flow modeling language would be very useful for the development of large-scale applications using labview.  No complaints here, LV is great, I would like to know more about features in 8.0 when they become public.
 
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
Message 64 of 129
(3,464 Views)
Paul, I assumed you know this, but just in case - LV scripting allows dynamic code generation, which can probably be used for what you asked. You can find more details in the scripting board of the LAVA forums. I think you have to be a member to read it. It is not currently supported by NI but will be in future versions (8.0?).
 
Regarding your other question - I asked early in the thread about taking LV in a more project oriented direction and letting us design the program in LV, so hopefully they will respond to that.

___________________
Try to take over the world!
Message 65 of 129
(3,464 Views)
Thanks tst, I will see what LAVA has.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
Message 66 of 129
(3,501 Views)

tst guessed "but will be in future versions (8.0?)".

 

From what I know, we may have to wait until LV 80.0.

 

Warning! LV Scr_____ is use at your own risk. If it destoys your aplication and you have to start over....

 

I believe supporting the "S" feature is a major hurdle. Imagine the newbies post of the future. It could read "I wrote code that writes code that wrote some code, and now it does not work anymore... What could be wrong?"

 

If you are really interested in making the "S" feature a reality, come up with a killer application that requires it and share the idea with NI. I have been told that this would help push the "S" thing. I have yet yo come up with a killer.

 

Ben

Message Edited by Ben on 07-27-2005 02:07 PM

Message Edited by Ben on 07-27-2005 02:08 PM

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 67 of 129
(3,493 Views)

@Ben wrote:

tst guessed "but will be in future versions (8.0?)".



Not guessed. This is based on something someone from NI said.
In an explanation of why a scripting related thread was removed from the forum, JR himself said that scripting will be licensed in future versions (he used the word "soon"). This response can be found in the LAVA forum. The 8.0 part was more wishful thinking.

___________________
Try to take over the world!
0 Kudos
Message 68 of 129
(3,485 Views)
er.  I did read the subject of the thread.    I posted my question here because it directly relates to labview architecture and challenges faced in the design and development of applications.   It relates to documentation that inadequately describes what is IN the various functions and how they work within that architecture.  It relates to the difficult design challenges presented by excessive code in current runtime engine(s), the apparent inability to edit such, and the subsequent need to leave applications running in abandoned versions to perserve their operational viability.
0 Kudos
Message 69 of 129
(3,525 Views)
Imho, when you are using a version of LabVIEW that is several years old, I don't think it much applies to the current or future direction that LabVIEW will take.
Message 70 of 129
(3,516 Views)