Jeff Plotzke

Thanks. Talked with NI and it turns out that this issue (CAR 447058) is fixed in the 2013 SP1 f1 patch. I've installed the f1 patch and my assembly works fine now.

Daklu, Were you ever able to get to the bottom of this error? I'm having the same issue. I've simplified my code down to a very basic lvclass and still get an exception thrown anytime there's both an input and output of a class as you've shown. Using LV2013, VS2013, .NET 4.0. I've created the lvclass Vehicle, which has 3 methods: initializeVehicle -- Returns a LV class object. setMakeModel -- Inputs strings for make and model and stores in class private data. getVehicleFullName -- Concatenates the make and model strings from the object and outputs the concatenated string. I call this from a simple C# console application: VIE.LVClassTest.Vehicle testVehicle;VIE.LVClassTest.Vehicle.initializeVehicle(out testVehicle);VIE.LVClassTest.Vehicle.setMakeModel(testVehicle, "VW", "Golf", out testVehicle); string vehicleName = "";VIE.LVClassTest.Vehicle.getVehicleFullName(testVehicle, out vehicleName, out testVehicle);Console.WriteLine(vehicleName); I get a VIAssemblyException at the setMakeModel function saying: "Failed to convert the LV Class to the .NET class because LV cannot get the LV Class Instance." The function initializeVehicle works fine. As a test, I also tried calling the .NET assembly in LabVIEW: I also get the same exception thrown at the setMakeModel invoke node. Probing the outputs for the functions, initializeVehicle returns a valid refnum, however setMakeModel returns a null refnum. Any thoughts? Thanks! (Also cross-posted as a reply on NI forums here: http://forums.ni.com/t5/LabVIEW/Problems-exporting-a-LVOOP-class-to-a-NET-interop-assembly/m-p/2801694#M821666 )

Another note is that you can take most PCI DAQ cards and use a RTSI cable between them to add the synchronization layer that PXI provides. It's the poor man's PXI and doesn't give you the convenient form factor PXI provides, but allows you to do synchronization between your DAQ cards on a desktop. What is RTSI: http://digital.ni.com/public.nsf/allkb/A120195AAAA9222A86256C69007C8B27

Thanks for noticing this -- We're currently re-organizing the Code Repository guidelines for LAVA 2.0 and don't have them up yet. We'll have that posted this afternoon and then those links will work.

A PXI backplane is essentially a PCI bus with added signals for dedicated timing and synchronization. I'd use PXI if you're specifically looking for synchronization between cards. Other than that, and being different form factors, there's nothing else largely different between the two. PXI systems run either with an embedded controller (which typically run Windows, but could also run an Real-Time OS) or can be linked to a PC using an MXI cable. You'd program in LabVIEW the same you would on a desktop. Here's a page that describes PXI: http://zone.ni.com/d...a/tut/p/id/4811

At the bottom of every page, there's a "Mark Board as Read" link that will wipe the "View New Content" content. Is this what you're looking for?

We've disabled the option to select your own skin for the site -- I've set your profile back to the normal skin.

Google's cache has been keeping up and started caching the LAVA 1.0 'Offline' page about a week after it went offline. But, we should have all of the missing pieces back up on LAVA 2.0 now -- Let us know if you see something missing. Thanks!

Because the second item in a list is always the coolest! I just turned off the B) shortcut for it. Lettered lists should work normal now

QUOTE (Yair @ Jun 3 2009, 02:34 PM) We'll definitely post our presentation along with notes and suggestions gathered during discussion at NI-Week for those who aren't able to attend. Is there anything in particular you'd be looking for in this presentation?

QUOTE (Thang Nguyen @ Jun 2 2009, 05:23 PM) If you're trying to do automated testing or control of your application, I've used AutoIt3 before (jlokanis also brought this software up in his post). AutoIt is a sort of scripting language where you can define mouse/keyboard events, looping, file manipulation, display interaction -- you name it. This software can do a lot. In my application, I needed to test running my application with about 50 different configuration files. I pre-made the configuration files and then had AutoIt automatically copy a new configuration into the application directory, run my application, wait for it to start, click the Run Test button, wait for a pass/fail indicator to turn red or green, then click the exit button, and then start again with a new configuration file. After about 10 hours (and several beers since I didn't have to sit next to the tester ), I came back and only had to look at log files generated from my application. That said, the button clicks were done solely based on a command in the script that said "do a single-click at coordinates 123, 345 on the display") -- I couldn't actually pass in the button name or the like. I had to do several test runs to smooth everything out. Perhaps this is up your alley. Best of all, AutoIt is open-source (read: free).

Christopher Relf and I will also be co-presenting another topic at NI-Week: "Software Engineering with LabVIEW from Requirements to Deployment". Focused on V-Model development from requirements to traceability through the product development cycle, we'll be discussing how to incorporate National Instruments tools (Requirements Gateway, Unit Test Framework, etc) to ensure quality in your projects. I'm also planning on walking through regulated industry case studies and how this process easily maps into these regulations. Note that this is meant to be an advanced session and I don't want to turn this into a sales presentation. What would you value most in a process-oriented presentation? How many of you have used NI tools in order to more closely tether your requirements and design to your development? Do you currently struggle to maintain a V-model development process? Thanks for any of your feedback!

I can't believe this... this is from a REAL TV show in Japan meant to teach "useful" English... http://en.wikipedia.org/wiki/Zuiikin'_English