Use of LabVIEW Merge

Is there any use for using LabVIEW merge if your software team does not to parallel development? We are starting to setup Perforce for source control, and I was considering setting up LVMerge.exe to work with Perforce. However, since we have no parallel development, I don't see any point to this. Is there a reason that I'm overlooking to setup and use LVMerge when there is no parallel development?
Thanks!

Dennis Knutson wrote:
Consider a single developer making multiple changes. Merge is just not for different users. I've had to do a quick patch to fix a bug in source while at the same time, do more extended edits on the same source for new release with additional features.
Now that I think about it, I was confused how a single user would use LVMerge, because I don't really understand some of the differences between the arguments LVMerge uses. What is the difference between the Base VI and Your VI? According to the LabVIEW help, the Base VI is "Absolute path to a copy of the VI from where you checked it out (Base
VI)," and Your VI is "Absolute path to the VI you edited (Your VI)." Those seem like the same things to me. Isn't the VI I checked out the one that I am editing? Could someone clear that one up for me?
Also, I am confused about Their VI, which according to the LabVIEW help is, "Absolute path to a copy of the latest revision of the VI in source control
(Their VI)." MY source control is on a server. Do I use the server absolute path, like \\SERVER\SourceControl\Project\VI.vi to tell LVMerge where to get that VI?

Similar Messages

Using New LabVIEW Merge Tool LVMerge With Tortoise SVN

Hi,
I've just posted a new blog article Using New LabVIEW Merge Tool LVMerge With Tortoise SVN to my blog at ExpressionFlow. Check it out!
Tomi
Tomi Maila

The LV merge tool really does become far more powerful when integrated into SVN than when used manually. Here's an article on Using LVmerge LabVIEW Merge Tool with TortoiseSVN with all the necessary setup instructions for LabView 8.5 and 8.6.
Jesse

Assistance with Printing to Zebra QL220 using the LabVIEW report VI

I currently am trying to use the LabVIEW report VI to output a formatted set of strings to the above mentioned printer.
The UMPC hardware that runs the developed application is bare bones XP box and doesn't' have MS office installed
I use the LV new report set to a standard report and successfully set orientation to portrait or Landscape, set margins and set report fonts and headers.. However in sending the text strings to this label printer (labels are 45mm X 60mm) I find that that two issues arise.
1. Printing out double labels. The pagination fails and prints a blank label after each print when text is output. However if I disable all headers and body text (i.e blank label print). This pagination works fine.?
2. The formatting of the information on the page reliably, I currently use inserted blank spaces, is there a better way?
I thought, perhaps I should try using the ZLP programming language, but then not sure how to I send it to a USB printer? Has any one had any experience with this and these label printers ?
Thanks
Greg Nicholls

