bbean

LV 8.0 I knew I was missing something. This should work for me. Thank you. Still can't figure out how you did this. These are the options I have for VI Properties: Regards, Brian

Am I missing something simple or is there no easy way to open a subpanel VI block diagram window while it is loaded in a subpanel ? :headbang: I would like one of two things: 1) Open only the block diagram window of the subpanel VI before I run the toplevel VI. 2) Put a button on the top level VI's user interface that allows me to open the block diagram of the subpanel VI I have in the subpanel so I can debug the VI's code while it is loaded in the subpanel. Right now it seems like I have to have the subpanel VI open before I run the top level VI if I want to debug the code. Even then, the subpanel VI window does not load in the subpanel of the top level VI. I looked at the VI properties and methods but didn't see anything for Block Diagram except "get image" Has anyone run into this before? P.S. Using LabVIEW 8

Thanks for taking a look at this. I found out the problem. I was missing a portion of the "Header message" when I sent the commands to the controller. The documentation doesn't really explain this header until you get into the examples. I missed it in my rush to get things done. Sorry for the false alarm about events and flow control. Brian

First, has anyone developed a driver to communicate via the serial port with a Digi-sense 68900-11 temperature controller? I've checked ni instrument driver network, google, and the company's website with no luck. I think its manufactured by a company called Eutech. Since I couldn't find a driver, I wrote a quick Labview interface with some simple commands to communicate with the instrument but couldn't get anywhere setting up the serial communication according to the serial communciation specification (see attached). I kept getting timeout's and was not able to read or write any data to the controller. The basic settings are 9600,8,n,1, XON/XOFF (w/ XON=11 hex and XOFF = 13 hex) So then I setup Portmon to watch the OEM's software application (which works fine). The OEM applicaiton seems to have a different setting for the "Shake:80" serial setting in Portmon. I've tried a bunch of different handshake settings using the VISA Serial Setup vi to try and match the OEM software to no avail. Also the OEM software seems to enable a bunch of Serial Events. Some of these I can enable and some I can't, but when I enable the events the computer justs grinds to a halt. Do I have to enable and handle the Serial Events or can I ignore them? So I turn to you guys for advice. Attached is my code, the comm spec, and port mon snapshot's. Download File:post-549-1153680070.llb Download File:post-549-1153680142.txt

Table 2 is just a link between the Graphs Table and the actual Plot Data in the Plot Data Table. Really you only need two columns for Plot ID and GraphID, the extra stuff is if you want to store information specific to the plot..like a color so that you could load the configuration into your graph property node when you query the db for a Graph. I have been using a similar technique on an application recently and it hasn't had any problems yet, but the Plot Data table is still relatively small ...about a million points. I can query and return a 150000 pt plot in about 5 secs across the LAN. Not too bad. We'll see how it does as the DB grows. I'll let everybody know if there's an issue.

Are you using a daq card and DAQmx to sample the data? The only time I have seen this is when I set the sample freq. too low by accident. I've seen NI's Express VIs automatically cutoff anything above the Nyquist freq (which makes sense)

Ich verstehe Danke, Brian

I'm familiar with the tree control so I guess what I'm interested in is: 1) What DB tools did you use? labsql, ni db toolkit, or custom, 2) Do your VIs automatically traverse the database to build the tree? 3) If it automatically traverses what technique do you use? thanks.

Slightly OT Forgot to ask about your DB and tree control. Are the VIs you used to populate the tree from the DB proprietary? If not I'd be interested in taking a peek. I guess I'd have to brush up on my ?German? though. B

The tree implementation you show is a pretty neat subpanel implementation. I especially like the icon use in the sublevels. Very professional looking. I have taken a look at the OpenG wizard style used in OpenG Commander. That was my initial inspiration because it looks and feels very professional also. I thought subpanels might help make it easier and more generic. I had another thought last night, maybe it would easier just to make a vi template to use as a starting point for each wizard screen (with queued state machine). Then use this template to create VIs for all the screens and put the screen VIs in a top level VIs to manage the flow. The trick is passing information between each step of the wizard. I'm using some GOOP objects so it may not be as difficult as I anticipate. Anyway this strategy is not as elegant but follows the kiss principle. Thanks for the feedback, Brian

Has anyone tried using a Subpanel and some Back, Next, Finished, Cancel Buttons in a VI as a generic framework for a Wizard style interface? The main reason I'm thinking about doing this is the functionality of many of the wizard screens is also used in other areas of my app where I don't need to lead the user through steps. I've created wizards before using tabs, but thought a subpanel might be better because I could run a subvi in the background for each wizard screen and also call a screens subvi somewhere else if I just want to execute one of the screens. Has anyone gone down this path before. Let me know if its a stupid idea. Brian

You're right, but sometimes its less annoying to give them the answer, especially when a language barrier is in the way. Won't let it happen again. B

See attachments. Download File:post-549-1148345218.vi

I have a project down the road where I need to store Graph data in a relational database. I wanted to see what other people are doing in terms of table structure in a database to store graph data from various tests. The graphs could have a variable number of plots and also a variable number of points (say up to 1k pts) in each plot. Based on my limited experience with database design I was going to make 3 tables in the dB: Table 1 (PlotData) col 1 = PlotDataID, autonumber (primary key) integer col 2 = PlotID_fk, (foreign key) integer col 3 = PlotDataX, real col 4 = PlotDataY, real Table 2 (Plots) col 1 = PlotID_pk, autonumber (primary key) col 2 = GraphID_fk, (foreign key) integer col (n) = (plot info ....) col (n+1) = (other plot info) Table 3 (Graphs) col1 = GraphID_pk col(n) = ....(graph info) col(n+1) =...(some other graph info) Then JOIN them altogether on the primary keys to retrieve the data. My worry is PlotData table will get huge and take a long time to query. Has anyone gone down this road before? Is there a better way? Thanks in advance