Swinders

I've used an ARM based board called Forebrain which is relatively cheap (about $44) and uses a 32bit ARM Cortex-M3 microcontroller clocked at 72MHz. To program I've used YAGARTO which is an open source tool chain based on GNU ARM for Windows and it seem to work well.

We have used Perforce for a few years and have our workspace as the whole D drive. Our PC's have their hard drives partitioned as a C drive for windows and applications and D drive for the user data. LabVIEW is installed in D:\Program Files and our user areas in D:\Documents and Settings\User\My Documents\LabVIEW. The decision to use the entire D drive was based on the need to include the user.lib and instr.lib (we have written our own custom instrument drivers) folders in the Perforce depot. This does not mean that the entire D drive is held under Perforce, what we do is set the View to target folders in the Perforce Depot to our workspaces. An example of our view settings would be: //depot/... "//workspace/Documents and Settings/user/My Documents/LabVIEW/..." "-//depot/LV 2009/..." "//workspace/Documents and Settings/user/My Documents/LabVIEW/LV 2009/..." "//depot/LV 2009/..." "//workspace/Program Files/National Instruments/LabVIEW 2009/..." "-//depot/Requirements documents/..." "//workspace/Documents and Settings/user/My Documents/LabVIEW/Requirements documents/..." "//depot/Requirements documents/..." "//workspace/Documents and Settings/user/My Documents/Requirements Documents/..." This targets the entire depot to the LabVIEW folder in My Documents but removes the "LabVIEW 2009 folder" and targets this to the LabVIEW programs folder. We also have a "Requirements Documents" folder that is targeted to our My Documents Folder. Our original thought was to hold the instr.lib and user.lib folders in a separate workspace but LabVIEW can not handle more than one workspace so it proved to be difficult to keep everything in sync.

Well done guy's. Got my CLA results back last week and I PASSED! It was a recertification but seemed much worse the second time around.

Could you use an UNC path of the form \\ComputerName\SharedFolder\Resource Something like: \\192.168.1.1\LabVIEW\temp.txt

We have been having some problems playing a sound file when running in a Citrix session. It looks like there are no sound devices implemented in the user session (error 4800: Selected Device is Invalid) but I can't see how to check this. Is there a way to find out what sound output devices are available? I have been looking for a function similar to the Query Input Devices.vi from the Connectivity->Input Device Control palette but with no success. The only way I have found so far is to start with a DeviceID of 0 and use the Sound Output Configure.vi from the Graphics & Sound->Sound->Output palette until it returns an error to give an array of DeviceID's that can be used. It works but is there a better way or am I missing something? Sound deviceIDs.vi

Hi, I'm from Portsmouth in UK and use LabVIEW all the time for our ATE's. Use LAVA as a great resource but never had the courage to post before.