LabVIEW ARM embedded systems tutorial

Similar Questions

• Variables in SubVIs reset on each call to MCB2400 in LV2009 ARM embedded

  Hello

  I have a problem with variables in SubVIs. If I put them on my MCB2400 (ARM) they reset at each call. So it s impossible to build a counter in a Subvi. If I run the same VI on my PC, everything works fine. Just on the ARM it doesn´t work more.

  In my example (see attachment) to build two counters. A hat of the Variable to increment in the mainVI and the other in the Sub - VI. And that, in the mainVI the other not work (on the MCB2400). But if I run the same on the PC, both work without any problem.

  Anyone has an idea where is the mistake of m or is this a bug in the LV2009 ARM embedded?

  Bye & thanks

  Amin

  This isn't a bug.
  When it comes to read the local variable program gets a value of the indicator that is in your PC, not on the target. Control/indicators are not updated continuously, but with the specified period in "Configure the target" of dialogue. In your application you do not give a chance for the indicator update until the next iteration.
  However, it is not recommended to use local variables. You can use something like this:

  

  As an alternative, you can use 1 iteration loops store this local in a shift register.

• examples of LabVIEW ARM code

  Hello

  I am new to Labview ARM I used an ek-lm3s8962 Keil Committee.

  I would like to know if there are a few tutorials and code examples on communications with devices:

  How to write you SD card?

  How to use CAN, SPI, I2C and UART?

  How to use the OLED?

  Is it possible to use the FIFO memory with labview ARM and how?

  Is it possible to target the daughterboard with Labview, this Board includes a processor LM3S2110?

  How communicate between a time critical Vi which runs on the ARM processor and not time critical Vi host that runs on the PC?

  Thank you very much.

  Your Neil

  Hi Neil,

  How to write you SD card?

  The SD card slot only is not currently supported in point 1.1 of the ARM.  The next version of the ARM should support this device.  Once this is the case, you can access the SD card using the primitives of e/s files.

  How to use CAN, SPI, I2C and UART?

  I found an example of UART in the Finder for example OR in Modules and Toolkits > ARM > Luminary Micro > protocol drivers > Comm.lvproj series.  I will attach also a project that uses CAN communicate with the LMS2110.  As for I2C/SPI, I suggest experimenting with the screws for this (located on the ARM > palette SPI and I2C) and consultation of the other threads on the use of these screws or create another thread.

  How to use the OLED?

  There is an example of this in the Finder for example OR in Modules and Toolkits > ARM > Luminary Micro > Device Drivers > OLED.lvproj.

  Is it possible to use the FIFO memory with labview ARM and how?

  FIFO on ARM is very similar to the desktop.  These screws are located in the data Communication > synchronization > FIFO pallet in real time.  There are several examples on how to use these FIFO on ni.com.

  Is it possible to target the daughterboard with Labview, this Board includes a processor LM3S2110?

  You can provide this Commission with CAN, as shown in the attached draft.

  How communicate between a time critical Vi which runs on the ARM processor and not time critical Vi host that runs on the PC?

  See the related example. RT FIFO If you use the FIFO screws I mentioned above, you should be able to do something similar.  I suspect that the FIFO is used to communicate between a critical time timed loop and while loop a criticism.  The while loop would then use TCP/series (or even shared network variables) to communicate to the host.

  Good luck

