LabVIEW 2014 array constant change

Why did the "graying out" of array constants change between LabVIEW 2014 and LabVIEW 2013? In 2014 the effect is much more subtle and it's far harder to tell the # of elements in an array constant. Please change this back ASAP!

My only thought was that they tried to make the disabled elements more readable.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Disabled Elements.PNG ‏24 KB

Similar Messages

[BUG]: Dll modifies input array constant

Hi,
Not really an important one, but some of you (Ben might like it... Tested
in LV6, 6.1, 7.0 and 7.1.
When a dll function modifies more (1d or 2d) input arrays, one constant is
used to initialize them and less then all indicators are wired, LV
overwrites the constant values...
To reproduce this, I created a two dlls (one in assembler and one in
LabVIEW, assembler one is attached). The dll fills the array with the number
2.
Run the VI, update the diagram (close and open again, or scroll). The values
in the constant array now have the same values as the output array!
This behavior is reproducible with (at least) 1d and 2d arrays, and (at
least) U32 and DBLs.
I'm sure other array data types (SGL, U8, I8 etc.) s
how the same behavior,
but pointers to scalar values do not. Perhaps strings also do this?
Try putting a flat sequence frame around it, and put a few seconds wait
before and after it. You can see the constant changing while the vi is
running.
Regards,
Wiebe.
[Attachment Callbug.dll, see below]
[Attachment Callbug.vi, see below]
Attachments:
Callbug.dll ‏3 KB
Callbug.vi ‏13 KB

Ben,
The topic from the advanced course does seem to be describing this. So this
behavior doesn't seem to be a bug. I couldn't find anything about this in
the "Using External Code in LabVIEW" manual.
When pointers to values are used, the constants are not updated, so that is
inconsistent, but it does say "may receive", so that is covered...
Perhaps the only bug is the fact that the block diagram is not refreshed
properly, after the values are changed... Just kidding...
Next question is how to make use of this?
Regards,
Wiebe.
"Ben" wrote in message
news:50650000000500000078D30100-1079395200000@exchange.ni.com...
> Hi Wiebe
>
> Your question reminds me of a phrase from proverbs
>
> "A wise man goes into his store house and brings forth treasures both
> old and new".
>
> I was not able to find documentaion on the the call library function
> that talks about this issue but I did find the following in the
> "LabVIEW Advanced 1 Course Manual, August 1998 Edition, part number
> 321366C-01 page 242".
>
> "If you do not wire an indicator to the output terminal of a terminal
> pair, LabVIEW assumes that the CIN will not modify the value you pass
> to it. If another node uses the input data, LabVIEW does not make a
> copy of the data.
>
> Note: If you don't wire the output terminal, the source code should
> not modify the value passed into the terminal. Nodes connected to the
> input terminal wire may receive the modified data.
> "
>
> This topic brought our class to a stand still when we(those who were
> still awake) realized that data could flow backwards through a wire!
>
> I believe the behaviour you have observed is correct and the quote I
> cited above.
>
> I will venture a guess that the requirement from the CLA exam
> "CLD-VPP-03-04 ...Review a LabVIEW application for run-time behavoiur
> and memory management issue, ....Destructive and non-destructive
> buffer reads on branched wires"
>
> had the behaviour in mind.
>
> I posted a Q re:this req years ago but never got a definative answer.
>
> All of the above is just my opinion.
>
> I would love to hear from others.
>
> What do you think?
>
> Ben
>
> BTW: I do not think they teach that anymore.

Array constant grey entry

Say I have a array constant with 3 elements
I want to delete the 3rd element and grey it out, so it look like this
Can't seem to find a good way to do this other than remake the entire array. It is fine when the array only has a few elements, but when it is an array of shared variable reference of 50, it takes some time.
Thanks
Solved!
Go to Solution.

Exactly like that.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

BD Array Constant cannot be "browsed"?

I've been annoyed by this in the past and a quick search did not yield any answer, so here is it:
Is there a good reason why an array constant on the BD cannot be looked at, in the sense that the array index is no clickable?
For instance, I am parsing a header using an array of strings and while I am debugging the process, I'd like to rapidly check what the index of entry "this" or "that" is so that I can put some conditional probe that will get me there quickly. The problem is, the array is too large to be seen at once on the diagram. Moreover, what I want to do is bring the item I am interested in to the top of the list so that I can check its index:
The problem is, once I step through the code, the array is "frozen" and I can't play with the index control.
That should not change anything to the code, so I don't understand why I am prevented from doing that.
I can browse through cases of a structure or a sequence. Why not an array constant?
Tested in LV 2011, but has been here forever.

You are specifically talking about run mode, right (in edit mode you can change the index).
You can show the scroll bar of the array container. It seems that still works in run mode, but I agree that the index should maybe also keep working.
LabVIEW Champion . Do more with less code and in less time .

Compile 9076 with LabVIEW 2014 Worked good with 2012 SP1

An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 7 occurred at Open VI Reference in nirviOpenVIRefByNameOrPath.vi->niFpgaRemapObjsAndListIfUnderXNode.vi->niFpgaRemapObjsHandleXNodeSubErrors.vi->nirviMassageErrorList.vi->niFpgaErrorDialog_ParseErrors.vi->niFpgaErrorDialog_ReadErrorData.vi->niFpgaGenerateCode_ErrorDialog.vi
Possible reason(s):
LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
VI Path: C:\Program Files\National Instruments\LabVIEW 2014\rvi\CodeGenErrorUtilities\Diagram Constant
All text parsed:
<CodegenErrorList>
          <CodeGenErr>
            <ErrorCode>-64001</ErrorCode>
            <DynamicText>
              <TreeLineInfo>
                <TreeInfo>
                  <TreeID>1</TreeID>
                </TreeInfo>
              </TreeLineInfo>
            </DynamicText>
          </CodeGenErr>
          <CodeGenErr>
            <ErrorCode>-64001</ErrorCode>
            <DynamicText>
              <TreeLineInfo>
                <TreeInfo>
                  <TreeID>1</TreeID>
                </TreeInfo>
              </TreeLineInfo>
            </DynamicText>
          </CodeGenErr>
          <CodeGenErr>

Hi Nieman,
You have the right compilers for your FPGA targets, based on KB 609GUVBT.
Error -64001 indicates that there is an issue with one of the nodes in your VI. Since you are able to compile a blank FPGA VI, then you should try to identify the node that is causing this problem. When trying to pinpoint this node, I’d recommend executing your FPGA VI with simulated I/O on the development machine, as described in KB 3W6EFRLX,
Also, are you able to reproduce this issue when running one of the LabVIEW Example Finder FPGA VIs that targets your NI 9076? You can find these examples in the Example Finder's Hardware Input and Output>>CompactRIO section.
Regards,
Tunde S.
Applications Engineer
National Instruments

Labview 2014 Excel Active X Property Nodes disabled - Why?

Hello,
I am using Labview 2014 and want to open, write to and close Excel by the use of Active X.
I am confronted with the problem, that, if connecting (Active X-) property nodes to the references (e.g. "Excel_Application"), right-clicking on the context menue doesn´t let me choose any properties, the item is disabled (one can read in German "Keine Eigenschaften" (no properties)).
How can I resolve this? What am I doing wrong?
Thank you!

I am having the same problem. When I left click to choose/change the property I do not get a list - instead I get the greyed No Properties popup - see screenshot.
If I drag and drop an existing property node from within an example subVI it connects to the reference and keeps showing the current property but I cannot change to a different one.
I am using LV 2012, Win7, Office 2013.
When I try with LV 2012, Win7, Office 2010, it works properly. So my guess is that is has to do with the version of office. But I would like to know the reason why as well.
Attachments:
NoProperties.png ‏67 KB

Creating string array constant

Hey, this is probably a stupid question but I am still trying to figure out everything in LabVIEW. Is there a way to create an array constant that holds strings? I know you can define an numerical array constant but can you also do one for strings, or do I just have to pass multiple text fields into a "build array" function.
Thanks,
Paul

Another tip:
Many times, you already have a function on the diagram that expects an array of strings (or whatever you specifically need), so the easiest is to right-click the connector and select "create constant". You will get an diagram constant of the default type for that input or output terminal.
LabVIEW Champion . Do more with less code and in less time .

LabVIEW 2014 x64 AppCrash StackHash crash

Our application is crashing somewhat inconsistently in the x64 compile, but not the x32 compile. We are using LabVIEW 2014. When it crashes, LabVIEW stops responding and has to be closed from windows. The View Details feature says it's AppCrash and further says StackHash_someHEXnumber. Another member of the team analyzed dump files and seemed to think it's crashing in the LabVIEW run time.
Any known issues out there that would explain this?
It happens on the original release of LV2014x64 and SP1. It happens in LabVIEW and in a compiled executable. If is not consistent, if we open the software and start running tests, sometimes it will never crash, other times it will crash before 1500 test runs. Our way of testing this has been to run 1500 runs, then close it then reopen it, run again. If it doesn't crash within 3 times of doing 1500 runs, we say that the crash probably isn't going to happen in that version of the software. So we've been selectively disabling parts of the software trying to figure out which code is triggering the crash.

Some more information:
In addition to not happening in LV2014x86, it does not happen in LV 2014 MacOS x64. So this is specific to LV 2014 Windows x64. Furthermore, if we save our code to previous and open it in LV2013x64 there's no crash (there's some hickups with the downgrade so it's not 100% apples-apples though) .
We have narrowed the crash down to a specific changelist in source code control. In that changelist we changed the architecture of how we pass messages around in our program. We used to use User Events to pass messages and the vi listening would subscribe to the user event. However, we found this created a memory leak in LV2012. So we switched to a queued based messaging architecture in this changelist. We created a variant which held the queues as a variant attribute associated with the message enum. This was so that when a message is sent we could do a fast lookup by taking the message and getting a varriant attribute associated with it (thus giving us the queues subscribing to that message). When we introduced this in LV2012 we stressed tested it all and it worked great. Later we upgraded to LV2014 and that's when the crashing started, we have gone back to this specific changelist and tried it with LV2014 it crashes.
We have found other parts of our code which if we disable the crashing goes away. Our suspicion is that this occurs due to a perfect storm of calling vi's asyncronously (which call other vi's ascncronously), passing messages to them via queues, and maybe the variant's containing queues in attributes. Based on what various programmers have seen via a variety of observations, our suspicions are that some combination of those circumstances is triggering some sort of LV2014 windows x64 bug.

File dialog crashes LabVIEW 2014 on Mac OSX Yosemite

I know that Mac OS 10.10 (Yosemite) is not technically supported by LabVIEW 2014. If that's the only answer to this question, then so be it.
The following causes LabVIEW 2014 to crash on Mac OSX 10.10 (Yosemite):
1. Run the native File Dialog in LabVIEW 2014 (Express VI) , using "New or Existing File" as the selection mode
2. Select "New File..." when the file dialog appears
3. Enter anything as the file name and click OK
4. LabVIEW either crashes immediately, or hangs indefinitely and must be force quit.
Is there an update for LV 2014 (and the RTE) that does support Yosemite?
This bug makes deploying apps to the Mac basically impossible, Yosemite is the latest OS. Does anyone have a workaround for the issue?
Thanks.

LabVIEW 2014 SP1 seems to solve that problem here on my Mac OSX 10.10 system.
Now Apple may be nice for end users, but all those Apple fan boys sure would think a little different about it, if they had to write programs on the Mac. Apple keeps changing its APIs and their behaviour continously, inventing new APIs (which is fine) in a rapid pace, only to depreciate and remove older APIs at almost the same speeed!
Microsoft sometimes goes to the other extreme with maintaining backwards compatibility but working with Apple systems surely isn't easy as a programmer (unless maybe when one uses their high level click and point together web design applications, but I don't know that).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

