Support to an MSP430 in LabView Evaluation Committee

Similar Questions

• Superposition of LabVIEW evaluation software

  Hi, I've migrated my test environment software LabView2009 and TestStand4.2.1 to LabView2011 and TestStand2010. Test software is then installed on the target machines where is allowed only TestStand RunTime, while LabView adapters is configured to use the runtime, then no license is necessary.

  Test sequences call a few screws and display front panel, forcing the operator. After the migration of the new versions, the front panel has the recovery notice: Labview evaluation software (see attachment). It's very noisy!

  Is there a way to remove this overlay? Unless of course license Labview.

  Thank you very much.

  Is it possible that you made the massive compilation of your LV screws using one unlicensed (read: Trial Version) installation of LV?

  Norbert

• NOR-Fieldpoint supported in Windows 7 and LabView 8.6

  We have a 'classic' with an ethernet controller FieldPoint system. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Windows 7. NOR-FieldPoint is supported in LabView 8.6 and Windows 7?

  Kind regards

  Nate

  Hi natewkidd,

  I feel like some confusion between the operating systems running on a development computer (as Windows 7) and real-time operating systems that run on our real time (such as the PS-2000) controllers. I will do my best to clear up this confusion first answering your questions.

  (1) what is the difference between 2009 LabView real-time and LabView 2009?

  LabVIEW Real-time 2009 is actually a software officially known as 2009 LabVIEW Real-time which is installed after the LabVIEW 2009 development software to allow the user to develop and deploy applications in real time on targets in real time as your PS-2000. You can consider the LabVIEW Real-time 2009 almost as a plug-in for LabVIEW 2009 deployment and development of real-time applications.

  (2) if I have a PS-2000 on the ethernet network and to use a computer that is running Windows 7 and LabView 2009 for record and display data, will I still be able to communicate with the network FieldPoint screws write FieldPoint to my Windows 7 computer?

  If you go just to use the PS-2000 as a network module (NOT to deploy a real-time application to run on the PS 2000 itself), you should be able to communicate with him using just the read/write FieldPoint screw on your Windows 7 with LabVIEW 2009 machine and the driver NOR-FieldPoint 6.0.5. In this case, you actually do not need the Module Time since you do not deploy the application to the target in real time.

  About the PS-2000 unsupported beyond LabVIEW 8.5.1, is because the controller's memory is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Module real-time and LabVIEW Real-time Module 2009. For more information on this, you can check this knowledge base article.

  I hope it's useful! Let me know if you have any other questions.

  Thanks for choosing National instruments.

  Aaron Peña

  National Instruments

  Technical sales engineer

  http://www.NI.com/support

• Support of NOR-DNET for LabVIEW 2013

  We currently use OR DNET 1.6.6 with LabVIEW 2011. I installed LabVIEW 2013 now also on my computer and tried to synchronize all of the drivers with my installation of LabVIEW 2011.

  Well, it seems that NEITHER-DNET does not support LabVIEW 2013, at least officially. compatibility of Version of LabVIEW and NOR-DNET indicates that NEITHER-DNET 1.6.6 supports 2011 NOR-DNET 1.6.7 2012 LabVIEW and LabVIEW.

  The list NOR system driver November 2013 set OR DNET 1.6.7 defined pilot. When I try to install it, there is no support for LabVIEW 2013.

  My question is, if there is a plan to include support OR DNET for LabVIEW 2013 or later in the game to pilot?

  I copied the directories vi.lib\DeviceNet and vi.lib\nidnet of LabVIEW 2011-2013 and I can load my programs without any problems. I always did not build an executable and does not run on the test set-up, but projects can be loaded in LabVIEW 2013 without any screws of brocken. should I expect any problems running LabVIEW 2013 with the NOR-DNET to 1.6.6 and 1.6.7 driver?

  Nick

  There should not be problems but it is a former pilot, we will not be updated for the future version of labview.

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

• "Languages: language ' not supported in this version of labview

  Hello

  I'm changing with the labels on the front of my vi, depends on which version of the language of the environment LabVIEW Runtime was installed.

  To check which language I'm currently using, I tried the 'VI' type property node class "languages: Current Language. When running, I was told that LabVIEW does not support this...

  Is it because I'm using LabVIEW Base or am I missing something?

  Cheers, Alec

  alecjcook wrote:

  Yes, that would do the trick. How to integrate this control with labview?

  Cheers, Alec

  Call function from Kernel32.dll:

  

  Take a note that LabVIEW is non-Unicode, so you could suffer langugae ID, which has been set for non-Unicode applications (check the advanced settings in the control panel)

  Andrey.

• Can I do an installer in Labview evaluation Mode?

  Hi all..!! I recently installed Labview 8.2 and I need to create an installer, but I don't know if I can do it in trial Mode... my guy is if after 30 days, I'll be available for always using my Installer... Thanks in advance for answers...!

  Sapingo,

  See this knowledge base. It shows the limits of the evaluation of LabVIEW version.

