-
Posts
381 -
Joined
-
Last visited
-
Days Won
16
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Bryan
-
Just a little update. We were to the doctor yesterday. She said that my wife is 8 weeks along and everything appears fine. I got my first view of our baby and it was a humbling experience seeing it and it's little 160bpm heart going a mile a minute. Here's a picture of the ultrasound:
-
I believe you can also do it through a command prompt if you want a little safer method of doing this, but I forget what the command is, it shouldn't be too hard to find though.
-
Well, since I'm the one answering my own Linux-specific posts, I guess you could say that I'm the resident Linux LabVIEW expert? Haha! Anyway, I found out that it was an issue with 2 environment variables not being set. VXIPNPPATH=/usr/[path to directory containing vxipnp]/vxipnpLD_LIBRARY_PATH=$VXIPNPPATH/binexport VXIPNPPATH LD_LIBRARY_PATH It varies I guess with what flavor of linux you're running, but with what I'm using, listed in the first post, I had to enter these variables in the /etc/profile file.
-
I'm kind of in a hurry to get this problem resolved, so if anybody has any leads, I'd really like to know. I've already changed permissions on the ports, and tried to run "visaconf", but it just returns an error "0xBFFF0000" Anybody? Bueller...? Bueller...?
-
I'm trying to access the COM ports on a computer running Fedora Core 2 Kernel version 2.6.5-1.358 and LabVIEW for Linux 7.1. The VISA controls don't show any COM ports available and there are 2 of them on the computer itself. Being new to Linux, I don't know anything about accessing COM ports through Linux, most of the information I've been finding online is C-oriented and hasn't been helpful in communicating with them from LabVIEW. I'd like to somehow make sure that the OS even sees the COM ports, if it doesn't, I have to find out why and how to talk to them through LabVIEW. Any help is appreciated!
-
Well, I just found out this weekend that I might be a daddy. It has yet to be confirmed by a doctor, but all of the symptoms are there and the home test was positive! We're thrilled, but at the same time, as normal, I'm scared. A new chapter in my life has begun and I'm hoping I can do my part and do it well.
-
transforming vi into .exe file
Bryan replied to Dniz's topic in Application Builder, Installers and code distribution
In order to build a windows application, you need to acquire a copy of LabVIEW Application Builder from National Instruments for your version of LabVIEW ($600 ish or so?). Also, computers that will be running your EXE version of software will have to have the appropriate version of the LabVIEW Run Time Engine installed. -
We just finished installing LabVIEW 7.1 on Fedora 2 and 3 and came across an interesting issue that would allow us to install LabVIEW but not run it (the splash window would open, then pause, freeze and close). Turns out that Fedora 2+ uses a filesystem convention that doesn't have "." and ".." as the first two directories. Apparently LabVIEW depends on this. To get LabVIEW to run on Fedora 2+ log in as "root" and execute the following code in your shell for all EXT3 partitions: tune2fs -O ^dir_index /dev/(yourPartition) I'm running Fedora 2 installed on a USB hard drive with (2) EXT3 formatted partitions, so mine was: tune2fs -O ^dir_index /dev/sda1tune2fs -O ^dir_index /dev/sda2 You should be able to immediately run LabVIEW afterwards.
-
Thanks for the info! I remember seeing that before but forgot about it. I see that the only stipulation is that you have to replace the VI in memory with one of the same name. It would be neat if I could do that even with subVIs that are not the same name, but I guess that's kind of a mundane detail unless one's forced to adhere to strict naming conventions and is in a situation where using a different VI of the same name is not acceptable.
-
I've had situations where I've wanted to replace multiple instances of a subVI in a block diagram by finding each one, right clicking on it, going to "REPLACE" and replacing each one with the same new VI. It would be neat if, along with the current "Find" function, that you had the option of replacing multiple instances of a function with a new one similar to how you would use Find/Replace in notepad to find and replace text, or a hybrid of LabVIEW's separate "Find" and "Replace" features if you will. Of course, my "wish" is geared primarily toward user-created VIs, but I suppose being able to do it with the provided LabVIEW functions would be helpful as well.
-
.. or should I say the ability to use them in path controls. I.e. for windows NT machines entering "%SystemRoot%" in a path variable would return "C:\WINNT" at runtime.
-
You can use a property node for a VI class and select the "Front Panel Window >> State". I don't remember, but I think LV6.1 has this function.
-
Nice trollish first post. :thumbdown: If you're using LV7, and it's crashing, it sounds to me like poor or inefficient programming style may be to blame which may have lead a memory leak or massive use of memory somewhere (i.e. unknowingly building massive arrays inside of a loop). I've been using LabVIEW for 5 years, and the only version I've ever used that sometimes crashed was LV5.1 when running NT4.0. I would suggest that you either take a look at your own programming ability/style, maybe read up a little on LabVIEW and look at what you yourself could have done wrong before pointing the blame at someone else. Who was it that had in their signature something to the nature of: "Software Development is a race between software developers creating more idiot-proof programs, and the universe creating more idiots"?
-
By what delimitation are you trying to split the string? Are you trying to break it up into pieces by finding spaces, commas, etc? If you're trying to do the above, you can use the "Spreadsheet to Array" function which will provide an array of each "piece" of your string that's separated by a character (i.e. comma, space, tab, etc). Or use the "Scan from String" function.
-
Has anybody programmatically changed a computer's IP Address using LabVIEW? I'm in a situation where I will have a LabVIEW App running on a computer having a few ethernet adapters. What I would like to do is somehow identify the adapters and programmatically set the ip addresses and subnet masks of each adapter and apply the settings without having to reboot. Sort of like how you can change the IP and implement the changes manually by viewing local area connection properties. Extra tidbit of info: we're going to be using W2k/XP machines. I'm thinking it's probably going to be a register-level implementation, which we would like to try to avoid. If anybody is able to at least point me in the general direction, I would greatly appreciate it.
-
Remember, aside from the application that YOU built, the installer creates files that actually perform and install your application and parts/shortcuts/etc onto the target computer(s). I'm not an installer guru by any means, so I don't know how much it SHOULD take up, but the idea that your built application + installer is larger than your application alone just makes sense to me.
-
What the best way to make and animated ID Icon
Bryan replied to Mark Balla's topic in User Interface
You can create them with Adobe Imageready too, but the Adobe packages cost mucho dinero. You could also do a search on shareware or on sourceforge for something like that. That's normally how I find things anymore. -
... I'm working on MY LAVA shirt...
-
After your talk about backdoors and easter eggs, I thought you had read that book because they're mentioned in there. I had done a very simple one that popped up a comical error message when a particular user logged in. Back at the time I didn't know they were called "easter eggs" until I read that book.
-
I would definitely check with your management as far as easter eggs are concerned. If it's something that would contribute to the use of system resources, you might want to rethink it. Back doors, depending on what type of software you're running can be a good things often times for support and troubleshooting. I've done easter eggs in the past on applications that stay in-house. I have yet to create a back door in anything I've written. You just got done reading Digital Fortress didn't you? yaorouseveethncs wecgewhyaaiortnu (<-- If you read the book, you'll get that)
-
Application builder has provisions for using a custom icon file (*.ico) for your built EXEs. To build these "*.ico" files, one would have to have a program capable of providing such files. It would be neat to have Application builder automatically use the top level VI's icon as the icon for the exe, OR have a utility built into LabVIEW that allows you to create your own custom EXE icon.
-
I believe you should be using a property node to set the control value. It sounds to me like you're not passing the correct (if any) control reference to the node, or you don't have it linked to the desired control. You can get a control reference by right-clicking on a control, and going to CREATE >> REFERENCE. Then using that reference with a property node to set/get control values. Additionally, you can right click and CREATE >> PROPERTY NODE which essentially creates one that's already linked to the control reference. The only way I see you needing to use the first method is if you're passing the control reference to a subroutine.
-
http://forums.lavausergroup.org/index.php?showtopic=605