GoGators

Hi, So LabVIEW currently doesn't support WPF. But I have figured out a way to put a WPF on a .NET Form (sometimes referred to as a WinForm). Now I need to be able to launch the Form from labVIEW so that I can interact with it. It is the equivalent of launching a VI at runtime (using VI Server) and having two independent VIs running separately. Anyone got any ideas? I think my main problem is that when I try to launch the Form with the Show method, it wants me to assign an owner application of the form. Thanks all.

Seems like it would be possible. The VISA Server has to be installed to download code to the RIO over ethernet: http://www.ni.com/pdf/products/us/6358_crio_rt_controllers.pdf I guess my first question is do you have both VISA and VISA server installed.

<br /><br /><br />I have to say the editor is not bad. I wish it explained more about the concepts of UML. Other than that I have just peiced to gether what I could get from free web pages. But the tool seems to line up well.

I was pretty sure that a QSM, no matter what you did, was going to difficult to model using Meally-Moore state machines. The reason is that the Queue essentially makes it event driven, and that events break the predefined transition from one state to another. The way I look at it is with the three cases below. 1) Basic Case. Enqueue state A, state A is processed, wait for next state. 2) Compound-State case. Enqueue state A, state A is processed but at the end of the state it enqueues state B. State B is processed, wait for next state. 3) Interrupted Compound-State Case. Enqueue state A, state A is processed but before the state finishes state C is enqueued, at the end of the state A it enqueues state B. State C finishes. State B finishes. Wait for next state. Essentially that could go on forever with events queued up, so that nothing processes sequentially like a SM needs to be modeled, and every thing is at the mercy of the queue. I would say to enforce the flow of the program if you need to model it. If a Sequence is running only allow states to be queued up to a secondary queue (or more). That makes it so that sequences must finish before moving on to other operations, thus the wait state must be preformed before operating on another sequence. I think that makes modeling much easier. Drawback is that new events have no priority and you have to wait for sequences to finish before responding. Event based modeling is difficult, and always makes me do star-type diagrams.

Thanks for the link. I read all five pages then realized I should look up AVL tree. I should have specified it needs to be bi-directional and non-binary. I am trying to make the basis of a configuration data-structure (or any other tree with non-restricting features), and it seemed like a good starting place. The idea being if you want to represent a file-folder structure you could with it. Then you would use the tree control (or multi-column listbox) as a way to visualize the data (much like the custom probes I made). So is a AVL tree similar to the problem I am trying to solve, and I can't visualize the problem correctly, or am I doing the correct thing with my code. On another note this might be the basis of making a custom run-time NSV deployment tool (obviously being tied to a project is little restrictive).

Definitely should crash. At least that is what it does to me all the time. If you want too log your memory usage here is where their are VIs to do it. In LV2009 they are native. http://zone.ni.com/devzone/cda/epd/p/id/4952

LAVA, I have a need for a tree data structure in LV. Rather than using a a tree control on the front panel and using its methods and properties to manipulate the tree I decided to see if I could do it using LVOOP with DVRs. In the end I have something that looks promising, but I was wondering if anyone has tackled this design pattern yet. TopLevelTest.vi is the top-level. There are custom probes for the tree and node class to see the data better. Also since that was my first UML design, if anyone wants to critique it that would be great too. Tree.zip

Thanks all, I think I'm gonna start with StarUML and see if I like it.

I have noticed some people posting their UML to demonstrate what they are trying to do with native LVOOP. What tool are you using and is it free? I tried finding it on another post, but the search didn't seem to come up with anything.

Thanks for the MDI search term. As soon as I had the name so many more forums were useful. I guess I like this one best since the first example is simplest: http://forums.ni.com/ni/board/message?board.id=170&message.id=113425&query.id=1089553#M113425

The link looks broken. I have reported it to the moderator. Any chance you could repost. Any chance you have a bit of code that could demonstrate it? If not I'll start digging around.

I think the bottleneck is the network cards. A new PXI controller will have a gigabit port and the 817x has a 100 megabit. Just a best guess and not a benchmark

