LabVIEW 2015 Buffer Allocation Bug?

Similar Questions

• LabVIEW 2015 scrollbar bug on block diagram

  Hello!

  I'm using Labview 2015 SP1 Professional. I use windows 10. Whenever I have do an action on the block diagram I get annoying move right on my scroll bar. Does anyone else have this annoying "feature"? I tried on three different computers and evertime same also on windows 7.

  There was a bug with nested structures that had enabled ' automatic'. Try disabling the automatic extension on all of your structures.

• buffer allocation and minimizing memory allocation

  Hello

  I am tryint to minimize the buffer allocation and memory in general activity. The code will run 'headless' on a cRIO and our experience and that of the industry as a whole is to ellliminate or minimize any action of distribution and the dynamic memory deallocation.

  In our case we treat unfortunately many string manipulations, thus eliminating all the alloc/dealloc memmory is significant (impossible?).

  Which leaves me with the strategy of "minimize".

  I did some investigation and VI of profiling and play with the structure "on the spot" to see if I can help things.

  For example, I have a few places where I me transpoe a few 2D charts. . If I use the tool 'See the buffer allocations' attaced screenshot would indicate that I am not not to use the structure of the preliminary examination International, both for the operation of transposition of the table for the item index operations? As seems counter intuitive to me, I have a few basic missunderstanding either with the "show stamp" tool of the preliminary examination International, or both... The tool shows what a buffer is allocated in the IPE and will once again out of the International preliminary examination, and the 2D table converts has an allowance in and out, even within the IPE causing twice as many allowances as do not use REI.

  As for indexing, using REI seems to result in 1.5 times more allowances (not to mention the fact that I have to wire the index numbers individually vs let LabVIEW auto-index of 0 on the no - IPE version).

  The example illustrates string conversions (not good from the point of view mem alloc/dealloc because LabVIEW does not determine easily the length of the 'picture' of the chain), but I have other articles of the code who do a lot of the same type of stuff, but keeping digital throughout.

  I would be grateful if someone could help me understand why REI seems to increase rather than decrease memory activity.

  (PS > the 2D array is used in the 'incoming' orientation by the rest of the code, so build in data table to avoid the conversion does not seem useful either.)

  QFang wrote:

  -My reasoning (even if it was wrong) was to indicate to the compiler that "I do not have an extra copy of these tables, I'll just subscribe to certain values..." Because a fork in a thread is a fairly simple way to increase the chances of duplications of data, I thought that the function index REI, by nature to eliminate the need to split or fork, the wire of the array (there an in and an exit), I would avoid duplication of work or have a better chance to avoid duplication of work.

  It is important to realize that buffer allocations do occur at the level of the nodes, not on the wires. Although it may seem to turn a thread makes a copy of the data, this is not the case. As the fork will result in incrementing a reference count. LabVIEW is copy-on-write - no copy made memory until the data is changed in fact, and even in this case, the copy is performed only if we need to keep the original. If you fork a table to several functions of Board index, there is always only one copy of the table. In addition, the LabVIEW compiler tries to plan operations to avoid copies, so if several branches read from a wire, but only it changes, the compiler tries to schedule the change operation to run after all the readings are made.

  QFang wrote:

  After looking at several more cases (as I write this post), I can't find any operation using a table that I do in my code that reduces blackheads by including a preliminary International examination... As such, I must STILL understand IPE properly, because my conclusion at the present time, is that haver you 'never' in them for use. Replace a subset of a table? no need to use them (in my code). The indexing of the elements? No problem. .

  A preliminary International examination is useful to replace a subset of the table when you're operating on a subset of the original array. You remove the items that you want, make some calculations and then put back them in the same place in the table. If the new table subset comes from somewhere other than the original array, then the POI does not help. If the sides of entry and exit of International preliminary examination log between them, so there no advantage in PEI.

  I am attaching a picture of code I wrote recently that uses the IPEs with buffer allocations indicated. You can see that there is only one game of allowances of buffer after the Split 1 table D. I could have worked around this but the way I wrote it seemed easier and the berries are small and is not time-critical code so there is no need of any optimization. These tables is always the same size, it should be able to reuse the same allowance with each iteration of the VI, rather than allocate new arrays.

  

  Another important point: pads can be reused. You might see a dot of distribution on a shift register, but that the shift register must be assigned only once, during the first call to the VI. Every following call to the VI reuses this very spot. Sometimes you do not see an allocation of buffer even if it happens effectively. Resizing a table might require copying the whole table to a new larger location, and even if LabVIEW must allocate more memory for it, you won't always a point of buffer allocation. I think it's because it is technically reassign an existing table instead of allocating a new, but it's always puzzled me a bit. On the subject of the paintings, there are also moments where you see a point to buffer allocation, but all that is allocated is a 'subfield' - a pointer to a specific part of an existing table, not a new copy of the data. For example 1 reverse D table can create a sub-table that points towards the end of the original with a 'stride' array-1, which means that it allows to browse the transom. Same thing with the subset of the table. You can see these subtables turning on context-sensitive help and by placing the cursor on a wire wearing one, as shown in this image.

  

  Unfortunately, it isn't that you can do on the string allocations. Fortunately, I never saw that as a problem, and I've had systems to operate continuously for months who used ropes on limited hardware (Compact FieldPoint controllers) for two recordings on the disk and TCP communication. I recommend you move the string outside critical areas and separate loop operations. For example, I put my TCP communication in a separate loop that also analyses the incoming strings in specific data, which are then sent by the queue (or RT-FIFO) to urgent loops so that these loops only address data of fixed size. Same idea with logging - make all string conversions and way of handling in a separate loop.

