LabVIEW 2009 SP1 image ROI identification number?

Similar Questions

• LabVIEW 2009 SP1 crashes when moving large selection with the arrow key

  If I select a lot (10 or 15) diagram components and try to move some distance with the arrow button, I'm often a program crash.  Because a reduced number of components seems to hang after a longer distance traveled, it looks like some sort of buffer overflow error.  I don't see this problem when you use the mouse to move selections.

  I checked to make sure I have the latest version of the video driver for my NVIDIA Quatro FX570.  I also tried to work with no hardware acceleration and no handset, written.  What happens on Windows XP SP3 with all current updates.

  It became so bad that I have to do a save as every fifteen minutes to avoid losing data.

  Why not use my mouse for all movements?  Because it is not as specific and not so easy to limit to only one dimension of the movement.   My hand is not as stable as it once was.

  I'm hoping someone will have a suggestion that will clear up this problem.

  As I have indicated, I had the same problem with 8.5 and just DID a new install of Labview 2009.

  Since it is possible that my three monitors configuration, which of course requires more memory video, may be at the origin of the problem, I am satisfied with workaround by dragging the objects closer to their final destination and then using the arrow keys.

  Three monitors are ideal for the front, block and help/Internet/probe damaged.  When I got to work in the field with a single monitor, I felt severely handicapped.

  You can consider the issue closed.

  Thank you for trying to reproduce the failure.

• "Decimal string to Number.vi" bug in LabVIEW 2009 SP1

  The "decimal string to Number.vi' seems to be the conversion of the input data in the type int32 internally even when the input tape in vi data is expanded floating point (no points of constraint).  This is causing me grief.  See attached vi

  This bug is still present in LabVIEW 2010?

  Thank you

  Richard Ballantyne

  There is no bug. You use the wrong function (see Help) If you want a floating point output. Use Fract/Exp string to a number.

• How to remove the scrollbars Panel sub with LabVIEW 2009 SP1?

  I did a search and found this thread on the subject: http://forums.ni.com/t5/LabVIEW/subpanel-scollbars-in-labview-8-0/m-p/284503/highlight/false#M149983

  I double checked that the horizontal and vertical scroll bars have not been successful in the appearance of window customize and they were not retained as shown in the image below.  You see scroll bars villain in the façade of the image at the bottom.  Of couse, since the code / sw cannot be shown, it has been repainted but you can still see the scroll bars along the frame of the side panel.

  Custom window appearance settings:

  

  Scroll bars appear at the bottom & right panel sub frame

  

  Found the solution...

  Right-click the scroll bars and select horizontal scroll bar and select always off.

  Repeat the procedure for the vertical scroll bar.

  

• LabVIEW 2009 sp1 not having replied to the questionnaire / accident

  Hello

  I seem to have developed a problem with LabVIEW, in which case it freezes at a random point during execution. It is not a matter of a VI gel, rather LabVIEW itself stops working and has closed by the Task Manager. What I have running at the moment is a VI host that sends and receives data over a TCP connection to a target in real time on a PXI system. The real-time application continues to operate after the crash. The host system is also running control of 3D image showing some basic graphics. The entire system is controlled at a higher level by a program crushed in c# via a TCP connection, but can work alone. When you run stand alone the problem will not occur.

  The communication between LabVIEW and c# works very well, but at a random time during the operation, LabVIEW freezes while c# continues to work. This does not appear to correspond to a particular action by the c# program. I guess my question is, is there any likely culprit by which LabVIEW can be crushed by an exernal program where the only communication is via TCP, which seems to work very well and where it does not seem to be excessive memory or CPU usage?

  See you soon.

  Fixed a problem with an update of the graphics card driver.

• LabVIEW 2009 SP1 - incorrect icon in connector component palette

  
  

  This was actually recorded under CAR # 116251 a long time ago. That being said, I can confirm that R & D is aware, but I feel that it is pretty low on the priority list...

• LabVIEW 2009 linux crashes when editing a control, or a constant of resources VISA

  Linux crashes when I click on a constant resources VISA (block diagram) or control (front).  This happens on LabVIEW 2009 SP1 32-bit for Linux on CentOS (similar to RedHat 6.3) 6.3.  I have updated drivers VISA 5.1.2 and that did not help.  Thanks in advance for any ideas of five Linux guys out there.

  Hello Jason,

  My problem has been resolved with LabVIEW 2012.  To answer your question, LabVIEW would crash only trying to select another device in the list.  Thanks for your help.

  Kind regards

  Marvin

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• Is there an Excel to TDM plugin for LabVIEW 2009

  I downloaded the Excel to TDM plugin and could not run. Dialog error usiReg said "this configuration file was created with a new version of the ICU and can not be used with the software you have installed." I installed LabVIEW 2009 SP1 and the .net version is 4.0. Y at - it another version of the 9

  the plugin I can use? Is there something else I can do, or am I just out of luck, until I update?

  Hello

  the functionality to open Excel files has been added to the ICU starting with version 1.8. However, the ICU in the manner described above upgrade you will register to use ExcelTDM and make it available through the _openWithRoot.vi in LabVIEW 2009. Simply install or DIAdem 2010 NI LabVIEW 2010 as a demo version.

  Please see also the comments from readers on the page of ExcelTDM use, a client has requested the use of using Excel in older versions of DIAdem:

  ExcelTDM use

  Greetings,

  Uwe

• convert elements using the DAQCard-6024E card to USB-6221using LabVIEW 2009

  I just got an old project, the VI has been primarily designed using the DAQCard-6024E map. Since we would be upgrading the equipment and the DAQCard-6024E serves not long. However, they want to keep the similar façade. I am trying to convert the drop-down menu that I can use with USB-6221 with Windows 7, but I don't know how. Can anyone help?

  Windows 7, NI USB-6221, LabVIEW 2009 sp1

  Hi smoothenigne007,

  After watching your upgrade.  All your writing VI should use the same task.  There is no need to close this task until the end of the program.  In addition, you can remove all the time because they do not allow the task close a loop.  I did a performance highlighted with your code and you can see that the first task was not allowed at the time wherever the data reached the second task.  When you try to create the second task, the error is generated.  Because you do not give me multiple writes to the same port there is no need to open and close the task each time.  Here is a link that will explain a little more about the DAQmx driver works.

  Getting Started With DAQ

  Kind regards

