Jordan Kuehn

Unless you are on a cruise ship, there's not much south of Texas.

http://joule.ni.com/nidu/cds/view/p/id/2127/lang/en I'm not familiar with the differences between windows drivers and mac drivers. If you experience problems I would suggest running in windows. Though NI probably wouldn't love that suggestion

http://joule.ni.com/nidu/cds/view/p/id/2337/lang/en

congrats!

Good map. Thanks for putting it together. Last year I really enjoyed the dueling piano bar you have on there.

Well here's a cheap solution: http://www.sparkfun.com/products/10812 I know its for windows, but I would imagine you already have some sort of software that lets you run windows as well.

I'll put it on my calendar. See you then.

I've read your whitepaper and I like your approach in general. Have you released this code for public use or is it proprietary? You can pm me if it's going to derail this forum thread.

I took the CLAD in 2009 and there wasn't anything regarding these topics. Perhaps they have changed it since you took it? I was working for NI at the time and had a pretty good grasp of what would be on the exam

very nice. one suggestion. perhaps a most downloaded section in addition to the rest?

the problem is that the UI code exists within the SubVIs. I will be pumping data into them in a producer-consumer fashion, but need to get User Interface events from them. Ok. That's what I was hoping to avoid, but I can make that work.

Here's possibly a simple question. I'd like to have a main program that launches subvis which provide the main UI. I don't want the subVIs to handle events though, I want the single controlling process to get the events and handle them. Is there an easy way to do this, or will I have to create custom user events for every single one I want using control references?

I've recently switched to Mercurial (Hg) from SVN and have found that I like it better. One nice thing is not having to export the files to avoid copying all the .svn files created with subversion.

Agreed. It seems to only work well when the only object in the pane is a graph or chart.

durnek60: I think the first thing that would come to my mind would be the second approach you have taken, gathering the data from the registry. I have not spent any time with the dll files and cannot help much with those. I'll think about it and see if another approach comes to mind.

On an unrelated note, what is your end application? It appears to me that you are having trouble getting the ueye drivers to work in LabVIEW. I have done this for use with an Edmund Optics camera and there were a few subtleties I discovered. If this information would be relevant to you, just let me know and I'll explain here in the forum.

Then it's not unfair, it's just a flawed game.

Perhaps this will be of some help. Also, your snippet fails to open it on my Win 7 Pro machine.

From the comments on the site:

I like the windows 7 style, but to each his own.

no problem. glad I could help!

It varies a bit from OS to OS, but it's something along the lines of this (Windows 7). Right click Computer -> Properties -> Advanced System Settings -> Advanced Tab -> Environment Variables... Then you are presented with user variables and system variables that you can modify all you want.

Perhaps, but I think in this case it would be about as unlikely as the user having tabbed several times, hit enter, and did it again. That button hasn't been used for quite some time. And perhaps the value change event structure could capture double click events in a similar fashion to how windows does it? Then it could be a boolean input into the case.

essentially I found the GET and POST commands sent by the web interface and then mimicked them in LabVIEW. You'll need to get familiar with the HTTP functions in LabVIEW as well as basic string parsing, type conversion, loops, and conditional structures.

I would start with a packet sniffer. You will probably have to develop/replicate the http interface. I've used Wireshark before to see what commands were used to interface with an unsupported IP camera.