I found a bug In LabView 2009!!!!!

When i am using String to Spreadsheet function i observed that there is not effect of "format string" if i declare it as "%.1f", "%.2f","%.3f" and so on. whatever is the input format (Precision) the output will also be of same type. My input data an 2.33545,2.3566,8.56666. I specified "format string" as "%.2f" but my output was same as input. Is this really a bug or not. Anybody help me
Abhimaniu

It's also documented in the LabVIEW Help in the Format Specifier Syntax page:
For functions that scan a string, such as Scan From String and Spreadsheet String to Array, a format specifier uses the following simplified syntax elements.
%[Width]Conversion Code

Similar Messages

Bug? LabVIEW 2009 Enum in Datalog Refnum Loses Data in LabVIEW 2010+

Hi
Can I please get support from an AE?
Attached is a LabVIEW 2009 VI with a Control of an Enum in a Datalog Refnum.
Whereby the Enum's FP Object is represented as an image.
In LabVIEW 2009 this works fine however, in any higher version (I have definitely tested with LabVIEW 2011, but have been told LabVIEW 2010 is the same) the image is blank.
Is this a bug - is data being lost?
Interestingly enough, if I remove the LabVIEW 2009 Enum from the Datalog Refnum then load in LabVIEW 2011 this image displays correctly.
Is there anything I can do (setting? etc...) in LabVIEW 2009 that will correct this problem so it displays correctly in later versions?
This issue originated in this LAVA thread.
Cheers
-JG
Certified LabVIEW Architect * LabVIEW Champion
Attachments:
Datalog Refnum Enum_LV2009.vi ‏10 KB

This was reported to R&D (# 311354) for further investigation.
As a possible workaround, if you move the enum control out of the datalog refnum before saving in LV 2009, when you open your VI in LV 2011 the image will still show up for the enum control. You can then move the enum control back into the datalog refnum and it should work fine.
Thanks for the feedback,
Daniel H.
Customer Education Product Support Engineer
National Instruments
Certified LabVIEW Developer

Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

We have discovered an issue with the above listed software. Specifically this pertains to Print Report.vi in the Report Gen palette. Basically, we have discovered that with Office 2003 installed the VI will error out. We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft). With Office 2007 we don't have a problem. We've tried building the examples into executables, and those work because they are printing HTML reports.
Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly. Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

yeah, we had seen that, and been told about it by another user. we tried, to no avail. we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

Bug? LabVIEW-2009: Boolean wire missing some dots

I opened a VI from someone asking a question on this forum and noticed some missing dots on two boolean wires.
This was opened using LV 2009. It's an Evaluation installation (in case someone is wondering about specifics).
I minimized and maximized the block diagram and the dots were okay.
I don't know if this was already reported.
R
Message Edited by Ray.R on 10-08-2009 06:06 PM
Attachments:
missingLine.PNG ‏45 KB

Ray.R wrote:
LOL! Imagine all the people that would need help if we came up with wireless wires...
Of course we could also ask for underground wires that could be threaded below the diagram for some busy areas where they are not needed.
Message Edited by altenbach on 10-09-2009 02:07 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
WireTunnel.png ‏2 KB

BUG: LabView 2009 WebServer crash

Here is a simple VI containing no controls, functions or libraries in LabView 2009 f3.
WebServer
settings are default. After Tools->Web Publishing Tool operation
from other PC we are connecting to this panel (IE6 for example) and
putting a finger to F5-button not raising it.
Web page with the VI is refreshing continiously.
There are 3 results.
1. In DevEnv: LabView die.
2. In DevEnv: Need to restart LabView so WebServer reloads and connection restores.
3. In App.exe: die
4. In App.exe: LabView interpreter loose some while-cycles in case they exist but connection stored.
5. In App.exe: connection lost but the application working good.

Link to original post
Justin Parker
National Instruments
Product Support Engineer

LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.
Attachments:
Connector pane.PNG ‏4 KB

Troy K wrote:
I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
So you must be using crazy non-standard connector panes, or you would not have discovered this bug. Right? Actuall this is a good catch for it to go unnoticed for this long.
- tbob
Inventor of the WORM Global

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing. Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO. I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
So far, so good. After much fighting with Windows 7 network location settings, I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
Any advice will be greatly appreciated.
Kevin
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
Export the variables from the master library as a csv file and copy that to the remote machine.
Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
Find the network path column (it was "U" in my file).
replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
NOTE the single quotes around the process name; they are required.
The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
Once the formula worked on line 2, I could copy it into all the other lines.
Save the CSV file.
Import the CSV into the remote library to create the variables.
Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
Open the properties for the first imported variable.
There is probably an error message at the bottom saying the alias is invalid.
In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
Change the setting to "PSP URL" with the same path and the error message should disappear.
Close the properties box, save the library, and then export the variables to a new CSV file.
Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
The first one is NetworkingleWriter; it should already be FALSE for all lines.
The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
Save the edited CSV file.
Go back to the remote library, and import variables from the just-edited remote library CSV file.
Once you have imported them and the Multiple Variable Editor opens, click on done.
You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
It actually took longer to write out the process here than to perform these steps once I figured it out.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