• Imaging Source DFG/SV1 acquisition card is not correctly recognized in LabVIEW 2009

  I have an Imaging Source DFG/SV1 frame grabber/capture card (I think that this example uses a Bt878 chip) that I am using with LabVIEW 2009 (Fall edition 2009 academic Site license), including elements of acquisition of vision (NEITHER Vision, NOR-IMAQ (4.3) OR-IMAQdx (3.4), etc.). I have all the latest sources of imagery support drivers and software for the Board of Directors (http://www.theimagingsource.com/en_US/products/grabbers/dfgsv1/ drivers: v6.0.3.0, IC Software v2.1 and IC Imaging Control v3.1) with drivers being compatible DirectShow. The DFG/SV1 is detected in MAX under devices NOR-MAQdx / DFG/SV1 / cam0 and I can grab and preview images, however to 320 x 240 resolution, I have a higher resolution camera and know that the jury is capable of greater resolution using IC software manufacturing and also via TWAIN with ImageJ software drivers. Interesteingly, if I try to acquire an image of the card purchase using the Vision Assistant, the DFG/SV1 card is not recognized as a card acquisition, but listed under IEEE 1394 or GigE peripheral, revealing with it being direct device that I can't understand. Despite this I can acquire images, but I am limited to 320 x 240 format and change the type of image (RGB, UYVY etc) causes an error. Once again, oddly enough, I can use "enter and select mode example VI" which should only be compatible with IEEE 1394 cameras.

  I'm not sure why LabVIEW is not seen this card properly, I contacted Imaging source who were also intrigued by the fact.

  Any information on how this could be resolved would be much appreciated.

  Thanks in advance.

  Hi OCastell,

  With this Council Imaging Source, the only interface supported with drivers of NI Vision Acquisition is through using IMAQdx DirectShow interface. It is possible that their DirectShow driver does not properly support all of the capabilities of their Council. Given that ICR software and TWAIN support can be routed to a different implementation of one of the DirectShow support, you can see the different features available. Unfortunately, you probably go through Imaging Source to determine why their DirectShow driver does not support the full resolution. You can confirm that it isn't IMAQdx this limiting trying other software such as Windows NetMeeting or AMCAP DirectShow and see what capture resolutions are listed.

  Because the DirectShow interface is managed by IMAQdx driver, it will not be detected as a framegrabber IMAQ using the IMAQ driver. This is expected since it fits in the same category as firewire and GigE Vision cameras and is supported with the IMAQdx driver instead.

  The "Grab and select the Mode" example VI isn't really specific FireWire, although he was certainly intended to highlight the various video modes that generally expose FireWire cameras. Since the DirectShow devices are similar and have several selectable video modes, it's why he's probably working. In any case, IMAQdx abstracts usually differences between all supported camera types and in general a single VI can run on all cameras IMAQdx-taking in charge unless you rely on buses or the camera-specific features.

  Regarding Vision Assistant marking the camera as 'IEEE 1394 or GigE', I think it's just an aesthetic issue (which may already be fixed in new versions). When IMAQdx was out, these are the supported types of cameras and so Vision Assistant was trying to say clearly what driver was used for the type of device. Now that IMAQdx supports a multitude of new interfaces (including DirectShow and some IP cameras) that the label is inaccurate.

  Finally, looking at the specs for this capture card, it looks like a standard reference BT878/848 model and then you could try potentially replace your Imaging Source driver with one here:

  http://BTWinCap.sourceforge.NET/

  I used this with a with IMAQdx BT878 capture card and can get it to capture an image full resolution (but of course, your results may vary...). It goes without saying that this solution using DirectShow is much more limited than using an industrial camera on 1394/firewire or a framegrabber IMAQ.

  Hope this helps,

  Eric

• LabView 2009 Service Pack 1 does this cause a problem with the MAthScripts for lo

  All,

  I just installed Service Pack 1 for Labview 2009.  All of my code that loops in my MathScripts now lets my MathScripts does not compile.  Have a clue what I do?

  Thank you

  Rich

  Windows XP (32-bit)

  LabView 2009 uninstalled, reinstalled after you have removed all files related to 2009.  SP1 installed, then applied for LabView and MathScript.

• LV 2009 SP1 Build error OR

  While trying to do a build on LV 2009 SP1, I get this error:

  The build failed.

  An error occurred during the recording of the following file: Sample.VI

  Details:

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use them following as a reference: 1 error this is produced to AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

  Possible reasons: LabVIEW: an input parameter is not valid. For example if the input is a path, the path can contain a character not allowed by the operating system such as? or @. = OR-488: command requires GPIB controller charge controller.

  Note that I do not use any GPIB. Also when I build the project NAV 2009 (without SP1) on another computer, I get no error. Any ideas?

  An Application (EXE). Now what I've done is removed the previous generation in the project framework > My Computer > specifications build and created a new Build > Application (EXE). And he built successfully!

  Now, of course was was wrong the first time... but it works now. Thank you!

• MCB2400 LabVIEW 2009 Embedded build error

  Hello

  I am evaluating MCB2400 with embedded LabVIEW 2009. Whenever I try to compile the application (even with a VI empty, no code block diagram), I get the following error:

  "" [15:35:15] status: error ""
  which connects...
  .\Obj\LabVIEW.axf: error: L6047U: the size of this image (16802097 bytes) exceeds the maximum allowed value for this version of the linker
  Target not created

  Status: Build failed. »

  I do not know whythe size exceeds even if I tried no code at all (white VI)!

  
  

• Question of LV 2009 SP1 EXE Builder

  Hi guys:

  I found the exe file, built from LV 2009 SP1 can be easily extracted with WinRAR, I can see all the main or sub - VI, is this a bug? or a risk of setting? I have not found the same problem in LV 8.6,

  Thank you

  I don't think that you should think about a lot of it. One of the first discussions on this subject is here http://forums.ni.com/t5/LabVIEW/decompiling-2009-executable/td-p/991662. It is true that they will be able to extract the screws, but they will not be able to see, any more than you show in your program.