crossrulz

Fab, my testing concurrs with yours (LabVIEW 2011 SP1)

I know you meant for this to be rhetorical, but about all you really can do is send in the crash reports and do what you have done. Finding the exact cause of the bugs is sometimes really hard to do. But R&D is doing a lot of work. Maybe your bug was fixed in the 2013 beta. Maybe they are still trying to figure out where the exact problem is. I understand your frustrations, but after attending the CLA summit this year I realized just how much work the R&D folks are doing between bug fixes and making the language better.

You will need the App Builder, which comes with the Professional version. In order to run your EXE, you will have to install the LabVIEW Run-Time Engine (RTE). Also be sure to read all of the EULA for LabVIEW. There's language in there that you have to put NI's copyright for LabVIEW in an About Box and/or elsewhere in your application. I'm a little fuzzy on the exact details at the moment.

They are in the February/March time frame. So I would it should be out within a month or so. There shouldn't be anything new in it. Just major bug fixes.

The problem is that you are dynamically calling your VIs. So once the dynamic VI is complete, it is pulled out of memory. So your clones are being disposed of when they complete.

If you only care about the latest data, a notifier is the guy you want. A queue is for lossless data transfer. A notifier is for lossy data transfer.

That's a lot of good information. Thank you for the article.

Cross-posted on the dark side

I have not gone through the LabVIEW for Everyone. But from quick skimming, it looked really good. The LabVIEW Style Book is really good, but it won't help you with the CLAD. I found the Advanced LabVIEW Techniques worthless. There's no code in it! The Basics I and II course books should be really helpful. The core of LabVIEW hasn't changed much. Here are some links that may help you in your studies. CLAD Information on NI.com - there's a few links for practice exams and other study material The Daily CLAD on NI Communities - CLAD-like questions to get you thinking about possible topics

NI sells them:http://sine.ni.com/tacs/app/fp/p/ap/ov/lang/en/ol/en/oc/us/pg/1/sn/n5:selfpaced/

cross-post on the dark side:http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Parse-one-String-containing-numbers-into-two-Arrays-and-display/m-p/2233252#U2233252

I was thinking of simply making a quick drop shortcut to do this. Just haven't found the time to make it yet.

Congrats.

Is this a CAR for the Delete From Array? I sure wish we had visibility into the CAR database...

Just a general comment: There is no need to set your file position inside of the loop. The position increments during the read. After a read, the position will be set to the next byte, so the the next read will start where the previous left off.

I fully agree with Philip. You can right-click on the Read from Text File and select "Read Lines". The glyph will change. Set the count to -1 to read the entire file in lines (the default becomes 1 line). The other option you have is to use the Spreadsheet String to Array.

Hate to burst your bubble, but Darren included a little nugget: <vi.lib>\Utility\High Resolution Relative Seconds.vi I know it's there in 2011 and 2012.

Ok, here's the updated VI with the correction found above. Long Wait.vi

Yeah, my benchmarks found that the delete from array was really slow. What I ended up doing in the proposed VI was to reverse the array and then index the first element. This method was slightly faster than the index array size -1.

Yep. I goofed it up when cleaning up. Will repost when I get a chance to fix it later today.

They actually use the Reshape array. But the math for how to setup the dimentions is done inside these VIs.

More submissions to OpenG. This time I have a few array functions that I have had to use over the years. These VIs are for taking a 1D array and turning it into a 2D array, taking a 2D array and turning it into a 1D array, and to simply get the last element of at 1D array. Thoughts? Critisism? Praise? Ideas to make it better? Good for OpenG? 1D to 2D array.llb 2D to 1D array.llb Final Array Element.llb

Here is another VI I am submitting for OpenG. It is for when you have to wait for something to happen and this wait is in the domain of seconds. You don't want the user sitting there wandering if the program froze. So I made a VI for these long waits that includes a progress bar. Notice that this VI uses my Global Stop VI found here. Thoughts? Critisism? Praise? Ideas to make it better? Good for OpenG? Long Wait.vi

Here's a few generic CRC VIs I made sometime over the years. They do not use the lookup tables, so they may be a little slower. But they can be set to any CRC configuration. Included are an 8-bit, 16-bit, and 32-bit versions. CRC.llb

I think I found it. In the testApp.vi, the first thing that happens is the Close. The shift register is of the parent’s class. Since the shift register hasn’t been initialized, it will have a class of the parent. Therefore you get your “parent class was used” error. This error is then causing the rest of the code in the event to not run and the shift register will have a “parent class” loaded into it. I recommend changing the error to a warning and see what happens.