Using PVCS keyword replacement with LabView

Has anyone tried using "fixed keyword expansion" with LabView? There is feature that you can use to replace text strings in a binary file but I've not been able to make it work for a VI.

> Has anyone tried using "fixed keyword expansion" with LabView? There
> is feature that you can use to replace text strings in a binary file
> but I've not been able to make it work for a VI.
I don't think that is going to work. PVCS has no way to know about the
offsets and size fields located in a given VI. I'm not familiar with
the option you are asking about, but my suspicion is that it is
specifically designed for a particular resource format or EXE format.
If you are looking for a solution to translate strings in a VI, there
are menu items under Tools>Advanced for Exporting and Importing strings.
The file format is pretty readable for hand translating, and pretty
easy to parse if you want to extract the strings to another form,
translate, an
d rebuild.
Greg McKaskle

Similar Messages

Req any examples of high to use midi controller/keyboards with Labview TIA

Req any examples of high to use midi controller/keyboards with Labview TIA

[email protected];
Check the following:
Communicating with a Windows MIDI Device in LabVIEW
Regards;
Enrique
www.vartortech.com

I want to use the sound card with LabView

Hi. Who can help me, I want to use the sound card with LabView, I have found the function but I can't use it. Thanks.

Christi,
In LabVIEW 6.1 I found some examples they use those sound VIs. They are located in \examples\sound folder. Those examples should give you a good overview how to use the VIs.
Hope this helps
Roland

Is it possible to use an IrDA protocol with LabVIEW 8.2.1 in DSP BlackFin?

Dears,
I'm building a project to communicate a DSP BlackFin 533 with a Palm E2 Tungsten between IrDA Protocol. The packaged LabVIEW installed in Palm allows to use IrDA protocol, but I don't know if the packaged for BlackFin DSP allows or not.
Is it possible to use an IrDA protocol with LabVIEW 8.2.1 in DSP BlackFin?
Regards,
Renato - RPS

OpPss ...
Sorry !!!
Attachments:
IrSerial.zip ‏11 KB
IrSerial1.zip ‏11 KB

Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

Hi,
My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
Thanks,
Alex
Solved!
Go to Solution.

Hi Alex,
In you case, you are getting a -18002 error.
The reason is explained in the following link:
-18002 Errors in TestStand
http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
Please have a look at the 2nd reason. This is your case.
Hope it helps,
Regrads
Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
National Instruments Switzerland

How do you use Synergy 7.1 with LabVIEW?

My company has reciently installed and configured IBM Rational Synergy 7.1 to be used as our Source Code Control tool. I have installed the appropriate Microsoft Source Code Control Interface so that Synergy will show up in LabVIEW and it does show up in the "Source Control" options window.
However when I select Synergy as my source control tool it does the following:
1. Brings up the login window - I am able to login with no problem
2. Brings up a dialog allowing me to select the project to work on, and after I select the project I get two errors...
one from Synergy: "The workspace/project you want to add to IBM Rational Synergy is not under the work area path 'C:\xxx"
(where xxx is my work area for the Synergy project I selected)
then one from LabVIEW: "Error -2941 occured at prefPage_Source Control.vi An error occured trying to get the source control project path. Possible reasons: LabVIEW: The source control provider does not support the specified operation."
I first tried this on an earlier version of Synergy that matched what is being used in:
http://digital.ni.com/public.nsf/allkb/16D37CCC8659123F8625720500087DB4
But I was getting pretty much the same errors back then too. It seems like it should work in LabVIEW, I just have no idea what I am doing wrong!
Anyone out there successfully using LabVIEW with Synergy????
Thanks,
Trevor.

