Labview 2012 sp1 Linux No Help ?

Hi all, my help is not working in Labview 2012 sp1 (Linux edition).
I keep reading that i need to change a .lvbrowser file, but this file does not exist anywhere on my system ( i have searched everywhere). When i first selected help it asked me to select a browser ( i chose firefox), but now when i click help nothing happens...
Any ideas?

Hi,
It sounds like the help file may not have been installed whenever you installed LabVIEW. I would try reinstalling and be sure to install any help file listed in the command prompts.
-Erik S
Applications Engineer
National Instruments

Similar Messages

Can I get MJD (date and time) in LabVIEW 2012 SP1?

I need to time stamp my data before sending it to the file. I have been doing this with the standard calendar date and time but MJD is what we prefer to use. How can I get an MJD timestamp in LabVIEW 2012 SP1?
Solved!
Go to Solution.

Hello Brad_Henry,
The Format Date/Time String will return the day of the year when the %j argument is used, as per this help document:
LabVIEW Help: Format Codes for the Time Format String
http://zone.ni.com/reference/en-XX/help/371361J-01/glang/codes_for_time_format_str/
If you're looking for the actual MJD, I'm not aware of a built-in function that generates this so you'll probably need to create or find a function to calculate it manually. This should pretty basic arithmetic, and it looks like people have already made a few public examples, the first two search results here look to be just about what you need:
ni.com search:
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:ex/q/julian/
Regards,
Tom L.

Measurement Computing USB-DIO96H driver issue with Labview 2012 SP1 on Windows 7 x64

Is anyone else having issues with measuremetn Computing's USB-DIO96H driver in Labview 2012 SP1. It throws warnings in Labview when loaded that are unresolvable as you can't save to the DLL driver file. Also it regularily crashes Labview randomly. I am not impressed with their driver. Anyone have any suggestion other than replacing with NI-DAQ solution, which I am working on?

I've taken a look and I don't see any drivers available for that device on ni.com. There are two potential workarounds that would both involve building your own driver:
1. Write a LabVIEW application that calls functions on the DLL you downloaded from Measurements Group
2. Write a LabVIEW application that addresses the device using NI-VISA and serial communication.
Some resources if you choose to go down that path:
http://www.ni.com/devzone/idnet/development.htm
http://www.ni.com/white-paper/3271/en/
http://www.ni.com/white-paper/3009/en/
Hope this helps!
Rob B
FlexRIO Product Manager

Vlm 3.0 LabVIEW 2012 SP1 disabled in Installer

Hello folks,
i have a Problem with die build Installer with my new updatet vlm 3.0.
I already get the the new license file for vlm 3.0 and installed it, then i made the installer for
LabVIEW 2012 SP1 like i have done it with the previous versions of LabVIEW 2009 2010 2011
In the produkt list of the installer LabVIEW and the DriverDVD is disabled by default (see Screenshot).
Solved!
Go to Solution.

Today i was looking on the server and i have seen that the licenses are LabVIEW 2012 licenses.
I want to install LabVIEW 2012 SP1.
So that's normal, i think i have to wait until i get the new license file for the new version.
Thanks BRennhofer for this idea.
I will report here.

Force LabView 2012 SP1 f4 patch installation

Hi,
it was necessary to repair my LabView 2012 SP1 installation. When I start LV now
it has the version 12.0.1. I had installed also f4-Patch. When I try to install the f4 patch
now after my repair installation it doesn't work.
How can i force the installation of LV2012 SP1 f4 patch?
Regards

Hi Chris,
no, i don't get any error message. The installer told me only "nothing to update" as text message
inside of the installer window.
1. i have had installed LV 2012 SP1 f4
2. than LabView crashed sometimes
3. than i made a repair installation of LabView 2012 SP1 (from DVD)
4. tried to install the f4 Patch afterwards (as download and via update service, tried both)
I don't know where the patch setup gets it's information about
the installed LV 2012 version, but it seems that a repair installation
doesn't reset that information and let that info still on patch level f4.
However, i deinstalled all developer editions and removed everything from
NI and reinstalled my developer editions. That was, for me, the only way
to get my LabView back on patch level f4.
I didn't find any setup switch to force the installation (the info was shown with "/?" as parameter)
Stefan

Labview 2012 SP1 f5 halting on Win 6 x64