• Remove the Labview evaluation software watermark

  Hi, I've migrated my test environment software LabView2009 and TestStand4.2.1 to LabView2011 and TestStand2010. Test software is then installed on the target machines where is allowed only TestStand RunTime, while LabView adapters is configured to use the runtime, then no license is necessary.

  
  

• Front says & quot; Evaluation of LabVIEW & quot; After SP1 update

  I just upgraded Labview 2011 by installing SP1.  Please note that I am a registered user.  When installing, I selected several complementary products for evaluation.

  Now when I run one of my many existing applications the front panel has the superposition of "Labview evaluation software.  I can't have that.  I'm not evaluate Labview, I assess some of the add-on.  I can't distribute my applications to customers with the overlay.  How can I get rid of him?  I'm perfectly willing to get rid of software assessment if you tell me how to make sure that the overlay will disappear.

  It is a matter of urgency.  Help, please.

  David Lieberman

  [email protected]

  Hi David,

  I'm sorry for the confusion about the option "ask an engineer".  I informed our moderators and they took your serial number.  I apologize. This looks to me to question you see is purely a question of activation.

  If you go to the License Manager, you should see a variety of software that has various boxes of color next to him.  Specifically, you will want to check this Application Builder and the version of LabVIEW, LabVIEW 2011 development system are green.  You have the serial number is valid for the system development and the request of the manufacturer.  You want to check, by highlighting the specific software, the status is 'Active for this computer' and that the Expiration of license file is 'never '.  If there is nothing else, right-click on the name of the software and choose Activate.  You will then be asked through our activation assistant who should be able to get operational.

  If you still have problems, I encourage you to call and create an application for one of our engineers can solve this problem and get your system in place and running especially if it is a delicate situation of the time.

• Can LabVIEW Embedded for ARM works with any Board or just with a few predefined?

  Hello

  Can LabVIEW Embedded for ARM works with any evaluation committee or just with a few predefined (MCB2300, MCB2400 and EK-LM3S8962)? I ask this question because even if I chose "another processor" in the definition of the new project only 3 options are the corresponding arm of Phillips and LuminaryMicro.

  Thanks in advance,

  Howdy,

  LabVIEW for ARM supports the feature of targets for tier 1 (the mentioned Evaluation Committee) following this schema:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/7066

  But you can transfer to other weapons if you follow this porting guide:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/6994

  The uProcesser SDK is intended for the port of other targets of DEPENDENCE (32-bit, of course) and technically it covers ARM as well. Alternatively, there are the LabVIEW C Code Generator: http://sine.ni.com/nips/cds/view/p/lang/en/nid/209015

• LabVIEW Embedded for ARM build fails

  I use the LabVIEW Embedded module for ARM microcontrollers with the
  The EK-luminary LM3S8962 Evaluation Committee.

  When I try to build/run vi as an example in the tutorial (pg 13, the start-up
  doc) I get the following error: Build Failed. Build failed with errors.

  The result is the following:

  Building target "LabVIEW".
  mounting Startup.s...
  compilation of RTX_Config.c...
  .. \System\RTX_Config.c(157): error: #130: wait a "{}".
  compilation of Retarget.c...
  compilation of TargetInit.c...
  compilation of ARM_irq.c...
  compilation of ARM_RTClock.c...
  compilation of ARM_Serial.c...
  compilation of EKLM3S8962_Display.c...
  compilation of LM3S_EMAC.c...
  D:\Program NIUninstaller Instruments\LabVIEW
  8.6\Targets\Keil\Embedded\RealView\Drivers\RL-ARM\Include
  \RLARM_Net_Config.h(31)
  : error: #256: invalid redeclaration of type name "S8" (reported on line
  37 of
  "d:\Keil\ARM\RV31\INC\RTL.h")
  compilation of ARM_I2C.c...
  compilation of ARM_SPI.c...
  compilation of LM3S_Pins.c...
  compilation of LVCGenIntInit.c...
  compilation of Untitled_ARM.c...
  compilation of lvEmbeddedMain.c...
  <-----snip------>
  compilation of RLARM_CAN_Wrapper.c...
  Target not created

  You forgot to tell us about your version of MDK - ARM (perhaps MDK 3.5 +).
  Open Keil uVision and double-click these errors:

  .. \System\RTX_Config.c(157): error: #130: wait a "{}".
  Just move __task at the beginning of this line
  __task void os_idle_demon (void) {}

  To make a permanent change, you could also modify the \Targets\Keil\Embedded\RealView\EK-LM3S8962\Template\System\ RTX_Config.c

  \RLARM_Net_Config.h(31)
  : error: #256: invalid redeclaration of type name "S8" (reported on line 37 of "d:\Keil\ARM\RV31\INC\RTL.h")
  Comment out the line:
  typedef char S8;     / * defined elsewhere from MDK 3.5*.

  It will be for good.