In theory if a source control provider supports the Microsoft SCC interface, it *should* work with LabVIEW. In practice, each provider has custom implementation that sometimes causes problems when trying to configure the provider from LabVIEW. One sticking point for many providers is the expectation or assumption that an IDE will use some concept of a "project" and therefore pass data associated with that project to the provider. LabVIEW does not enforce that concept but does pass valid information.
Synergy was tested back when it was a Telelogic product. It was difficult to configure and required exact steps to get it to work correctly. The linked knowledge base were steps taken that worked for a few customer setups. It's possible that on other Synergy setups the exact steps may not work. Also, you might check to make sure you try to configure existing Synergy projects and not try to create new ones from LabVIEW.
The error you mentioned seems to imply that some data is not supported by Synergy. I am not sure if Synergy would be able to track down the issue, but I would recommend contacting them to see if they can pinpoint what data LabVIEW is sending is not valid.
George M
National Instruments

Issues when using a Pixelink camera with LabView 9.0

In my lab, we have a program for video acquisition using LabView and the low level camera functions for Pixelink cameras. We run into some problems trying to run this program and other demo gui programs that came with the Pixelink SDK. In our data acquisition program, we have problems with our image coming out all scrambled. We use the low level functions to obtain a frame from the camera in the from of a vector. We then reshape the vector into an array and then send the array to a vi that turns it into an image. When we try to view this image using the standard Labview image viewer, the image comes out all scrambled if the zoom factor is not set to .5 on the image viewer. The full resolution of the image is supposed to be a 1024x1280 image which when we use the Capture OEM software for the camera provided by Pixelink we can see. The image that we can see through LabView when we have the correct zoom factor seems to be only the top left quarter of what the entire image is supposed to be. We also encounter strange problems when we attempt to use the demo programs for labview 8.6 that are provided with the SDK. When trying to run the simpleGUI.vi, for example, the program connects to the camera just fine. After you hit play to view an image, the problems start. The program will play the video for a few seconds until it just freezes up and quits responding. Labview must be exited and restarted in order for the camera to connect again. I am not sure if it makes a difference that we are running labview 9.0 on our computers or not. Any help you have on these issues would be of great help. Attached are pictures of the scrambled/unscrambled image and of the part of our block diagram for camera control.
Attachments:
Incorrectimage.jpg ‏126 KB
Errorexplanation.jpg ‏543 KB
correct image.jpg ‏22 KB

IMAQdx is the driver that National Instruments provides to interface Firewire, GigE and USB cameras (Directshow compliant USB). This is a licensed driver, so if you don't currently have it, then testing in MAX is not an option.
So if I understand correctly, you have the Pixelink software which works fine, but you have Pixelink VI's that are used in LabVIEW, but those do not work correctly? That to me seems like a driver issue, which I'm not sure how much I can help with since it is not our driver.
Do you know what dll's the Pixel link VIs are calling into? Are they Pixelink dlls? If so, I would suggest speaking with the manufacturer or perhaps on of our other users has worked with Pixelink before.
Sorry I can't be much more helpful.
Tejinder Gill
National Instruments
Applications Engineer
Visit ni.com/gettingstarted for step-by-step help in setting up your system.

Using a DaqBook/200 with LabVIEW "Driver set up"