• Why this specific buffer Allocation?

  Win Vista, LabVIEW 8.6.1, PXI 8196, LV RT 8.6.1

  I have a problem with a PXI program used to control a motor/dynamometer by PID loops on a cycle prescribed thresholds (objectives specific speed/torque to meet).

  The normal use of the processor (as the output of the PXI monitor shows) is normally 2%.  My loop is 100,000 Hz, and I have been diligent in spreading the bypass, so it runs very efficiently.

  A 'normal' test was for 20 minutes, so we have never noticed a problem.  However, my client has recently published a test of 8 hours, and he noticed that the CPU would creep upward and upward during the test, to where it was 75% after 8 hours.

  I ran my own test of 2 hours and observed the same thing - the CPU usage crept up to 20%.

  In the hunt for things, I noticed it is correlated with the size of an array of values of the PXI controller: larger than array, the CPU usage more.  During the test, the set values are located above the host right in front of the time, so the table grows slowly as the test goes along.

  When the test is finished, the table does not, and nor does the CPU usage.  I can go right through to start a new test and the CPU usage drops when I send an order to clear the table.  Therefore, I am sure that the size of the array is the problem.

  A two hour test contains 120 x 60 x 10 = 72000 set points (the host set points are 10 Hz, 100 Hz setpoints are interpolated from the controller) to 24 bytes, which is 1.728 MB.  NOT a RAM huge hit (available from 2 gigabytes).

  I couldn't imagine why the existence of this large table would be time-consuming CPU, but the evidence is with myself: the bigger picture, the most used CPU.

  In the search for an answer, I started the buffer ALLOCATIONS view and found a place where LV makes a COPY of this buffer, and I don't understand why.

  But that would explain things: copy a table from 1.7 MByte to 100 Hz will certainly put a load on the processor.

  So here's the code: in the TRANSIENT state table is used to select and interpolate the next set.

  

  When the test is finished, we go to the State of SLOWDOWN, if the table is not yet used:

  

  After that, we are in idle state, where even once, the big Board is not used.

  

  Then, before I have to change the architecture of things to eliminate former set points (I have many problems with accounting), can someone explain WHY the buffer allocation shown is happening?

  Note that I show the case of '0', the other is 'default' which manages other 9 out of 10 cases.  But there is there again, a buffer allocation when the table is not yet connected to the inside.

  More importantly, avoid this allowance?

  It's hard to say without poking at him but I saw the similar models result in a copy of the additional buffer.

  (1) (less likely) the wire branch off to feed the size of the table is confusing LV and he thinks he needs another copy. I saw this in all LV 7.1 and can not ask with LV 8.6.1.

  (2) the sub - VI "to choose and interpolate the next set" has NO control on the connector of the icon on the "root" of the diagram and or data are not connected through. To understand what I'm upgrading to please see the "clear as mud" thread , where it was called Grg McKaskle out of retirement to explain how it can work Subvi in the buffer of the appellant (that's really what you want in the code you showed us).

  Reader Digest Version:

  When LV 'sees' data be passed to and from a Subvi and there is no operation that will change the content of the data, the data will be passed by reference so sub - VI will do its job in the buffer of appellants.

  This image of code shows the difference.

  

  Ben

  PS "Buffer Allocation" in the hand catches my attention.