I am using the latest Labview 2012 x64 SP1 with f5 update and am finding that it halts and forces me to close labview and restart. Anyone else having the issue or knows what might be causing the issue?

I regularly get 2012 SP1 f5 shut-downs but these tend to only occur when I am working on a project with a nested LVOOP hierachy and I'm making changes to that hierachy.
I don't know what activities you are doing that cause the re-start but it might help to know what you are working on when it happens; or post your LV internal error report to NI (I assume NIER is doing it's job).

LabVIEW 2012 SP1, Can't get correct mechanical action on boolean buttons

I am trying to use boolean buttons and events to programatically change the properties of a graph. I basically want to click a button on the FP, and have the graph change the desired property. All the property changing is fine, but I am really struggling with the mechanical action of the buttons.
I'll preface this by apologizing that I cannot post my code, as the computers with LV installed are isolated. My code is basically OK buttons, a while loop, and an event structure with a value change event for each button.
I want the user to click and release the button. After the click and release, I want the button to be in the same state it started, and I want the value change event to only trigger once. Sounds to me like I want the Latch When Released mechanical action. The problem is that this isn't working. I cannot create buttons that behave like this. None of the 6 mechanical actions exhibit the desired behavior.
To make matters worse, I have two OK buttons both set to Latch when released. Both buttons are True before the click. One button behaves as intended (button is true again after the click and release) and the other button doesn't switch back. I tried to copy the correctly working button, but still the copied button does not work the same as the original. Both buttons fire a single value change event, dispite behaving differently.
To answer the question "Where did I get the working button from?" A while back I made a simple button test vi that tested all 6 of the mechanical actions and kept track of how many times they fired a value change event for a single click. My buttons worked when I made this vi...eventually, i remember having trouble with this back then too. The results of that trouble had me using switch until released buttons with mouse down events for a long time, until I got the button test VI working properly and learned how buttons actually work. But now buttons are being funny again. I tried to copy working Latch when released button into my current program, but for some reason only one of the two copied buttons work as intended, despite them being copies of the same button.
Is there some bug in LV2012 SP1 (64 bit) where mechanical actions don't work consistently? Am I just being dumb? I'm sorry I can't post the code. I have this issue on both Windows 7 and Linux.
A bit more info, as I wanted to make sure I tried eveyrthing before posting. I tried to make a new button test VI. The old one still works, but I cannot get the buttons in the new button test vi to behave the same as in the old one I made. In the new one, Latch when pressed behaves the same as switch when pressed, and latch when relased behaves the same as switch when released. Switch until released and latch until released behave slightly differently. They both fire two value change events, but SuR actually switches twice (there and back again), where LuR just switches state once but still fires two value change events anyway. I have checked to make sure the mechanical actions are set properly at least a dozen times.
Pretty confused over here. My old button test vi works as I expect it to, and the Latch when released button works like I want, but I can't for the life of me reproduce it.

To Bob_Schor
I realize the folly of mouse down events, and I'm trying to move away from them. I originally started using them because I couldn't get the desired button behavior out of value change events and any other mechanical action.
I use LabVIEW 64 bit because I was hitting the RAM limits with the 32 bit version. I hit the limit when I try to plot a great deal of data in 3D, which I do fairly often. I get away with this because I don't interface with any equipment or use any of the specialized modules, but maybe I should consider only using 64 when it's absolutely necesary and get 32 bit on there as well. But I have the same issue on Linux, which only has a 32 bit labview version (still 2012 SP1)
There is only one event structure in the program. I have two buttons because I'm just using them to fire two separate events. My current situation is that I am plotting 9 plots on a single graph. One of these buttons is a "check all" button for the visibility check boxes. I click the check all button, and all 9 plots become visible. The other button is an "Uncheck all" button, which does the opposite.
That's for my current program. I also have a button test vi which has 6 boolean buttons, each set to a different mechanical action. A single event stucture in a while loop has a value change event for each button. I made this so that I could see for myself how the buttons worked (i.e. I see that the switch when released mechanical action produced two value change events.). I have an old version of this program which works as I expect it to. This morning I tried to remake it (it's very simple) and it does not behave the same, despite the block diagram being pretty much identical. I described the differences in the OP.
I can reporduce the behavior on a second computer that is restricted. Which is 32 bit labview for Linux. I don't have an unrestricted machine with LabVIEW installed. If I did, I would have tried to rebuild my button test VI (again) to see if it works.
At it's most basic, create an OK button on the FP and set in the True state. It defaults to the Latch when released mechanical action. Throw an event structure in a while loop. Give the ES a value change event for the button. In this even just increment some counter to indicate how many times the value change has been triggered. I did this using a shift register. Run it. For me, when I click the Latch when released button it fires one value change event and doesn't reset to true when after the click. I can change the mechanical action of the button, and none of the 6 give me what I want.
So my issue just boils down to Latch when released not behaving properly.
In my original button test vi (which was this with 5 more buttons and 5 more value change events in the ES), the latch when released button DOES reset to true after my click. Copy and pasting this button creates a new button which does not behave the same way, despite still being set to latch when released.
My problem is not so much with the events, but the behavior of the button. Am I correct that Latch when released is what I want? A single click, and the button fires one VC event and returns to the same state before the click?

