Porting labview 6.1 to 7.1

Hi: I am working on a Labview program which I worte a similar one on LV 6.1. I just upgrade to 7.1 recently. I was trying to copy some of my code from my pervious 6.1 program to my 7.1 program. Strange thins is that same code works fine on LV6.1 environment but cause error on 7.1 environment. I have tried to move the code to a stand alone 7.1 vi. It worked fine when I first executed, but cause error the second time. I also have tried to re-write the code using 71 function. It did not work also.
Can anyone give me a hint what's going on???
Attachments:
Untitled99.vi ‏32 KB

What errors are you getting? It appears that you are trying to determine whether the path leads back to an exe, and then open a config file of the same prefix, while creating a new file (results?) of the same prefix with a timestamp. It appears to be correct, you might have a problem with the "New" file though if you run it again immediately, as the date stamp is only out to "day" and the New throws an error if it tries to create a file that already exists. You could do a check of the name and have the result select a case to either create or not depending on its existence.
P.M.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Similar Messages

Reading/writing to parallel port LabVIEW 7.0 Win2000

I'm using LabVIEW 7.0 on a Windows 2000 machine which also has the CVI runtime engine version 6.0.4.105.
I wish to write to the parallel port, simply on/off signal to eight lines. I have previously done this with LabVIEW 5+Win98. I have downloaded the accessHW libraries and installed them but have discovered that I also need the CVI rte version 5.0 . When IT personnel try to install this run time engine "A newer version of this run time engine is currently installed"
appears and won't install version 5 over version 6. Has anyone else come up against this and is there a way around this (without having to install an older version of LabVIEW)?

Leeser wrote:
> I'm using LabVIEW 7.0 on a Windows 2000 machine which also has the CVI
> runtime engine version 6.0.4.105.
> I wish to write to the parallel port, simply on/off signal to eight
> lines. I have previously done this with LabVIEW 5+Win98. I have
> downloaded the accessHW libraries and installed them but have
> discovered that I also need the CVI rte version 5.0 . When IT
> personnel try to install this run time engine "A newer version of this
> run time engine is currently installed"
> appears and won't install version 5 over version 6. Has anyone else
> come up against this and is there a way around this (without having to
> install an older version of LabVIEW)?
You could also use the PortIO library from the OpenG project
http://www.openg.org.
It is currently only in the CVS source code
repository on that site and not yet part of the OpenG Toolkit. Because
it is not everybodys thing to use CVS I include that library as
attachement here.
I tested it myself on Win95, NT4, 2000 and XP and had no problems at all
with it. But please consider it beta software and if you have problems
let me know with as much details as possible.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions
Attachments:
portio.zip ‏195 KB

Can I port labview 3.1.1 to latest ver 8.x is there a tool for this

Is there a tool to port a labview 3.1.1 app to latest ver 8.x

LV 8.x allows us to open any VI that is built using LV 6.x & upwards. So, you ve to convert them to an intermediate version like 6.x or 7.x & then you can open them in LV 8.x.
AFAIK, there is no toolkit available for this purpose.
Maybe you can contact someone in NI to do this for you.
- Partha
LabVIEW - Wires that catch bugs!

Has anyone ported LabVIEW to VxWorks 6.6?

I was wondering if anyone had ported the LabVIEW runtime library to VxWorks 6.6 using microprossesor SDK. My final target is a motrola 6100 VME SBC running VxWorks 6.6.
If someone has done this....have you been sucessful in implementing Queues? Timed Loops? Clusters?

Claire,
Upon some more debugging it is clear that a problem exists upstream of these individual functions which is casuing the error.
The problem is that we are unable to pass data between subVIs using clusters on our
embedded (VxWorks) target.
The exact same VI will function properly under (1) native
LabVIEW windows environment and (2) windows console, however it will not
function properly on the VxWorks target. An example of the output differences
between target types is provided below:
Windows Console (expected behavior):
--TYPE before SubVI--
4
--Words before SubVI--
100
--TYPE inside SubVI--
4
--Words inside SubVI--
100
--TYPE after SubVI--
4
--Words after SubVI--
100
VxWorks Target (incorrect data passed):
--TYPE before SubVI--
4
--Words before SubVI--
100
--TYPE inside SubVI--
4
--Words inside SubVI--
0
--TYPE after SubVI--
0
--Words after SubVI--
0
I think that there is some alignment issue which is causing the
data to be dropped, though not positive. I have a zipfile that I could email you with our project and the generated code. Could I email it to you?

FTDI virtual com port driver (VCP) and Labview 2009 - random connection loss

