Yair

QUOTE (neB @ May 28 2008, 08:03 PM) Just look at the picture. It clearly is an older version. My guess would be 6.0 or earlier. As for the Project menu item, that's easy - it has nothing to do with the current project concept. Ever wonder why you have to put VIs in the "Project" folder to make them appear in the Tools menu? That is why - backward compatibility. As for different wires crossing each other, that was my initial guess, but it doesn't fly - when wires cross in newer versions they always have a boundary.

QUOTE (Michael_Aivaliotis @ May 28 2008, 07:47 PM) I was refering to this: QUOTE (Yen @ May 28 2008, 07:29 PM) My guess would be using an old version of LabVIEW (as can be seen by the toolbar) which does not prevent this.

What about the guess which was hiding under the diagram?

Nice one, Michael... How about this one: QUOTE (Michael_Aivaliotis @ May 28 2008, 07:02 PM) My guess would be using an old version of LabVIEW (as can be seen by the toolbar) which does not prevent this.

Since you're running on a cRIO, the issue might be the overhead of dealing with variants, but I saw that using the OpenG VIs (on a PC) without the NI VIs caused huge performance improvements. If you want, you can modify that or the MGI VIs to use the OpenG format, but my quick look into it showed that it might require a couple of days of work to get right with all the differences.

QUOTE (Michael_Aivaliotis @ May 27 2008, 12:24 PM) Ahh, Vivaldi... :thumbup:

The Express>>Signal Manipulation palette has a From DDT VI which will allow you to convert the DDT data to a 2D DBL array, which you can then write to a spreadsheet file using the Write to Spreadsheet File VI from the file palette.

QUOTE (crelf @ May 26 2008, 04:10 PM) I think you're judging too fast. Even if it was a HH (which I'm guessing it isn't), the question is perfectly legitimate and formed properly.

QUOTE (Michael_Aivaliotis @ May 26 2008, 09:19 AM) That's not Mars! It's in Nevada!

Oooh, leet! D'oh!

Cross-post. It's considered polite to link when cross posting. As mentioned in the other thread, without code, you probably won't get much.

QUOTE (jgcode @ May 25 2008, 04:30 AM) Yes. I was refering to http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=270051#M270051' target="_blank">this post, which should work around the issue you mentioned and save your users a click.

It looks like the Value Change event for a color box is fired twice even in the current beta. I'll report it. Here's a much more simplified example (8.0).

I don't think there is anything left to say other than thank you and keep it up. You already know how valuable your contribution is.

QUOTE (Justin Goeres @ May 24 2008, 07:19 AM) I didn't recognize almost any of them, so I would say that means you should be ashamed :laugh: . Actually, I think it just shows that in any culture you will have creations which become highly popular, sometimes even if they're not very good. By the way, I personally think this video is great.

QUOTE (jgcode @ May 23 2008, 12:47 PM) Well, I was about to point to that thread because I did post an example there of how to use the native LabVIEW palette. Of course, I don't think there is any way to get it to work nicely with the native context menus, but there are other options.

QUOTE (Gary Rubin @ May 22 2008, 10:10 PM) Nah, that guy can barely get to the 4th dimension...

QUOTE (TobyD @ May 22 2008, 07:15 PM) Or you can use the http://forums.ni.com/ni/board/message?board.id=170&message.id=260737' target="_blank">resize dialog:

Thanks for the responses. It might be a while before this actually happens, but I'll try to remember to post an update. P.S. Welcome, Matt.

QUOTE (orko @ May 21 2008, 11:11 PM) No, sorry. I think they used to have them, but I can't find them now.

You might wish to go over some of these tutorials.

Thanks for the replies. The approach suggested by Chris and Mikael might be good. Mikael, what kind of update rate can you get from that camera? I'm still fuzzy on all the details of the specific project, but my understanding was that the gauges are in fixed locations and can't be moved. A further detail I obtained today is that at least some of those gauges are small (about an inch in diameter). Do the cheap cameras have the ability to see details of this size with reasonable quality (assuming of course you have proper lighting and place them close)? Another thing I learned is that $500 might not be too much, so I might go with GigE. Neville, is the 5-10% CPU usage a constant overhead or will it happen for each camera? If I have 20 cameras, each taking 5-10% CPU, I'll probably have to do some synchronizing. I'm hoping that at least most of the gauges don't have to be read more often than once a second, so I may not have a problem there. QUOTE (crelf @ May 21 2008, 04:51 PM) As long as it's in a known format and is served.

You can also try looking on eBay, but if you just want to look at the source code, you can download a fully functional evaluation version from NI's site which works for 30 days. I believe that if you look around their FTP server you should find versions going as far back as 7.0, but you might find only the latest.

QUOTE (crelf @ May 20 2008, 08:52 PM) I didn't realize FW can be split effectively and in any case it requires specific hardware, while any decent computer anywhere has an Ethernet port. Regardless, IP based systems are extremely easy to set up, extend and modify using existing infrastructure. By "cheap" I mean "as cheap as possible". It doesn't have to be the ~$10-20 you pay for USB webcams, but I wouldn't expect a $500 price tag for each camera either, since the requirements don't call for something uber-powerful. I will look into FW and AVT, thanks. Any other suggestions?