• 2012 LabVIEW Eval/training MVC tutorial must IMAQ but Vision must LV 2011 installed in order to install.

  I'm using LabVIEW 2012 evaluation of training mode in order to find a location using LabVIEW. A MVC tutorial looks like a very good example and I can open the first VI, Starter.vi of MVC, but when I try to open the project which includes screws to MVC OOP advanced with controls and Factory.vi, it must IMAQ live but when I try to install Vision in order to get the screws IMAQ, it needs LV 2011 installed in order to install the Vision and will not proceed with the installation of Vision/IMAQ.

  After searching the site OR days to get responses LVOOP I found this tutorial that could be useful, if it's actually working.

  Setup of Vision should probably work with 2012, but the installer was not setup to work with 2011 or later.

  In addition, I have not found a good description of what the MVC "framework" is all about.

  I used LabVIEW since the beginning of the 1990s, but not from my NI Suite which included LV 8 and LVOOP about 2007. I desperately need a step by step "how-to and why ' for LVOOP, ACTOR, etc. I'm through the core I and Core II manual of training for certification, but it needed LabVIEW work as soon as POSSIBLE and do not have the $2,500 to upgrade my NI Suite or $10,000 for training or time to complete certification now.

  It seems that every time that I start to make progress and NI LabVIEW, I hit a roadblock. Nothing seems to ever work as announced.

  Help, please!

  First, you must determine what version of LabVIEW, you: 2011, 2011 SP1, 2012, 2012 SP1. You can find this by opening LabVIEW and navigate using-> on LabVIEW...

  Then, you download and install the compatible version of the Vision Development Module. Here is the link you should use:

  http://www.NI.com/downloads/products/ (search for Vision Development Module).

  In addition, there is a driver software that exists that is called Vision Acquisition Software. But, if you do not interact with the hardware at this stage, then you don't need it. Here's a better explanation:

  What is the difference between software Vision VDM, VBAI and going TO?

  About MVC, I'm no expert, but you should know what a MVC is and understand LabVIEW and characteristics before you dive into this example of MVC in LabVIEW. My recommendation is to not try to understand/learn MVC for the first time looking at this example. More information can be found by conducting a search on any search engine. Here is the Wikipedia article.

• LabVIEW arm pwm

  Hi all

  I'm trying to generate PWM with Laminary LM3S8962 signals.

  At first, I thought that always the entrance of the PWM output is the ratio between the width of the pulses.

  I connected to AI0 PWM2 and run this VI:

  

  By changing the value "PWM Input" AI0 strangely varies

  Hi Neil84,

  Thanks for posting on the Forum of National Instruments.

  Just to add some information about PWM with LabVIEW Embedded for ARM. Set you the divider in the properties of elementary school of e/s of the project? Here is some information pulled using LabVIEW:

  «The PWM frequency is the inverse of the period PWM.» A 16-bit system clock divider controls the frequency. For example, if the system clock is 50 MHz, the lowest possible PWM frequency is about 760 Hz. If you need a lower frequency, predivide based on the system clock of time PWM. To change the predivider, click the basic I/o node in the Project Explorer window, and then select Properties. This property affects the dating: 0/1, 2/3, 4/5. For example, if you set the output frequency 4, you also set the output frequency 5 because the two outputs share a common time base. "

  Thus, with a 50 MHz clock and a 16 - bit divider, you would get 50 MHz/2 ^ 16 = 762, and therefore the lowest frequency you can achieve (using the value of the divisor of 64) would be around 12 Hz. You set this value of divisor of the project for the e/s specific PWM.

  Let me know if this clears up things or if you have additional questions.

  Kind regards

• Freescale in the LabVIEW ARM controller?

  Hi all

  Is it possible to use the freescale MC9S12XEP100RMV controller in the ARMS of LabVIEW?

  Thanks and greetings

  Ben aljia P

  Hi Suren,

  The LabVIEW Embedded Module for ARM Microcontrollers using the "Keil uVision development toolchain to compile, download and debug applications", as this article explains.  (Taken peripheral ARM supported by LabVIEW)

  With this in mind, you should be able to use any microcontroller that supports the "RL-ARM real-time library."  Keil device database lists microcontrollers currently supported with this library.  (RL-ARM real-time library)

  The Freescale MC9S12XEP100RMV MCU is not listed as being supported.  Knowing this, you will not be able to use the LabVIEW Embedded Module for ARM, but you can use the LabVIEW Microprocessor SDK of Module.  The only difference is that the ARM Module has been built on the Module SDK.  The Module SDK is more "generic" and allows to develop support for virtually any 32-bit microcontroller software.

  I hope this helps.

  Kevin S.

  Technical sales engineer

  National Instruments

• Work of doesn´t of reading binary file on MCB2400 in LV2009 ARM embedded

  Hello

  I try to read a binary file from SD card on my MCB2400 with LV2009 Board built for the ARMS.

  But the result is always 0, if I use my VI on the MCB2400. If use the same VI on the PC, it works very well with the binary file.

  The
  access to the SD card on the works of MCB2400 in the other end, if I
  try to read a text file - it works without any problem.

  Y thre constraints for "reading a binary file" - node in Embedded in comparison to the same node on PC?

  I noticed that there is also a problem
  with the reading of the textfiles. If the sice of the file is approximately 100 bytes
  It doesn´t works, too. I understand can´t, because I read
  always one byte. And even if the implementation in Labview is so
  bad that it reads the total allways of the file in ram it sould work. The
  MCB2400 has 32 MB of RAM, so 100 bytes or even a few megabytes should
  work.

  But this doesn´t seems to be the problem for binary-problem. Because even a work of 50 bytes binary file doesn´t.

  Bye & thanks

  Amin

  I know that you have already solved this problem with a workaround, but I did some digging around in the source code to find the source of the problem and found the following:

  Currently, binary read/write primitives do not support the entry of "byte order".  Thus, you should always let this entry by default (or 0), which will use the native boutien of the target (or little endian for the target ARM).  If wire you one value other than the default, the primitive will be returns an error and does not perform a read/write.

  So, theoretically... If you return to the VI very original as your shift and delete the entry "byte order" on the binary file read, he must run a binary read little endian.

  This also brings up another point:

  If a primitive type is not what you expect, check the error output.

• This module requires a Lynxmotion AL5A robotic using LabVIEW arm control

  Hello world

  I'm a little confused about what NI LabVIEW toolkits to be used in order for me to program the arm Lynxmotion robotic. Somebody has arms lynxmotion robot programming experience using labview? What should be awared by selecting the correct tool boxes. Do I need to have the tools of design and simulation of control? What about embedded design modules? Please help me.

  Thank you

  Hi DK,.

  The Module digital output NI9474 high-speed Sourcing should be more than enough.

  In fact, we have a demo of work available by using the AL5D and NI CompactRIO. The concept should always be the same property.

  Best regards

  The Ilana Joshua

  Technical sales engineer

  NEITHER ASEAN

• ARM Embedded LV: Error: L6218E

  I have a simple program I wrote initially to operate on the cRIO. I'm now the porter to the ARM Keil MCB2300. I created a new project and configure the MCB2300 sucessfully (run several demos of specific LV ARM). I have added the original vi to my library project and deleted all references to the cRIO material. So basically I have a 'stand-alone' vi which may as well work on my host PC (i.e. without reference to any material, just a few loops and before panel buttons/lights)

  When I deploy it in my ARM Board I get the following errors:

  [11: 23:43] status: error
  which connects...
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol FreeEventNodeData (called state_machine.o).
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol FreeLVEventQ (called state_machine.o).
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol LVFrontPanelUnlock (called state_machine.o).
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol LVGetNextEvent (called state_machine.o).
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol LVUpdateScreen (called state_machine.o).
  .\Obj\LabVIEW.axf: error: L6218E: Undefined symbol RemoveFPEventQ (called state_machine.o).
  .\Obj\LabVIEW.axf: not enough information to generate a file with your COMMENTS.
  .\Obj\LabVIEW.axf: not enough information for image list symbols.
  .\Obj\LabVIEW.axf: not enough information for the plan of the image in the list.
  .\Obj\LabVIEW.axf: finished: 3 information, 0 warning and error messages 6.
  Target not created

  Status: Build failure.

  The name of my vi is 'state_machine' I have no sous-de VI. I know that there are some features limited blocks of LV for the ARMS. I use:

  -While loops

  -structure of the event

  -case of structure

  -arithmetic compoud

  -local variables

  I can't imagine that these would cause the build fails. I don't want to have to re - write my full arm program, if I can avoid it.

  Thank you

  Jason

  Yes, it's the structure of the event. Looks like I'm not the first person to have this problem. The structure of the event is a pretty complicated operation. I guess that LV Embedded for ARM does not support the structure of the event. All these interruptions C nice-code conversion is complicated.

  To resolve this problem, I just rewrote my structure of the parallel event multiple while loops. Inside of each loop is a structure of business T/F. The case is then triggered by what triggered my event.

  Thus, for example, if I had a structure of event with 5 tests, I have 5 simultaneous while loops, each with a structure of T/F case inside of them. Each case structure is then triggered by the Boolean that initially triggered the event.

  Sucks, but...

