Mike Ashe

Interesting if this turned out to be the first real headbutting between NI and Microsoft.

Dead? I get busy for a couple weeks and I feel like I lost touch with the planet. So what happened with Qubix?

Yes, a very big congrats on posting and then passing 500. It's appropriate for me to post my 501th to congratulate you on your 500+th. I stuck around on 500 myself for the last couple weeks since my custom text line over the 5 LV icons cannot yet be edited. Seems that you get to edit this if you pay for a premium membership, but not if you only earn it by 500 posts. Just my bit of passive protest. Still, your achievement is worthy of celebration. I've always enjoyed reading your posts and found your insight to be invaluable. Cheers to you Chris! Aha! it seems I spoke too soon, so I must apologise to the management. Although the <customize this text> appears under your avatar *at* your 500th post, it actually becomes editable only at your 501th post. So you have to pass 500. Speaking of preemptive congrats, there must be some type of big bash being planned soon for our FFF Michael Aivaliotis, since he is very soon to pass the 1000 mark. ;-)

If you have a problem with a VI that you have written, then post the VI here for us to look at. Often times someone will modifiy it quickly and post it back. So post your VI. On the second question, about adding in images or VIs, please see this post which describes how to do attachements. Also note the post after that one. Cheers PS: I hope everyone's coffee is as fine as mine is this morning

There is a strange property interaction with text colors. If you go to the properties popup list you will find that there are two "paths" to set BG color: Numeric Text>Text Colors>BG Color and Numeric Text>Colors>BG Color You can therefore modify tcplomp's VI as so: If you change the second color box and run the VI twice you get the same colors in the array both times. However, if you change the upper color box, (yellow in my example), the first time you run the VI the box is entirely yellow. On the second run it will be yellow with the red border color. Bug? Download File:post-45-1150375036.vi

Actually, since even Australians can get so thirsty that they drink water, I guess we must make allowances for anyone to indulge or not as they so desire, or to partially (read non-integer) indulge in their DSP's*. Too bad there isn't a fractional :beer: emoticon ... As for FORTRAN, if you keep using language like that you'll be forced to stay after school and wash your CPU out with CPM. *Digital Suds Processor

Actually I was thinking more of the episode where Boomer #2 and her shipmate try to warm themselves up in the rainy steamy jungle. Fortunately I watched that one with my wife. Later, I made the observation to my wife that I appreciated six packs, that was in the scene where #2 meets #'s 3-9 on the Cylon ship. I almost slept on the couch for that comment ...

My wife and I are hooked as well. This show is what scifi should be. The old B.G. ? Well, it was almost everything scifi should not be. I really got hooked on the show in the first 2 episodes when, faced by war, the writers did not let the fleet/characters off the hook with some last minute "deux ex machina" unrealistic rescue. They had to make hard choices, real sacrifices and they were really scared. Non of the hokey bravado of the usual action hero types. Boo-mer! Boo-mer! Boo-mer! Good thing my wife doesn't read this forum

Hi Adrian, As one of the more outspoken "Noob-Bashers" let me welcome you to LAVA. Seriously, I hope you find a lot of code, techniques and new friends here. I don't think it is true that we bash newbies in general here. What we take a dim view of is HH's, or "Homework Hustlers". People who ask us to do their homework or job for them without showing any indication that they themselves have tried to solve the problem on their own. You obviously did not do that, and as a result I think you will find a warm welcome from the regulars here. Hope to see you around. Cheers

Right now it looks like you have a good architecture worked out and your CPU utilization has plenty of engineering margin. I try to keep my utilization below 50%, and I like 40% for comfort. You are well below that. I would test things out quickly by creating a prototype of your new event additions. Don't try to simulate everything, just the extra data throughput. Dummy up at least twice the maximum additional data you expect and pump that through your system and check for strain. If you are still under 40% I would say you probably want to stick with your queues and current architecture. If you go over 50% or show spikes or data drop after a reasonable test run time, then you may want to think about architectural changes. Otherwise, stick with what seems to be winning in your current paradigm. Good luck.

Methinks the potential for abuse is high, but it is still a very nice nugget to have. It seems to be smart enough to avoid self reference and it doesn't let you enter at a "T" point. Anyone have any meatballs & marinara?

True, but there are also small ActiveX based libraries giving LabVIEW programmers limited functionality in sevveral of the Office applications. Several of these tools are free and you even get some in the \examples\comm folder that ships with LabVIEW. So if you want more, but do not want to pay for it you can add to the tools in the examples. Here is an idea: JdP, if you really want Open Office access why not start small on a proof of concept project that won't take much time? Take the ExcelExamples.llb in the LabVIEW and copy over to a new OO_Examples.llb and then just get these few VIs to work with the Open Office spreadsheet application. That will give you a good idea on how big the project would be to do a major toolkit like NI's Report Generation Toolkit. Further, if you released even that much here or as yeast/starter for an openG / sourceforge project I bet you would then get some help to add more functions. In fact, I'll make a pledge JdP: If you will do the conversion above, I will download and add at least 10-15 VIs/functions. I'm sure a few others would do likewise.

I downloaded this a while back and played with it. It is nice. But I found that I got frustrated with some of the limitations compared with the $$ version that they dangle in front of you like a carrot. I decided that if I was going to do modeling I'd go with 3DS Max or Blender if I wanted free/open source. Still, you're right, nice toy.

Are you sure that you don't just want the IMAQ Vision Toolkit/Module? It is rather pricey but is full of most of the vision VIs & utilities you could ever want. You can download a trial version from NI's website.

Backing up from the Test Executive stuff for a moment, you ask about menu and event handling, interVI communications (queues & notifiers) etc. Might I suggest that you go on over to www.openg.org and get the OpenG Commander. Then, stop before you download the OpenG Toolkit and all the other available goodies. Take some time to study the source code, architecture and style of the Commander itself. You will find great style and LabVIEW architecture principles all through it. Events, dual event/processor loop architecture, dynamic load/run, queues/comms. Spend a couple days studying it, then see if it doesn't answer a lot of your issues above as well as provide you with a lot of code/snippets/VIs to use in your test systems. Enjoy

Rolf is right about the hi-low tech trade off. Liberal use of Occum's Razor will keep your code neat and portable over the years. However, it is also good to learn new and more powerful interfaces/APIs, so perhaps your use of WMI on this simple case will give you some experience that you can use later on more complicated problems that actually require something with the power of WMI. Elegant, well written code almost always uses the simplest means to get the job done.

JdP, Although I'd still love to see (someone else ) create a nice OutLook &/or Thunderbird API, I officially doff my hat and hoist :beer: :beer: :beer: You solution is simple, direct and I suspect might even have an almost direct analogue on the MAC. Thanks for posting your (better) solution, Cheers, Mike

Quick and dirty: Add a TCP/IP channel between your caller and the remote VIs. Send a VI name (the one in the remote panel) and simple commands consisting of the control name and on/off/diable/enable/etc Yes, I know you'd probably like to just use the remote panel itself, but you have obviously ran into a limitation, showing that, while really neat, RPs are, in some ways, still not ready for prime time. Hope this helps, it is not pretty, but simple

I mean two methods: First try simple copy to new name: - Open VI Logger.vi and File Menu >> Save As... To new name: VI Logger_2.vi Try to run this way 2 copies. If that does not work Second Try: - On Windows Explorer >> Tools Menu >> Map Network Drive Create a new mapped drive pointing to your own machine and the directory where the LabVIEW.exe is. This, from this directory make a link on you desktop to the LabVIEW.exe here. Call it LabVIEW Instance 2. Now run LabVIEW the normal way and also by double-click on this new link. This should let you run two copies of LabVIEW at the same time and then two copies of your VI Logger. They will be in separate memory spaces and will not be able to interact except maybe through TCP/IP. Good Luck

Thanks Aitor. Nice modification. I am using your new version in a spash screen for a new project now. Great Job! :thumbup: (And thanks again to Irene for starting this :worship: )

You can only run one copy of a normal VI in one memory path at one time. You might try to rename one and run two copies with different names. Another option is to map a network drive letter to your LabVIEW directory and run a second instance of labVIEW from that drive path. That will give you two LabVIEWs, each in it's own protected memory area. Then run your VI copies in the separate LabVIEW instances.

Hi Rocky, Welcome to LAVA. I hope you find the forums both fun and useful. We look forward to learning a little more about you and your company. Best Regards, Mike

Although this can be a bit dangerous, as jpdrolet indicates, if it is defanged and modified, then combined with a few other snippets it could be a pretty useful tidbit. I referenced this thread to the guy over on the Inline subVI thread, then I added ref's to a few other threads. If he puts them all together it could result in something pretty powerful if he codes it well. This is one of the most encouraging things about LAVA to me. Enough people have donated enough snippets that you can search and combine and now come up with answers to a lot of things people ask for that were impossible just a short while ago.

The price looks familiar as well ...

Little bits of lore like this are fun to learn. Amazing the enertia (or is it amber) that surrounds some of these fossilized gems. Your tail of the break reminded me of hearing about how we got the standard distance between railroad rails. Internet rumor says it dates all the way back to Roman chariot wheels. (that internet rumor would be false, by the way, but it evokes tha same "aha!" feeling of having discovered a gem among the junk).