Enum in a Typedef Reverts to Default (LabVIEW 2009)

When I add additional items to a typedef'd enum, constants of that enum on some BD's revert back to the default zero index enum value. In the past (8.6.1 and previous), adding items to an enum in no way would ever change constants that were already dropped on a BD. Now, in LabVIEW 2009, when I add items, about 60-70% of the constants dropped on different block diagrams will be changed to default value.
This happens in a "large" enum (~400 elements) that spans about 3 dozen VI's between RT and HMI block diagrams (a total of about 300 instances). This is a mature project that has never had this problem with 8.2, 8.5, 8.6, or 8.6.1...
I cannot post an example, because in the process of stripping down the VI, the problem goes away. It is extremely repeatable in the context of the project, but I cannot repeat it on an individual VI basis.
The current workaround is to edit the typedef'd enum while all referencing VI's are in memory. If the VI's that use the typedef are in memory, they will always properly recompile and maintain the correct constant value. However, if the VI is not in memory, and the typedef is changed, the next time the VI is opened, when it recompiles it will change the constants back to the zero index default value of the enum in only about 60-70% of VI's. Unfortunately, we cannot yet find a common thread in the VI's that recompile wrong, and the ones that recompile correctly.
Has anyone ever seen this problem? Suggestions?
Best regards,
Jack
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