• Entered Unwired error cause buffer allocation

  Recently, while playing 'Hide the Dots', have I noticed that wiring not not admission of error on the functions (such as the authors of the notifications, queues or nodes of property) may be coming to a bill of costs.

  If a cluster of error is X bytes and you have dozens of these unwired (let) laying around, declaring it is buffer allocation [X bytes * notifiers n]? Correct me if I'm wrong, but the old saying no error output?

  Edit: I know that is not the wiring error may cause a race condition, the non-LabVIEW-esque program sequence, etc, but I would like to talk about the aspect of memory of this alone.

  Hi all

  As the 'error' is only a recommended terminal, when he is not wired LabVIEW must locate and assign default values for this entry. To do this, a memory to be allocated. Therefore, not wiring error as well as the terminals not required tickets will actually increase the initial memory allocation. However, this additional allocation should be minimal compared to the rest of your VI.

• Support of NI CompactRIO for LabVIEW 2015 missing

  Hello

  I have one NOR cRIO 9038 I want to use for a project, but I continue to have problems with incompatible software. I downloaded the two 64-bit LabVIEW, CompactRIO 15, FPGA Xilinx tools, FPGA Module OR and then 32-bit LabVIEW. All these components are updated in the Service Manager OR.

  I am trying to learn to use this device, and I am going through the guide of http://www.ni.com/compactriodevguide/ where the first example is a Turbine including different screws when you open the files it succesfully scans and all the screws under loads, but only at the opening, I get the following error message

  

  Here is a view of the software installed in my MAX

  

  Looking for 'The NI CompactRIO for LabVIEW 2015 drivers Support' brings me to this page http://www.ni.com/download/ni-rio-15.0/5363/en/ which I already downloaded and installed.

  How can I solve this problem?

  Thank you

  EDIT: also miss me cRIO sample projects referenced by the guides NOR as a good starting point for any new application. They must be visible when I want to open a new model/sample. Is a further indication that I'm missing something - or should try to reinstall? Simply, I can't understand what it is that I might be missing.

  You also have LabVIEW Real-time and LabVIEW FPGA installed? You probably need to install those before the CompactRIO drivers. I don't know if LabVIEW RT/FPGA is supported in LV 64-bit - it does not look like it does in LV 64-bit in your screenshot MAX.

  Edit: Sometimes the installation order can be important - LabVIEW/FPGA/RT first and then the CompactRIO drivers - you might want to do a reinstall and see if that sorts it.

• LabVIEW 2015 SP1 missing palette for target touchpanel

  Hello

  I had an interesting problem for my installation of sp1 LabVIEW 2015.

  When I select a new project for a target of touchscreen, I don't get the palettes to add functions and commands.

  The palettes appear, but they are empty.  (Note that if the target is 'My Computer', everything works fine)

  After a lot of head scratches and research here, I found that there is a way to manually load the .mnu files to fill palettes.  All seemed well until what all I'm back have had a lot of icons with? in them.

  I then tried to install it on some other machines and they all worked well.

  Then, I discovered that when you choose a location to load the files .mnu, on my main pc, with the question, he kept pointing to a directory other than the one on my work pc...  I've searched and searched but cannot find where LabVIEW gets to this place.  All my paths are the default.  I even checked the registry keys (that I can find) and they are all ok also.

  So, I finished to cheat and copy the .mnu files in the path, its research and its working now.  I am not happy with that as its limit causing me problems if there are updates etc...

  My pc was looking for this path

  My work pc has been searching for this

  I'm guessing that my problem will be solved by resetting the locations by default of LabVIEW, but I can't find a way to do it.   I've done several uninstalls / reinstalls and no still no luck.  If anyone knows where these values are stored, so please let me know.

  Concerning

  Andy

  Hi Andreas,

  Thanks for the reply.

  I have now managed to solve my problem.

  It seems that one of my components labview has not activate properly when I applied the license key.

  I ended up asking another activation (via the online system) and it looks like its all working now.

  Not sure why LabVIEW behaved as he did, and why there is no indication of a license number.

  Very strange.

