Labview 2012 DLL bug need solution

DLL initialization routine failed error for lvanlys.dll..........Should be located in resource folder
When you place a sinewave generator vi on a vi call library function node error: library not found or failed to load.
Have viewed LV bug list. Did not find this bug.
Can you provide a patch to fix problem. Have all updates and problem not solved
Regards
Michael Ryan

I must not have your toolkit....
All I see is "Sine Waveform.vi", there is no "Sinewave generator vi" in sight anywhere (see image). Are you really sure about that name? In any case, nothing in that palette generates any errors for me.
You did not say if you tried to repair your installation. What is the exact make and model of your CPU?
When you installed LabVIEW, did you use the default installation locations or did you "personalize" for lack of a better word? Were there any problems during installation? Did you reboot after the installation? What other NI software is installed?
Have you tried other functions? There are plenty of function that use lvanlys.dll. Do all the other functions still work fine? (for example try "A x B.vi" form the Mathematics...linear algenbra palette).
Do other labVIEW program run fine?
wetland wrote:
If it works for you then you are lucky. This is my first bug l have found
This has nothing to do with luck, because in my case everything works exactly as intended. Luck only plays a role with bugs that only occur once in a while when trying to reproduce the problem, but in your case it seems 100% reproducible on your system.
I still seriously doubt it is a bug (and I probably have found hundreds of real LabVIEW bugs over the years ). If it really were a bug, you could post a link in the monthly bug thread. Is is checked regularly bi NI.
To be a confirmed bug, it needs to be reproducible by others (and also by somebody at NI).
To help out, I have tried hard to reproduce your problem, but since your instructions are insufficient and ambiguous it is still not possible. You need to give much more detail!
Does LabVIEW create a crash report? Is there anything interesting in the Windows 7 event viewer?
Have you checked your computer for viruses and malware? What antivirus program are you using (maybe it triggers a false positive reaction on this file).
LabVIEW Champion . Do more with less code and in less time .
Attachments:
SineWave.png ‏18 KB

Similar Messages

XYGraph Cursor legend bug instantly crashes LabView 2012

Hi!
I am just facing a very annoying bug.
Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
It instantly crashes my LabView 2012 Full version: 12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
Anyhow, very strange and annoying behaviour...
Anyone could repeat the same bug?
Thanks for support!
Solved!
Go to Solution.
Attachments:
XYGraph_bug_test1.vi ‏149 KB

hello,
please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
thanks!
Attachments:
cursor_offset_label_via_propertynode.vi ‏12 KB

LabVIEW built DLL's in a multi-threaded C++ app, Help Needed!

I'm working on a software application that is being developed
primarily in C++. There is a component of this larger application,
however, that is being developed in LabVIEW (for several reasons that
I won't dive into here). This LabVIEW code is therefore executed
within a C++ wrapper class that calls a LabVIEW built DLL.
All this was fine and dandy, untill we decided to multi-thread our C++
application. As a result, the LabVIEW DLL now gets called from
multiple threads simultaneously. From all of my testing, it appears
that resource locking is occuring such that only one thread has access
to the .dll at a time. If I make the .vi used to define the dll
function prototype as non-reentrant then this is what we see. As an
example, say we have 3 threads all calling the same .dll method call.
Thread 1, 2, and 3 all call the .dll within a few milliseconds of each
other. Thread 1 completes the .dll call after X milliseconds. Thread 2
completes the .dll call after 2X milliseconds, and thread 3 completes
after 3x milliseconds.
Now, changing the vi to reentrant, and running the same test, we see
Thread 1, 2, and 3 all complete the .dll call in 3x milliseconds.
While the fact that they now take the same amount of time to complete
would lead you to believe they are happening in parallel, the fact
that it takes 3x milliseconds as opposed to X milliseconds means they
are not.
Has anyone ever dealt with these issues before? Is it possible that
messing with the "execution system" for the vi will have an affect?
What if different .dll methods but still attached to the same .dll are
called from different threads? Same behavior? Is it a lost cause? Is
there no way to make code within a single LabVIEW built .dll run in
two different threads at the same? From what I understand this is
easily doable with a normal (non-LV built) .dll.
Please, if anyone has any advice in this area, let me know!!!
Much appreciated,
Jesse Hurdus

Duplicate post.

Labview 2012 (64bit) not working with ActiveX and MSAccess

I have a program developed to open a MSAccess database file and import data using ActiveX commands. The program works with LabView 2012 (32bit) but fails on the ActiveX open command when using LabView 2012 (64bit). I also have the application built as an EXE and it works fine in a windows 32 bit environment (XP or Win 7-32bit) but fails when run on Win 7-64bit. I isolated the error down to the Active X automation Open VI.
Anyone have a solution for the incompatibility?
summary
1.) VI and EXE works on XP and Win 7-32bit
2.) EXE fail on Win 7-64bit.
3.) VI works on Win 7-64 bit with LV 2012 (32bit)
4.) VI fails on Win 7-64 bit with LV 2012 (64bit)

It looks like you are trying to load a 32-bit DLL from a 64-bit OS. Do you have a 64-bit version of access installed? You'll need to change to that. On the other hand, ActiveX with Access is so slow. You can speed things up considerably by using ADO (i.e. NI's Database Connectivity Toolkit or something like LabSQL).

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.

Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

