Phil Duncan

Hi All, I have read quite a few posts about labVIEW XML and I have used it quite a bit in a few projects already. We are in the process of planning ournext generation DAQ system for rotarty wing flight test applications. After some research, we have decided to implement more file IO utilising XML and came across XidML which is trying to become the industry standard for flight test systems. It would be beneficial if our LV apps can read and write XidML files, but I am at a loss as to how to efficiently implement such an interface. Has anyone else played with XidML? Is there a way to get LV to play nice with XidML files? Cheers & Beers :thumbup: :beer:

Greetings all, I have been asked to provide "a boolen LED" style indicator that does more than a standard boolen LED so many times now that I have decided to create an XControl for it. (And yes, once it is complete I will submit it to the code repository). typically this "boolen" needs ito indicate 4 different states: On (green); Off (Green); On (red) and Off (red). Recently I have been asked several times to provide an indicator that distinguishes between 6 different states: the 4 previously mentioned states as well as Flashing (green:on/off) and Flashing (red:on/off). I believe this falss squarely in the realm of XControls. I can easily replicate the 4 state boolean but I am having difficulty with the 6-state version. The problem I have is that the facade VI is designed to respond to events and then run once only. To "Flash" the LED I need to switch it's value according to a timer (flash rate). I am aware of the Blinking property of LED's but they only flash at a pre-determined rate and only between yellow and the current LED value colour. I have attached a VI showing the behaviour I am after and the XControl as it's currently implemented ie 4-states. (Both are LV 8.2) I am sure some of you out there have a cool innovative way to achieve the desired outcome. Cheers & Beers :thumbup: + :beer: [ attachment=7324:BOOL_XCo...imulator.vi]Download File:post-4848-1192774641.zip

Problem solved. I simply selected the option "... do not disconnect type definitions or remove ..." Cheers & Beers :thumbup: :beer:

QUOTE(LV Punk @ Jun 13 2007, 10:07 AM) Thanks for the info. My app is performing several DAQmx functions within the timed structures however it has been developed in LV 8.2. I will keep trying to nut this one out. Cheers & Beers :thumbup: :beer:

Hi all, I have been working on an application that I recently improved by implementing a timed loop and timed sequence structure. The VI's work fine in the LV environment but the compiled application tells me it can't find several of the timed structure controls. Namely the wakeup.ctl, nitl_modes.ctl and the timing_clust.ctl. I pointed the dialog box to the appropriate ctl's in the LV directory and the app then gave me the following errors. The program was developed with the LV professional dev suite. http://forums.lavag.org/index.php?act=attach&type=post&id=6073 I am at a loss as to why the app thinks I don't have the full dev version and secondly why the app builder hasn't included the required files? :headbang: Cheers & Beers :thumbup: :beer:

QUOTE(JFM @ May 23 2007, 04:09 PM) Fantastic! That did the trick. I had to disable "Allow dragging" but now the annotations sit over the data and don't interfere with the user clicking on the XY-plot. Thank you very much Cheers & Beers :thumbup: :beer:

QUOTE(Jon Sweeney @ May 22 2007, 10:21 PM) Thanks for your suggestions Jon, I like the second option with a black decoration under the XY plot. Unfortunately, plotted data covers up the labels because they are behind the data. The first picture in this thread represents a typical data set to be plotted and as you can imagine, with the labels sitting behind the data I can't see some of them. I guess I need a way of having the labels in front of the data but tell LV to ignore them as an interactive item. So we are back where we started. Cheers & Beers :thumbup: :beer:

QUOTE(Michael_Aivaliotis @ May 22 2007, 02:09 PM) Sure, here is a stripped down version that should help. Cheers & Beers :thumbup: :beer: http://forums.lavag.org/index.php?act=attach&type=post&id=5912''>http://forums.lavag.org/index.php?act=attach&type=post&id=5912'>http://forums.lavag.org/index.php?act=attach&type=post&id=5912

