LabVIEW for the STM32F100 or the STM32F4 ARMs

Hi, i was wanting to get started with LabVIEW for ARMs.
http://www.st.com/internet/evalboard/product/250863.jsp
and
http://www.st.com/internet/evalboard/product/252419.jsp
I wanted to know whether the above ARMs are supported are not, already looked at the RL-Libraries provided by kiel
http://www.keil.com/rl-arm/chips.asp
Since the STM32F100RB is listed,
http://www.keil.com/dd/chip/5086.htm
can i use LabVIEW ARM to directly code the board?
Thanks.
LabVIEW 8.2,8.6,2009...still learning

Thanks for the reply andrey. I haven't ordered it yet, wanted to be sure about the compatibility. How about the STM32F103RB?. Its listed in the kiel libraries too.
http://www.keil.com/dd/chip/4231.htm
Here is a guy who has worked with it. Seems like he got it working. The boards the same as well.
http://forums.ni.com/t5/LabVIEW-Embedded/labview-for-stm32f103-development-board/td-p/1022402/page/4
PS: Both have the same code memory, surprising to see the STM32F100 gives an error.
LabVIEW 8.2,8.6,2009...still learning

Similar Messages

How do you add a third party sensor to LabVIEW for Lego Mindstorms?

I recently purchased an IR Sensor from Mindsensors (DIST-Nx-Long-v3) which I need for a SLAM (Simultaneous Localization and Mapping Application) that I am developing using the LabVIEW for Lego Mindstorms software. I installed the Mindsonsors IR Sensor, and it works under NXT-G and RobotC, but am having trouble finding a way to get LabVIEW for Lego Mindstorms to install the sensor.
The Mindsensors website gives the following instructions for installing the IR Sensor:
1.Unzip the folder mindsensors.com LVEE
2.Open a blank vi in LVEE
3.On the Block Diagram Go to Tools->Advanced->Edit Palette Set...
Unfortunately, on the Block Diagram of the LabVIEW for Lego Mindstorms, there is no "Advanced->Edict Palette Set" under Tools.
As an alternative, I consulted the documentation that came with LabVIEW for Lego Mindstorms. The Schematic Editor of LabVIEW for Lego Mindstorms lists several sensors, i.e. the Lego Mindstorms sensors and several Hi-Teach (HT) sensors, but there are no procedures listed in the documentation for adding other third party sensors to the Functions Palette.
So, how does one go about adding a third party sensor to LabVIEW for Lego Mindstorms?

Hi Ethan,
As you can see from my Word document, I am a little light on the proper terminology. That's because LVLM comes with inadequate documentation.
I have already followed your recommended protocol for installing a 3rd party sensor (in fact, its the protocol recommended by Mindsensors) with the application set in the Remote Mode (.lvrbt), and it does create a sub-palette with all the Mindsensors functions on it. But when I drag the Mindsensors icon to the Block Diagram and select "Distance Sensor," the Distance Sensor (an IR sensor) doesn't work (even though the Mindsensor's Distance Sensor does work with NXT-G, RobotC and LVLM under other circumstances (see below)).
If I repeat the above process with the application set in the Direct Mode (.vi), I also get the sub-palette with all the Mindsensors functions on it. When I drag the Mindsensors icon to the Block Diagram and select "Distance Sensor," the Distance Sensor does work.
What I need for my mapping application is for the Distance Sensor to work in the Remote Mode. I called NI tech support and the first engineer told me to simple drag the Mindsensors Functions (.vi) onto the Block Diagram. I did this, but when I selected the Distance Sensor, the icon appeared, but the sensor did not work. Since I have no idea what's under the hood of the vi or a function, I assumed that simply dragging the vi/function onto the desktop didn't install the vi/function properly. I went back to the Applications Engineer, and he confessed that he did not understand the LVLM product.
My frustration is being punted to new people, none of whom so far (other than you, of course) understand LVLM.

