Labview for stm32f103 development board?

hi,
good evening, i'm a student who's currently working on a thesis that involves the stm32f103 development board. our board uses a 32-Bit ARM Cortex-M3 Processor with a 128KB flash memory. it also has RS232 and USB ports for direct connection to the computer. i was just wondering if there are any labview products that are compatible with our board?

Hi mat2_chan2,
You have a few options depending on what you mean by "compatible with our board." There are 2 options I see:
1) You can use LabVIEW to communicate with your evaluation board (through RS232 or USB). If you've already got your code working as you wish on the evaluation board, this would be the option for you.
2) You can use LabVIEW and the LabVIEW for ARM module to download actual LabVIEW code to the board itself. I tried to identify whether or not your chipset would be supported, but you didn't specify enough information. You can look here: RL-ARM Real-Time Library. (Chips for which the RL-ARM Real-Time Library exists can support LabVIEW code.) More information can be found at www.ni.com/arm. This method would require background work in order to port LabVIEW to your chip - integrating all of the chip's functionality into the LabVIEW environment. (If you're really tight on time, you need to take this into account.) See this link: Programming Additional ARM Microcontrollers with LabVIEW (without the LabVIEW Microprocessor SDK)
I hope this helps,
Kevin S.
Applications Engineer
National Instruments

Similar Messages

Developing in Labview for De2 115 Board

is there any way to make code for altera De2 115 in labview ?

Hi
The LabVIEW FPGA module only supports the following:
Virtex-II 3000
Virtex-II 1000
Spartan-3 1000
Spartan-3 2000
Virtex-5 LX30
Virtex-5 LX50
Virtex-5 LX85
I am not optimistic about a cinvenient development for an altera board.
However, there ia compicated way that I can think of. It might be possible for you to design the system in labview and use one of the labview embedded modules ( http://www.ni.com/embedded )to generate c code which you can then port to systemc and compile for the altera fpga using a suitable compiler.

How to build executable from labview for R-series board

Hi all,
I have a PC with Win XP 32 and a PCI-7852R board. I have labview installed on it and have done all my development on that machine. Now that I'm done, I'd like to build more of the systems but don't want to have to install labview on every one. Plus, I'd like to be able to take labview off this machine so that I can start working on the next project on another machine.
So is there a way to build a distributable package of host and FPGA code on one machine and install it on target machines without having labview on them? Ideally I'd like to be able to build the package on a machine that doesn't have the R series board - instead just have a simulated board. But that doesn't seem to be an option in NI MAX.
thanks
Solved!
Go to Solution.

Hi Manick,
I mean that it would be best to create a new thread on the forum. I've attached a screenshot to show what I mean. From there, you can enter a unique title, and have a unique description for your case. That way, we can support you better, and other users of the forum can search for the same behavior that you're seeing.
Regards,
Che T.
Applications Engineer
National Instruments
Attachments:
new_post.png ‏70 KB

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

Do I need to buy the development board from Phytec or would any LPC229x board do the job?

Hi,
I am planning to test LabView embedded on an LPC2294 development board.
Should I buy the PhyCore development board for LPC2294 or would any other LPC2294 development board do the job?
I have seen a huge difference in price between the PhyCore LPC229x development board and a standard LPC2294 from other parties. However, the other party's development board seems to have more features than the one from the PhyCore development board.
Please, let me know your advice and recommendations.
Thank you
Kolemale

Hi,
The example target in the LabVIEW Microprocessor SDK is designed specifically for the Phytec LPC2294 development board, so it would be easiest to start there. You can certainly modify the example target implementation to fit your needs for alternate development boards (in fact, that's the idea!).
Michael P
National Instruments

IPhone Development Board

Hi,
Does IPhone provides a development board for any of its version? If yes, from where they can be obtained?
Regards,
Khan

I am just interested to use IPhone computing architecture as a computing platform. That's why I am looking for a development board from apple. Don't they provide any development board?

Labview fpga+Driver for Spartan-3E-1600K Gate Development Board

hi
is thier a device driver for Spartan 3e XC3S1600 (1600K gates) Xilinx FPGA development board. You(NI) are providing driver only for Spartan 3e XC3S500 (500K gates) FPGA Xilinx University program board.
regards
hi ?Q>

Dave.C wrote:
Hi again,
I can understand your frustration, but unfortunately I don't have those details.
what is the problem that make ni not make driver for sp 1600 3e
is it related to money or other issue with xilinx company??
hi ?Q>

LabVIEW for Single Board Computer

Planning to develop a compact portable Data acquisition system.The idea is to use a Single Board Computer and PC 104 cards.The PC 104 vendor confirmed that LabVIEW drivers are available for Windows XP OS.Thats fine.Now I would like to know if I can use the LabVIEW that I have used on PC on the Single Board Computer as well.Please suggest.
Thank you.

Nothing with the answers I got there.In fact they were very useful.
Thats a good point let me make it clear.The focus on that post was primarily on the interfacing of the PC104 cards for LabVIEW.
This post was made to make a note of the process,if any of using LabVIEW on a Single Board Computer - This was mentioned in the former post but isnt detailed.
So,Now,I would like to know the available options for using LabVIEW on a SBC.
- Can I load the Developer Suite onto it?
- Should I develop application on a PC and use an executable on SBC?
- What is the practise and what are the issues likely to be faced during the process of application porting/development?
I guess there are people around here who worked/working on similar projects.So,it would great if details of what and how they have done can be shared.
Hope this explains.

Labview fpga development board

hi all
can i programme my own development board having xillinx fpga using labview fpga .. or lab view fpga can only be used by national instruments hardware ?
Regards

Just to reiterate what was already said, The LabVIEW FPGA generates VHDL code that can not be used or downloaded into non-NI hardware, even if it uses the same Xilinx FPGA.
That being said, there is one board that you can use that is not National Instruments, Xilinx SPARTAN-3E XUP Starter Kit
Regards,
Andrew Eddleman
National Instruments
RIO Embedded Hardware PSE
CompactRIO Developers Guide

Labview Drivers for a PC104 board

I have just purchased the PC104 CPU module from RTD technology:
PCI/104-Express cpuModule™ & Controller
Intel® Core™ 2 Duo 1.20 GHz – 1.86 GHz
http://www.rtd.com/PC104/CM/CMA22/CMA22Mxx.htm
I have installed Windows XP and Labview succesfully.
This board has an embedded advanced analog Input Output board with 8 ports.
The Windows Driver has been succesfully installed. Now i would like to use these ports to acquire analog data using labview. However when i open the DAQmax i can't see it. In the Device Manager of Windows is listed as RTD aAIO and is properly working.
What should i do to use this device with labview?
Attached are the Windows Drivers and some example code for the aAIO in case it helps
Thank you,
Christos
Attachments:
aAIO_windows_v01.00.00.zip ‏3494 KB

Thanks for your response.
I have tried the Call Library Function Node to call a function out of the attached DLL. More specifically i have tried to call "aAIO_General_EnumDevices" but i am not able to retreive any values.
It is the first time that i am using this Call Library Function Node and i am not sure if what i am doing is correct.
I am attaching the vi that i am trying to run and i am also including in the lines below the documentation of necessary functions/parameters/structures.
Thank you,
Christos
aAIO_General_EnumDevices
aAIO_Enum_Info *
Info,
uint8
Limit
Enumerates all aAIO devices in the system.
Parameters:
Info
A pointer to an array of aAIO_Enum_Info structures to fill with information about the aAIO devices in the system.
Limit
The maximum number of aAIO devices to enumerate.
Data Fields
uint32
dev_num
This is the device number which represents this device.
aAIO_Intrfc_Avail
avail
This is the current availability of this device.
uint32
base_addr
This is the base address of this aAIO device.
uint32
irq
This is the IRQ that's been assigned to this aAIO device.
Attachments:
Enumerate device.vi ‏7 KB
aAIOLib.zip ‏51 KB

Interface labview with the test board to identify opamp pins automatically

is it possible to interface LABVIEW to a test board in such a way that the input, output pins of an op amp (8, 10, 14, 16 pin opamps) are identified automatically when DUT is placed in the socket

pratheek wrote:
Thanks alot. pin numbers are variable. I need to test the functional and test parameters for 8, 10, 14, 16 pin opamps.
The first thing you need to do is ensure that +VCC, -VCC, and GND are always connected to the correct pins. I think the best way to do this is have preset wire options that you manually select with some switches (reduces the complexity of the LabVIEW controlled wire switching).
pratheek wrote:
The desired out put for my project is to check the functionality of the opamps
I understand the end goal, but what you need for first specity is the test sequence.
1. Identify In/Out pins & number of op-amps. What is the sequence for this??? What voltages do you apply to the various pins and what is your desired outcome??? How do you identify each pin as in/out and whether they are for OpAmp1, OpAmp2, etc. Since this sequence will inevitabely apply voltage to the output pins, make sure your test sequence doesn't damage the chips.
2. After identfying each op-amp, what is the test sequence for evaluate its "functionality"?? Do you wish to evaluate the gain for various resistor combinations in an external circuit????
3. Now with your test sequences outlined, you can finally begin on getting LabVIEW to implement these functions. I'd use the DAQ digital outputs to a decoder (3-to-8 or 4-to-16). Use the outputs of the decoder to control switches (these switches control the connections between a second DAQ and the test pins). A third DAQ may even be necessary to control the selection of various test resistors. Keep in mind that each of these switches will add resistance to the path so your evaluation must be made measuring the voltages at the op-amp pins (not using the sourced voltage values). Planning the full measurement sequence and requirements before you start will not only help guide your program's development but it will tell you which DAQs are useful and how many you will need.
This is quite an undertaking and we can't really provide any help on the LabVIEW end until you have a full write up of what you want to happen and how (step-by-step details). Once you have that, start thinking about the sequence of events your code will have to follow to make it happen, then come back for guidance/help.

Availability of 64-bit LabVIEW for Mac?

Hello world,
A quick search of the forum seems to indicate that there may have been some 64-bit versions of LV for Mac produced, but I can't seem to find any recent posts, or how I might obtain a copy. Does anyone know if there are versions available, or if NI will produce them at some point?
My primary issue is that when reading in and manipulating data files bigger than 500MB, I get out of memory errors (my machine has 8 GB RAM, and OS X has been 64-bit for some time now). Looking at the Activity Monitor reveals that LV allocates just over 2.1GB when reading binary files of this size (before manipulation and making copies, etc). This of course is pushing up against the 32-bit limit. Some of my files are this size or bigger, or may require making copies during data reduction/manipulation, hence the request.
Many thanks,
S-
PS: I know, I know, I have heard the arguments for MS Windows before, I am mostly seeking an answer to the question, not an explanation of why system X is better than system Y. FWIW, in my lab, we use Windows (less stable, more software), Macs, and Linux (more stable, less software; does correlation == causation? Hardly ever :-) ).
Solved!
Go to Solution.

Hi Ben,
I'm getting the feeling that something has happened which has left you frustrated with our Mac support. I'm sorry if we've caused you undue inconvenience, especially if it was due to technical inaccuracies in the documentation that is available online. We make our best effort to keep an accurate record of our products and their compatibility. That said, mistakes do happen and we do our best to fix them. If you ever come upon inaccuracies in documentation, please let us know by commenting on the page or contacting our support staff.
As this thread was originally discussing, there is a gap between the software which is available for Mac and Windows operating systems. There are a plethora of reasons for that, and many of them are valid topics of debate. The purpose of these forum boards is to provide a space where users of all types can work through issues they encounter or get the opinions of others. We try to foster a professional, constructive environment for all our customers.
As a company, we gather large amounts of very helpful feedback from our customers. One of my favorite parts about the LabVIEW user community is the number of generous, helpful people who love the product and want to see it improved. I regularly encounter customers who go out of their way to demonstrate obscure bugs which we may have missed otherwise. Many of these bugs get fixed and improve each subsequent version of LabVIEW we release. If you have specific questions or concerns that are actionable, please post them in new threads on the topic; the more detail you can provide, the easier for us to investigate the issue. It's very common for a user to post a link with a question about something that seems unclear or misleading.
I don't know what the goal of your post is exactly. To address the frustrations that Mac software availabilities are less than perfect, we do know that the Mac community of LabVIEW users is left wanting with our current offerings. I'm not sure what else I can contribute other than suggesting to do research to understand the tradeoffs when choosing a development platform. Every language and OS has unique pros and cons; knowing them is always a good idea.
I maintain that in all cases you should choose the language that suits your application and development cycle best. I frequently use LabVIEW because I enjoy using it and find I save tons of time. For the type of application development I do, it makes sense. If your usage of Java solves the problems you face, that's a good thing, and it would be silly of me to suggest you choose the wrong tool. It goes back to pros and cons.
To come back to the point, I'm sorry to hear you (and the other Mac users on this thread) have faced frustration. I don't think my attempt at a didactic post fixes those problems, but I care about LabVIEW and this seemed like a fitting place to remind that we need your help to fix the problems you encounter. We're not always able to get everything done, (notably there still is not a 64-bit version of LabVIEW for Mac) but don't give up on us. We're always trying to figure out the best way to help our customers pursue new goals and we've noticed there is room to grow in Mac.
Verne D. // LabVIEW & SignalExpress Product Support Engineer // National Instruments

LabView for Linux - Ready?

I am setting up a research lab and would like to use linux for all my
computing needs. I was wondering how peoples experiences with LabView on
Linux have been? I would be using it to control instruments via GPIB
and to take data using DAQs. Is it stable and reliable, or is it too
early in its development to make the switch from LabView on windows? How
is NI's LabView support? Thanks for the help.
G. M. Steeves
California NanoSystems Institute
U. C. Santa Barbara

Geoffrey,
The LabVIEW for Linux FAQ page has many of the answers you are looking for.
LabVIEW for Linux is very equivalent to the Windows versions with the exception of ActiveX and NI-DAQ. Data Acquisition is supported on Linux through the Comedi. This is a third party, open souce driver that supports many of National Instruments' DAQ boards. Also, the only toolset available for Linux at this time is the Internet Toolkit. For more information go here.
Support is done at the same level as for Windows and can be done through all of the same ways.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

LV 8.6 will Not Compile in LV 2010 - Labview 10.0 Development System Has Encountered a Problem and Needs to Close

I submitted this support request to NI on 8/12/2010.
When I compile my LV 8.6 app in LV2010 I get this error:
"LabVIEW 10.0 Development System has encountered a problem and needs to close. We are sorry for the inconvenience."
I was told to do a "Mass Compile" of my LV 8.6 app in LV2010...this failed too.
I was then told to go to each and every vi and "Mass Compile" individually...after about the 50th vi this got old quickly...and it still didn't compile. I then sent NI tech support "my code". The good news is my LV 8.6 app didn't compile with LV2010 @ NI.
My LV 8.6 app compiles and runs great in LV 8.6. I don't want to be left behind with the newer upgrades and I want to move to LV2010. I have lots of LV8.6 code to maintain and I really don't have the time to debug all of my apps.
I was told this will be looked @ in LV2010 SP1.
One note...back up your LV8.6 data before you move to LV2010. Once your LV8.6 code is compiled in LV2010 you will not be able to go back to LV8.6.
I restored all of my LV8.6 code and I'm back working with LV8.6.
It's a tough call, do I stay in LV8.6 and get left behind?
Do I bite the bullet and try to debug this mess in LV2010?
I was told the compiler is completely different in LV2010. That's great, but one reason I have NI Maintenance Agreement is to keep updated with the latest software. I can't afford to re-compile LV code every few years. Like most people, maintaining my Apps with customer's revisions, and modifications is enough work. I don't want more work!
I was told LV2010 SP1 would likely appear in May or June of 2011. I'd hate to break out my old Turbo Pascal apps again...but hey...they still work! My NI maintenance agreement is due this month too, I guess I'll pay NI one more year, and see if they come up with a solution. But if NI doesn't fix this LV8.6 compile in LV2010 problem...I don't see any value staying current with LV software.
I found another Bug with LV2010...you are going to love this one!
There is a new "LV Update Service". Perfect! I like updating my LV software when new patches are available. When I click "update" the update spins over and over "Checking for New Version". I have let it run ALL day with no results...just sits and spins over and over.
OK, I know give NI a break! Yes, LV2010 has a new compiler...and Yes, I will renew my NI maintenance agreement. I just want NI to know failing to compile just one LV8.6 app in LV2010 is not a good idea for customer relations.
Thanks,
Doug

For your update service problem
Unable to Update Current Version of NI Update Service
Why am I Unable to Update My Version of NI Update Service in Windows Vista or Windows 7?

How to create a standalone executable in LabVIEW 2009 Professional Development System?

How to create a standalone executable in LabVIEW 2009 Professional Development System?
Solved!
Go to Solution.

This should help you out http://zone.ni.com/devzone/cda/tut/p/id/3303
Also remember that quick search with Google in many cases will be quicker than asking in this forum. I always use Google before I ask for help in any forum. It is much quicker
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Labview for stm32f103 development board?

Similar Messages

Maybe you are looking for