Ok here's another round of dumb a*& questions.
I'm using a DaqBook/200 with DaqX software version 7.12.10 "latest and greatest except for the differential bug" I used their Daq* Configure Utility to set my DaqBook up. I created the following:
Device Name: DaqBook0
Device Type: DaqBook/200/260 (you pick this from a pull down menu)
Port (parallel) setup: LPT1
Protocol: Standard 4-bit
Having never used a Data Acquistion box before I tried to start with the simplest VI configuration I could find. I decided to use the "AI SAMPLE CHANNEL.VI". There are only five connections.
1st. Called "Device" this is the number I assigned to the Daq device during configuration. Now this should be what I typed above beside Device name: DaqBook0 "but I can only enter a number it want let me enter letters so I really don't know what to enter here now"
2nd. Called "Channel" identifies the analog input channel you want to measure. Using the DaqView software there are several columns that have names. The 1st column which you can't edit is labeled CH. Underneath is written P1 0 Direct. This means P1 (port 1 on the daqbook which is the analog port) 0 (which is channel 0 or the first channel) then the word Direct (meaning a direct connection to the Daqbook. Now next comes the "On" column which indicates if the channel is on/off. Next is the "Type" column this indicates if the channel is analog, digital, or frequency. Next is the "Polarity" column where you select either Bipolar/Unipolar. Next comes the "Label" column where channel 0 is labeled CH00 (by default)or you can enter a custom name. Then "Units" which indicates what type of measurement voltage, amps, counter, etc... The "Reading" column that indicates the output of that channel if DaqView is used as a stand alone.
Now out of all the columns above I'm not sure which to enter as the Channel as requested by the Labview VI above.
3rd. Called "High limit" this is the highest expected level of the signal I want to measure. This I think I can understand.
4th. Called "Low limit" this is the lowest expected level of the signal I want to measure. This I think I can understand.
5th. Called "Sample" contains the scaled analog input data for the specified channel. I know this is the data being measured, but I'm not sure what they mean by "Scaled"
Ok now that you know the information here's how I entered it.
Device- I put 0 because it wouldn't let me enter alphanumerical units. Help showed "I16" as the representation units. So I figured thats what I needed to enter and it could be change.
Channel- I enter CH00. I just could see entering a value that could be changed and the "P1 0 Direct" under the "CH" column just didn't seem right. But who am I to know.
High Limit- I set to 10.000Volts ( because I'm using a 9volt battery as a voltage source)
Low Limit- I set to 0.000volts
Sample- I just used an indicator to show the results.
When I run the VI I get the following error 10401 telling me that the specified device is not a National Instruments product, the drive does not support the device. Which I'm sure you know the error and the reason that it occurs.
So what do I need to start on first? Let me know

Dennis is correct here!
I did a project with one of these gizmos (the customer already had the device and was convinced it could do what he wanted). I was extemely disapointed with its capabilities.
At first glance it has some cool spec's but if you look real close it turns out that ther was no way to do a continuous acq with these things. That resulted in the app only being able to capture what the customer wanted every now and then.
I convinced hime to switch to an NI device.
If you are going to use this device, you have to use the drivers they provide.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Use Photonic Science Camera with LabView/IMAQ

Has anybody had any experience with a Photonic Science camera ? I want to use the PS CoolView 12 with LabView 6/IMAQ 2.5.5.
Thank you !
Guido

Hello,
I come from France and got exactly the same material as you. If you get the chance to have answers to your questions just give me the place to deal becaus I'm still looking for answers
Regards
PIL

How can I transmit and receive messages using Vector CANTech CancardXL with LabVIEW?

I'm a new LabVIEW user and I need transmit and receive CAN messages using a CancardXL from Vector CANTech with LabVIEW.
Could somebody have any vi or suggestion?

I made a set a LabVIEW VIs to work with Vector/Softing CANCards starting from an example program I downloaded from Softing. These use the Call Library Node to interface with the cards .dll.
I can't give these out because they were developed for a customer. I would contact Vector and see if they have an example program for your card. Might be the same one I started with.
[caution, salesman hat going]
Of course if you need help developing the VIs, we'd more than happy to assist you.
[remove saleman hat]
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Crosspost: Has anyone used a Redlake camera with LabView/Imaq?

"I can't seem to find any drivers or utilities for the Redlake camera i'm using in my project.
Only this: http://www.imagemill-tech.com/Redlake/ Fr_Redlake.htm
But there's no info on how to get that VI (I've e-mailed them, of course).
Any additional information on using the camera with LabView/Imaq would be much appereciated"

"Kasper B. Dall" wrote in message news:<[email protected]>...
> "I can't seem to find any drivers or utilities for the Redlake camera
> i'm using in my project.
>
> Only this: http://www.imagemill-tech.com/Redlake/ Fr_Redlake.htm
>
>
> But there's no info on how to get that VI (I've e-mailed them, of
> course).
>
>
> Any additional information on using the camera with LabView/Imaq would
> be much appereciated"
I just find the section out for you about remote control of your
camera:
1.7.1 Remote Control.
Redlake Imaging also supplies the Serial1 program that enables a
computer to control the
MotionScope system from a remote location through the serial port.
Refer to Manual Addendum
9400-0014 for detai
ls of the Serial1 program and how to control the
MotionScope system from a
remote computer using a standard communications program.
So you need to find the serial command (for RS232) in manual addendum
9400-0014. I couldn't find it in website maybe I did not search
throughly, but you may have it if you own the camera. And these
commands are just for controlling the camera system, not grabbing the
image, so you may need a frame grabber to get the image into your
computer and do the further processing.
Irene
[email protected]
> http://www.geocities.com/irene_he/IVision.html