LABVIEW FOR LINUX

Hello,
Presently i am a user of labVIEW 7.1 and 8.2.1 windows version.
and also working on following hardware.
SCXI-1001 12 chassis,
SCXI-1125,SCXI-1124,SCXI-1160,SCXI-1162,PXI-1001,PXI-6251,PXI-6602,USB
1600,USB 6602,PXI-1044,PXI-6133,PXI-8187,PXI-9257.
since i am facing the problem of virus and sudden restarting of system,I am planning to switch over to linux version of linux.
what is ur comment on my deceision?
which version of linux OS will support all above mentioned products.
what are the other advantages i can get from LINUX version?.
Wil i get full programming help as available in windows?
Can we easily learn the programming by reding the help?

Hello chandhuu,
Most of your hardware will be supported except for the USB devices. The readme file for DAQmx 8.0 for Linux lists which devices are supported and by which Linux OS.
The LabVIEW 8.5 readme file for Linux would also be helpful, along with this KnowledgeBase article, which lists which Linux OS versions support National Instruments software and drivers. You will find that programming in LabVIEW for Linux is basically the same as in Windows, so you shouldn't have any trouble switching over if you are familiar with Linux and with LabVIEW. Personally, I am not too familiar with Linux so I feel much more comfortable with LabVIEW for Windows. What about just having a dedicated Windows PC that you can take off the network and use with LabVIEW so that you don't have to worry about viruses?
Regards,
Clint M
National Instruments

Can I target the STM32 Primer2 hardware with LabVIEW for ARM

The STM32 Primer2 hardware looks very cool. Can LabVIEW for Arm target this hardware? From looking at the list of ARM devices supported by LabVIEW, this would appears to be a Tier 2 device (ARM Cortex-M3) with no support for TCP/IP or IO.
Can anyone tell me the feasibility or effort required to get TCP/IP, IO, and maybe even display support for this device?
Message Edited by Jim Kring on 09-11-2009 10:46 AM

