problems with labview 2013 build specification

Similar Questions

• Software FPGA with LabVIEW 2013

  I have a system with a rotating computer "development" under Windows 7 and an NI PXI-1036 chassis with a PXI-8101 controller as well as a card FPGA PXI-7853R. Recently, I upgraded to LabVIEW 2011-2013 of LabVIEW. I kept LabVIEW 2011 installed just to make sure everything is still working on the new LabVIEW.

  Now, when I open my project in LabVIEW 2013 Project Explorer, my FPGA comes with a warning triangle yellow next to him (see attached photo). The warning says:

  "Software support for this target FPGA is not installed on the computer. You can view and copy elements into the project, but you can not compile any screw under the FPGA target, until you install support for the target. Refer to the documentation of specific material for more information on the proper drivers and for more information about the installation and configuration of the target FPGA ".

  Regarding the installed software, I have LabVIEW SP1 of 2013, 2013 of LabVIEW FPGA Module SP1, SP1 of Module 2013 LabVIEW Real-time, and Xilinx Compilation tools 14.4. On the chassis of the TARGET (with the PXI-8101 controller), I have attached a list of installed software.

  Interestingly, when I open the project in LabView 2011, no errors or warnings are present with the FPGA card. It is only under LabVIEW 2013 I see the warning. Did anyone see a glaring omission of software that could be the cause of LabVIEW raise this error? Thank you for your help.

  

  

  Best guess is that're missing you the driver for your FPGA device. Try to install the latest version of NOR-RIO (or at least the version supplied on your 2013 SP1 install disks). Have you installed device drivers at the time that you have installed SP1 2013 LabVIEW?

• Problems with secondary after building the application .exe

  Hi people,

  as I like am a self taught Newbie on LV and TestStand I have some problems with the construction of an exe file.

  I don't know if it is a question of LabVIEW and TestStand, so I posted this question in the two Forums.

  I use the interface simple chart that came with Teststand and added a secondary. TestStand is supposed to open the called VIs dynamically in this secondary.

  I used the code from the tutorial respective http://zone.ni.com/devzone/cda/epd/p/id/6278

  Everything works fine until I build the application. The screws are then open in pop-up windows clean AND in high school, but only the popup version is usable.

  I hope that I am too dumb to find the answer and that there will be a quick solution.

  If you have built the exe in LabVIEW 2009 selected in the configuration of your adapter TestStand and LabVIEW 2009 and your screws have been opened and saved in 2009 LV?

  

• cDAQ works correctly with Labview 2013?

  I have already upgraded to the LV805 for Labview 2013 in an existing system that has the cDaq-9172, NI9205, NI9263, and NI 9403.

  When executing NI MAX, it detects that cDAQ 9172 (chassis), but none of the cDAQ modules are detected.

  When I open my application, the paths of the cDAQ doesn't appear in entry options, so when it works, and the error message.

  I have SP1 2013 LV f2 and NEITHER-DAQmx 9.8

  This is a known issue, or I have a configuration problem?

  Help, please

  EDGAR_PLATRONICS wrote:

  Now, I have another problem.

  When I turn on my PC cDAQ does not start automatically.

  I have to go to services Windows and manually start OR Setup manager. Same startup is set to Automatic

  Once I run it, cDAQ works correctly.

  My company uses McAffe antivirus

  Concerning

  Edgar

  Mine also.  (McAffe)

  It turns out than if you change the startup type to "Automatic (delayed services start)" service OR McAffe plays more enjoyable.

  

