Chris Davis

To late, as of LV 7, or 7.1, and IMAQ 7. The vision wire was purple. Looks just like a string, except purple. :thumbup:

Lets not go there... :thumbdown:

My wife was also disapointed that I didn't know it was Whitney Houston. Perhaps I was still in shock from the heavy caramel...

Sorry, I was thinking of Dancin on the Ceiling...

Thanks :thumbup:

:laugh: :laugh: :laugh: :laugh: :laugh: Scary man, Scary... I mean any time you can work in Lionel Richie into a short film, you've got it made...

Sorry to hijack the thread for a moment, but was this work related to LV Embedded, or some other project?

You should take a look at the IMAQ also known as the Vision Development Module to do this task. You could also check out IVision, or the C code its based on OpenCV. If you decide to use IMAQ or IVision and run into trouble, you can post again with code samples / snapshots and we can try to help you more then. If you decide to use OpenCV it has its own forum to ask questions.

Is there a work around for this issue. I have beta 7 of the OpenG Builder and LV 8.2

I think you are out of luck with seeing the subvi's front panel in design mode in a subpanel. From what I understand you can edit the subVI at will, but not while it is "in" the subpanel. I also think you could run two subVI's in two subpanels, using parallel loops. You'll have to post something you've tried to get a whole lot more help... right now we can only speculate on what you are doing.

OHH the Humanity... How did you ever survive?

NewEgg's whole Mini-itx collection to save a little time check out this as a possibility, or this. I'm still curious as to what (computer) hardware Mike's using... Its not mentioned in his blog.

You don't mention the computer you are using, but I would think that something like this might work. Low noise because its all passive heat sinks..

care to share some system specifications for your media center / arcade setup. Of course pictures would help to visualize the setup as well. I don't have this setup (yet) but I have looked at doing it many times...

I think aspect of Vision Builder you are thinking about is its LabView code generation. I think this is doesn't work if one doesn't have LabView installed alongside Vision Builder. I haven't used Vision Builder in a long time, so I'm not an expert on it.

I haven't used the VIs you are looking at, but you might read through this post to see if you want to look at this solution as another way of accomplishing the same task. I have downloaded this VI, but I haven't tried it yet, so YMMV. :thumbup:

Its all printed right there on the page, if you can read it. Do you have one of these devices and want to learn how to communicate with it?

The casual user might be detered by changing the extension from an easily open file type. You mention that one is an XML file, but you could always rename it something like .mysettings or even hide them using the operating system's hiding capabilities ( assuming that the user hasn't turned that option off! ) Chris

Ah...Windows 3.11 those were the days...

I don't know where these people are getting new computers with parallel ports. Most of the ones I'm getting now don't even have this anymore.

Its a wonder that consuming more :beer: wasn't in the blog. But it does fit, if you want to get better at consuming more :beer: you simply have to keep practicing! :thumbup:

I thought of a possible solution to this problem last night. If the traditional DAQ vis were packaged as an openG package, you would have the ability to install them in any version of LabView that they could run. If it is as simple as copying the files from the 8.2 directory to the 7.x or 8.0 directories, an openG package would be easy. I don't use traditional DAQ (anymore), but I would be willing to help with this process. The only problem I can think of with this situation would be an NI Liscense agreement issue. What do you think? Chris

I too scan the digest version, as I have for several years now. That usually means I don't contribute very often, and I was ok with that. But I find myself better able to track and keep track of information with LAVA, and have started spending most of my time here as a result. I think info-labview will continue to exist, as it has for years, but I believe that many posts and posters will find thier home here at LAVA.

You are in luck, I believe our forum administrator and one of our most active members are located in the bay area.

I agree here. I believe it was Stephen Mercer that stated that we should think of changes and improvements to LVOOP to happen in years, not months. I think a few people are using LVOOP, and this is one of the places you get a lot of discussion on the topic. Anyway, I believe that by reference OOP is needed, but I also believe that we can do without for right now. As jimi has already mentioned in other places, NI has some other bugs (classes with more than 10 get/set VIs, etc.)to work out before new features start getting added. I also agree with jimi, that, for the most part, the implimentation of the by reference design should be hidden from the programmer / user. I also know, from experience, that to make something good, easy to use, and close to perfect is not as easy as it sounds... Discussion on this topic is good, and it provides a good resource for NI to use in the future. :thumbup: