Why does LabVIEW generate -0?

I have attached a bit of code that occaisonally generates a value of -0.
Solved!
Go to Solution.
Attachments:
negative zero.vi ‏7 KB

Darin.K wrote:
Jeff·þ·Bohrer wrote:
Run that one through again Mike! BOTH outputs are -0 (REALLY thats the correct behavior!)
There is something missing, both outputs should not be -0, and if they are that is really not the correct behavior. Max & Min is simply a comparison and a swap (ie. a conditional swap). In this case, comparing 0 and -0 should result in no swapping since they are "equal" by definition. The Max and Min should simply passthrough the values, one output will be 0 and the other -0 with the order depending on the order of the input.
At the risk of hijacking the thread - My oppologies to the OP
Go- ahead and debate it in the next IEEE conferance. I have at least as much disrespct for authority as Dr Kinion.! But, unlike (or maybe just like) Schroedinger and Heidelberg, I bow to thie wisdom of generating reproducalbe results- even if the results are technically incorrect. Math is funny- with computers its even "funnier" because it needs to ......
Too bad humans were not gifted with a random number of fingers.
Jeff

Similar Messages

Why does labview generate Dr. Watson error "C0000005 access violation"

I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
*----> System Information <----*
Computer Name: ANDANTE
User Name: Administrator
Number of Processors: 2
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
When the crash occurs, I see a dialog appear with the error
labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
The Dr. Watson error log is generated and the error is
Application exception occurred:
App: (pid=1160)
When: 4/25/2004 @ 01:57:56.640
Exception number: c0000005 (access violation)
I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
State Dump for Thread Id 0x574
eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: StrLen
00748230 55 push ebp
00748231 8bec mov ebp,esp
00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
0074823b 84d2 test dl,dl
0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
0074823f 8a10 mov dl,[eax] ds:00000062=??
00748241 40 inc eax
00748242 84d2 test dl,dl
00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
00748246 2bc1 sub eax,ecx
00748248 48 dec eax
00748249 5d pop ebp
0074824a c3 ret
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
*----> Raw Stack Dump <----*
0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....

For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.

Why does Labview allow a cursor in a indicator?

Hello,
Why does Labview allow the user to position the cursor with the mouse inside a numeric indicator? Users think that just because they can put a cursor they should be able to type something and enter data. Is there a way to disable/stop the user from putting the cursor in a numeric indicator?
Regards,
Kaspar
Solved!
Go to Solution.

Disabling the indicator satisfies your requirements, but this is funnier. It would be even better if I calculated the position of the indicator and the "entry point" and just kept the mouse from entering, but I have a project to finish...
Message Edited by jcarmody on 03-27-2009 11:58 AM
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
Attachments:
move.png ‏4 KB
test.vi ‏9 KB

Why does LabVIEW allow me to have 2 controls with same name

Here's a general LabVIEW question:
Why does LabVIEW allow me to have 2 controls with the same name in the same VI? It seems like this only increases the chances of confusion. Especially when someone is just looking at a block diagram (or documentation of a block diagram).
No other programming language that I know of allows this. I realize that uniqueness of name is not as critical in LabVIEW as it is in any text based language. For example, in a text based language, if I had 2 variables called abc and I wrote a statement
abc = 12;
the compiler would not know which abc was being referred to. In LabVIEW, if we had 2 controls called abc, the equivalent of doing an abc=12 is writing to a local variable (which is always linked to one of the controls) and there is no ambiguity. Still, someone looking at the code cannot figure out which abc is linked to unless he does a right click>>Find>>terminal (or a double click).
Even though I have never and never will name 2 controls the same, I think it would be a nice constraint to see enforced by LabVIEW.
Any input from NI engineers on this?
Message Edited by S G on 12-18-2007 03:38 PM
S G
Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor
Attachments:
Trial1.JPG ‏21 KB

I know when you copy and paste a control or indicator, LabVIEW automatically increments the label. But since you can hide the label, and show or hide the caption, there must be another mechanism that LabVIEW uses to keep track of all the controls. I thought I remember back in the "old days" (ver 6 or 6i) LabVIEW would give you an error if you tried to make two controls with the same name. Perhaps that was LabWindows/CVI.
I don't know where the index is actually stored, but if you look at a property node linked to the Pane, you will see an array of references to the controls and indicators. Since the references are stored in an array, I assume that any local variables are tied to the index of that array. Since the labels themselves are properties of the control, I guess there's no reason to limit what that label is. They all have a unique index number.
Interestingly, this array of references grows from the beginning. That is, any new control or indicator is put at index 0, not the end of the array.
B-)
Message Edited by LabViewGuruWannabe on 12-18-2007 08:45 PM
Attachments:
Labels.png ‏12 KB

Why does Contribute generate extraneous HTML code?

Why does Contribute CS4 generate so much extraneous HTML code that is either redundant or conflicts with styles specified in our style sheet? Below are examples of what we've encountered in the first two weeks of using the product. It seems that, if we keep using Contribute, our website will soon be cluttered with junk code. (Some of the special characters listed below and generated by Contribute do not display correctly in this forum.)
1. This simple Heading 1 tag: <h1>Heading 1</h1>
gets replaced with this code:
Heading 1 
2. This simple Heading 2 tag: <h2>Heading 2</h2>
gets replaced with this code:
Heading 2
3. This simple Paragraph tag: Text
gets replaced with this code:
 TextText
4. The standard straight quote symbol (") gets replaced with left and right quotes (“) (”)
5. Apostrophe’s get replaced with “’”.
6. Odd, non-visible (in some browsers) characters are inserted, like: “Â”.
7. Dashes get replaced with these special characters, which may not display in all browsers: “â€””.
8. This non-standard style tag gets inserted at the top of some pages:

</style>
9. Trademarks, which are reliably denoted with just ”™”, get replaced with this code and these special characters, which may not display in all browsers: “â„¢”.
10. The simple Heading 1 tag: : <h1>Heading 1</h1>
gets overridden with this code:
<h1>Heading 1</h1>
11. This simple Paragraph tag: Text
has the inappropriate “ServNAV” navigation style applied to it:
Text
12. This simple Paragraph tag: Text
gets replaced with this code:
Text
13. Extra filler space gets inserted at the bottom of a page with this code:
 
14. Internal links are created as absolute (<a href="http://www.company.com/subfolder/Client-One.html">) rather than relative links ()<a href="../subfolder/Client-One.html">.
15. Links to other sites are coded incorrectly,
as in “<a href="www.company.com">www.company.com</a>”
instead of: “<a href="http://www.company.com">www.company.com</a>”.
16. This simple bold Paragraph tag: About Company
gets replaced with this
About Company
17. This simple Paragraph tag: Text
gets replaced with this code:
Text
Message was edited by: JerryWeb

I've just written a detailed list of editing tips for our internal use that, in addtion to using "Paste Text Only", describe how to avoid or re-key Microsoft Office curly quotes and apostrophes, use only Contribute's Insert | Special Characters, etc.
In addition, I created a new role in which I made the following changes:
Under Editing, under“General editing restrictions”, checked the “Prevent users from inserting images (except shared assets); under “Paragraph spacing, changed so “Enter key moves insertion point down:” “Two lines, as in web page editors (uses standard tags”; under “Other editing options”, unchecked “Allow multiple consecutive spaces”
Under Styles and Fonts, under “Styles and Fonts”, unchecked “Include CSS styles in the Style menu; unchecked “Allow users to apply fonts and sizes”; and unchecked “Allow users to apply font color and background color”.
Under New Pages, unchecked “Create a blank page”
Our initial experimentation indicates this eliminates most of the extraneous and junk HTML code that Contribute otherwise introduces. Time will tell. However, it requires contributors to be pretty rigorous.

For Experts: Why does LabView cause System reboot while accessing hardware with driver?

Hello NI Developers!
I use LabView 7.1 under Windows XP
I have a programm console application which accesses through Jungo Windriver PCI-E board.
This program works fine - and performs DMA data transfer between PC and Board's memory.
In order to implement this console application work together with LabView I did following:
1) Added this function inside the source:
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
    AllocConsole();                   //Open new console window
   SetConsoleTitle(L"Debug Window"); //Set a title for console window
    freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                    // so we are able to see "printf" outputs
   freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                    // so we are able pass inputs from keyboard
   main();                          //Call applications main function which does all the work
2) Compiled this new source as DLL library
3) Call LVMainFunction(...) function from LabView using Call Library Node
In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
It works fine till the last function, which perform DMA data transfer - and reboots PC.
1) Why does this happen?
2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
   So does LabView have somekind of restrictions of accessing Hardware's functions?