Have you ever said something you wish you could take back after having time to reflect upon it? Another forum I like, http://newsbusters.org lets the author edit his posts for a short time. Maybe NI could to that and I would not be pulling out my foot so often.
Well, perhaps I was a bit more "colorful" than I meant to be. Frustration does that to me sometimes. Still the idea of a strong rope covered with disgusting risks does get the point across magnificently. I just wish I had saved it for something more suitable.
Let me think back to some of the problems I've had in which I've lost hours trying to figure out...
1. Can't use the Wait ms function. It halts the program. Express wait works fine. It was sprinkled throughout which made it hard to isolate.
2. Some sub VIs don't run unless they are checked as inline code. I don't yet understand why.
3. At the beginning of my main vi there was a small cluster in which I filled the data from an SD card file. I used a constant of the cluster on the input of the Bundle function, but because my program and variable sizes were near the max I changed a number of variable representations to save memory. ...But I didn't replace the constant. The program started exhibiting really strange behaviors. I couldn't even get a simple state machine to run. I was reduced to commenting out (disable structure) sections to find the problem before noticing the coercion dot on the input to the bundle (The dot against the red string color doesn't stand out very strongly which is why I missed it). Apparently it overwrote memory since the older cluster was significantly larger than the new.
4. Spent a lot of time trying to get the SD card to work with SPI functions. Even though I read that 2009 supported SD card file services I didn't intuitively understand how to wire up since the Open/Create/Replace function has a ref num output which actually connects to the file(use dialog) input of the read and write functions.
5. Had a problem with breakpoints and probes not working. That apparently was caused by item #3.
6. Typo bug in the Arm_irq.c file LM3Sxxxx_GPIOCAHandlerP to LM3Sxxxx_GPIOCHandlerP
Some of these are of the rope variety. A few are actual bugs. All probably could have been solved in moments had I a local guru. Anyway, I've spent hours and my hands hurt. I hope to have this little project working on the LM3s8962 today and after some hardware changes will port it over to the Primer2... Hopefully...
This forum has been a real help... especially your quick responses.
regards to all,
David

How to let the user define the colors for each plots in the graph (I use LabVIEW 7)?

How to let the user define the colors for each plots in the graph (I
use LabVIEW 7)?

Hi,
Take a look at this example, it uses property nodes to select tha
active plot and then changes the color of that plot.
If you want to make the number of plots dynamic you could use a for
loop and an array of color boxes.
I hope this helps.
Regards,
Juan Carlos
N.I.
Attachments:
Changing_plot_color.vi ‏38 KB

LabVIEW 6.1 If For Loop count terminal is zero then value going through the loop is not passed on to the output of the loop

Hello, one of our customers just encountered an execution error in a vi running under LabVIEW 6.1, which doesn't exist under LabVIEW 5.1 or 6.01. I have a simple vi that has two encapsulated For Loops. Two string arrays go in, one goes out of the outer loop. Inside the outer loop the first array is indexed. The string which results from this indexing is compared with all other strings from the second string array in the inner loop. If it matches one of the strings of the second array, it is not outputted, otherwise this string goes through the inner For Loop to the output of the inner loop and from there to the output of the outer loop. The count
terminal of the outer/inner loop is connected to the Array Size of the first/second string array. If the second array is empty, that means that the element in test from the first arry cannot match anything from the second array, so the element in test is send to the output of the inner loop and from there to the output of the outer loop. This works fine in LabVIEW 5.1 and 6.01, but NOT in LabVIEW 6.1. In LabVIEW 6.1 the inner loop is never executed if the count value is zero (which is correct), but the data line running through the loop is not executed either, which is different to what LabVIEW 5.1 and 6.01 do. There, the input string is sent to the output of the inner loop correctly even if the loop counter is zero. The solution is easy - I just have to connect the output of the outer loop to the data line BEFORE it enters the inner loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is supposed to be a feature, but it brings some incompatibility in programming between the
different LabVIEW versions.
Best regards,
Gabsi

Hi,
When a for-loop runs zero times, all outputs are 'undefined' (and should
be).
Besides, how would LV know what the output of a not executed routine should
be?
It might be handled differently in LV5 and LV6, which is unfortunate. In
both cases, the result is undefined.
It's not a bug. It's just something that should be avoided in any LV
version.
> The solution is easy - I just have to connect the
> output of the outer loop to the data line BEFORE it enters the inner
> loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is
In some cases this does the trick. But if the data is changed in the inner
loop, this will effect the results if the N is not zero.
Technically, I think the output in this construction is also 'undefined'.
But LV handles this as expected / desired.
Another solution is to use a shift register. If N is zero, the input is
directly passed through to the output.
Regards,
Wiebe.
"Gabs" wrote in message
news:[email protected]...
> LabVIEW 6.1 If For Loop count terminal is zero then value going
> through the loop is not passed on to the output of the loop
>
> Hello, one of our customers just encountered an execution error in a
> vi running under LabVIEW 6.1, which doesn't exist under LabVIEW 5.1 or
> 6.01. I have a simple vi that has two encapsulated For Loops. Two
> string arrays go in, one goes out of the outer loop. Inside the outer
> loop the first array is indexed. The string which results from this
> indexing is compared with all other strings from the second string
> array in the inner loop. If it matches one of the strings of the
> second array, it is not outputted, otherwise this string goes through
> the inner For Loop to the output of the inner loop and from there to
> the output of the outer loop. The count terminal of the outer/inner
> loop is connected to the Array Size of the first/second string array.
> If the second array is empty, that means that the element in test from
> the first arry cannot match anything from the second array, so the
> element in test is send to the output of the inner loop and from there
> to the output of the outer loop. This works fine in LabVIEW 5.1 and
> 6.01, but NOT in LabVIEW 6.1. In LabVIEW 6.1 the inner loop is never
> executed if the count value is zero (which is correct), but the data
> line running through the loop is not executed either, which is
> different to what LabVIEW 5.1 and 6.01 do. There, the input string is
> sent to the output of the inner loop correctly even if the loop
> counter is zero. The solution is easy - I just have to connect the
> output of the outer loop to the data line BEFORE it enters the inner
> loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is
> supposed to be a feature, but it brings some incompatibility in
> programming between the different LabVIEW versions.
> Best regards,
> Gabsi

LabVIEW could not generate code for the shared variable.You must open the VI in the project that contains the library where the shared variable resides

HI
When I put a network shared variable with fifo RT activated on my diagram, the arrow is broken.and I' ve got this message:
""LabVIEW could not generate code for the shared variable.You must open the VI in the project that contains the library where the shared variable resides""
If I uncheck FIFO RT option for this variable the arrow isn't broken anymore.
I 've no idea how to correct this weird error?
Autodeploy is on, and I've check copy / delete in diagram in tool/options\diagram
regards,
james

Hello,
I don't reproduce this error.
Could you send your VI?
Regards
VéroniqueD
NI France

LabVIEW for ARM 2009 Read from text file bug

Hello,
If you use the read from text file vi for reading text files from a sdcard there is a bug when you select the option "read lines"
you cannot select how many lines you want to read, it always reads the whole file, which cause a memory fault if you read big files!
I fixed this in the code (but the software doesn't recognize a EOF anymore..) in CCGByteStreamFileSupport.c
at row 709 the memory is allocated but it tries to allocate to much (since u only want to read lines).
looking at the codes it looks like it supposed to allocated 256 for a string:
Boolean bReadEntireLine = (linemode && (cnt == 0));
if(bReadEntireLine && !cnt) {
  cnt = BUFINCR;    //BUFINCR=256
but cnt is never false since if you select read lines this is the size of the file!
the variable linemode is also the size of the file.. STRANGE!
my solution:
Boolean bReadEntireLine = (linemode && (cnt > 0)); // ==
if(bReadEntireLine) {    //if(bReadEntireLine && !cnt) {
  cnt = BUFINCR;
and now the read line option does work, and reads one line until he sees CR or LF or if the count of 256 is done.
maybe the code is good but the data link of the vi's to the variables may be not, (cnt and linemode are the size of the file!)
count should be the number of lines, like chars in char mode.
linemode should be 0 or 1.
Hope someone can fix this in the new version!
greets,
Wouter
Wouter.
"LabVIEW for ARM guru and bug destroyer"

I have another solution, the EOF works with this one.
the cnt is the bytes that are not read yet, so the first time it tries to read (and allocate 4 MB).
you only want to say that if it's in line mode and cnt > 256 (BUFINCR) cnt = BUFINCR
the next time cnt is the value of the bytes that are not read yet, so the old value minus the line (until CR LF) or if cnt (256) is reached.
with this solution the program does not try to allocate the whole file but for the max of 256.
in CCGByteStreamFileSupprt.c row 705
if(linemode && (cnt>BUFINCR)){
cnt = BUFINCR;
don't use the count input when using the vi in line mode. count does not make sense, cnt will be the total file size. also the output will be an array.
linemode seems to be the value of the file size but I checked this and it is just 0 or 1, so this is good
update: damn it doesn't work!
Wouter.
"LabVIEW for ARM guru and bug destroyer"

LabView for ARM - MCB2300 Audio

Hi, and thanks for reading!
  My name is Chuck and I'm an undergrad ME student taking a mechatronics course. We were asked to create a proximity alarm with the MCB2300 and an IR proximity sensor. I have the entire program running correctly, but this lab has brought up a couple questions about how to better implement audio with the LabView for ARM processors.
  I understand how interrupts work, and I've seen a couple examples online of using an interrupt with a timed loop, but I believe the current version of LabView (2010) doesn't support that feature any more. I had a couple questions about how to get a feature similar to this to work with LV 2010.
  I was thinking I could have the proximity trigger enable an interrupt that I could use to generate higher quality audio than I am already making with a While - Timer loop. However, I'm not sure how to make an increment in the interrupt VI without using some form of a loop. The solution I'm thinking of at the moment is to make a For loop run once and to have an incrementing integer separate from the loop iteration (which would only go from 0 to 1) that stores its most recent value in the shift register.
  My other question is about playing a sound file through the MCB2300. I wrote a VI that reads a .wav file and writes each sample as the output needed to drive a speaker, but that decompression turns a 10KB .wav file into a 300KB text file. I also don't have a way to really load the text file onto the board. Is there any reasonable way to go about this? I found an example online that processes audio data using the MicroVision software, but I don't want to learn a new language to implement this.
  Sorry for such a long post, I just had a couple questions and was looking for some feedback. Any help would be greatly appreciated.
Thanks so much!

charlestrep91 wrote:
Hi everyone,
I just got my Labview for ARM cortex M3 evaluation kit and I can't download a simple program to the target. I'm using the Keil ULink 2 programmer and I get this error when compiling/downloading:
[4:23:16 PM] Status: Error
SWD Communication Failure
Error: Flash Download failed - Target DLL has been cancelled
Detail: [UVSC_PRJ_FLASH_DOWNLOAD, MSG: 0X100A, STATUS: Ex.] (1)
Status: FLASH download error.
I have read about this error and NI simply refers to Ulink2 user's guide which has this description for this error:
Serial Wire Debug communication is corrupted. The target SWD interface is not working properly. Mainly caused by the target: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section.
I have tried to "Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section" but it didn't resolve the problem.
I have also tried to download the program using the usb port on the dev board but instead I get this error:
[4:51:22 PM] Status: ErrorUnexpected error occurred.
[Source: Target is in debug mode
Detail: [UVSC_PRJ_ADD_GROUP, MSG: 0x1002,
STATUS: 0xA] Code: 10]
What am I supposed to do with that?? I'm wondering if the dev board is defective. And this was supposed to be plug and play...
Any help is greatly appreciated!
I'll ask the obvious question, are you intending to use SWD or just download through the JTAG. Check your settings. I have not used the ARM with LV, but can you download anything using the Keil software? Give that a try. That may tell us where the problem lies. Try to duplicate your settings in LV from the Keil sw.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

Accessing Onboard ADC with LabVIEW for ARM

I am working with the LM3S9062 Evaluation board and LabView for ARM system, and want to measure an analog voltage using the ADC, however I cannot determine which of the Digital Inputs is linked to the ADC. I need to know how the gpio mapping corresponds to the pinout of the Device. Any thoughts?

Do you mean the LM3s8962 evaluation board? If so, the pins should be labeled accordingly on the board - ADC0, ADC1, ADC2, etc.
Drop an EIO node with the same name as the pin and it should work fine from there.
Here are the schamtics : http://www.realview.com.cn/UploadFile/2008111510295067433.pdf

Why writes LabVIEW only every 2 seconds the measured Value to a Excel (In a while loop with 100 ms tact)?

Hi everybody,
I use the myDAQ to measure speed, ampere, and voltage of a battery driven motor. (For Current measurement, i use a Sensor which outputs a 0-10 V signal). I placed all DAQ-Assitants in a while loop with a [Wait until next ms multiple] clock and set a value of 100 ms. I thougt, Labview will now write into my text file 10 times a second all values. In fact, as you can see in the attached text file, Labview only writes in a unsteady interval of 1-2 seconds a value, which is too less.
The question: Did I do anything wrong, how can you create VI that writes you lets say 10 values a second into text file? Or is simply the DigitalMultimeter input of the myDAQ not able to sample a rate of 10 Hz? I couldn´t find any information in the specification handbook about the sample rate of the DMM?
If anyone can help me would be great! Thanx a lot, Markus
Attachments:
Measure Speed+Current+Voltage into Excel.vi ‏175 KB
Test7.txt ‏1 KB

File I/O is not very efficient. I recommend that you do you file logging in a parallel task. Have one task do your data acquision. This task would then pass the data to be logged to the logging task via a queue. That way your file operations do not impact your data acquision. Also, express VIs are not very efficient. You would be better off accessing that directly using the DAQ VIs. The express VIs contain lots of steps that do not need to be done every time you call it such as initializing the device.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Need example vi using AT commands for dialing the modem at the remote end

Can any one give example vi for dialing up a modem and sending data to remote end

Hi sindhu6,
Presuming that you are connected to your modem via a serial connection:
I did find a forum related to your enquiry: http://forums.ni.com/t5/LabVIEW/AT-commands-in-labview/td-p/1213335
And I did find an example from ni.com: http://zone.ni.com/devzone/cda/epd/p/id/2577
Basically, what you need to do is to find out what are the AT commands used for your modem and send the command over using VISA related functions (e.g. VISA Read VI). You can send the command in a sequantial method. You can do this by using the method found in the first link. The best would be that you can create a state machine where by each case/state will consists of commands that you need to run in a sequence (let's say a sequence of AT commands for sending a message via TCP/IP communication).
You can also use a sequence structure but I would not suggest that since you cannot stop the sequence half way and if your command is very long, this may look pretty messy for your code.
The main question is:
What is the version of your LabVIEW?
What is the modem that you are using and how is your hardware setup is going to be (e.g. how did you communicate with your modem)?
Thank you
Warmest regards,
Lennard.C
Learning new things everyday...

LabVIEW Report Generation Toolkit in the application does not work

I have LabVIEW7.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1, which was updated after installed. I made a VI in LabVIEW7.1 enviroment using the Report Generation Toolkit and it works very well. After the VI was build an application.exe and installed even in the same PC, the Report Generation Toolkit didn't work. Excel that should pops-up does not do anything.
the office i used is office xp. would you like to help me?
thank you very much.
Jing

When you build the application, you have to include as "Dynamic vi" in Source file tab the vi:
_Word Dynamic VIs.vi. from _wordsub.llb
_Excel Dynamic vis.vi from -Excelsub.llb
in the following library
...\National Instruments\LabVIEW 7.1\vi.lib\addons\_office\"
Refer to the following discussion thread
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000053460000&ECategory=LabVIEW.LabVIEW+General

I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
I have the professional development system
I can run the main VI
all the required DLL's are in the dependencies section of the project window.
I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
Thanks in advance to all labview users for your help
Attachments:
project window.PNG ‏36 KB

other PNG
Attachments:
Broken Arrow on EXE.PNG ‏179 KB

I would like to read a text file in which the decimal numbers are using dots instead of commas. Is there a way of converting this in labVIEW, or how can I get the program to enterpret the figures in the correct way?

The program doest enterpret my figures from the text file in the correct way since the numbers contain dots instead of commas. Is there a way to fix this in labVIEW, or do I have to change the files before reading them in the program? Thanks beforehend!

You must go in the labview option menu, you can select 'use the local
separator' in the front side submenu (LV6i).
If you use the "From Exponential/Fract/Eng" vi, you are able to select this
opton (with a boolean) without changing the labview parameters.
(sorry for my english)
Lange Jerome
FRANCE
"Nina" a ecrit dans le message news:
[email protected]..
> I would like to read a text file in which the decimal numbers are
> using dots instead of commas. Is there a way of converting this in
> labVIEW, or how can I get the program to enterpret the figures in the
> correct way?
>
> The program doest enterpret my figures from the text file in the
> correct way since the numbers contain dots instea
d of commas. Is there
> a way to fix this in labVIEW, or do I have to change the files before
> reading them in the program? Thanks beforehend!

LabVIEW for the STM32F100 or the STM32F4 ARMs

Similar Messages

Maybe you are looking for