Chris Davis

QUOTE(Jim Kring @ Sep 10 2007, 06:43 PM)

set

spike!

QUOTE(jlokanis @ Aug 29 2007, 12:43 PM)

I am trying to build an application with the OpenG builder that includes this function and discovered that the OpenG builder cannot deal with lvlib files properly. Since my application is dependent on the namespace feature of the OpenG builder, my only option is to reinvent this math function myself outside of a lvlib.[/font][/size]

I'm using the built in formula parser with the OpenG Builder inside of an LLB with name mangling (adding a prefix specifically) and its working fine. I'm using builder beta 7 in LabView 8.2. I did have trouble with beta 8 when I beta tested it, so I switched back to beta 7. If I remember right, the OpenG Builder beta 7 doesn't actually name mangle files inside a lvlib, but my application was ok with that.

QUOTE(torekp @ Aug 29 2007, 06:59 AM)

But this means I'd have to start using source code control - probably a desperately needed idea even without this side-benefit...

It really is worth it. As a side benefit, everything that you source code control can usually be backed up with calls to the source code control program. For SVN you can use the concept of a "hot copy" to back up all of the data in your source code control repository to another path.

QUOTE(Michael_Aivaliotis @ Aug 26 2007, 07:06 PM)

That's it? Not nearly often enough in my opinion.

And your suggestion would be? I've been avoiding more freqent gatherings because of topic scarcity and the lack of people who are willing to present.

QUOTE(Michael_Aivaliotis @ Aug 24 2007, 06:42 PM)

Question, how do all of you perform testing on your LabVIEW VI's?

For my whole applications I've started using AutoIt to script user functions. I'm still working on a test suite for the whole VI hierarchy.

I started a NI user group for my company just like what you are asking about. We meet once every six months, and we have a 20 minute presentation by one of the members of the user group on a recent project involving LabView and/or CVI. We've been going for 2 1/2 years now and its been worthwhile. We have had 12 to 17 people attend these group meetings so far, and our local NI rep has been gracious enough to provide lunch for the group in exchange for getting to present for 10 minutes on the latest NI product / software he thinks our group might find interesting. We then eat for 30 - 45 minutes and everyone goes back to thier office. I think we could meet more often, but twice a year keeps the pressure to find something to present about to a minimum. I think its worth it, if only to get a chance to meet others in your company who are using LabView.

QUOTE(yen @ Aug 17 2007, 09:24 AM)

Great trick. :thumbup:

But where did you find a Pentium II?

1997?

Its probably what Norm surfs the web and checks his email on!

QUOTE(crelf @ Jul 26 2007, 02:01 PM)

Can you get a big box of those neat little NI screwdrivers? Although I'm not sure the winner will be able to take those on as cabin luggage...

I think one (or more) of http://forums.lavag.org/index.php?showtopic=2777&view=findpost&p=28367' target="_blank">these would be great prizes...

QUOTE(Aristos Queue @ Jul 20 2007, 02:42 PM)

Does anyone have a standalone DLL that has a function which, given a memory address, returns the byte, word or int at that memory address? It would be useful for a hack I'm contemplating, and I don't feel like coding a DLL for a one-off project.

IMAQ Mempeek should do what you want, or you can check this thread to find other ways.

QUOTE(Michael_Aivaliotis @ Jun 23 2007, 07:31 PM)

I don't think you have a choice.

He may or may not have a choice. If you download the NI-CAN installer from NI's website, and unzip it, but not install it you would be able to see all of the MSI packages it installs. This would let you pick out just the NI CAN MSI package. You would then have to provide this MSI file with the installer, and install it manually for the user after your program has installed. This may, or may not work in your situation, since I've never used NI-CAN I can't really say if you have to have MAX for it to be useful.

QUOTE(gbugnard @ Jun 19 2007, 06:36 AM)

I am looking for a image acquisition system in LabView. I would like to use a FireWire camera. My question is the following: can I directly plug the camera in the built-in FireWire port of the computer, or do I have to buy one of those NI-FireWire PCI card? Will the camera be recognized by the system?

You can do image acquisition on a firewire camer without NI's firewire card, but you will still have to buy a liscense to http://sine.ni.com/nips/cds/view/p/lang/en/nid/12892' target="_blank">NI-IMAQdx to be able to do the acquisition with native NI Vision tools.

QUOTE(PaulG. @ May 30 2007, 10:42 AM)

What version control software seems to work the best with LV? Does NI have any plans to develop their own? Does the industry seem to have a favorite?

I believe they use Perforce, NI did have their own source code control software, and dropped it after LabVIEW 7.1. I don't know if the industry has a favorite, but I do. SubVersion.

What about the meaning of life? Or at least the meaning of alfa...

QUOTE(jaegen @ May 29 2007, 05:34 PM)

Well, since I'm an NI-Week rookie, I figured I'd tap the LAVA brain trust before picking a hotel. Does anyone have strong feelings about a particular hotel?

Thanks,

Jaegen

I stay at the Radisson, its within walking distance and it falls within my companies per diem. I've stayed there twice, in 2003 and 2005. I also hear that the OMNI is nice.

QUOTE(ars_stowers @ May 29 2007, 05:59 PM)

3) Copy Executable to local drive, run, and get following message: "LabVIEW: An input parameter is invalid. The file " is not a valid LabVIEW file."

...

This is my first big project and builds are taking over an hour which is driving me crazy! I know most of you probably work on projects that require overnight builds and such, but for me long build time = frustrating. I shouldn't complain though because I'm sure the time is proportional to how bad (ie: spaghetti coded) my project is. Sorry for slipping off topic here.

Are you, by chance missing a file that your LabView EXE needs to run? Builder puts files that are needed for execution (such as DLLs and / or CINs) into a RSRC folder with the exe.

I've got big projects (300 - 500 vis) that I compile with Builder and havn't ever had a build time that long. Which leads me to my next suggestion. Have you tried performing your build after a clean restart of LabView? I'm currently experiencing an issue with Builder where I seem to have found a memory leak, but it has to do with building LLB files with VIs from vi.lib and user.lib. I haven't gotten to the bottom of it, but it doesn't seem to affect building an exe, from what I can tell.

Are you experiencing a long save time? Building an exe in LabView requires re-saving your code to a new place, so if saving your code takes a long time this would contribute to your build slowdown. Have you tried building your exe on your local hard drive? It might let you know what is missing from your network build copied to a local drive...

QUOTE(Michael_Aivaliotis @ May 21 2007, 02:02 AM)

Question for you. How are the additional msi files included? Are they a post or pre install task? Also, upon an upgrade, what happens when the additional msi gets called again? Do you get the repair, or uninstall dialog for the msi?

With NSIS you get the same amount of control as you would get if you ran the msi file from the command line. I usually copy the msi file to the target directory/install directory, run it from there, either silently or with user interaction if it can't be run silently. So, if the user already has a newer or the same version of the software you want to install, they would get the restore dialog instead of the install dialog.

QUOTE(kunal227 @ May 22 2007, 02:14 AM)

i want to use fp-1000(network module), fp-tc-120(i/o module) and fp-tb-3(terminal base) for temperature measurement using t-type thermocouples. i also want to use omega omb-tempscan 1000 to the same job because of large no of thermocouples and thats the hardware i have available in the lab.

I don't know anything about the omega tempscan 1000's, but the fieldpoints are pretty easy to work with. If you can see and talk to the module in MAX then there are many many example of how to read a temperature from your tc-120's in LabView. The biggest part of Fieldpoint reading is getting the setup right. I've never used a fp1000, only cFP 180x and other cFP modules. These are ethernet based, and pretty easy to deal with once you have all the software installed to talk to them.

Welcome to lava and good luck!

while it is true that the full install is 90 mb zipped, you may want to look at all of the msi files that are packaged together in the default runtime engine to see if you can weed out what you want. i.e. the LabView 8.2.1 runtime engine itself is only 25 MB (acceptable by your standards) and it may serve your needs.

After all for a MS Office add on you probably don't need TDMS support, data socket support, etc. You'll have to play around with what gets installed, but if you try you may find everything you need for less than the 20ish MB.

QUOTE(Michael_Aivaliotis @ May 16 2007, 07:57 PM)

So it turns out that the best way to resolve this is to uninstall ALL drivers and install the one I want before the build. Does anyone else see problems with this methodology? I mean, let's say for instance that you are supporting multiple projects with differnet driver version requirements. What then? If anyone's gone down this path, do you have any suggestions?

As I've stated in other threads, I use http://nsis.sourceforge.net/Main_Page' target="_blank">NSIS and have been pleased. You can include the specific runtime as well as fieldpoint / daqmx / vision installers and compile it all into one (compressed) exe. I know its not the NI version, but when using the OpenG Builder, I usually give myself the option to build the installer (NSIS can be called from the command line) in a post-build vi.

QUOTE(crelf @ May 12 2007, 05:28 PM)

Great idea - who's up creating the page?

http://wiki.lavag.org/index.php/Block_Diagram_Images' target="_blank">Here you go

BTW, the process of capturing the images could be scripted and creating a simple wiki page could be scripted, but the uploading could not. Michael, is there any way to upload a lot of images at one time?

QUOTE(JodyK @ May 10 2007, 01:23 PM)

Is it possible to make it install DAQmx without the user having to select options etc? Also is there anyway to use it with the smaller Runtime DAQmx installs?

I've used NSIS to install the runtime engine, but never DAQmx. Although I'm sure it is possible. My co-worker recently used NSIS to install FieldPoint, but simply used NSIS to copy the FieldPoint zip file that is downloadable from NI, then call thier installer. It isn't a silent install, but that may be enough for you here, I don't know.

QUOTE(Mike Ashe @ May 10 2007, 08:03 AM)

Possibilities, possibilities ...

How do you propose to convey the desired information without wires?

What would really be great, is if there was a LabVIEW installation in a dedicated editor (with button on the compose post page, just like inserting a picture or link) on the web, that we could do the quick diagram on, etc, then hit a "publish" button, and it would be inserted into the LAVA post.

You have this option, but it is probably more than most people want to wait for. I agree the LabView related emoticons might help some people understand a text based explanation of LabView. I don't know if Mike can add them or not, but I don't think he's added the emoticons from this page yet, so it may not be possible...

QUOTE(crelf @ May 7 2007, 07:50 AM)

That's an excellent idea: are you volunteering? I'm a bit busy writting the http://wiki.lavag.org/index.php/Custom_LabVIEW_configuration_file' target="_blank">Custom_LabVIEW_configuration_file wiki at the moment, and if anyone has a spare ten minutes, I agree that this thread could be an inpotant wiki article...

I'll work on it, although I'm not quite sure how to start a new wiki article, I've just edited one that already existed. Guess I'll have to learn.

QUOTE(JodyK @ May 7 2007, 03:46 PM)

For some reason even though he has the same version number of max, the devices were connected differently. I am including a screenshot of his system and one of mine to demonstrate. In his the USB devices showed up somehow related to VISA in mine they are USB devices.

I had this problem with the 6009 as well, but it was because I had used it with DAQmx base at first. http://digital.ni.com/public.nsf/allkb/634CEF92DEC749CB8625703800708FC5' target="_blank">This link might clear up the problem.

QUOTE

I use the install DAQmx by CD or download method as well. I have used the NI installer in the past around LV7, but quit after I found NSIS and was able to understand it and use it for my installs.

Chris,

I don't know if you meant to post this in the lounge, it sounds like a response to a different thread. I personally think this topic might make a good wiki article. I'm sure you'll get lots of responses so I'll throw my two cents in too.

Upgrading versions of software, LabView or any other software, is a time consuming thing. It should never be done in or around "crunch" time. Having a source code control system is a must to make the process of falling back to an older revision easier. Use a virtual operating system to test out your "this upgrade is a piece-of-cake/walk-in-the-park/5-minute-job" theroy.

Finally, my rules to upgrading new software

1. Backup

2. Backup

3. Backup

If all else fails, remember to use your backups.