Bryan

I know it's off topic for this thread, but since I mentioned it in here, I figured I'd post an update. I just got notification that I passed the CLAD exam! Woo hoo! I've been using LV since '99, so I should have been looking at CLD, but I took the free CLAD exam at a nearby seminar. I'm just happy that I finally have a bona-fide certification after wanting one for so long.

Sorry guys... I've been out of the loop for a while. On a personal note, I just recently completed Advanced I and II training and am awaiting my results on the CLAD (free at a NI seminar) and will hopefully be taking the CLD before next year.

Thanks for the reply. I did find the VIs you were talking about... however, I was looking for one for LV 7.1. I'm able to save it for a previous version though. Thanks!

I thought I had some encoding/decoding VIs at one time, but can't seem to find them now. I've done countless internet searches of LAVA and other sites and all I found were links that led to nowhere. Does anybody have any base64 encoding/decoding VIs that they would like to share, or could point me to? I'm also looking for some various checksum VIs, but I haven't searched for them yet as they may be more readily available. For some reason I can't get my OpenG commander to work on my work desktop. I don't know if our IT department has locked down programs from accessing the internet or FTP anymore. It used to work, but when I tried to use it today, it wouldn't work.

Well, just as an update, I was able to get the RTE to install and work by using the "ldconfig" command after I installed it to update the shared library links. However, my only problem now is figuring out how to create an image that includes the RTE.

Hello again. I know I've dropped off of the face of the planet for a while. Sorry about that. I'm working on something for a project and have successfully been able to install LabVIEW 7.1 development environment for Linux on a machine running PuppyLinux 3.01. My only problem is that I can't get the RTE to work, although there were no reported errors when I installed it. When I try to run my application from a command prompt, like ./myLinuxLabviewApp . I get the following error: Can't load LabVIEW runtime library /usr/lib/liblvrt.so.7.1 libLVMesaGL.so.3: cannot open shared object file: No such file or directory The files are all there under the /usr/local/lib/LabVIEW-7.1 directory with symbolic links in the /usr/local/lib directory. I don't know enough about linux to find out where it's trying to look for this file.

Well, here's what I've got:I have 3 copies of Developer's Suite (one with Auto Test, the other with Ind. Monitoring/FPGA/RT and a Dev Suite core only) each with their own SN and with 5 "permissions" for each. I also have 1 seat of LV full development. I've been our VLA for almost 3 years now and I never had any training in it and have no idea what I'm doing. I'm trying to create "network installers" as I'm now finding out that I distributed the software incorrectly before. Now, I'm trying to do it correctly, creating network installers for people to use to access their permissions and what not... but I'm confused as to how I'm supposed to distribute them easily. I know how to create an installer, it's straightforward, but since I have 3 copies of Dev Suite, each under their own SN, do I have to create a new installer for EACH software component under their specific SNs? I.e. LabVIEW installer for A12B4567, C89D0123 and E45F6789 (I made up those SNs) and for each copy of LabWindows, etc? Then create file structures with shortcuts that point to each "correct one"? I don't know if any of the above made sense as it's late and I'm tired...I've looked at the online literature and examples and they don't cover the Dev Suites in the VLM very well, let alone multiple Dev Suites in a VLM. Forgot to mention... all of my permissions are computer based.

Is there a section on LAVA for VLM-Related Stuff? I'm currently the NI VLM Admin for our site and I'm just getting around to working on getting things working "properly". I've come up with a lot of questions though since I never had any formal training in VLM Administration and some of the online stuff on the NI website doesn't cover things to the level I'd like. Is there a place in here for this type of stuff (I couldn't find a section that "fit" except maybe LabVIEW General), so I put this in here.

Congrats! Makes me think back to when my son was born. He turned 2 a couple of weeks ago and it's just been a blessing all around. It is too bad that they don't come with instruction manuals. The scariest day of my life was when we strapped him in his car seat for the first time and the nurse waved "bye-bye". My wife and I are actually kicking around the idea of trying again for another one this spring. We're going to shoot for a girl, but of course will be happy with either gender so long as he/she is happy and healthy. Again, congrats and welcome to the toughest job you'll ever love!

QUOTE(TobyD @ Sep 10 2007, 01:35 PM) Makes sense for recruiters, but not for potential candidates where location plays a huge role in whether they're willing to relocate for a job... unless someone's desperately looking for work.

Would you be able to tell us the city/state of this position or any additional details?

Yes, I have that, but I'm one of those "double-click anywhere and start typing"-type person. I guess I'm looking to save myself some mouse clicks.

I'd like to change the font/colors/etc properties of the font text box so that it stands out a little more. Right now, I have to do this by manually changing its properties with the color tool/etc and then copy/paste it wherever I want to add a comment. I'm wondering if there is a config or something in the LabVIEW INI file that will allow me to change the comment properties so that I don't have to manually do it myself everytime I want to add a comment. Anybody know?

If that's the case, than I'm the LabVIEW Architect for my company... and (have been told) the guru. Quite frankly, that scares the chit out of me since compared to most seasoned people in here, I'm pretty much a little ankle-biter.

So, if I understand you correctly, if the other application sets the serial settings and accesses the port, the command line method will then contain the values used/set by the application? Interesting. I'll have to give it a try. UPDATE: You're right! Now the command line returns the correct values. All I need to do is write a function to parse out all of the information. Thanks!

I just tried using the command line approach and the values returned to me don't match the configuration in device manager. i.e. Device Manager = 9600,8,n,1. command line = 1200,7,e,1. I only have one com port on my current machine, so I'm sure I'm accessing the correct one.