LabVIEW 2012 SP1?

Is there a plan when or if LV2012 SP1 should be released?
Labview 2012 f5patch was released on 2013-01-05.
Labview 2013Beta was announced for one week.
Labview 2011 SP1 was released in December 2011.
I expected 2012SP1 in December2012 or January 2013. We are now February 2013 and I cannot find it...
Will 2012SP be skipped?

I had an application working fine withe LV 8.5 FDS
I migrated to LV 2012 PDS yesteardy in since that time at any restart of the PC , when I lanch my appplication I get a message of the installer and then an error otf the MIcrosoft Installer
As you can see in the attached word file, the window event log tell that cwdss.exe.manifest does not exist
It is the case , but I llok to another thread of ni.com called
Why Does DataSocket Server Fail to Launch After Installing LabVIEW 2012? it is told to supress this file ....
So What should I do ?
For information on other PC where no Pb occur , the cwdss.exe.manifest does exist
Attachments:
Journal Evenement associé au PB Msg Installer.doc ‏161 KB

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

LabVIEW 2012 SP1 takes ages to install

Just wondering - why on earth should the SP1 patch to LV2012 take 45 minutes to install on a 2.8 Ghz multi core PC with 8 GB ram ?
I get a feeling that I am saddled with quite a massive amount of unwanted universal stuff - like the zillion printer drivers that install with a Windows OS - just so that it can be called plug and play !
Gone are the days when programs used to come in minimum foot print code ;-)
Raghunathan
LV2012 to Automate Hydraulic Test rigs.

Raghunathan wrote:
Just wondering - why on earth should the SP1 patch to LV2012 take 45 minutes to install on a 2.8 Ghz multi core PC with 8 GB ram ?
I get a feeling that I am saddled with quite a massive amount of unwanted universal stuff - like the zillion printer drivers that install with a Windows OS - just so that it can be called plug and play !
Gone are the days when programs used to come in minimum foot print code ;-)
I'm sure this post was just a rant to vent some frustration, but I'm going to take it at face value, hoping this doesn't annoy you.
LabVIEW has always taken a long time to install. I remember having the task of installing the new fangled LabVIEW 6.1 on our machine and mass compile our reuse library. I was told it would likely take a couple days. I was pleased when I did it in one day. The install took many hours and I think it was done around 2 or 3 in the afternoon. This was without any toolkits or add-ons just LabVIEW and the Device Drivers. Then I set it up to mass compile our library and I'm unsure how long into the night it took but it was done by morning.
I've gotten good a streamlining the process of setting up a development environment. When a new set of developer suite DVDs come in I combine them so it doesn't prompt me to swap disks during the install. I do still get prompted for the Device Drivers after the Developer Suite is installed. Then I have a VI Package Configuration in Package Manager which install all internal/external reuse, add quick drop shortcuts, templates, LabVIEW.INI settings, and other settings with just a single prompt at the start.
It isn't fast by any means, but I'd guess I can go from a fresh Window image to having a PC setup, including a SVN repository checkout in 3 hours or so.
Oh but I do appreciate a minimal footprint program. I heard Doom was originally written in assembly. And that the full binary of Doom 1 takes up less space on disk, than a save file of Doom 3. Also .kkrieger blew my mind when I first saw it in 2004.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Lot of bugs & Crash labview 2012 SP1 in Table control