No aparecen los iconos de vision al instalarlo en labview 2014

Hola, instale la version de prueba de labview 2014 y de vision. Resulta que me aparece el nombre en el menu de funciones (vision and motion) pero no los iconos, por lo que no puedo usar este modulo. Por otro lado si realizo la instalacion de labview 2013, si que puedo utilizar vision. Parace como si hubiera algun problema con labview 2014 y vision. ¿Alguna idea?
He descargado la ultima actualizacion de vision que he encontrado que corresponde a febrero de 2014.
gracias

Do you have the Zoom feature activated? To zoom out, do this:
¿Tiene la función de zoom activado? Para alejar la imagen, haga lo siguiente
Zoom in or out: Double-tap the screen with three fingers. By default, the screen is magnified 200 percent. If you manually change the magnification (by using the tap-and-drag gesture, described below), iPod touch automatically returns to that magnification when you zoom in by double-tapping with three fingers.
copied from iPod_touch_iOS4_User_Guide , page 160ff

Is there a possibility to start the VeriStand 2014 Gateway programatically using LabVIEW 2014?

Hello,
This is a reload of the Is-there-a-possibility-to-start-the-VeriStand-2011-SP1-Gateway because what worked in 2011 SP1 does no more in 2014.
I ported the code from the previous topic, do do the same thing (calling "__cdecl Int32 StartVeriStandGateway(out Int32 handle)" in "C:\Program Files (x86)\National Instruments\VeriStand 2014\Data\NationalInstruments.VeriStand.Gateway.dll".
Doing this from a .NET programme (console or windows process) or directly from a DLL node in LabVIEW 2014 seems to have no effect, knowing the .NET code worked in 2011 even when called from a Windows service.
Is there a new way to do it?
By the way, the "NationalInstruments.VeriStand.WindowsRegistry.GetInstallationDirectory()" method has disapeared from the assemblies.
Best regards,

Hi Jarrod,
You're rigth, after PC reboot the Gateway starts when calling the DLL node (OpenWorkspace & GetSystemStatus are called with no errors), but when I try to ConnectToSystem the program stays blocked into the sub-vi, although the code works well if the Gateway was previously started normally by running VeriStand from Windows.
I tryed to change the call policy in the DLL node (UIThread & any thread) but it seems doing nothing.
Please find here joined the test files and debug capture of the stall.
Best regards,

Open vi reference conversion from Labview 6 to Labview 2014

Is there a way that someone can help me convert this VI written in Labview 6.1 so that I can work en EXE in Labview 2014.
I succed to open this vi from 6.1 to 2014 but it does not run. The open vi reference those not work in exe program. Someone know how I can replace that function...
Thanks!
Solved!
Go to Solution.
Attachments:
to convert 2104.zip ‏17 KB

Error 7 is File Not Found. So your dynamically called VI is not in your executable.
In the build spec for the executable in your project, there is a section for "Source Files". On of the options for the VIs is "Always Include".
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

I want to play video on my computer to make some analysis to frames,the problem that I face ,I can't change video frame rate using labview,but I can change frame rate to the video out of labview using some program

HI All
I want to play video on my computer to make some analysis to it's frames,the problem that I face ,I can't change video frame rate using labview,but I can change frame rate to the video out of labview using some program .
I used IMAQ AVI Read Frame VI
for example I have avi video It's frame rate is 25 fbs ,my image processing code is very fast that can process more 25 fbs,so I want to accelerate video acquisition

Hi abdelhady,
I looked into this further, and reading an AVI file into LabVIEW faster than its frames per second won't be possible. LabVIEW could read in frames faster than 25fps, but because it will be pulling the available frame at that point in time this would just give you duplicate frames. If you want to be able to read in frames at faster than 25fps, you would need to speed up your AVI file before reading into LabVIEW.
There's a good shipping example to show how to read in from an AVI file, "Read AVI File.vi". You'll notice that they add timing to make sure that the while loop runs at the right speed to match up with the frames per second of the file being read. This is to make sure you're not reading duplicate frames.
Thank you,
Emily C
Applications Engineer
National Instruments

In LR CC 2014 how to change darkness/lightness of interface as in other CC programs

In all the other programs I've used in CC 2014 I can change the interface to a lighter one that doesn't hurt my eyes. I've just taken awesome training for LR and want to do some major revamping of photos, but can't seem to find this option. What am I missing?
Thanks, Suzi

In other apps of CC this is true, but none of the settings gave me a lighter interface. Only a slightly lighter desktop, all the ones that matter are light text on dark and I just can't use that type of interface with my eyesight as they tire quickly. Thanks so much for the help anyway, I really appreciate it.
Suzi

String Array Constant Addition

Is there an elegant way of marking the last element in a string array
constant? i.e. I take an Array constant, and add a simple string to it,
so that it becomes a String Array Constant. Now I add elements 1 and 2
and 3. But now I want to take element 3 out. If I just delete Element 3
contents from the string control, that is fine, but the # of Array
elements is still 3. It is just that the 3rd elelment is null. How can I
make the array length 2? Now I know that starting over is one option
(just creat a new array constant, and add the two elements) but what if
my array constant has 100 elements and I want to make it 99. I also
know that programatically I can remove these elelents, but I am taking
about in the programming of th
is constant. I must be over looking
something... Any ideas???
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
> Is there an elegant way of marking the last element in a string array
> constant? i.e. I take an Array constant, and add a simple string to it,
> so that it becomes a String Array Constant
Arrays must be all the same type. If the last element is a constant, all
elements are
> Now I add elements 1 and 2
> and 3. But now I want to take element 3 out. If I just delete Element 3
> contents from the string control, that is fine, but the # of Array
> elements is still 3. It is just that the 3rd elelment is null.
In a string, yes, Empty strings are essentially nulls.
> How can I
> make the array length 2? Now I know that starting over is one option
> (just creat a new array constant, and add the two elements) but what if
> my array cons
tant has 100 elements and I want to make it 99. I also
> know that programatically I can remove these elelents, but I am taking
> about in the programming of this constant. I must be over looking
> something... Any ideas???
This is one of my problems. It is easy to size an array up, but hard to size
down.
Of course you can resize at run time but the only way I know to do this
when editing is to start over.
Kevin Kent
Attachments:
Kevin.Kent.vcf ‏1 KB

LabVIEW 2014 array constant change

Similar Messages

Maybe you are looking for