Hi,
I am using an FTDI chip to go from USB to serial communication (FTDI Driver: 2.06.00). It seems to work at first but then after some time the connection gets lost ("connection for the given session has been lost" or "I/O error"). This happens in MAX as well as the built executable of the program I am running. Latest VISA drivers are installed - 4.6. I have tried flushing the buffer before and after communication with both visa clear and visa buffer flush vis. The lost connection seems to happen randomly.
I have seen other threads about this issue but they never reach a resolution. One thing i notice is that there are two FTDI devices in this system and only one fails, however when I unplug the working device the one that fails is able to connect again.
To sum up here are the system specs:
Windows XP SP3
FTDI 2.06.00 and older 2.04.02 drivers both fail.
2 FTDI devices on the system - they do get assigned different COM ports
Labview 2009 run-time
VISA 4.6 run-time
Thanks for any help.

We use Targus ACH63US Super Mini USB 2.0 4-Port Hub. It doesn't require external power but if you have a high power device you will have to plug the Targus hub into two usb ports on your pc (one provides power and the other does power and data transfer). They provide the usb Y cable to do this.

Error 37 with serial port / no with hyperterminal

I have added to my Pc a card with two serial port, I can access to them by hyperteminal or by labview but only at port 0 and 1 at the same time or 2 and 3, if not I have an error 37. What can I do?

Error 37 means that LabVIEW cannot find the appropriate serial device. This indicates that one of the following conditions exists:
LabVIEW cannot open the specified serial port;
LabVIEW cannot find the file serpdrv.
Make sure that the serial driver was installed before the board, and that the com ports appear normally in the control panel. If you cannot get it working, contact NI through either phone or email support. Since there are several potential causes, this is difficult to diagnose without more information. You can contact NI using the following webpage.
http://sine.ni.com/apps/we/niae_asc.main
Kim L.
Applications Engineer
National Instruments

Creating a Labview VI for controlling an Atmel at32uc3a1512 device.