I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
console window - and the result is the same.
3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
Thank you in advance!
ACiDUser
Message Edited by ACiDuser on 11-13-2008 09:37 AM

Hello!
At LAST!!!
I solved this problem!
From the beginning I was following National Instruments manual on how to build DLL with external IDE:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_library_project/
Set the Struct member alignment control to 1 Byte.
Now this option caused my PC to reboot!
So could someone explain why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
- wasting 2 monthes of time determining the problem.
I changed it to Set the Struct member alignment control to DEFAULT.
and now everything works fine.
Regards
Message Edited by ACiDuser on 11-13-2008 11:14 AM

Why does LabView crash when unloading my DLL (reentrant calls)?

I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine. All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
OR
Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
OR
Your DLL is only called from one, non-reentrant VI
OR
Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
Hopefully this information can help you out in some way.
J.R. Allen

Why does ADF generate referenced classes (FK) as Accessor not as Attribute?

Question is simple when ADF generates Entity classes, it does not generate referenced object as Accessor, not as Attribute and this causes problems on SelectOneChoice.
Is it normal?
Child Class : { id, name, parentObject } (ID and Name is generated as Attribute, parentObject is generated as Accessor)
Parent Class : {id, name}
When I create ADF Form for Child class, it only creates form for ID and NAME attributes, and ignores parentObject attribute. When I add selectOneChoice manually for selecting parentObject of child class, it does not update Child Class with mergeChild() action. Simply ignores?