hi all
i am C sharp programer
and i have zebra QL 220 plus
and roll type is 42X20mm
and i have the zebra sdk
and i create mobile application in C# smart device
and i tring to connect to printer from my application by bluetooth
in sdk i got this and use
using System;
using ZSDK_API.Comm;
using System.Text;
using System.Threading;
// This example prints "This is a ZPL test." near the top of the label.
private void SendZplOverBluetooth(String theBtMacAddress) {
try {
// Instantiate a connection for given Bluetooth(R) MAC Address.
ZebraPrinterConnection thePrinterConn = new BluetoothPrinterConnection(theBtMacAddress);
// Open the connection - physical connection is established here.
thePrinterConn.Open();
// Defines the ZPL data to be sent.
String zplData = "^XA^FO20,20^A0N,25,25^FDThis is a ZPL test.^FS^XZ";
// Send the data to the printer as a byte array.
thePrinterConn.Write(Encoding.Default.GetBytes(zplData));
// Make sure the data got to the printer before closing the connection
Thread.Sleep(500);
// Close the connection to release resources.
thePrinterConn.Close();
} catch (Exception e) {
// Handle communications error here.
Console.Write(e.StackTrace);
// This example prints "This is a CPCL test." near the top of the label.
private void SendCpclOverBluetooth(String theBtMacAddress) {
try {
// Instantiate a connection for given Bluetooth(R) MAC Address.
ZebraPrinterConnection thePrinterConn = new BluetoothPrinterConnection(theBtMacAddress);
// Open the connection - physical connection is established here.
thePrinterConn.Open();
// Defines the CPCL data to be sent.
String cpclData = "! 0 200 200 210 1\r\n"
+ "TEXT 4 0 30 40 This is a CPCL test.\r\n"
+ "FORM\r\n"
+ "PRINT\r\n";
// Send the data to the printer as a byte array.
thePrinterConn.Write(Encoding.Default.GetBytes(cpclData));
// Make sure the data got to the printer before closing the connection
Thread.Sleep(500);
// Close the connection to release resources.
thePrinterConn.Close();
} catch (Exception e) {
// Handle communications error here.
Console.Write(e.StackTrace);
and once i use ZPL method it print 17 barcod always with 16 blank Patches (labels)
and when i use CPCL method it print 12 BarCode always with 11 blank Patches (labels)
and i dont know why ?
it must print 1 Patch (label)
what i can do and i dont think there is eny rong with my code
all waht i want is how i can give Length and width and how much label print coz it is always print 17 or 12 what i can do ?

Is there a way of using a mail merge function while on the iphone or ipad, i wish to email a "Word style, ot TXT" document to 250 of my contacts

Is there a way of using a mail merge function while on the iphone or ipad, i wish to email a "Word style, ot TXT" document to 250 of my contacts, I have tried downloading my contacts to my PC's outlook but only 1 contact comes across at a time despite the fact that Icloud says downloading namedperson + 249 other contacts to a CSV file

Hi everyone!
Looking also for an app that allows me to merge email and send them out to each recipient individually. Apparently that's not possible yet. Here's what the guys at RedbitsApps told me about Group Email capabilities:
"The current version of the app relies on the device operating system to send the emails. For this reason, sending individual email instead of a single email to multiple recipients is not possible. Apple doesn't allow apps to send single emails to many recipients easily. We may use a custom sending software in a future version."
Let's keep looking guys...

CR3000 driver to use in LabVIEW

Hello All;
I have a CR3000 Micrologger from Campbell Scientific, and I would like to interface it with the PC using the RS-232 port. I would also like to use LabVIEW as a programming environment to Read/Write data from/to the CR3000.
It there any Driver specific for the CR3000 to be used in LabVIEW through the RS-232 port?
Looking forward to your valuable replies.
Thank you.
Tarek

There are no drivers for that instrument in the Instrument Driver Network. Writing an instrument driver isn't all that hard. You should first see if there's a driver for a similar instrument available that you can use. You can also look over this tutorial. Other resources are available. LabVIEW has an Instrument Driver Wizard that you can use to create a boilerplate.
Before you do any of that, though, you should verify that you can communicate with the instrument. Use a terminal program to work out any communication issues, such as serial communication parameters or cable issues (such as whether you need a straight or null modem cable). On Windows HyperTerminal is your best bet.

How can I use the LabVIEW Symbol Editor as a Sub-VI?

How can I use the LabVIEW Symbol Editor as a Sub-VI?

mc-hase wrote:
> Thank you for your ansver.
> That means that you see no possibiltiy to use the built in window? (I
> think the built in window is programmed with LabVIEW as well...)
The icon editor at least up to version 7.0 of LabVIEW is not written as
VI but directly implemented inside LabVIEW, which is written in C/C++.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Making DLL with C++ builder to use in Labview

Anybody knows how to make DLL in C++ builder to use in Labview??
Regards,

smercurio_fc wrote:
MCFSE wrote:
This is a good question that does not appear to be addressed in that other thread.
But is addressed via several NI KnowledgeBase articles and NI Community examples. For example: https://decibel.ni.com/content/docs/DOC-14564
Well not verbatim, as that document refers to Visual Studio, not C Builder. But creating DLLs in C Builder for use in LabVIEW is no different than creating DLLs in C Builder for any other programming environment that can call unmanaged DLLs. How to configure C Builder to create a DLL, is really beyond the tasks anyone from NI should be required to explain. This requires someone who is familiar with C Builder and requesting a supplier to have specific experience with tool X goes a bit far. NI and most others are using Visual Studio so that is what gets explained. If some C Builder crack would come up with a tutorial targeted at integration with LabVIEW and post that here or someplace else, that would be of course great, but alas, nobody so far has felt the desire to step up to the challenge. There is no inherent difficulty with C Builder created DLLs to be used by LabVIEW, but apparently some difficulty of people to understand how to use C Builder to create working DLLs at all. Similar problems can appear for beginners with Visual Studio and since this is the tool mostly used here around, there are several tutorial style documents available that try to handhold the beginner to get a DLL at all.
Personally I'm not sure that is ideal either, since those people usually know very little about C programming, or more precise if they know about C programming, they will be able to learn to use the tool in question, with some simple, non LabVIEW oriented examples from elsewhere and then easily apply that knowledge to LabVIEW with the help of the Visual Studio examples posted in quite big numbers, even if they use a different tool than Visual Studio.
Other even more challenging topics would be to use CygWin, MingW, Bloodshed Dev C++ and similar compilers and write tutorials about them. However the challenges with all of these is to get them even installed well on your development system and to figure out various configuration hassles, also when trying to distribute the result later on.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Use NI LabView and LabView RT with third party PXI chassis

I want to use NI LabView and LabView RT, some PXI chassis of N.I and
some PXI chassis of Third Party( not N.I ) for diversity, How I will Install
Pharlap ETS ( LabView RT ) on those third party PXI's.
More simply
Third party PXI chassis and controllers support LabView RT or not?
Note: Mark Andre Hary [email protected] of Sensing Systems LLC answer to this question as:
"You can't. I think NI bought Pharlap, and they do not offer board support packages (BSPs) for non-NI PXI controllers. There is no way to get LabVIEW-RT running on a controller not purchased from NI. You will have to use a standard RTOS like Linux,VxWorks, or QNX.
Regards

As described in the web links below, the only way to run LabVIEW Real-Time for ETS on a third-party system would be to follow the procedure for desktop PC computers. You may find that your third party PXI controller may meet the requirements listed in the below link and you will be able to run Real-Time on the controller. If you decide to do this, you will need to purchase the LabVIEW Real-Time Desktop Deployment license (also linked below). After purchasing the deployment license, you will be sent boot disks that will install the real-time OS onto your system. There is no need to purchase Pharlap ETS from Ardence directly.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/cb3434da94466dd286256e9e006bb775?OpenDocument
http://sine.ni.com/nips/cds/view/p/lang/en/nid/13751
Instead of using LabVIEW Real-Time for ETS, you could use LabVIEW Real-Time for RTX instead. This system allows you to run Windows and the Ardence Real-Time eXtensions (RTX) real-time kernel concurrently on one machine. Currently device support for LabVIEW RT for RTX systems is limited to RIO devices. This is all described in the below link.
http://zone.ni.com/devzone/conceptd.nsf/webmain/9cc60298315a687e86256e78007b3a96
I hope this answers your question.
Regards,
Kristi H - National Instruments

Correct use of LabVIEW 8 with Visual Source Safe

I have LabVIEW 8.0 and Microsoft Visual Source Safe 6 (VSS) installed and was looking for help with the correct way to integrate the two environments. This will be used in a team environment and code modules will be shared between team members. I have used and understand the new project manager with it's virtual directory structure. I have also used and understand VSS and its abilities to share and branch vis or project folders.
When you share an item in VSS, the vi is available for use in both projects and physically resides in both projects within your working directory. If I were just using VSS, this is the method I would use (and what is recommended in the VSS documentation). This way an entire project contains all the files and can be retrieved all at once.
When you use the LabVIEW 8 project manager, it appears that the intent is to only have the code in one location and share it through virtual folders. This makes sense and works fine until LabVIEW 8 and VSS are both used. LabVIEW 8 can handle check in/out and adding files to VSS. A LabVIEW project can even use vis that belong to other LabVIEW projects and other VSS projects.
My concern with all this is what happens when a team member wants to bring down code to their working directory or rebuilding my own working directory. LabVIEW's project manager does not appear to provide a direct view to the VSS database. I can go into VSS and pull down a LabVIEW project file (lvproj file only) and open it up. All appears to be fine and all VSS information is intact. What is not there is any indication of which files actually exist in my working directory or any way to perform a "bulk" retrieval of all the files required in my project. If all the files reside in a virtual directory, I don't even know where to go get them from. One solution could be to follow the VSS style and ensure everything is native to a project or at least shared with a project (within VSS). This may be cumbersome and would not follow the LabVIEW project philosophy. I may also miss something since LabVIEW "remembers" where stuff is for you. Following the LabVIEW project method could make it difficult to bring a project back to life and also has the potential to leave some vis out of source code control (sub vis don't have to belong to a LabVIEW project).
Does anyone have thoughts on this subject? What is the most efficient way to ensure that all project items are in source code control and that all projects are retrievable and functional?
Thanks,
Greg Cloutier

Greg,
I'm not a VSS guru but I do know that currently there is no automatic functionality for checking in\out a project and all associated files from LabVIEW.
As for finding the location of the vis that have been checked out, LabVIEW can display the full path of a vi from the project explorer. If you right click on a vi and then select properties, the General category will show the full path.
There are a number of papers that do relate to using SCC with LabVIEW 8. check out Using Source Control Software with LabVIEW and that will link you to other documents as well.
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

Error when compiling my API Programm thant i want to generate DLL for use in Labview!

Pls see the attachment!!I use API "GetComputerName" to programm in vc6.0 to make a dll file for use in Labview.But i get the error in the attachment. Pls give me a hand!
Attachments:
machinename.zip ‏1493 KB
error_when_compiling.txt ‏1 KB

Hi,
If you are using the CVI libraries on this you can use the GetCompName() function from the programmer's toolbox. However, your code looks fine, the only thing that you need to change is the data type of the paramenters in CompNameLength. Just declare them using the predefined Windows data types; like this:
LPTSTR computerName;
DWORD compNameLength = MAX_COMPUTERNAME_LENGTH+1;
computerName = malloc(MAX_COMPUTERNAME_LENGTH+1);
GetComputerName(computerName,&compNameLength);
printf("%s",computerName);
free(computerName);
Don't forget to include windows.h where those types are defined.
Good Luck!
Juan Carlos
N.I.

I would like convert a c++ dll for use in labview--my device has no labview dll

I have a piezoelectric control board (Piezomechanik gmbh) that I would like to use through LabView. Currently, the company does not offer any support for Labview. Windows sees the device (It came with a driver file), but the company only provides dll files for C++ and Visual Basic. Can I convert these files to a format Labview can use? How can I get Labview to communicate with the control board (and ultimately the piezoelectric device attached to it)? Thanks!
Solved!
Go to Solution.

This will only help you when you have the header file for the DLL, otherwise you will have to create the wrapper manually using the "Call library node" and the DLL api description or write an header file for the DLL yourself based on the api documentation and use the wizard.
Regards,
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Who is eligible to use the Labview 8.0 Student Edition

Who is eligible to use the Labview 8 student edition? Can an individual who is not in school or affiliated with a learning institution purchase and register it for the purpose of learning at home?

This post was answered here
Chetan K
Application Engineering
NI

Q: Must one use special LabVIEW types (e.g. float64) for DLLs in LabWINDOWS/CVI?

Hello,
I have recently started compiling C code using LabWindows/CVI, and have successfully called a simple DLL function from within LabVIEW.
I have a question about the types defined in LabVIEW's extcode.h file:
These are defined to explicitly quantify the number of bits used for each data type (e.g. float64 instead of float) in order to eliminate ambiguity across compilers.
When I am using LabWindows/CVI to compile, do I need to use the LabView numeric types defined in LabView's extcode.h, or can I use the standard C types (int, float, etc.)?
Is there a distinction between having to use these special types for CIN versus shared library calls in LabVIEW?
Thanks
in advance,
Frenk

You do not have to use the defines in extcode.h, but you certainly can if you want to.
The float64 is equivalent to CVI's "double", and the float32 is equivalent to CVI's "float".
These correspond to the double- and single-precision types in the IEEE Standard for Floating Point Arithmetic, IEEE-754.
I hope this helps.
Brian

Using the match/merge operator

Hi guys,
I have created a simple table with 4 columns:
EMPLOYEES
- employee_id
- emp_firstname
- emp_lastname
- emp_telephone
I have placed 5 entries in the table:
11, jane, doe, 80980980
12, william, gates,6876876868
13, john, anderson, 545646546
14, michelle, millo, 340580334
15, john, anderson, 545646546
Row 13 and 15 are duplicates, except for the employee_id. I'm trying to use the match-merge operator to check for matches on emp_firstname, emp_lastname and emp_telephone. I would like to merge the rows matching on firstname, lastname and telephone number, and would like to keep the lowest employee_id as PK.
I have tried to use the match-merge operator with the following settings;
Input connections:
- employee_id
- emp_firstname
- emp_lastname
- emp_telephone
Merge output
- employee_id
- emp_firstname
- emp_lastname
- emp_telephone
Xref output
none
Match bins:
- emp_firstname
- emp_lastname
- emp_telephone
Match rules:
MA_0, all_match
Merge rules:
emp_firstname: all match
emp_lastname: all match
emp_telephone: all match
When I debug the match merge operator I get " 4 in, 4 out", but I expected to have "5 in, 4 out". Am I using this match/merge operator the right way?
thx for you help!
michiel
null

Hi Robert,
I tried on 3 database installations (all 10.2). there is no parameter DB_BLOCK_BUFFERS set. And i do not assume that there is a reasn for increasing the db_cache_size - means: why i did not get any error for that presumed case?
btw: can you explain why i should increase db_cache_size?
thanks,
Andreas

Where can I find an example of a vi which reads a xml file using the Labview schema (LVXMLSchema.xsd)?

Where can I find an example of a vi which reads a xml file using the Labview schema (LVXMLSchema.xsd)?
�Unflatten From XML� is of little use in parsing because it requires the data type. So it seems that the user has to parse each data value, and then �Unflatten From XML� can help a little.
I would like to see NI provide a VI for parsing it�s own schema.

LabVIEW's XML functions are another way of saving data from controls and indicators that is in a more standardized format. If you look at the Unflatten From XML shipping example, it shows taking the data that you would normally send to a Digital Wveform Graph and converting it to XML instead. This data is then unflattend from XML and wired to the graph. Since you know what you wrote to the file, this is an easy thing to do. If what you are looking for is a way to look at any data in any LabVIEW XML file, then you are right, there is not a VI for that. However, I do not believe that that was the intention of the XML functions in the first place.
By wiriting data in XML, this allows other applications outside of LabVIEW to parse and recognize the dat
a. In LabVIEW, you would already know the types and can place a generic item of that type. The issue of knowing the type is that you need to know the type of the wire that comes out of the Unflatten function so that the VI will compile correctly. You could always choose a variant value to unflatten and then do some parsing to take the variant a part. Maybe this will help you out.
See this example for using the Microsoft parser for XML. (http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9FE111EE034080020E74861&p_node=DZ52050&p_submitted=N&p_rank=&p_answer=)
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Use of LabVIEW Merge

Similar Messages

Maybe you are looking for