Hello,
I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
I'm confused; did I accidentally install LV 2011 too?
Thanks
Solved!
Go to Solution.

Also, some addons use older RunTime Engines. It is not suprising that you need the 2011 RTE patch.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

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

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

Convert TCPIP_Nagle_algorithm.zip from LabVIEW 2012 to LabVIEW 2011

Hello,
can somebody convert the VIs in the zip file from LabVIEW 2012 to LabVIEW 2011 please. I need them to study.
Thank you very much for your support.
Solved!
Go to Solution.
Attachments:
TCPIP_Nagle_algorithm.zip ‏63 KB

Additionally I am sorry that I have put my post in LabVIEW and not under Version Conversion

Exe created with labview 2012 won't run using LVRTE2013

I created an exe using Labview 2012. I had the user install the latest rte (lvrte2013). The exe would not run and told the user it needed 2012 rte. Do users have to have the same rte for each exe?
Solved!
Go to Solution.

Yes. But the various RTEs can coexist on the same PC.

CRASH: Replacing enums in statecharts can bring LabVIEW 2012 down

Environment
Windows 8 64-bit, LabVIEW 2012 32-bit
Steps to reproduce
Open the attached project
Open Statechart.lsvc/Diagram.vi
Double-click on the blue Transition in the middle, navigate to Guard
Right-click on the enum constant -> Replace -> Select a VI...
Choose "Enum 2.ctl"
The "Select the VI to Open" dialog pops up again. Select "Enum 2.ctl" again
Observe first weird behaviour: The Guard block diagram is replaced by the enum's front panel
Click "Cancel"
Double-click on the blue Transition again. LabVIEW crashes here.
Error messages
I first encountered this in a large project with a complex statechart. This was the message shown before LabVIEW died:
With the small example I attached, there was no message at the time of crash -- LabVIEW just aborted silently. When I restarted, it showed (tested twice, same message):
Solved!
Go to Solution.
Attachments:
Statechart Crash.zip ‏138 KB

Hi JKSH,
Sorry for the incorrect post, I was talking with one of my colleagues on this issue. I was able to reproduce the issue on Windows 7 32-bit and LabVIEW 2013 (32-bit). I filled a bug report (called a Corrective Action Request or CAR) on the issue. The CAR number is 421985. You can use this to track when the CAR will be fixed as there will be a list of resolved CARs in the release notes. I also wanted to post that the workaround for this error is to just add the VI manually and then delete the original VI (as opposed to using the replace feature).
Thanks for helping find this bug.
Thanks,
Best Regards,
Bill
Notes for Branch AE:
Please reply to This Post within 24 hours
The US AE is expected to reply to all of your posts within 24 hours. Having this expectation will keep the escalation moving quickly and toward a fast resolution.
You can also use other communication channels: Phone, Sametime, Lync,etc. to discuss the issue with the US AE. This can help with troubleshooting and quick diagnosis of the issue.
Click here to provide kudos for a post on this page

LabVIEW 2012 while event structure cannot stop

I am trying LabVIEW 2012.
An example of while-loop with Event structure inside cannot be stopped with the boolean stop button. Any thing wrong?
Please see the attached VI.
Thanks.
Solved!
Go to Solution.
Attachments:
Close VI prompt.vi ‏9 KB

Yep, something is wrong. You need to add a event case to detect a value change on the stop button.
The thing is now your event structure keeps waiting for one of the event that it handles, and ight now it only handles the "panel close" event, the "timeout" event is handled too but since you haven't connected anything to the timeout terminal (top left corner of the event structure) the timeout is -1. So when you run the VI the while loop is stuck in the first iteration and waits for a panel close, the stop button will only be taken into account after the even structure catches an event ; I think this is because LabVIEW will execute code linked to the stop terminal of the while loop only after all the rest of the code in it has finished executing.
Hope this helps
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Upgrade to LabVIEW 2012 caused Additional Installers issue

Hello again all you helpful forum-goers!
I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project. In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them. However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot). This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file. I need to have both 2010 and 2012 on my computer for the time being.
Does anyone have any idea what is going on with my system, and/or how to fix it?
Thank you very much in advance for your suggestions and time!
-Joe
Solved!
Go to Solution.
Attachments:
Additional Installers Blank Lines.png ‏45 KB

Hi Joe,
I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
jmorris wrote:
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
jmorris wrote:
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully.
One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
Please let me know if you have any additional questions/comments regarding these issues.
Regards
Doug W
Applications Engineer
National Instruments

Some fonts are not shown correctly in LabVIEW 2012

I found a bug related with fonts in LabVIEW2012 f3 KR.
- When I select NI7SEG in font selection dialog, right font is not shown in the example box.
- Draw text at point.vi shows same problem for some fonts while other fonts are working.
I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google.
So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK.
* OS: Windows 7 32bit KR

Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
- Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
- LabVIEW 2010 but on same PC shows correct fonts.
Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
(1st group)
Arial Unicode MS...
Bookshelf Symbol 3....
Windings 3
(2nd group)
@Arial Unicode MS...
@Terminal
(3rd group)
Arial...
Consolas...
Courier...
Licida Console...
NI7SEG...
Verdana

Labview 2012 DLL bug need solution

Similar Messages

Maybe you are looking for