There have been requests on this and currently this is not supported. (check this thread http://forums.adobe.com/message/2267567#2267567)
you can vote for the bugs for this to be supported in a later build / release.
https://bugs.adobe.com/jira/browse/FB-23156
https://bugs.adobe.com/jira/browse/LCDS-971
Thanks
-Sunil

Why does wrapping generate different results?

Hi,
I have a tex box that I am using as a caption for an image. Both the image and caption are laid out in a column of text and both objects use text wrapping for some breathing room from the body text. I would like to create a tad more breathing room under the text box but when I add a pixel to the wrap buffer it causes the body text to move an entire line away. In other locations within the document performing the same action causes the body text to move away from the text box incrementally in direct correspondence with the added buffer values.
Why does increasing the wrap buffer sometimes cause the body text to jump an entire line away and sometimes just inch away one pixel at a time?
Thanks,
b

Thanks for the prompt reply.
I uploaded a .pdf that includes callouts to explain what I am asking.
If I understand what you are saying, the example I cite where the text moves one pixel at a time derives from the fact that the wrapped object is located at the top of the column, whereas when the text jumps an entire line it is because the wrapped object is below the first line of body text.Correct?
Is there a workaround you can think of? Split the text frames so the object is at the top of the column? modify the leading slug or baseline grid behaviors somehow?
http://www.seawead.org/wrap2.pdf
thanks again.
b

Why does LabVIEW skip over commands in programming structures

Hello everyone!
Is there a certain way you program to make labview execute ALL commands within a loop before going into another loop? For example, I have a while loop that stops if either the stop button is pushed or if the set point input is greater than 8. If both of these are false, then the code entered a case structure where it controls the output from a plant model. However, labview will enter the case structure without checking if both conditions are met. I've attached the VI and in the next message will post the VIs from the plant. I want it to do the below code,
IF (Set Point > 8 OR Set Point < 0) THEN
SET_Point OK= False
ELSe
SET_Point OK = True
END IF
IF (SET_Point OK = FALSE OR Stop Button pushed) THEN
! STOP VI
ELSE
! Enter PID Control Loop
END IF
But labview likes to just jump around and skip parts for some reason. So when it for example, skips the OR check it uses the default value of true for the next case structure. It's driving me crazy. Can anyone please tell me why its doing this??
Thanks.
Solved!
Go to Solution.
Attachments:
General Auto PID Simulator.vi ‏83 KB
Global 1.vi ‏5 KB

Ah! I can't believe I made that dumb of a mistake. And thanks for the advice altenbach. My overcomplicated diagram probably lead me to making that error.
I have another question though. How come when I use the Write to measurement file VI it will start the process variable at like 40 inches but when I don't use it, it'll start it at 0 and do as its supposed to? I've attached my updated VI with the write to measurement file VI in it. You'll see that if you delete it then it'll do as its supposed to. I don't understand why though..
Attachments:
General Auto PID Simulator.vi ‏118 KB
Global 1.vi ‏5 KB
problem with PV initialization.JPG ‏132 KB

Why does labview close whilst my program is running?

I am running a program doing data acquisition using the PCI-6602 cards. Everything works fine but somehow after I have been doing acqusition and saving the data for approximately 2 days, I find out that the program has been stopped by LabVIEW and find all the windows closed including labVIEW. In my program I did not use any of the exit functions provided with LabVIEW but somehow, labVIEW exits by itself without issuing any error messages. Why is this happening?

I experienced a problem with LabVIEW 7.0 shutting down unexpectedly. It may be completely unrelated, but I thought I'd mention it just in case. My problem was that I was calling a DLL that used a reference handle. At the end of my test (using TestStand), the test closed, and thus the DLL was unloaded from memory as well. Because there was still a handle open to this DLL, LabVIEW must not have known how to handle this and shut down (or it confused Windows and it shut down LabVIEW). In any case, the solution was to have a VI stay in memory which calls this DLL, and put the DLL in a the true case of a case statement wired with a constant false. Thus, the DLL is never actually called by this VI, but it keeps the DLL in memory.
So if you call any VIs dynamically, etc., where a VI could be unloaded from memory, check those VIs and make sure you aren't leaving any references open or something like that.
Hope this is in some way helpful.
Tom

Why does Labview insert quotations in the case structure selector box?

I was building a case structure with an array of strings. So, I copied the strings from the array on the FRONT PANEL directly into the SELECTOR LABEL. My 3 strings have the form; to me, these are 5- character strings with spaces, or 7 characters if you count the spaces as string characters
A, B, C
A, B, D
A, B, E
So, when I copied and pasted them directly into the selector box A, B, C appeared as "A", "B", "C" and A, B, D appeared as "A", "B", "C" and then I got an error for selector values not unique. Why didn't it appear as "A, B, C"?
Why did it transform the string I pasted and insert the quotation marks? I used no quotation marks in my array. Does the selector label interpret commas as functional characters that require quotation marks??
Thanks,
Dave

dav2010 wrote:
I was building a case structure with an array of strings. So, I copied the strings from the array on the FRONT PANEL directly into the SELECTOR LABEL. My 3 strings have the form; to me, these are 5- character strings with spaces, or 7 characters if you count the spaces as string characters
A, B, C
A, B, D
A, B, E
So, when I copied and pasted them directly into the selector box A, B, C appeared as "A", "B", "C" and A, B, D appeared as "A", "B", "C" and then I got an error for selector values not unique. Why didn't it appear as "A, B, C"?
Why did it transform the string I pasted and insert the quotation marks? I used no quotation marks in my array. Does the selector label interpret commas as functional characters that require quotation marks??
Thanks,
Dave
Actually in CASE STRUCTURE, any frame can have multiple values as 'Case Selector value' and these are separated by a comma. Also if you choose to operate a CASE STRUCTURE using string, it will automatically prefixs & suffixs quotes (") to that string.
But you can enter "A, B, C" manually and it will remain as it is. But if you copy and paste A, B, C, the CASE STRUCTURE will automatically change it to "A", "B", "C".
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Why does LabVIEW take significantly longer to display a large amount of Chineese characters? (intentionally misspelled)

EDIT: I am intentionally misspelling the word for "the language of China" otherwise the forum will censor me, seriously.
We have a large application based on LabVIEW. In this application, we use flattened strings to pass data between VIs. I recently noticed that some VIs who show their Front Panels when called were taking significantly longer to draw their Front Panels on computers that are localized in Eastern languages (Chineese, Korean, etc.).
I eventually traced it down to the fact that if you try to display a large amount of characters (anything over 2000 characters) in a string on a Front Panel where the text in LabVIEW is localized to English, the Front Panel is launched and drawn instantly. However, if the string becomes localized in an Eastern language, say Chineese, it can take significantly longer to draw the Front Panel (anywhere from 40 seconds to 2 minutes or more depending on the length of the string) and the CPU is being taxed.
I've attached a simple VI (LabVIEW 2014) which demonstrates this behavior. It simply generates a random sequence of characters of a predefined length.
In order to notice the problem, follow these steps:
Make sure LabVIEW is closed first.
In Windows, go to Control Panel > Region and Language.
In the Formats tab, observe which language is currently selected. If it is not set to "English (United States)", then switch to that and click Apply.
Launch LabVIEW and run the attached VI. You should notice that the string indicator updates almost instantly.
Completely exit LabVIEW.
Going back to the Region and Language panel in Windows, change the Format drop-down from "English (United States)" to "Chineese (Simplified, PRC).
Launch LabVIEW and run the attached VI. You should notice a significant delay it takes for the string indicator to display the text.
Anybody have any idea why this is happening?
Thanks!
Attachments:
Random String Generator.vi ‏8 KB

Drat.
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.

Why does Labview create a .vi for each global variables?

Hello,
I wrote an Labview application which use several global variables (almost 30 variables). All the variables are of variable type "single process". For each of these variables, Labview creates a vi.
For example, for the variable "_TS.Measures.channes", Labview creates a vi named "TS_'_TS.Measures.channels'.vi". Which means, I have almost 30 "name of variable".vi files: this is confusing!
All my VI are inside library (.llb). When I try to put the VI of a global variable in a library, Labview can't find them anymore.
May be can somebody explain me, why LabVIEW does create these VI and how is it possible to put them in a library.
Cheers,
Risotto

Hi everybody,
Thank you for your answers, I get a lot of informations.
Yes, I use the new shared variables in LabVIEW8, which I am using like sort of global constants. Now I am understanding what guys are telling me all this about global variables in LabVIEW7.1. Sorry, I forgot to say I was using LabvVIEW8.
I will have a look on the tutorial too.
But yet one point about the library collecting all the shared variables in the windows explorer and in the project explorer: When I create a shared variable in my LabVIEW project - for example "test1" as double/single process - the variable doesn't appear in my file directory, but it appears in the project explorer in a library (.lvlib).
When I drag/paste my shared variable on the block diagramm of my VI, then a file "Math_test1.vi" appears in my file directory. There is no extra .llb created to contain my shared variable vi.
If I drag/paste the file "Math_test1.vi" in the Math.llb (see picture), then the file is moved in the llb and disapeared from the directory.
If I created another shared variable "test2" as double/single process and put it on the VI, then LabVIEW creates2 files in the directory: "Math_test1.vi" and "Math_test2.vi". So that I get 2 vi for the "test1" variable now (one in the llb and one in the directory).
I use several library in the project explorer. But the library in the project explorer seems to create file with other extension (.lvlib) than the sdtandard LabVIEW library (.llb).
Cheers,
Risotto
Attachments:
picture.jpg ‏223 KB

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

Why does LabVIEW generate -0?

Similar Messages

Maybe you are looking for