alexwarrior

Hi Paul, Probably the way I'd do it is through an XSL transformation. That's a good way of translating between different XML applications; you write an XSLT file, pass it along with the XML input file, and the XSLT processor outputs the translated XML file. You'll need to create an XSL stylesheet, and then pass it through an XSLT processor. LabVIEW can't do the transformation though, so you'll need to use an external one. I remember using command line tools that do it, that just take the two input files as arguments and the output file is produced. Or you can do it programitcally, although I haven't done it in Java, just .NET languages. In .NET, it just takes a few lines of code (three or so?), and I'm guessing with a Java base processor (Xalan-java perhaps?) it's just as easy. A beginner might be tempted to do the transformation by manually traversing a DOM and picking out elements with lots of if..then...else... but this can be tedious and error-prone. Hope this helps! - Alex

Hi Justin, Can you explain a little more about what hardware you're using? I.e. what LabVIEW is running on, what FPGA, any other DAQ hardware you're using, etc. Best, - Alex

Hi Paul, I've been using the FTDI chips for quite a while. With the virtual com port driver, you can pre-set the latency timer to something other than 16ms in the ftdiport.inf file before installation. I believe there's also a Windows registry value that you can get at for changing the value without going into the Device Manager after installation. A couple of app notes on FTDI's website will hopefully help: This one talks about latency and modifying the inf file before installation: http://www.ftdichip.com/Documents/AppNotes...LatencyFlow.pdf And this one mentions some registry keys you can try: http://www.ftdichip.com/Documents/AppNotes...s_AN_000073.pdf Good luck! - Alex

I couldn't quite fully grasp your question, and I've not worked with that particular debugger, but if it's just a matter of invoking an executable and passing it some command-line options, the System Exec VI might be what you need: http://forums.lavag.org/index.php?act=attach&type=post&id=5879 - Alex

You may have seen this: http://zone.ni.com/devzone/cda/tut/p/id/3586 It's a unit test frame work that you can use with LabVIEW. For most of the LabVIEW applications I work on, I am the only developer and I write my own unit tests, but don't use an automated test system. I keep a subdirectory under my main VI called 'Unit Tests' where I test out some of my SubVIs. I try write my SubVIs with unit testing in mind. So instead of writing a SubVI called 'save data file', or 'send data over UDP' I might write one called 'generate data file contents' or 'generate UDP packet contents'. That way I can easily write a unit test that displays what the data would be on the screen in a string indicator, instead of writing actual data to disk or the network. - Alex QUOTE(Tomi Maila @ Feb 14 2007, 01:20 PM)