We just realized a flaw in our "workaround", as partially pointed out by Ben (he was probably typing his response as we were confirming it here). If the constant is inside of a cluster on the BD, even if it is in memory, it will null out the enum inside of the constant. Therefore, the "workaround" is to rewrite the clustered enum constants from scratch (in other words, there's no workaround). Two of us spent a decent portion of the morning finally nailing this as the source of what we thought was an unrelated bug... and that's after spending a long day yesterday trying to find a fix. Yes, we feel Ben's angst of reverting back to previous SCC editions and manually editing dozens of VIs.
The severity of this bug is a showstopper for us. We cannot risk adding elements to an enum and consequently have referencing VIs changing their constants.
Force compiling a VI one at a time is not an option for us. I know this bug manifests itself even after a mass compile. So, is there a way to "mass force re-compile" that we could test?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Error in ni visa control out for usb in labview 2009

Hi,
I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface.
the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL OUT.vi gives error "0xBFFF003E : Could not perform operation because of i o error.". while the control in.vi works fine in both the labview versions and any other PC that i tried.
I have run the application in total of 4 PCs with same set of cards/interfaces. two of them having labview 8.6 are running fine and giving no error but other two with labview 2009 are giving error.
and it doesn't stop here.... i searched in the vi and did some experiment and found that when i give Request value input to control out.vi as "0x36 "(as required by my PIC program) then it is giving error but when i give other value such as " 0x35 or 34 or 55"(used for other purpose) then it is not giving error.
Can it be a PIC programming problem? (i dont think so as everything is fine in other PC with LV 8.6)
I have already explored the ni forum for this error solution but could not find helpful.
Can anyone solve my problem?

I installed labview 8.6 in that machine and made a small program with only 3 vis (visa open session, visa close session and visa usb control out.vi) which is working in LV 8.6 platform.
Sorry the above statement is not correct actually.
When i run the program in LV 8.6 it giving that same error but this time it is not displayed as pop up window. so i could not judge that error was still there.

Serious Bugs in LabVIEW 2011

Dear Sir or Madam,
I have been working with LabVIEW for 10 years.
recently I have istalled the last version (LabVIEW 2011) and encountered some fundamental Bugs as bellow:
1-when I want to close LabVIEW 2011 Platform,it taks about 3 sec time to be closed ! while this was not in earlier version such as LabVIEW 9 sp1.
2-In a typical Front Panel,when I press Ctrl+M to chenge to Run mode,it went but after pressing Ctrl+M again,it will not exit from run mode(THIS BUG HAPPEN SOME TIMES NOT ALWAYS) or when I do right-click to view Function pallet or Control pallet,nothing happen!(THIS BUG HAPPEN SOME TIMES NOT ALWAYS).
I will be happy if you tell me what is the reasons and can I trust on LabVIEW 2011 for big projects or It is better for me to used LabVIEW 2009 as the past.
thank you for your kind attention.
Regards,
Ata Rahai,
Specialist Engineer.

Hi
I believe that 2011 is a very stable version (I was beta testing) and in my system the CtrlM works both ways, always.
Taking a few seconds to close is normal since version 8.0, depending on how many services are running. LV does clean up the system.
greetings from the Netherlands

Cannot find older CAN-2.0 .vi's in labview 2009

Hi,
I'm trying to use a (rather old) Series 1 PCMCIA-CAN/2 card in Labview 2009.
I've installed latest NI-CAN driver that supports this old card (NI-CAN 2.0, I think), but I don't see any of the can.llb vi's in the functions palette. The CAN-2.0 documentation says it supports Labview versions "6.1 and later".
Will Labview 2009 support this driver? How do I get CAN-2.0 vi's to show up in the function palette?
Thanks,
Phil (labview newbie)
Message Edited by phil___ on 01-30-2010 03:09 PM
Message Edited by phil___ on 01-30-2010 03:10 PM
Solved!
Go to Solution.

I found the relevant .vi's in the "Labview 6.1/vi.lib" folder of the "National Instruments" directory.
The vi's I was looking for now show up in the addons section of the function pallette.
Thanks,
Phil

Excecutable VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly

Dear all,
I have a VI which runs perfectly and I can control, a Keithley 2612A for transistor measurements.
The VI run well when I excecute it from the computer which has the platform Labview 2009 (XP OS)
The equipment (ie Keithley 2612A) is linked to another computer which don't have labview 2009.
I installed Run-time-engine 2009 (OS XP 32 bits) on this computer.
Then I create an excecutable of my VI with the "build application" option.
The excecutable VI starts normally on the computer but when I want to run it, I am getting an error message from the Keithley 2612A (which was not the case when I ran the VI directly from the computer haing Labview 2009 installed on it). The error message is 222 (ie parameter too long)
I thought that I did something wrong and I create an excecutable from an original VI from Keithley (ie without any change). I am getting the same error message.
When I create an excecutable with run time engine 2009 included (as it is possible to do it wiht LB 2009) , I am geeting the same error message.
So I need no to check step after step when the message happens but
Does anyone knows anything about such an issue ?
Thank you
Solved!
Go to Solution.

Dear all,
Just for those who might encounter a similar issue.
I found the solution after tackling all possibilities.
The source of the problem was (for unknown reason) that the country setting of the computer was wrong
and decimal numbers were written with a , instead of a point.
Since I reset correctly the country setting, the stand alone files are running normally.
Best regards
Youki

How to install Labview 2009 on Windows 7

This might be a Windows 7 configuration. I tried "Run as administrator" or Run in Compatibility mode" the setup.exe file. Windows 7 does not allows to copy files in the System32 folder, so I can't install Labview.
Is somone can help to install Labview 2009 on Windows 7?
Thank you

Seems as though you're seeing something different than what I first thought.
LabVIEW should install to a drive other than "C" without trouble.
I had a look around to see if anyone else had seen this problem, and I found something interesting here: http://windowstipsandfixes.blogspot.com/2008/10/error-1310-cant-write-to-configmsi.html
Specifically with regards to resetting the Windows installer with the following:
msiexec /unreg
msiexec /regserver
Other than that, I'm not sure what might be causing the problem you're seeing.
Patrick Allen

NI Goop Wizard not working with LabVIEW 2009

I have added the NI Goop Wizard using VIPM (VI Package Manager) into my LabVIEW 2009 SP1 installation however it is not working. Whenever I select Create New Class from the drop down (same applies to menu selection) nothing happens and the drop down returns to it's default selection. I have tried this on 2 PC's both with 2009 SP1 installed, both exhibit the same unwanted behaviour. One of the PC's also has LabVIEW 8.2.1 installed also with NI GOOP Wizard and this installation works fine.
Anybody using GOOP Wizard with 2009 ?
Cheers
Chris
Don't forget to give Kudo's for a good answer !
LabVIEW Champion
Certified LabVIEW Architect
Certified TestStand Architect

Hi there Chris,
Off the top of my head it's my understanding that NI GOOP wizard is legacy software that was made redundant by the native GOOP tools in LabVIEW 8.2.0 and later.
In light of this it's a bit confusing that everything is working fine with 8.2.1 for you. Is there a version to the NI GOOP Wizard that you are using?
I had a search across the website but I'm afraid I haven't found any other examples or poeple using the GOOP Wizard in LabVIEW 2009 or 2010.
Kind Regards.
Rhys
Applications Engineer
National Instruments

I found a bug In LabView 2009!!!!!

Similar Messages

Maybe you are looking for