• JavaFX ARM embedded on Freescale i.MX 6

  I appreciate the work of the Java FX Embedded team and the excellent work they have done since the announcement of Java FX Embedded. I know that the current overview of developer for JavaFX on ARM Board works only on xM BeagleBord, but I thought it would be a good idea to play the Freescale i.MX 6 processor. I know restrictions on intellectual property within the Oracle or binaries of the preview, I tought this thread could be the first step in the participation of the community.
  
  Here is little information on the Freescale i.MX6 processor:
  
  * Quad-Core ARM® Cortex A9 processor at 1 GHz by heart
  * 1 GB of DDR3 wide 64-bit @ 532 MHz
  * Multi-stream-able engine video HD delivery 60 1080 p H.264 decode, encode 1080 p 30 and 3D HD video playback
  * Graphic of Triple Play consisting of a 3D Quad-shader unit and an acceleration of OpenVG Vertex 2D engine and system separated separated for superior 3D and 2D acceleration interface
  * etc.
  
  More information is available at the community Linaro - https://wiki.linaro.org/Boards/MX6QSabreLite, Freescale i.MX6 - http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX6X_SERIES and limit of the devices - SabreLite Council http://boundarydevices.com/products/sabre-lite-imx6-sbc/.
  
  JavaFX shipped to J1 team confirmed that a number of technical requirements for the operation of on-board JavaFX must be completed, including:
  
  * Linux 3.x kernel
  * ARMv 6/7 Core
  * Integrated EGL / GLESv2 support
  * Built-in touchscreen support
  * Integrated Gstreamer with hardware decoding
  
  From a technical point of view, the i.MX platform 6 meet these criteria largely. For this reason, I have collected the parts of official source code, I want to share with the community.
  
  * Freescale - Ubuntu service https://www.dropbox.com/s/ofhdrga8toju5ho/oneiric-freescale-12.09-GA.tar.gz file system root (October 2012)
  * Kernel Linux Freescale Sources - https://www.dropbox.com/s/1h8bqq2ibcog2e1/boundary-L3.0.35_12.09.01_GA.tar.gz
  * U - Boot Boot - Loader Sources - https://www.dropbox.com/s/th5irqowqbqlmm3/u-boot-2009-08-boundary-L3.0.35_12.09.03_GA.tar.gz
  
  The instructions to compile and run the sources are available in the limit of devices - SabreLite Board - http://boundarydevices.com/blog or the Linaro-https://wiki.linaro.org/Boards/MX6QSabreLite community.
  
  What I really want to do is put on a first step in the dialogue between Oracle and Freescale. I appreciate any kind of feedback on this topic, please feel free for any kind of comments.
  
  Greetings
  
  Hannes

  I thought that I give a brief update on it. Recently, we had the chance to test the last JDK 8 binary EA for ARM including JavaFX.  Embedded JavaFX team did a great job and development is progressing rapidly. To keep a long story short, for now, there is no support for the i.MX6 platform. Also be prepared to adapt your code to a few changes in JavaFX runtime. Several internet stations by hill david noted that the team definitely works on the i.MX6 platform.

  • https://community.Freescale.com/thread/297721
  • Re: JavaFX + UDOO - David Hill - net .java .openjdk .openjfx dev - MarkMail

  There are also rumors about a commitment to J1@2013 i.MX6 as a platform for high performance. Because Freescale as strategic partner this platform is extremely interesting for industrial purposes. So I'm really excited about how things are changing and looking forward to J1.

  Hannes cordially