Yeah, I've thought of that. I haven't been able to get LabVIEW and other support applications I need to all install on DSL and run in RAM. I have 62+ machines that I'd like to have up and running the same application all at the same time. I don't really want to have to buy 62+ USB sticks to accomplish that task. I'd really just like to get something up so that I can run a LabVIEW executable and install GE's "vmisft" software onto it (since my LabVIEW application depends on it to access the VME bus). Inasmuch as I would like to do this in LabVIEW, I'm afraid I may have to go an alternative route and get some sort of linux-only solution where I have a linux C-application that does the features I'd need, which is essentially to receive, parse, execute and respond to commands I send to the computer over the network. Unfortunately, with my little knowledge of c-programming in Linux, I may have to consult one of our resident Linux gurus for help with this.

I thought this would be an easy one? Nobody has any insight? I can provide add'l information if anybody needs it.

This is in LV8 BTW. It seemed like a simple enough task to do, but it doesn't work how I envisioned. I haven't beat my head over this too much as I have other things going on, but maybe you guys can tell me what I'm missing. We have a computer that has it's serial settings applied by a completely different application (non LV or NI). What I want to do is read those serial settings into LabVIEW for use in one of our verification applications. Sounds simple enough, right? When I look at say, the COM1 settings under device manager, I see certain settings. When I try to read those settings into LabVIEW using the NI VISA resource name and property node, I get the typical default values (9600,8,N,1). Then, I'll open MAX and it will show a port settings conflict. I'm not a VISA guru by any means and this is the only way I currently know of to access a serial port in LabVIEW and it's always worked fine for me, but I've never used it in this manner before. Is it possible to see the "Windows" settings from NI VISA to read into LabVIEW, or do I have to look at a different route? For those curious, our LabVIEW application runs a hardware verification on the system and checks for communication over the serial ports. The other application that's supposed to run on the system sets the values, which are different per system (and we have 60+ systems to check). Whenever we wrote our verification application,we weren't told what the settings were SUPPOSED to be, so our application has always used the defaults just to check for communication. But, when we run our application, it changes the settings in VISA and seems to be affecting the windows settings to the point where when we finish our verification and start the other application, it generates errors. At least, I THINK that this is what's causing the errors. I just figured it better (and the easiest way to remedy the problem) to just read in what the other application set the com port settings to, then use that for our verification so that we don't see the problem anymore. Maybe this is something easy and I'm missing something simple. I've been working 8pm to 6am for the past couple of weeks and my brain isn't running at peak performance.

QUOTE(LV Punk @ May 9 2007, 06:30 AM) Welcome to the club. They haven't banned YouTube where I work yet, but I'm sure it's on the way. It's funny though, most (respectable) employees are responsible with their non work-related internet surfing. I don't think the "powers that be" understand that by closing a sometimes much needed avenue for distraction, or stress relief only coerces employees to find other ways to seek the occasional much needed escape. That, or they just become stressed out. One of my favorite "demotivational poster" quotes: "Pressure - It can turn a lump of coal into a flawless diamond, or a good employee into a perfect basketcase."

What if one wanted to use the parallel port on a computer anyway to save money, or for a home project or something of the like? I've thought of doing something like that just to do it. It would be cool (or IS cool if it already has been done) for someone to write a LabVIEW driver for the parallel port. I know I'm risking someone saying "Cool! How 'bout you do that?" (it happens a LOT here at work), but it would be something neat for people interested in creating something for a home project or in case someone just is set on using a parallel port anyway.

I'm not familiar with using BootROM or any type of network image booting, so I'll have to read up on it. All of my linux stuff I'm pretty much learning as I go. Would this require me to permanently change things in the BIOS? I'm assuming it would as I would have to somehow tell the computer not to use the image on it's local drive at boot, which would require me to go into each computer's BIOS and force it to look for a network image instead of using the installed local image. My intent is to disturb the hardware/firmware the least amount possible. This would be done on equipment for a military contract and thier configuration control is very strict. If I change anything it may have to go through a documentation and possibly an approval process. The software engineering group boots from a USB device on these units frequently, I'm essentially going in through the same method as they do, but with different software and a different USB device.

Okay, here's our setup. I'm working with a VME-based system. It has a single board computer with no OS on it. It's essentially a dumb VME setup with a computer and some I/O and communication cards. My task is to have an automated test that exercises the cards to verify their functionality, signals, etc. I can't install anything to the computers since they will later have a home-grown and condensed Linux OS on them (all text, no GUI which runs headless) that loads from the 512MB flash HDD and runs in the 512MB to 1GB RAM memory. Sometimes the linux software is already installed and I don't want to touch, change or otherwise affect what's on the on board hard drive. Right now I have a USB HDD running Mandrake 10.1, LabVIEW 7.1 for Linux along with some other softawre to give me accessibility to the VME cards. The only problem is that I can only run it on one setup at a time and I can have anywhere from 1 to 62+ to check at a time, but I only have one drive and the drive needs to be mounted while the computer is running. The program that I'm running on it acts as a server, allowing me to manipulate and read the signals from another computer on the same network. If I can get multiple computers up and going with the same software, I can verify more than one at a time from a central location. When I'm done, I want to be able to restart the computers and allow them to run off of their own hard drives again. Essentially, my sofware is not intended to be permanently installed on the computers. The use of a text-only OS prevents that anyway. I only want to load/use my LabVIEW stuff when I need to test the system. I wrote this quickly, let me know if it doesn't make sense.

I'd definitely be interested in a "How To" if you want to post one. I'm still looking for a Load into/run from RAM solution, but it's for a future project. My current project is just running off of a USB HDD and doesn't run completely in RAM and I'm not pressed right now for the RAM solution.

A Software Engineering Approach to LabVIEW I personally liked this one and still reference it. Although I don't believe it covers LV8.0+, it has some good techniques and info that I've made standard in my programming.