• Is LabVIEW 2015 for Mac?

  We have a license for LabVIEW 2015 and received the software on a USB Flash drive.  I have used successfully to install LabVIEW on my Windows PC, but am confused how to install LabVIEW on a Mac.  When we arrived LabVIEW on separate DVD, there was a DVD of MAC or Linux, but there is only this Flash drive.

  I searched through files and folders on this drive, looking for Mac and Linux.  The only Mac that I found was "MAComponents", which is a record for the Components Wizard of movement.  Similarly, references to Linux seem to be especially RIO LVRT related and.

  I called AND ask for help, but so far have not heard back.  I probably made a mistake in not making a formal request for Service, but the system was down for the day, I called...

  A Web search for a download for LabVIEW 2015 detects a lot of downloads of Windows, but even once, I don't (yet) found nothing for Mac.  I don't know miss me something (like 'just connect the Flash drive to a Mac, and it will "do the right thing") - I must confess that I did not (yet) experience that I just mentioned...

  Bob Schor

  http://FTP.NI.com/evaluation/LabVIEW/ekit/other/Downloader/LabVIEW2015-evaluation.dmg

  There is the assessment of 2015 for Mac.  I'm trying to find a Readme for this.  But I expect that it has only been tested on Yosemite and earlier versions

• LabVIEW 2015 do not install it, autorun.exe "met a bad argument.

  Hello

  I recently got a new laptop and tried to install labVIEW on it. He started to install, but the system loses power in the middle and close. I deleted the National Instruments folder in Program Files (x 86) and retried, but when I run autorun.exe said he "met a bad argument" with a red 'X'. So I tried to launch setup.exe, and he starts, but bypasses LabVIEW and continues for the module in real time, where it says "LabVIEW 2015 must be installed before you install the real time module. Any help would be appreciated.

  Thank you

  
  

• LabVIEW 2015 "not responding" on the open project

  I worked on two projects in LabVIEW 2015 for awhile.

  Today I wanted to install an upgrade to SP1 2015 LabVIEW. This included a patch for 2015 SP1 f1.

  After installation and reboot, I opened one of my projects again. LabVIEW froze with "do not answer" in the title.

  After several minutes, I noticed that the Project Explorer had indeed appeared, but when I do something (try opening a .vi) it freezes and crashes again.

  I tried to open the other project, and it works fine.

  I have the same exact files on a laptop, that I haven't had not upgraded to SP1 f1, and everything works fine there.

  I have troubleshooted for a little while, but decided to uninstall SP1 and reinstall 2015.

  After doing this, I still have the same problem with the number 1 of the project.

  I will attach the .lvproj here, in case someone is a magician and can say something to him.

  LabVIEW hangs on the message "opening Hawk.lvproj.

  Any advice or help is welcome! Thank you!

  Concerning

  Oksavik

  As I mentioned the Project Explorer seemed finally after about 10 minutes of "not responding".

  I clicked 'save everything' and left. Upon return, this is sensitive yet and since then: no problem.

  I don't know what caused it, but 'save everything' seems to have solved any problem LV had with my project folder.

  Maybe this will help someone else in the future.

• Compilation of Xilinx not installed labview 2015 FPGA tools

  Hello

  I just installed Labview 2015 + FPGA Module on my computer with an older version of Labview 8.6.

  When I compile a labview FPGA project 2015 I got this error message "year error occurred while communicating with the server compilation" and warning "tools of Compilation of Xilinx not installed."

  I can assure you that my server of 2015 lunch perfectly and I installed everything correctly. I assure that it is a conflict between labview 8.6 and 2015 therefore uninstalled the older one.

  The problem is my build configuration is set to Xilinx 10.1 (which should be 14.7) and there is no way to change this.

  After looking around I found that Labview looking for best compilation tools then maybe this is not the problem

  Is there something I missed?

  Kind regards

  Hello

  I found the source of the problem. The FPGA, I used was based on a FPGA Virtex II matrix that is not compatible with this version of the build tools.

  Thanks for helping me!

• LabVIEW DSC 2015 with Labview 2015 64-bit

  Hi all

  I would like to know if it is possible to install the labview DSC 2015 with Labview 2015 64-bit module. When I run the Setup program, a message appears telling me to install Labview before installing the DSC Module. Maybe I need to install a 32-bit version of Labview? If anyone has an idea...

  Thanks for all,

  Alex,

  From the Readme of LabVIEW file:

  Supported modules

  LabVIEW 2015 (64 bit) supports only the NI Vision Development Module. Refer to the documentation of the Vision Development Module for more information. No additional modules support LabVIEW 2015 (64-bit).

  Looks like you need to run 32-bit LabVIEW.

  Bob Schor

• How to read the tag bluetooth data in labview 2015 running on Windows 10

  Hi all

  I have a Development Board Nordic semiconductor nr51. This card is programmed as a tag bluetooth which simply announces his address with 16 bits of data appended to the end.

  My laptop came with loan materials smart bluetooth. I installed an app interactor lighthouse to bluetooth on my laptop and the software is able to detect the tag as if shown on the image below.

  

  I wanted to write a LabVIEW program that will simply be careful bluetooth headlights and notify me in my computer every time a lighthouse with the specified address is detected. This mobile application below is provided by the manufactuerer of the Board of Directors and I wanted to develop a LabVIEW program something similar to what will read the given data and extract values.

  

  Somehow, all the sample applications provided data only shows how to read and write in a connected bletooth device but not analysis for tags. I also tried using the Bluetooth ' discover ' and it does not detect the bluetooth beacons.

  Could someone provide me with the necessary information or example program for detecting / reading of tags bluetooth in LabVIEW 2015 running on Windows 10?

  Do I need to install a third-party software to read data from bluetooth?

  Bluetooth in LabVIEW function nodes using the Winsock interface to access bluetooth resources. This works very well for Bluetooth 2.0 devices but not Bluetooth 4.0 devices WHEAT aka. Microsoft has created a completely different interface for these resources API as the model of overall service for WHEAT devices has radically changed.

  The API to use WHEAT devices is the API of the GATT (generic attribute profile) in Windows. There is supposedly a .net interface available that you can try to use (Windows.Devices.Bluetooth.GenericAttributeProfile). The WinAPI to lower level (https://msdn.microsoft.com/en-us/library/windows/hardware/hh450825(v=vs.85).aspx) is a C DLL API and does not lend at all to be called directly by the LabVIEW call library node, since some of the parameters of the function are quite complicated and you need to also access the SetupDI APIs to enumerate resources WHEAT and even harder to function parameters. In order to access this low-level API to write an intermediate DLL which results in low level API C a more acceptable API for LabVIEW.

  Another possible problem is that Windows don't at least in Windows 8 not allows devices to pair per program. Microsoft wanted to force developers in the use of the "inbox" experience, which means that all users must go through Microsoft provided service pairing, instead of each request for implementation of his own matching technique.

• Police Wingdings 3 is no longer an Option in LabVIEW 2015

  My company just put update 2015 of Labview.  In a number of legacy VI, Wingdings 3 police was used to display the up and down arrows.  Use an image to display the arrows is not an option and Alt Codes display in the form of '?'.

  If I highlight text, drop-down list box displays font Wingdings 3, but is no longer an option to select in the menu dropdown.  Please tell me that I should not edit every VI that has used this font.

  Wingdings 3 do not appear on the list of fonts for my installation of LV2015, but the police disappeared from the c:\Windows\Fonts directory.

  I copied the Wingdings 3 police in this directory from another machine and it appeared instantly in the drop-down list of LV (without having to close and restart).

• Discreet Integrator (control and Simulation Module) - LabVIEW 2015

  Hey everybody,

  I'm trying to drag the discreet Integrator on a block in 2015 of LabVIEW diagram. All other vi in the "range of discrete linear systems are draggable, but not the"discreet"Integrator." I noticed the same thing for the continuous Linear Systems Integrator. Anyone explain how to solve this problem?

  Sincerely,

  Lex

  Lexicondi,

  Unfortunately, these functions cannot be moved out of the loop control & Simulation. We support only discrete transfer, of State spaces and ZPK models function.

  So, if you want the "discreet Integrator" outside of the SIM card, you have the following options:

  one) to use the "discreet transfer function" as T /(z-1) (or any other type of discretization available in discreet Design continuous monitoring);

  (b) you can develop your functions inside the control and the Simulation loop and then create a subsystem of her. The subsystem can move outside the SIM card also. Here, you can use any SIM function you want;

  I hope that this should be sufficient for your application.