• SD LabVIEW ARM storage limit

  What is the size limit for storage SD card on the plateau of MCB2300 ARM?  I want to use this forum, but you need to know the storage capacity before buying hardware and software.  I would use a 8GB card, but I'm guessing that maybe it's not possible.

  Hello

  ARM targets use the RL-ARM flash file system.  However, it seems all only 4 GB max.

  With the Flash file system, you can also write and read files on the standard SD (Secure Digital) and memory cards Flash MMC (Multi Media Card). They are used in SPI mode. Sizes of standard device of a little MB up to 4 GB are supported. Files on the memory card reader are stored in the standard FAT12, FAT16 or FAT32 file format.

  http://Keil.Asia/support/man/docs/rlarm/rlarm_fs_flashfs.htm

• 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)!

  
  

• LabVIEW Object - Oriented Programming - tutorial

  Hello

  Are there tutorial manual LVOOP? I'm looking for a tutorial as LabVIEW Basics I and II, which explains the basics

  If you have any SSP you have access to a range of online courses , including the object-oriented design and programming in LabVIEW (the recommendation is to have taken 1 Core, Core 2 and Core 3 before taking this course to get the most benefits).

  If you come from of the object oriented and want to see how it applies to LabVIEW, take a look at the decisions behind the white paper Design.

  Hope that helps,

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments | Certified LabVIEW Architect

• modulation toolkit for labview for embedded controller PXI-8106

  Hello

  I have an on-board controller: 8106 PXI OR PXI 5661 and 5671. He came with DAMA RFSG but not the Modulation Toolkit (TM). Now I cannot access some screws RF Toolkit as NI DAMA close.vi etc. I opened a code that uses this DAMA close.vi and since I donot have probably MT, I can't run since the claim code to choose the path!

  I checked for the TM in the start menu-> all programs-> national instruments-> modulation but in vain. Also, I opened MAX and under "Software", I could find DAA, pilots RFSG etc but not the Mt.

  When I checked online it says I have to buy the cd/dvd of MT. If I do, how I run on my controller?  What are my other options?

  PK

  Hello

  I think I solved the above problem. I had to install the RFSG and ACD for labVIEW. For some reason, the equipment was delivered to me with DAMA and RFSG, but only for C. This part was misleading because I saw on my National Instruments system but not the DAMA DAMA and RFSG vi. Also spectral measurement Toolkit (SMT) has not been installed. SMT is a MUST for the good functioning of the RF VSA. After you install the required drivers and tool boxes, I am able to run and use the VI completely.

  Thanks for your support Abhishek.

  PK

• Possible to use labview with daq system not of NOR?

  Hello

  I have a daq system and the software from another company that NEITHER. But I want some changes in the software. If the opportunity was to make a new program with Labview.

  Is it possible to use the old system of data acquisition? Is this compatible with Labview? Or I have to buy new hardware?

  Thank you.

  Hi VIassaks,

  Good afternoon and I hope that your well today.

  Thanks for the post.

  LabVIEW can communicate with 3rd party hardware using the library function call is located in the tip under the functions Palette palette. If your equipment is equipped with a DLL at the driver level LabVIEW can communicate with the hardware. However, you must obtain documentation of the DLL so that you can create your own interface for the material of the part 3.

  Another option would be if the hardware manufacturer provided LabVIEW VIs that control their material. You will not be able to use the screws (National Instruments Data Acquisition DAQ) because these screws use the DLL OR-DAQ, which is our software at the level of the driver for our DAQ cards. Other companies use their own software to the driver level to control their own material. Only the National Instruments hardware uses the NOR-DAQ driver that allows you to use LabVIEW DAQ screws.

  Hope this helps,