• Can what cards I use to develop communication SPI with Labview?

  First of all, I'm an intern is currently working on a project that involves communication with an SPI interface. I have absolutely no experience with SPI, but I finally decided to try. I work for about 6 months with labview and understand the function of basis of a large number of its resources.

  The problem:

  We want to connect Labview to an evaluation Committee that is connected to the PC via USB (but it can also be adapted to connect through SPI). The evaluation board mainly reads and writes if sign up for issuers that are connected to it by a Module assessment. The program which is already which is the Studio of SmartRF (that works via USB), but as we want to link all the functions in Labview we redevelop a platform to do so. If shortly, we want to make a Studio of SmartRF version in Labview. We want to be able to get all the information that makes the program and others... and all this is possible through SPI.

  Here is a link in case you are interested what is SmartRF Studio: SmartRF Studio link

  My question is which card do you recommend for what we are trying to accomplish? We are looking for something not very expensive but who fail to meet our requirements.

  I think of the NI USB 8451, but please make suggestions.

  Thanks a lot in advance and please stay tuned to my many questions coming about how to accomplish this enormous task with no knowledge whatsoever of SPI or how to mix with Labview only one student. I am reading as much as I can find, so all the links will also be very much appreciated. If anyone has any experience with NI USB 8451 with Labview be kind enough to guide me

  Sincerely,

  Gisela

  If you have very little experience with LabVIEW and SPI, the 8451 is a good choice. It's expensive, but it's really easy to use and configure.

  The Aardvark is also a good choice. There pilots LabVIEW is also easy to use in LabVIEW. The disadvantages is that it doesn't have a lot outside of simply making SPI or I2C - in other words, it doesn't have a lot of GPIO. This can be important when control of multiple SPI devices, because it requires to select them lines individual slave.

  Dinah is really more than a product of laboratory, or something that is meant to be placed inside a camera. It is expensive, compared to the other two, but it doesn't have native drivers in LabVIEW. On the contrary, it comes with a DLL you can call from LabVIEW. I wrote a set of LabVIEW drivers for it, but I can't distribute.

  There are other products on the market, which some will resemble a device series to your computer. For example, you would use VISA to communicate with the SPI controller, and it would appropriate communication of SPI.

  Among the three mentioned here, I would suggest that you go with the neither of the Aardvark, one.

• LabVIEW for LEGO MINDSTORMS and EV3

  LabVIEW for LEGO MINDSTORMS can be used to program the EV3?

  There will be support for the EV3 with LabVIEW to come. Our plan is to be ready in the first half of 2014.

  MINDSTORMS EV3 of LEGO development environment is the only software I know that can be used to program the EV3 brick when it is made available for purchase.

• How to sit interface with matlab 2010A and labview 2010

  I use tools of simulation interface 5.0 with matlab 2010A and labview 2010, I want to take my cue from matlab, labview but signal transfer, I am facing a problem. I want to know is there any compatibility issue in sit 5.0 or I do something wrong?
  photos of errors are attached.

  natasftw wrote:

  http://digital.NI.com/public.nsf/allkb/02F5FA55FC28BDE1862578A30071F975
  While it is for 2011, I doubt that they decided to remove 64-bit compatibility as they went forward as 64-bit has become more rather than less demand.  In this document,notes LabVIEW Simulation Interface Toolkit does not support 64 bit versions of MATLAB application software."

  The extent of the compatiblitly for 32 - bit, I'd take a peek at: http://digital.ni.com/public.nsf/allkb/D174674A91E5536286257428005C2426

  The OP's question was SIT support 64 - bit version of LabVIEW and 64-bit version of the MATLAB/Simulink itself, not the operating system software.

  Document in your second link is on a completely different topic to have API for LabVIEW and MATLAB/Simulink/RTW (well, mostly Simulink & RTW). Here is the relevant link for the 32-bit compatibility: http://digital.ni.com/public.nsf/allkb/049295038FF0EE2A86257A06006B2DAD is no SIT 64-bit.

  Other underlying issues is that Pharlap does not have a 64-bit version. Finally, simulations are better performed on some RTOS (embedded PXI) for a deterministic execution rather than PC operating systems.

  -BTC

• What versions of software Labview should I install for mindstorm NXT

  I would like to know what version of Labview evaluation software, do I need to install in order to communicate and to control the embedded Mindstorms NXT controller and its outputs (engine, sounds) and inputs (sensors). I used the nxtg software, but want to learn and activate the Labview associate for learning and teaching. Should I install all components of this version or just a little?

  I ask this question because I want to save space in my PC.

  No matter what version of LabVIEW is fine, but you want the NXT module which is free. Download LabVIEW. Simply search our site for 'module NXT' to get the latest version that corresponds to your LabVIEW.