B Chavez

I like this idea, is there a way have a VI open automatically when the project specific INI file is opened?

Thanks for the help, very useful info. I guess I knew that the safe approach would be to close all references, and I'll start doing that. I was mostly concerned about Control References (right click a control -> Create -> Reference). It seems that they do not change whenever they are read and therefore do not 'need' to be closed, so I don't need to go back and fix old code. Thanks again

I have a few questions about using Control references, any input will be appreciated. 1. Should control references be 'closed' when no longer needed? I've played around with them and it doesn't seem to do anything if you do close them. 2. If I do need to close them, do I need to close every instance where I have place one on my block diagram? 3. Is any of this considered bad practice? My first two questions may be insignificant if I shouldn't be using Control references anyways. Thanks in advance.

They are visible when you have the mechanical action set to "Switch When Released" or "Latch When Released." When you click the boolean and hold, the "False to True" or "True to False" colors will be shown.

I've never used it, but there is a "Save Instrument" Method. The context help simply says "Saves a VI." I may be missing something, but this seems like what you're looking for.

Is this what you're trying to do? Download File:post-1591-1128223691.vi Maybe if you explain why you are trying this, we could be more helpful.

Try this and see what you think. I use the "Top Left Visisble Cell" property to determine which items in the listbox are visible. The boolean array is fixed in size equal to the number of rows visible in the listbox. The array now "adapts" to only the visible items in the listbox. Download File:post-1591-1128008052.vi

If you wire an empty array to the "Item Names" property, it will clear it. Download File:post-1591-1127935335.vi

Hope this helps. Download File:post-1591-1127863509.llb

I've done what you're explaining (I think..) Give me a chance to dig it up.

I've come across a problem with a case structure as well. I have a case structure with a string wired to the selector input. There are three cases: "", "Idle" "copy this state" Default When I try to right click the case structure and check "Case Insensitive Match," LabVIEW generates an error and shuts down. Deleting or modifying the cases seems to fix the problem, but this shouldn't happen. I've attached the VI if anyone is interested in trying it. I'd be interested if it doesn't do the same thing on someone elses machine. Download File:post-1591-1125504444.vi

Yeah, I have done this. It works great I like it. It just doesn't fit into what I'm trying to do here, that's all. I was just hoping I could create something (like a DLL) that can be called in another language (like C or VB) that does not require LabVIEW. I think my solution is to create a DLL in C that writes a binary data file (not a datalog file). This way, I can read and write the files easily in most languages. Thanks for all the input.

I do have access to the Application Builder, and I have created executables. However, whenever I have done this, it required the Run-Time engine to be installed. I'll just have to read up on the App Builder and figure out what I need to do. Thanks for the help <Edit> Looks like DLL's created by the App Builder require the run-time engine as well. I guess I don't really see the point then, but now I'm in the wrong forum.

Thanks for the input, that's a good idea. I personally have never created a .dll from LabVIEW so there will be some learning there. I would still like to see an NI document that describes how those files are layed out, for curiosity. Thanks again

Has anyone created datalog files in another program (such as C) that is readable in labview? I really like the way datalog files are handled with the records and I would like to create these files elsewhere. I've opened some datalog files in a hex editor and I can see some header information and type descriptors, but I can't really determine the structure of the file. Also, I have noticed that LabVIEW 7.1.1 creates a different file structure than LabVIEW 7.0, but they seem to be compatible with eachother. Any help will be appreciated. Thanks

Try this, I think it does what your looking for. Download File:post-1591-1116428533.vi

I think we need a little more information. How are you communicating with the FTDI chip? Are you using FTDI's .dll or are you using NI-VISA? Also, what is the FPGA configured to do?

I have recently encountered a similar problem with events on a top level that also contains a subpanel. I am losing the ability to click in a subpaneled VI after an event has occurred in the top level. I have tried my code in LabView 7.1 and the problem still exists; is this possibly fixed in LabView 7.1.1? If not, has anyone found a work around? For me, Subpanels really lose their usefullness if suddenly you can no longer interact with the SubVI running in it. I appreciate any feedback.