Has anyone used a Redlake camera with LabView?

I can't seem to find any drivers or utilities for the Redlake camera i'm using in my project.
Only this: http://www.imagemill-tech.com/Redlake/Fr_Redlake.htm
But there's no info on how to get that VI (I've e-mailed them, of course).
Any additional information on using the camera with LabView/Imaq would be much appereciated

It looks like the Redlake VIs from ImageMill allow you to write serial commands to your camera. In LabVIEW, you should be able to write your own serial commands using the Serial Read/Write examples that ship with LabVIEW.
I'm curios exactly which Redlake digital camera you have. Redlake cameras are often found under the names Roper (their parent company) or Kodak. I suggest going to www.ni.com/cameras to see if there is a camera file written for your specific camera. If not, please go to www.ni.com/ask to contact an applications engineer.
Kyle V

Using Global Mapper SDK with LabVIEW

I am actually new to using any SDK with LabVIEW.The basic idea behind the whole thing is to plot lat and long coordinates into global mapper cutomized app through Labview.I mean I am acquiring data in labview, but i want to display the coordinates in global mapper.For that what I have to do.I don,t have much idea abt MFC too.
Solved!
Go to Solution.

Hello sets,
I found some resources on the Global Mapper site that you may find helpful. They seemed to have the same questions as you, and an employee helped answer some questions.
Global Mapper SDK for LabVIEW Software: http://www.globalmapperforum.com/forums/technical-support/8917-global-mapper-sdk-labview-software.ht...
Global Mapper and LabVIEW: http://www.globalmapperforum.com/forums/sdk/9116-global-mapper-labview.html
Are you using LabVIEW, LabWindows/CVI, or Measurement Studio? This is a Measurement Studio board, but if you have LabVIEW questions, I suggest posting to the LabVIEW board. (http://forums.ni.com/t5/LabVIEW/bd-p/170)
Regards,
Jason D
Applications Engineer
National Instruments

Using Metex MS-1280 with LabView.

I am trying to connect a Metex MS-1280 oscilloscope, used in DMM mode to LabView 6.
The only thing I found is an example for some other Metex DMM: http://schulen.eduhi.at/htlbraunau/lehrer/ploetz/Labbsp/upmetex/metex.pdf
Unfortunately this example does not work on my Metex.
I get erros like: Visa read in Metex.vi (-1073807339)

Hi,
It appears that the instrument driver does not correctly set up the termination character and Serial End Mode for Read properties for the instrument. Use VISA property nodes to set the "Message Based Settings:Termination Character" property to 10 ('\n'), "Message Based Settings:Termination Character Enable" to True, and "Serial Settings:End Mode for Reads" to 'TermChar'. This should force LabVIEW to pick up the '\n' termination character appended to data returned from the instrument. It will also be helpful to know which vi is throwing this error.
Thanks,
Arjun K
National Instruments
Applications Engineer

Can I use any acquistion card with Labview?

I have got a non NI acquistion card, how can I use LabVIEW to program it?

> But are all the software drivers provided by vendors recognized by
> LabVIEW? In other terms, must these drivers get a satandard
> architecture or protocol so LabVIEW can communicate with them? Or, if
> I develop my own acquisition card, how can I write it's driver so
> LabVIEW can communicate with it?
The LV drivers for various NI products are essentially VIs that call
into a user level DLL. That DLL does its work and returns the results
and/or error info to the diagram.
If the board has a DLL that allows it to work, then you can make quick
wrapper VIs to make it fit the LV language a bit better.
There are no architectures or protocols for drivers to replace NI-DAQ or
other NI driver wrappers.
Greg McKaskle

Using PVCS keyword replacement with LabView

Similar Messages

Maybe you are looking for