I have a custom device that has a USB port and an ethernet port,
This device (and it's USB port) are controlled by an atmel at32uc3a1512.
I have an old version of Labview (V8.2) nd I would like to create a VI to communicate and pass data
back and forth with an Atmel at32uc3a1512 but I am not sure how to create a driver for this with the MAX utility.
The device shows up in my Windows XP control panel as a USBLib device...
Any direction, suggestions, or links to examples or whitepapers on this is appreciated
thanks

Hello Japper,
If you would like to attempt to communicate to the Atmel at32uc3a1512 as a device using USB, then the following tutorial should be useful. This details how to use NI-VISA to communicate with a USB device, however this requires detailed knowledge on how the device sends, receives, and processes data.
USB Instrument Control Tutorial:
http://www.ni.com/white-paper/4478/en
If you are attempting to write LabVIEW code that will be deployed to the Atmel at32uc3a1512 as a target then that is a whole different set of needs. This device is not an officially supported target, and would require a significant amount of modification and tweaking in order to get this to work, if it is possible. The best resource that I can provide for that would be this guide on how to port LabVIEW to ARM devices. I understand that the Amtel at32uc3a1512 is not an ARM device, however this would be the closest guide that we have for porting LabVIEW as a target VI.
LabVIEW Embedded for ARM Porting Guide - Chapter 1: Introduction:
http://www.ni.com/white-paper/6994/en
Let me know which method you are attempting to use the Amtel at32uc3a1512 as; either a target, or a device.
Thanks,
Joel
Motion PSE
National Instruments

Auto code(Hex) generation in labview

I wanted to know is there any possibility of generating Hex code automatically from the VI we have made the moment we run the VI.
This is because as MATLAB has this provision which adds major advantage in automotive companies.
Solved!
Go to Solution.

Hello Praveen,
Which microcontroller are you planning to code in?
If it is ARM microcontroller then the following KnowledgeBase Article might help you:
http://zone.ni.com/devzone/cda/tut/p/id/6207
Following webcast discusses how to port LabVIEW code to a 32b Microprocessor.
https://lumen.ni.com/nicif/us/demolvportembd/content.xhtml
Thanks.
Karun Jain

Strange init serial port issue

Hello:
My Labview application is reading data from the COM1..COM6 ports (I have
added a MOXA serial board to get 4 more ports). I am using RS232 reading
on each port (old legacy Vis, 9m long communication cables). The devices to which I am connected are weigh scale that continuously send weight readings to the Labview app through 3-wires RS232 (RD, TX and GND). Everything goes well for hours and hours. Then after a while (maybe after power is cut and restarted on the PC side?) I restart the PC and launch Labview. If I try to init the serial port that I use to connect to the weigh scale I get an error 37. I also tried to init thru HyperTerminal right after restarting the PC and could not. The only thing that works to unlock the port is
this:
- unplug the weigh scale communication cable from the Moxa connector
- restart the PC
- relaunch LV or HyperTerminal
Unplug then restart Labview or HyperTerminal is not sufficient.
To the same Moxa board I connect other devices such as PLC or PC through serial ports but never see any problems even after restarting the Host PC. So there is something strange with weigh scales (I tried two different brands) but what? I cannot use the built-in serial port as it is already in use by another application.
Does someone out there have an explanation and ways to avoid this very annoying problem?
Thank you very much, I am completely lost,
Christophe

Chris:
Thank you for your help. I investigated the problem further and this is what I found. I am still clueless so if you think of other tracks that I might explore I would be glad to hear them.
- Hard boot (power off, remove power cord, restart) does not release the port
- I change the port ie. I used the built-in COM1 PC port, got the communication, could read char, then restarted the PC and fell into the same trap: could not init the port (Labview). I did the same after restarting and could not open the port with HyperT. Hence it is not a Moxa issue.
- The question is: how can I resolve that, is it an HW or SW issue, a combination of the two, has it got something to deal with WIndows 2K, are there some tools that allow to diagnose whi
ch service or application grasps the serial port during the boot sequence? Or is it a problem during the shutdown sequence that the port is not released properly?
TIA,
Christophe

Cross compiling in Embedded /LabVIEW

Hi,
I am trying to create an embedded Unix UI App .I have installed cygwin with cross compiling gcc.
while trying to build an app i get the following errors:
In file included from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/MemCheck.h:24,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/LVCCG.h:37,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/LVCGenIncludes.h:15,
                 from /cygdrive/d/EddyCurrent/Microprocessor/Unix UI/Unix_UI/UI_Application/lvEmbeddedMain.c:20:
C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/LVCritSect.h:22: Invalid token in expression
In file included from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/CCGDataSupport.h:40,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/frontpanel/CCGChartGraphSupp.h:16,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/frontpanel/CCGCtlSupport.h:22,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/LVCGenIncludes.h:17,
                 from /cygdrive/d/EddyCurrent/Microprocessor/Unix UI/Unix_UI/UI_Application/lvEmbeddedMain.c:20:
C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/CCGFXPSupport.h:573: badly punctuated parameter list in `#define'
C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/CCGFXPSupport.h:623: badly punctuated parameter list in `#define'
In file included from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/comms/CCGCommsSupport.h:19,
                 from C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/blockdiagram/LVCGenIncludes.h:19,
                 from /cygdrive/d/EddyCurrent/Microprocessor/Unix UI/Unix_UI/UI_Application/lvEmbeddedMain.c:20:
C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/comms/CCGTcpUdpSupport.h:24: Invalid token in expression
C:/Program Files/National Instruments/LabVIEW 2009/CCodeGen/include/comms/CCGTcpUdpSupport.h:36: Invalid token in expression
make: *** [/cygdrive/d/EddyCurrent/Microprocessor/Unix UI/Unix_UI/UI_Application/lvEmbeddedMain.o] Error 1
How to overcome this error?All are header file errors.
This is the first time i am trying to cross compile.
without cross compiling i can build my app. But how to do with cross compiling....
I have followed the steps gn in Microprocessor SDK Porting labview to new platform.
can anyone help me pls.........
regards,
Indumathi.C
LabVIEW Developer.

Hi Anshul,
Its not possible with "Query Browser". One thing possible which is possible is,it need not be a single row, you can divide the labels in any number of rows and any number of columns. See the below example. The yellow highlighted ones are the labels of chart, the greyish ones are the corresponding values for the labels. The sequence will be the same.
If you dont need this way, then there are two best ways to achieve cross tab functionality.
One thing you can do is, you can directly connect the Bex queries to the Dashboard using BICS Net weaver connection.
But this way you can only Publish-Launch in BW. The dashboard cannot be made available in Infoview/Launch Pad.
Other way is through Webi and BIWS connection. As Suman has mentioned.
This way it ll be available in Infoview/Launch Pad and BW as well.
Thanks,
Sara

LabVIEW Embedded - Support for device: NXP (ex. Philips) LPC2146 Microcontroller (ARM7)

Hi,
I would like to write some code in 'LabVIEW embedded' 8.5 for the NXP LPC2146 microcontroller (ARM7).
http://www.standardics.nxp.com/products/lpc2000/lpc214x/
The 2146 device is used within one of our main 'volume' products and I would like to write some special test code for the product in LV Embedded. I have the full NI development suite at 8.5 level.
The question is, does LV embedded suport this microcontroller fully?
I have found this info but still not sure: http://zone.ni.com/devzone/cda/tut/p/id/6207
Many thanks in antisipation of a reply.
Andrew V

Hi Andrew,
Using the LabVIEW Microprocessor SDK, you can "port" LabVIEW to build applications for any 32-bit microprocessor. The LabVIEW Microprocessor SDK Porting Guide describes the steps involved in the porting process.
The amount of effort involved depends on these factors:
How similar your target is to one of the example targets that are included in the LabVIEW Microprocessor SDK. As you can see in the article you linked, the SDK contains an example target with a Philips ARM and an eCos BSP. If your target is similar to this one (especially if the OS is the same), the porting process might take less than a week.
Familiarity with LabVIEW and embedded domain expertise. The porting process involves writing "plug-in" VIs in LabVIEW and building C run-time libraries for your target. However, once the porting process is complete, your target can be programmed solely in LabVIEW by someone with no embedded expertise whatsoever.
Target selection. We recommend a target have the following characteristics: 32-bit processor, OS/microkernel (not "bare metal"), and 256 KB RAM. Also, if you plan to make use of the LabVIEW Advanced Analysis libraries, a floating point unit is recommended.
Michael P
National Instruments

Error 37 using serial port with an executable file

Hi all,
I have developed a VI that controls a setellite receiver using RS232
serial port (LabVIEW 5.1.1).
The VI program run properly, but when I compile it and try to run the
executable file I receive an "Error 37, Device not found" error message.
I have already put serpdrv and my_file.ini files in the same directory
of my executable program my_file.exe, but I have not been able to solve
the problem.
Any help greatly appreciated.
Regards
Antonio
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
>
> Hi all,
> I have developed a VI that controls a setellite receiver using RS232
> serial port (LabVIEW 5.1.1).
> The VI program run properly, but when I compile it and try to run the
> executable file I receive an "Error 37, Device not found" error message.
> I have already put serpdrv and my_file.ini files in the same directory
> of my executable program my_file.exe, but I have not been able to solve
> the problem.
> Any help greatly appreciated.
>
> Regards
>
> Antonio
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Maybe you used the serpdrv from an older version of LV
Regards, Roland
Roland Lampka - Nortel Dasa - ESN 565-7257 - FAX 8160

PC parallel port access with XP

I recently got In Port and Out Port working on XP.
I searched the ni site for AccessHW. The CVI Run Time Engine has to be
version 5.510 or earlier. I checked the version number of one file, i.e.
cvirte.dll to verify.
I directed the installer to install accesshw to the directory where the new
In Port and Out Port and the rest of the new parallel port .vis were going
to be, i.e. Labview\Labview 6\vi.lib\platform.
I downloaded parallel.zip from ni.com and moved the parallelnt.llb file to
this same directory. Parallelnt.llb has a number of parallel port vis, not
just replacements for In Port and Out Port. I replaced the In Port.vi and
Out Port.vis in the diagrams I was trying to make work with the new .vis.
So, on this XP machine, with
a monitor program, parmon.exe, running to
display the bits on the parallel port, Labview can be seen to be using the
new parallel port .vis, and, bits on the port are changing.

I wonder if there's a reason why there's a javax.comm 3 series for *nix, but not for windows. Hmmm.

Can LabVIEW be compiled to run on an ARM 7 CPU

Hi All
Wondered if anybody knows whether it is possible to cross compile LabVIEW code to an ARM7 Embeddded CPU. DO ayny of the LabVIEW add ons allow this?
Thanks in advance for your help.
Tristan

Sure. It is easiest if you use WindowsCE or the Palm OS as the OS on the uP. Then you can use the PDA toolkits. The PDA toolkits are much easier to program for, but more expensive to deploy ( OS license + LabVIEW license). If you choose to not use an OS or use another OS, you will have a lot of work to do, but you can do that as well with LabVIEW embedded (which is also not cheap, but has no per unit licensing fees). IT IS NOT EASY. It is do-able, but not easy.
Begin sales pitch
We specialize in embedded software. We have ported LabVIEW to several processors as well as used the PDA toolkits. If you need help, feel free to write me and we can do as much of the work or as little as you need. We also offer training.
End sales pitch
Hope that this helps,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

Old Labview versions

Hello everybody!
I want to use some parallel port, labview programs with my old laptops using windows 95 and 98.
Which Labview version can I use for that purpose?
From where can I download such an old version for free or a trial version?
Thank you!
Solved!
Go to Solution.

Hey Nicku,
Attached is the image that was missing from the above linked Knowledgebase. In regards to accessing older versions of LabVIEW, if you have a valid support contract, you can access some earlier versions of LabVIEW from the Service Resource Center . However, versions of LabVIEW available there do not go back as far as LabVIEW 6.1 which is what you would need for a Window 95 machine. Unfortunately, free or trial versions of LabVIEW would not be available for LabVIEW 6.1. It might be helpful to contact a local sales representative to discuss what options you have.
Message Edited by BCho on 12-22-2009 10:22 AM
Message Edited by BCho on 12-22-2009 10:24 AM
Hope this helps.
-Ben
WaterlooLabs
Attachments:
lv versions.png ‏88 KB

Porting labview 6.1 to 7.1

Similar Messages

Maybe you are looking for