I have a need for a workspace in an application I am making. I was wondering if anyone has done this, or has some basic ideas. A workspace is similar to the concept of a subpanel, except you can insert multiple VIs into it, and they can float around on their own. The best way to put it is like excel. You can view many spreadsheets simultaneously in the workspace, but they cannot leave the workspace. The sheets can be minimized but they still exist inside the workspace.

As a side question to LAVA, is there an "control or indication repository"? I have made a bunch of common ribbon-type buttons that might be nice to give to the community. Stuff like a Exit button, Save, Busy, the sort of thing that makes an application look more stylish and modern without being too flashy.

Jason is right. The only thing you will need to copy is the project since source distributions are target based and not project based and it can drag all the interesting (vi.lib, user.lib, and inst.lib) stuff over. Just be careful not to include files you don't need, because cross-linking problems can be annoying.

I work in SE for NI. I was making a webservice based communication for the CVT (was going to call it webCCC), but since I don't think webservices are quite there I am putting it off. I had heard about someone who had done it with variants and variant attributes, and was fishing to see if anyone had posted something like that. Maybe for a different thread.

I guess the bonus of a webservice is it meets RESTful architecture, connection management, security, and a little help meeting internet standards (XML, JSON, etc.) Not being able to debug on RT, and separate application space lowers the advantage of connection management and RESTful (state management). How do you manage your tags? I ask because I have been do a lot of that lately. Originally I got into webservices trying to make the communication layer for my tags a little better, and meet more standards.

Are you setting the user access in the project or manually ftping the ni-rt.ini file over? I would say the correct way is through the project.

Great post by the way. I was trying to do this exact thing for my application. The way I ended up doing it was to open up a reference to the other application using VI server, then reading and writing to controls and indicators that way. You could also do it using TCP IP to localhost. Both of these are not great solutions, but they did work for me. Ultimately the problem of WebServices on realtime targets is that it does make sense to have them in their own application instance. A control system does not typically act like a command-respond system. I think the restful server needs to be more tightly integrated with the rtexe, rather than separate. Might make a good idea market.

Well, it is not really translations of controls, so much as resources. Naming the resource and control the same thing makes it easier on the developer though. Looking at the article would probably clear that up. The translator and the developer can be different people, as long as they have agreed upon the resource naming convention. I assume that's how most applications provide run-time translations.

It certainly took some effort to make the editor. Hopefully it gets some use. The nice thing about a single file is transportability. Also grouping translations into resources helps with accessing data if you want to change the language setting at run-time. Plus the editor helps you organize resources into folders, so all the controls for a single VI can go into folder. Just makes it pretty.

I made a Localization Configuration Editor and for NI week this year. http://zone.ni.com/devzone/cda/epd/p/id/6257 It helps you to create/edit a resource file with all your translations. Then there is a library that helps you pull the information from the resource file into your application. Its all open source if you want to give it a try.

The schema is not too complicated. To be honest I just wrote out a bunch of files on a windows machine, and recreated what they wrote out (simple read/writes). The documetnation on MSDN is pretty poor. I'm starting to think an XML parser on a real-time target would be a useful feature. I published the article and examples here: Supporting Relational Databases on LabVIEW Real-Time Feedback should go http://forums.ni.com/ni/board/message?board.id=deployment&thread.id=11

Sorry for not looking over these posts earlier. Like Christian_L said the VxWorks version is up and running. A simple LV API is already made. Still working on the PharLap version in CVI RT. Since I am still working on it the code it is still messy, but if anyone needs the VxWorks portion right now I can post what I got. As a side note: From my original post I ran into an interesting idea for #2. The file format I choose was ADO schema XML. It turns out the Database Connectivity toolkit has some Save/Load Recordset VIs in the Utilities palette. These Write and Read in XML. If you reverse engineer the schema you can make your RT target write files that can be read into database using the toolkit. Just something I noticed and implemented if anyone is interested.

This is so awesome. I was in the middle of making it myself.