Hi all, I am trying to allow a user to interact with a special XY plot. The goal is to have them click on the XY-plot and draw (plot) a point where the user clicks and maintain the position of the point on the XY plot under the mouse until they click again. The problem is that this XY-plot has labels on it that interfere with the mouse. A cursor appears in the plot area but the "operate" cursor appears when the mouse is over the labels and I can't trap a mouse event. I can turn off/on the labels with a mouse enter/leave event but that makes the labels invisible while the mouse is in the plot area which it will be for most of the time. The labels must be in front of the plot area to be visible. I am looking for some fresh ideas to help circumvent this problem. Here is a pic of the plot for assistance. http://forums.lavag.org/index.php?act=attach&type=post&id=5909

QUOTE(Jim Kring @ May 2 2007, 12:12 PM) This will also make a nice repository for the teachers/lecturers who set the assignments to peruse occasionally as Louis mentioned. Cheers & Beers :thumbup: :beer:

Thanks for the prompt replies. I had a look at the forums and found quite a few very useful VI's for rotating picture control images. After playing with it a little more I have managed to nut out a solution I think is a little quicker than all the pixmap calculations. I can plot data on an XY graph and rotate it quite easily. For the compass rose, I ended up making the FG and BG of a gauge indicator transparent (as well as the needle), changed the tick marks and numeric values to yellow, and overlaid it on the XY graph. rotating the gauge is then done by simply changing the Scale.ScalePosition.Start value programatically. It now rotates with the data in the XY graph and the user can not tell they are two separate entities :thumbup: . Here is a pic of the display as configured. Cheers & Beers :thumbup: :beer:

G'Day all. I would like to plot some data on a compass rose type display and be able to rotate the data along with the compass rose. I guess the closest thing I can think of to describe it is a radar image that has bearing markings and can rotate about it's centre. Like the image attached. Currently I am playing with XY plots (rotating data blobs) and I can programatically rotate a simple gauge indicator, but I need to incorporate the data "into" the gauge (without any needles) and rotate the lot. Any ideas? Thanks in advance for your help. Cheers & Beers :thumbup: :beer:

Thank you both for your input. I will do some more research and see if I can do "the impossible". Watch this space.

Greetings all, I was once told "The quickest way to get an engineer to do something for you is to tell them that it can't be done." True to form I am trying to achieve what I have been told is not possible. My goal is to implement several remote stations (PACs) controlling some equipment and be able to access these PACs over a wireless broadband connection via the internet. The remote sites are just that, they would be scattered over hundreds of kilometres (miles) from each other and a central monitoring station. I spoke with a representative from Australia's largest telco who supply modems and cards to access their "Next G" wireless broadband network (HSDPA). I was informed that the minimum requirements for a any card (USB or PCMCIA) that connects to the wireless broadband network is a windows O/S. Compact fieldpoint units run a real-time operating system, so unless some very smart person has already developed labview drivers for these cards that can be included in a real-time application on a PAC I have reached a large high brick wall. :headbang: Another issue is that the remote sites will obtain a dynammically assigned IP address upon connection to the network, meaning the central monitoring station will have a number of moving targets to try and communicate with. So my question to you all is can one set up a remote PAC and connect to it via a wireless braodband internet connection? Has anyone done anything similar to this? Cheers & Beers :thumbup: :beer:

Thank you all for your excellent input. I will let you know which way we go and will no doubt have lots of development questions/bugs to iron out in these forums. Cheers & Beers :thumbup: & :beer: PS. I hope you are celebrating Australia Day Chris!

I am investigating options for developing a SCADA type system that includes remote monitoring/control of PLC's. I have been reading all about SCADA, LabVIEW DSC, NI Lookout, PAC's vs PLC's etc. It seems that this sort of project can be completed using LabVIEW DSC but it looks like this may be the low level approach. Does NI Lookout simplify the process enough to justify the cost? Will LV DSC allow me to do everything I need? Your advice is most welcome. Cheers & Beers :thumbup: & :beer:

Hi all, I am having a very furstrating time trying to get a digital ouput to remain high for a certain number if pulses (from a pulse train) generated by a counter. Both the counter and digital ouput are modules in a SCC-2345 carrier. I am using a PCI-6221 card to communicate to the SCC but so far I have not had to refer to the card in my code. I would like to keep it that way. I have read articles like this one http://zone.ni.com/devzone/cda/epd/p/id/4455 that refer to routing the counter output to PFI12 etc but I cannot get the sample clock to see the counter output from the counter module as a valid source for timing the digital output line. Thanks in advance for you help. Cheers & Beers :thumbup: :beer:

Thanks to all for your replies. Ben, I am using XP 64 on a developement machine for other (non NI) reasons. I currently do not have any clients requiring a solution to be hosted on such a beast. I do like the speed improvement of XP 64 though. So I guess all I have to do is wait for MS to release VISTA, then wait for NI to release those 64-bit drivers. Cool, should be able to get stuck into this project by around 2009. :headbang: Cheers and Beers :thumbup: :beer:

Have you tried installing each component from its MSI file individually? Right back atcha! I tried a couple of the 125 MSI files individually (max.msi, then daqmxef.msi), some worked but others displayed an empty list of components that were (not) going to be installed. I stopped because I don't have a spare day to manually install all the msi files and I don't want an installation that is incomplete in some areas. Right now I am resorting to using my laptop for LV8.2 app development. Cheers & Beers :thumbup: :beer:

Greetings all. I am running LV8.2 on a windows XP 64-bit PC and I cannot get the device drivers (dated Aug 2006) to install. I get a "This installation is not supported on a 64-bit operating system" error. I have searched these forums, the web and NI.com for any information on how to get around this limitation or indeed if there are any plans for an updated set of drivers that are XP-64 compatible. Has anyone else solved this problem or got any information about this? Thanks in advance. Cheers & Beers :beer: :beer:

Nice. Just be aware though. It starts all innocently with a simple "find and move red ball" application next thing you know ... I Robot! Cheers & Beers :thumbup: & :beer:

WOW, you started a thread that was not about beer and managed to conclude the new thread by discussing beer. In one post !!! :worship: This is a fine example of Godwins/Kring's/Crelf's/<Insert Name here>'s law. Cheers & err Beers :thumbup: & :beer:

Here here. Congratulations. I often wonder how much work you actually get done? It seems you must spend the good part of each day providing valuable input and solving the worlds wire problems. Now that you have moved to the other side of the world "Up Over?" I get a small window to post replies before you Seriously though, your input is very much appreciated mate. Cheers & Beers (Tooheys Old of course!) :thumbup: & :beer:

I have a client that just purchased a cDAQ9172, 9481, 9205 and 9215 as an upgrade to some ageing hardware last week. They decided to implement an application themselves as they have a few years of "self taught" programming experience. They wish to do similar things that you are. I am visiting them this week as a followup. I will see how they are going and let youknow if they have run into any issues. Would rather be playing with the gear myself Cheers & Beers :thumbup: & :beer:

ann, Some of the required fils are not included in you post. Regardless, I think the problem is in the writeserial 4.vi. You may need to carefully review the code to ensure that you close every VISA resource that gets opened. Using a VISA global vi as you have is not a bad way to do it but you must be quite vigilant about what references (VISA or otherwise) that are open/initialised and how (& when) the application closes those references. For instance if your main VI calls the "Init" mode of writeserial 4.vi twice with the same settings, the second call should produce an error as that port is already open. This is more likely to occur when reading/writing though. There are two main schools of thought on how to handle this type of resource access as it is functionally identical to file I/O. 1) You open the VISA resource with an init type function and maintain the reference in a shift register (or other repository), perform all reads and writes to the VISA resource and close it when the application is complete. This may improve performance but you run the risk of leaving COM ports open if your application crashes before closing the VISA resource. You must ensure that ALL VISA resources are closed when they are no longer required. 2) Your application controls the VISA resource as follows: open->read/write->close any time it needs to communicate. This ensures that VISA resources are handled appropriately and minimises the chance of a COM port being locked out by LabVIEW causing problems on subsequent executions. This method will no doubt incur a perfromance penalty as serial devices often require a finite time to establish communication though. Sorry if I am regurgitating stuff you already know. Cheers & Beers :thumbup: & :beer: