PJM_labview

I noticed this "unwanted behavior" since the first time the subpanel where introduced in LV 7.0. I spend considerable amount of time trying to figure out what was causing it, but I was never able to exactly identify the problem. As best as I can remember (I have not used subpanel that extensively since then) this has to do with how "fast" you swap your subpanel and how you are doing it (meaning how you used the subpanel properties and in which order). One thing I seem to remember is that if you stop the SubVIs when they are not in the subpanel it seem to help. I never tried the defer panel update, but this might actually help now that I think about it. Sorry if this is not that helpfull, but this is all I can remember. PJM

In LV 8.0 you can create (and control programatically) a right click menu on every control. I am not sure that this is what you are trying to do though. PJM

If I understand you right, it look like a tab control with hidden tab is what you might be looking for. PJM

Please post your OpenG question on the OpenG Forum. Thank you PJM

It is usually a good practice not do any work in the event structure. Event structure are used to catch events and then through some mechanism, the job to do in response to that event is selected. The major advantages is that instead of beeing tightly coupled to the event, the job to do can be very easily recalled by anything at anytime. In the image below the job is passed to the case structure through a shift register. You could also use a queue to pass job and data to another loop. You might want to investigate queue, as you will see they are a lot more efficient to pass data between parrallel loop than locals. PJM

The best advise I can give you is to contact your local National Instrument sale rep in your area (a quick google search for arcadia high school seem to indicate you are located in LA, so the link is for the LA sale rep contact person). They are all technically savvy people that can help you selecting some hardware. You might even succeed in convincing them to give you a loner or two. For example, for the vision system there are Compact Vision System available (I have no idea whether this will interface with the camera that ship in the kit or whether the rules allow you to use this additional hardware). Another type or hardware (which could potentially replace the whole control system shipped in the kit) is the compact RIO. Note: these are NOT cheap items, and they require some good knowledge in LabVIEW programming. Also make sure to ask your local NI sale rep if the LabVIEW version you got allow you to target these system. Hope it help PJM

While this is nice, I wish that we could reduce the border thickness at will. Not beeing able to do so pretty much render array of cluster as user interface object useless (because every items inside the cluster is spaced 8 pixels apart). Note: if someone figured out a way around this, please speak up PJM

Have have been following this threads on chief delphi (they have some information with LV code example)? LabVIEW, like any programming langages, can do everything that the user programs it to do. The added benefit is that it is usually a lot faster to develop application with it and that it has a lot of built in support for communicating with different type of hardware. So what in particullar are you trying to simulate? Motors, encoders, picking up balls, shooting balls, getting data from the camera...? In any case, there might be some code available for simulated some specific things, but you might have to wrote some as well. PJM btw, what team are you on?

Out of curiosity, are you participating in the FIRST Robotics Competition? PJM

Well, I would use activex only as the last recourse. If I have a way of doing something in labview (even if not perfectely), I will not use ActiveX. There are too many issues of stability and compatibility (for example your client install a piece of software [unrelated to your software] on his PC that update one of the ActiveX component you were using and suddenly your whole application is no longer working). Just my though on the topic... PJM

Just a quick comment about that statement. I think what other people mean if that you might want to consider updating the display at a slower rate while still logging your data (if applicable) at an higher rate. It may not apply in your situation, but this is just a thing to keep in mind. I dont think the mesa library that ship with labview support hardware acceleration (unfortunately). This mesa.dll (version 3.0.0.0 Copyright

It seem like this to me as well. We will should expect 8.01 soon (hopefully). PJM

Thank you guys for the feedback. This is very useful information which will let us move forward with our design. PJM

This is a dependency error. The package you are trying to use depend on another package. You need to download the "oglib_error" package. To prevent further occurences of this error, I will strongly advise you to download them all. See image below for a list of packages you migh want to download. Cheer PJM

I have seen people using it for dumping stuff they dont want to see on the UI 5. Garbage collector -- Use a 2 tab control, put everything in the first one that the user should not see (for example VI inputs, VI outputs ...). In the second tab put the UI controls that the user is expected to interact with. At run time make sure the second tab is selected and that the user do not see the tab control. PJM

Hi I am currently working on a project that has about 1000 IO Points. The IO Point are connected to PLCs that are accessible through OPC server. I would like to get some benchmarking information for data socket and for LabVIEW DSC. For example, can I expect to be able to read the 1000 tags within 100 ms using data socket? What about LabVIEW DSC? Does the share variable introduced in LV 8.0 increase performance? Btw, I was watching this presentation from NI regarding LabVIEW DSC 8.0, and it mention the following: "The LabVIEW 8 DSC Module introduces integration of DSC events, such as monitored value changes and alarm condition changes, into the LabVIEW event structure...Now, the desired event conditions can be easily registered with the LabVIEW event structure and are automatically monitored." This seem pretty cool. Thanks in advance PJM

I noticed you are using LabVIEW 7.0. I sort of remember feedback nodes having performance issues in LV 7.0. Try replacing them with shift register. PJM

Indeed, Now I can reproduce this in 7.0, 7.11 and 8.0 on my Win XP machine. It crash also if step 6 is any interaction with the newly created scale legend. PJM

Heu, may be it is too late for me now, but what do you mean by "duplicate scale" ? Trying what you describe (without "duplicate scale") does not crash labview 7.0 for me PJM

I think the official name for the "LabVIEW 2 Globals" is "Functional Globals". It is certainely not easier to visualize what it mean than "LabVIEW 2 Globals". PJM

Did you actually click on the link I provide you in your post about the navigation window? If you click on the "here", you will get a page (although now obsolete) with screenshot, explanation about this navigation window replacement and a download link. Cheers PJM

This is a good idea, but I will argue that there can be even a simpler one. Just add an option for disabling this auto resizing all together (whether as a global ini settings in the labview.ini, or per enum typedef through the right click menu). I would rather have the capability to set my own size permanently rather than having LabVIEW doing it for me (until LabVIEW can "read my mind" ). PJM

This is correct, but as an alternative to the Navigation Window, you can use the Bird's Eye View (which has similar capabilities and works for LV 6.x and better) accessible through the OpenG commander as a package or by itself here. PJM

Did I hear anyone say clueless? PJM

Before you go investigating GOOP, did you download Michael presentation on process spawning that Jim linked to. It explain how to use Queues to span process? From reading your description I am still not quite sure what's going on. So let me re iterate my questions Is your reentrant SubVI a LV2 Global? Is it use in only one location in the template? If you anwser yes to both, you do not need to instantiate your LV2 reentrant subVI, just drop it as such and pass parameter through the connector pane. Now I jus re-read your initial post and I think you issue is that you need a different queue name for each template instance. Once again read michael post on process spawning you will learn a lot about queues. Good luck PJM