• Problem with sharing of data specific to the application via BBM 10.2

  Hello - I am having a problem of data sharing applications with BBM 10.2-specific. I take the advice of some comments here, and it seems to work on 10.1. I can receive the file on 10.2, but when I try to share on the same device that I get this:

  InvocationWrapper::onQueryFinished: no matching result from Menu Service for query
     mimeType=""
     uri=QUrl("file:///accounts/1000/shared/misc/My App Data.myapp")
     data= ""
     metadata= QMap()
     perimeter= 0
     action= "bb.action.SHARE"
     target= "sys.bbm.sharehandler"
     invokerIncluded= false
  InvocationPrivate::onQueryResolved: no result matching query, no armed signal sent.
  

  It is the call that I use, which works on 10.1 but not 10.2:

  Invocation {
     id: invokeBBM
     query {
        InvokeQuery {
           id: invokeBBMQuery
           uri: "file:///accounts/1000/shared/misc/My App Data.myapp"
           invokeTargetId: "sys.bbm.sharehandler"
           invokeActionId: "bb.action.SHARE"
        }
     }
  }
  

  I also tried it with a "text/plain" MIME type and a few other variations, same result. If something has changed in point 10.2?

  (And while I'm asking, any reason why I can't use the data instead of a file uri? I need to convert the data in JSON, save the file, share the file, send, receive, save the file on the receiver, then open it, read it, and convert it back. Seems a little roundabout, if I could share the JSON data. "(And this is the only reason that my application requires permissions of shared files)."

  Thank you!

  It is a problem with the current version of BlackBerry Dev 10.2 Alpha.  You can call C++ BBM, but citing QML does not work.

• Problem with DPS App Builder and iPhone

  Anyone else see a problem with launcing is a 'DPS App Builder"App on the iPhone 4S. The app will launch, shows the splash screen and then close. Closing the application or the phone and launch new doesn't make any difference. He arrived with version 22 or 23. The same app launched on an iPad 2 has no problem.

  Anyone else seeing this?

  Ok. I built a new version of 22 App from scratch rather than update the 21 to 22 version I already had my DPS App Builder. This time it worked, no crash at launch on the iPhone. Also downloaded an edition in the sandbox and it worked fine.

  I would caution anyone to spend 21 to 22/23 with this new version of the App Builder. Take the extra few minutes and build it from scratch.

  Thanks for the pointer to Nathan.

• Modbuss problem with Labview 12 DURATION

  Hey guys / girls.

  I have a labview.exe work created with Labview 12 on a PC with the completely installed verstion LV12

  As I said created and built and tested again on the pc

  On another pc I just installed labview RT and the exe to bed

  the program consist of modbus

  but it does not work.

  Y at - it an additional package, I need to add more to the Runtime to get my Modbuss to work

  additional information:

  I tried two different com Modules while both B & B electronics is with drivers other works out of the 232/485 with drivers troubleshooting

  It is on Win 7 32 bit labview is 12 32-bit

  -Kurt

  What modbus library are you using? DSC or VISA? You have the runtimes for what you use.

• Problem control pumps syringe with LabVIEW 2013

  Hi all

  I try to use a program that was sent to me by a coworker to control 2 pumps to KD scientific syringe using LabVIEW.  The pumps are connected to a Windows 7 computer via a telephone line attached to the pump, which is then connected to an RJ11 to D - type RS-232 converter.  A Hawking Technology RS-232 to USB converter cable connects this converter to a USB port on the computer (this is because our computer has only 1 serial port but we have 2 syringe pumps).  It's the same establishment that has been using my collaborator and it worked without any problem.

  The problem arises when we try to control pumps syringe with the LabVIEW program.  We have drivers for Hawking and KD scientific syringe pumps cables installed on the computer, but our computer recognizes that the cable is plugged in - it does not recognize the syringe pushes like a 'peripheral '.  We can run the LabVIEW program, but essentially, nothing happens.  When we press "stop"button, we get an error message that says: "error 1073807202 occurred when opening VISA in Science KD 2XX series Initializes vi."  In my view, this means that the computer/LabVIEW is not able to communicate with the pumps, even if we have installed the drivers and in the same folder as the program.

  I enclose the program we are trying to run (it's Version 2, it includes the drivers for syringe pumps), the pilot shot of the error message, we installed the cable, as well as a screen.  If anyone knows anything we can try would be much appreciated.  The author of the program has been at a loss because it works wonders on his computer.

  Thank you in advance!

  Laura

  Indeed, I am convinced that the pumps are connected to the correct COM ports.  So I just thought of something... I noticed on the website OR that there are drivers for NI-VISA.  I know for a fact that I have not installed on this particular computer.  Does make sense that these missing drivers could be the problem?  That would explain the error to the opened VISA.  I do not have the administrator rights for this computer so I have to wait for an admin to connect and install the drivers.  I'll give you an update with what's happening.  Thank you all!

• Signal Express version unknown problem with Labview VI

  Hi all

  I am trying to run 2010 Labview Signal Express VI. It gives me "unknown version" problem. When I checked for Labview versions, he said 10.0f2 and Signal Express can read the version of LabView 2010. I don't understand this. 10.0f2 is not just a patch for version 10.0? I will appreciate if someone can help me with this.

  Kind regards

  Kanu

  Hi Kanu,

  I tried to write a simple VI and its importation to the Express Signal and I have not had any problems. I use 32-bit LV2010f2 and Signal Express 2010. I have attached the VI I used so that you can try it yourself. I followed the instructions of this KB to create a distribution of the source file. If you follow this KB and still can't make it work, can you please post the VI?

  Thank you

• Problem with LabVIEW

  I met a problem when using the peak detection function in LabVIEW...

  Basically, I load a waveform in VI to detect peaks using the function of Ridge detection. of the waveform, it is obvious that the first peak will happen about 10570Hz...

  Using size 3 subgroup, it detected 1 pic to 10567Hz (correct)

  When you use the size of subgroup of 4, it detected 1 pic to 10569Hz (correct)

  When you use the size of subgroup of 5, it detected 1 pic at 12737 Hz (bad)

  When you use the size of subgroup of 6, it detected 1 pic to 10588Hz (correct)

  When you use the size of subgroup of 7, it detected 1 pic to 10588Hz (correct)

  And using other different sizes of subgroup, the freq agrees with waveform... Why when you use the size of subgroup of 5, it does not give good playback? Is there a theory or a reason for this? or just a bug with the LabVIEW function?

  A VI is fixed and the default values are loaded.

  Appreciate any assistance/advice.

  
  

• Problem with Labview communication with Arduino Uno

  Hello

  I tried to run a simple program in labview through my Arduino Uno R3 all morning and keep running into the same problem: no response from my Board of Directors. I'll catch you up on what I've done so far:

  -flashed LIFA Base to my Arduino
  -Downloaded the driver update of VISA

  written-a the block diagram (I hope) for a led on off function

  When I run the program in labview, the RX flashing intermittent, continue for 30 seconds before stopping. The led on pin 13 is not turned off as it should, and I have no control over the power function light. I also tried a program of control of servo with no response and the same flash of RX. Never the TX flashes.

  I am quite stuck, so any help is greatly appreciated. Also I'm not a comp sci guy, I'm just an engineer in mechanics with a half of C++ so keep pg when it comes to the language of the computer.

  I've attached a picture of my diagram of LED, see if you can spot a problem.

  Thanks in advance!

  SOLVED: Reset the Arduino card after that labview had sent his orders (while the RX light was still flashing). Works like a charm.

• Problem with the last Build 442 contentHeight

  Hello

  I'm having a problem to access the controller contentHeight.

  The syntax is below.

  private var _controller:ContainerController;

  var newHeight:Number = _controller.contentHeight;

  It throws an error now, I was previously using IContainerController with build 370. It was working fine, but now that I switched to 442 with ContainerController, it displays error.

  Please suggest how I can access it.

  Kind regards

  Rajesh

  Hello

  Yes strange to delete this reference useful for the height.

  The way to achieve this goal now is to use

  textFlow.flowComposer.getControllerAt (0) .getContentBounds () .height

  or if you have a variable for your controller then just use getContentBounds () .height

  concerning

  Micheal

• Problems with labview on TestStand deployment system (usually run without a license of labview)

  I'm trying to deploy a system using testStand for a machine of deployment for the 1st time. I built my Installer and image etc files The files of the installation on the target however machine when I try to run my program in mode operator TestStand I get errors relating to Labview. The only way I can work around this error is to activate a Labview license on the deployment computer, is not viable.

  The error I see when I turn off my Labview license simply indicates that an error has occurred accessing the Labview ActiveX automation server.

  I have included engines of execution etc. in my Installer. As this is my first build is there something obvious I've missed here?

  Thanks for any input.

  Vinny

  Vinny,

  My first guess is that the setting of the LV adapter on the deployment computer is always set to "LabVIEW development environment". You must change this to "runtime".

  hope this helps,

  Norbert

• Modbus tcp 1.2 problem with labview 8.5

  I have a new upcoming project that involves a link to modbus tcp.  I downloaded version 1.2 of the modbus library and installed.  Everything appears on my palette, but if I try to open one of the examples he comes as for version 8.6.  I am currently using 8.5 but the download says it works all the way back to 7.1.  Any ideas?

  Are you sure that you have selected the correct folder for the "installation"? When you download the 1.2 OR Modbus Library (here: http://zone.ni.com/devzone/cda/epd/p/id/4756), you get a zip file. Inside this file, you will see 4 folders, one for LabVIEW 7.1, (issue 71), one for LV 8.2 (case 82) and also records 85 and 86. So make sure that you have done the installation with the correct folder.

  Let us know if this helps or not.

  Kind regards.

  Robst.

• Problem with LabVIEW 9.0f2 and VISA 5.0 on Mac OS x 10.6

  Hello

  I'm using MacOSX 10.6 and Labview 9.0f2. I installed the lates VISA (5.0.0) drivers, as they are the only support OSX 10.6.

  Now, I try to run the "basic series write and read" example and get the following error:

  Error 1073807343 has occurred to the property node (arg 1) visa set up a Serial Port (Instr) .vi-> basic series writing and Read.vi

  Possible reasons: VISA: information about insufficient localization (Hex 0xBFFF0011) or the device or resource is not present in the system.

  As I am a newbie to Labview, I'd appreciate any help on this...

  Thank you

  Daniel

  Hello

  You do not have a device series on behalf of resource, you use to write and read and take?

  Did you check with Max OR and log on to this device.