Run applied vi.
We see lot of bugs in Table control. I fixed some on the right table, but not all.
How fix other?
Thanks in advance, Alex.
Attachments:
NI_BugReport_in_Table.vi ‏30 KB

The attached modification includes a workaround for the ctrl+z bug on the Data Mixer (Not Table). It basically keeps a history of your deleted headers and adds them back in when the user types ctrl+z. Not the most elegant solution, but gives you an example of what you can do to work around it.
You could clean it up by using functional globals instead of shift registers.
www.movimed.com - Custom Imaging Solutions
Attachments:
NI_BugReport_in_Table (Modified).vi ‏49 KB

Cannot activate Labview after update to 2012 SP1

Hello
I just updated from Labview 2012 Spring edition to Labview 2012 SP1 as suggested by the NI Uodate Service, and when it came to activate the product, the activation wizard tells me that the serial number does not match the software. I don't have any other serial. It is an academic license.
Thank you in advnace for your help
Regards
HelderC

nyc wrote:
SSP = Standar Service Program http://www.ni.com/services/software_benefits.htm
Here is NI's webpage about LabVIEW 2012SP1 http://www.ni.com/labview/release-details/
LabVIEW 2012 Service Pack 1 is an exclusive update to LabVIEW 2012 for NI Standard Service Program (SSP) customers. There are no new product features introduced in service pack releases; instead, these releases provide bug fixes and improved stability for LabVIEW 2012.
In my opinion, bug fixes for a specific release such as LabVIEW 2012 should be FREE; NI has chosen to be yet another greedy company.
I have to agree. Your words were more opinionated than mine, but yes, I agree with you.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

Thanks for the info, Kyle. I will probably try to find an older 32-bit XP machine. VM is just not an option for me right now.

Hello everybody,
I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit. I am able to compile the example code for LED shift. I am however unable to transfer code to the FPGA. I get the following error message:
Error Code: -310602
NI-COBS: Unable to communicate with device over communication cable.
Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
My system configuration is as follows:
Windows 7 (64 bit) on Dell XPS laptop.
Labview 2012 SP1 (32 bit)
Labview FPGA 2012 SP1
Labview 2012 FPGA support for Spartan3E
Xilinx 13.4 tools
DEFB LV FPGA 2012sp1 support installer
Xilinx USB cable driver v1.3 installed.
I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly. I even uninstalled and reinstalled the entire Labview software set I had. I still get the same error.
A few other questions:
1. Is the Xilinx cable different from a regular USB cable of the same configuration ?
2. When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board. Should any other cable be connected ?
3. What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
I have been at this or over 3 days trying to figure it out. Any help will be greatly appreciated.

Labview 2012

I am developing the application using labview 2012 with pci cards 6514,6221.
When I run it from design, it blinks (finished late occurs) whenever tries to output digital or analog signals with scan of 10ms. There is no blink happens at all try to save this project in lv2009 and runs.
So I would like to know whether lv2012 is creating a problem or is it needs any patch exe has to be downloaded to make it for stable run. I just thought and downloaded f5 patch too, but it says labview 2012 sp1 must be installed before installing this patch. I am not able to locate the lv 2012 sp1.
Any help is appreciated.
Thanks
Kousy

Kousy,
your information is indeed quite vague.
LV 2012 SP1 is a separate version and therefore not simply to download.
Regarding your observations:
Runtime performance is affected by many different things. As NI made some significant changes to the compiler between 2009 and 2010, i would expect your issue to come from those.
One little thing you can check for further testing: Disable debugging for your VI(s) before looking on "finished lates" of timed structure.
Also please make sure that priorities of timed structures are unique (no default 100!).
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

LabView 2012 Security System Main vi's have error 200559

The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step
is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current
version of LabVIEW. http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
I appreciate help from any one.
Ali Tariq Bhatti
Ali Tariq Bhatti
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
NI ELVIS II Security System VIs (2).zip ‏313 KB
Error 200559.docx ‏500 KB

RavensFan,
I) Yes, I open up the front panel of the Express VI's and probe into them.
2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
did probes for Export Press and Key vi's file.docx ‏340 KB

Labview 2012 sp1 Linux No Help ?

Similar Messages

Maybe you are looking for