LabVIEW 2011 WSN Module?

I just received a NI WSN Starter Kit and it came with LabVIEW 2010 evaluation disks and the WSN Module Pioneer 2010. On my work laptop I have recently removed LV 2010 to upgrade to 2011. The WSN Module won't install without LabVIEW 2010...
Is there a walk-around or a new version of the WSN Module for LabVIEW 2011? Or do I have to install LabVIEW 2010 again?
Thanks.

Hello GrigS,
This is Andrew Brown, an Applications Engineer from National Instruments. There is a newer version of the NI-WSN driver (1.3) that is compatible with LabVIEW 2011. You do not need to install LabVIEW 2010 again.The download page for the driver is:
NI-WSN 1.3 - NI Wireless Sensor Networks - Windows 7/Vista/XP x86
Please note the installation instructions on the page are:
Installation Instructions
Perform the following steps to install NI-WSN 1.3.0:
Install LabVIEW
Install LabVIEW Real-Time Module (required for NI 9792 and NI 9795 support)
Install NI-RIO Driver Software 4.0 or later (required for NI 9795 support)
Download and run the self-extracting executable NIWSN130.exe. This will install NI-WSN 1.3.0 and all necessary driver files.
Regards,
Andrew Brown
Applications Engineer
National Instruments

Similar Messages

DSP Module For LabVIEW 2011

Dears,
I need the DSP Module For LabVIEW 2011, is it Available? and where can I Download it ?
Thanks
Ahmed Abdulbaky

Hi Ahmed,
I posted this in error. I did not see that Ryan had already answered this.
Ryan is correct. The latest version is 8.6
You can download the latest version of the DSP module from ni.com/downloads. The exact URL is shown below:
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnavdl/q/dsp/#
I hope this information helps.
Regards,
James D.
Applications Engineer
National Instruments

Cannot download LabVIEW NI SoftMotion Module 2011 SP1

LabVIEW NI SoftMotion Module 2011 SP1
http://joule.ni.com/nidu/cds/view/p/id/2776/lang/en/rating/1
All link in this page you can download is a downloader, and the downloader can only download it self.
A CLA from China
Solved!
Go to Solution.

Hi,
I'm not sure what is going on. For now, please download the NI SoftMotion Module from the following link: https://lumen.ni.com/nicif/us/EVALTLKTINDCTRL/content.xhtml
I have verified that this works.
Thanks,
Paul B.
Motion Control R&D

Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
Any help on this matter would be appreciated.
Solved!
Go to Solution.

Just a thought but I think the register addresses used by LabVIEW are one off of the actual register #. I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1). This is documented somewhere on ni.com but can;t seem to find it now. But here is another link that may help:
http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
Dan

Labview 2011 FPGA Compile Error

Hi,
I'm new to FPGA. I want to use Labview 2011 SP1 with the Spartan 3E starter kit from Xilinx (Spartan 3E driver available from NI labview website).
I'm trying to work my way through the examples that came with the driver. I've run into the same compiler error with a number of the examples. The error is attached.
Error 7 occurred at Read from Text File in niFpgaCompileWorker_CheckForErrors.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:1
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
C:\NIFPGA\compilation\Shift_FPGATarget_Shift_87E8371C\Spartan3EStarter.bld
I've checked the registry to ensure that the path to the compiler is correct.
Any assistance would be welcome.
Regards,
James.
Attachments:
Labview2011_FPGA_CompileError.JPG ‏96 KB

Hi,
I don't have any Xilinx tools installed - other than the ones that installed with the Labview FPGA module.
I have attached the compilation logs and output results from my attempt.
I have renamed the extension on the following files from .lvtxt to .txt
BuildResults.txt
CodeGenerationResults.txt
Regards,
James
Attachments:
BuildResults.txt ‏5 KB
XilinxLog.txt ‏42 KB

Transfer functions in the 64 bit version of Labview 2011

Hallo all,
I am running a 64 bit version of Labview 2011 and I would like to know is it possible to use transfer functions in this version?
I found only a 32 bit version of Control Design and Simulation Toolkit, is there something else I could use for this?
Thank you,
Vladimir

Hello,
Thanks for your posting in this forum. Unfortunately you cannot use this function in the LabVIEW x64. You can check the link below
http://forums.ni.com/t5/LabVIEW/LabVIEW-64-bit-support-for-modules-and-toolkits/td-p/996044/page/2
But you can try the option below, but I cannot say that it would work.
You can install the LabVIEW x32 and then Control Design & Simulation Module .
Then copy the library of this module somewhere else.
Then you can install the LabVIEW x64 and copy that library in its folder.
Maybe it works.
Regards,
Hossein

Labview 2011 64-bit install problem

I'm trying to install the 64 bit version of LabView onto a win7 64 laptop. The install seems to go ok. When I try to run it, it crashes with this exception 0xC06D007E$r. I've tried uninstall/reinstall and I still get the same error. I have the 32 bit version of LabView 2011 installed on this machine and it runs fine. What else should I be looking at?
Thanks
dp
Attachments:
lvlog.txt ‏2 KB

To address the point made by smercurio_fc, the Program Files (x86) folder is generally reserved for 32 bit applications. As I understand, Windows uses the distinction purely for organization. Having done more reseach, I will concede that we should look for a different workaround.
By your responses, it seems you may not need LabVIEW 32 bit. This article discusses the pros and cons of each version. This Q&A may be particularly useful in deciding whether or not you can continue on 64 bit alone.
Q. Which LabVIEW modules and toolkits are available for LabVIEW 64-bit?
A. Currently, the NI Vision Module, Application Builder, and Measurement Suite for Fixed WiMAX are available for use in LabVIEW 64-bit. Any other modules and toolkits must be run using LabVIEW 32-bit. See this Developer Zone Tutorial for more information.
Depending on your applicaion, this could be our solution If you are able to install LabVIEW 64 bit after uninstalling the 32 bit version.
KyleP
Applications Engineer
National Instruments

Restarting PXI RT from Labview 2011 64 bit

I have a customer trying to issue a restart command to a PXI-RT system from Labview 2011 64 bit. He says the command doesn't work.
I currently don't have 64bit so I can't test it very well right now.
Is this something anyone else has tried or experienced?
Thanks,
Josh
G Systems
Certified LabVIEW Architect

The real-time module is not supported for 64-bit LabVIEW. As a work around, you could install 32-bit LabVIEW onto your 64-bit OS. This should solve your customer's issue.
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98?OpenDocument
Ben D.
Applications Engineer
National Instruments

Upgrading LabView 2011 to 2012 for Mac OSX

I am considering Upgrading LabView 2011 to 2012 for Mac OSX.
Is this a free upgrade?
Is a Mac OSX version available?
Is the NXT module still working in LabView 2012?
LabView 2011 ain't broke but I just recived a vi which requires a newer version :-(
Thanks.
Michael
Dr. Michael Vallance
Future University, Japan.
Homepage http://www.mvallance.net
International Virtual Environments Research Group (iVERG) http://www.iverg.com

Is this a free upgrade?
It depends if you have a current service contract. You get a 1 year period where you will get updates to LabVIEW after purchase.
Is a Mac OSX version available?
http://www.ni.com/labview/os-support/
Is the NXT module still working in LabView 2012?
I have no idea.
LabView 2011 ain't broke but I just recived a vi which requires a newer version :-(
You can download a 30 day trial from the NI site.
http://www.ni.com/labview/whatsnew/upgrade/
You might have to contact NI directly since you are not in the US.

What is the Difference between WSN Module and Pioneer

I am confuse on the usage between LabVIEW WSN Module and LaBVIEW WSN Pioneer in some texts. Please, forum I need clarification on it.
Ilublessing
Solved!
Go to Solution.

Hello, llublessing,
It is the same thing. The pioneer name will be removed in the future completely as the product matures. This modules allows you to program using LabVIEW directly on WSN nodes! Hope this helps!
http://www.ni.com/labview/wsn/
Cheers
Corby
WSN R & D Product Support Engineer

NI-WSN and WSN Module for LV2014

I am picking hardware for a new project and noticed, that NI-WSN is not supported by LabVIEW 2014. Further investigation showed that the newest version of WSN Moule Pioneer is only suported by LabVIEW 2013.
First question is if anyone has some info about the relase date for the new NI-WSN (LV2014 compatible version)? and WSN Module Pioneer.
The second question is if use of WSN for the new projects should be avoided due to no new drivers available and replaced with cRIO with Acess Point (configured as a bridge) to connecto to wireless.

Hi Mitja_G.,
You are right, there is no current support of WSN in LabVIEW 2014 nor LV 2014 SP1.
There are some plans to release in the future tbut there is no official release date.
My suggestion will be to contact NI Branch in your country and discuss what are the options.
Knowing more about the opportunity and your hardware configuration, it will help finding the best solution for you.
If you need contacts of your local NI Branch, please tell me your country and I can send you exact e-mail address and phone number.
Best regards,
IR

Labview 2011 always disconnecting over wireless Ethernet bridge!

Hello, we recently upgraded from labview 2009 to labview 2011. We use a Labview cRio-9014 and FPGA backplane 9114. For connecting the cRio to our laptop we use Digi XPress Ethernet Bridge: Multipoint 900MHz industrial wireless part# XEB09. This program worked over our wireless link running labview 2009 with the old cRio software.
After upgrading the desktop, upgrading the cRio's software and recompiling the FPGA code we tested our setup via a wired ethernet connection and ran it all day with no problems. However once we switched to using our wireless ethernet bridges the cRio disconnects always 2-3 minutes after starting. It also does not allow us to reconnect without powercycling the cRio. The radio modems show a solid connect and no problems the whole time. Now I've searched through known issues and all over the forums without finding anyone having a similar issue so I hope someone can chime in and let me know if something else in LV2011 changed or what.
My current hypothesis is that labview 2011 uses UDP packets for status/keep-alive and our radio modems are not guaranteed to recieve all UDP packets. Please correct me since this is only a guess and I don't know what's going on under the hood on the cRio side.
P.S. I've captured the packet data using WireShark on the laptops side from deployment until disconnection but can't find any obvious problems. It's a fairly large file so let me know if it's needed and I'll try to find a way to upload it.
Hopefully someone can help.
Best Regards,
Sam Bingham
Great Lakes WATER Institute

Our host OS is WIn7-64Bit, and XP-32bit but they all display the same behavior.
cRIO hardware: cRio-9014 and FPGA backplane 9114
Our system is has 4 modules installed NI-9205, NI-9401, NI-9401, NI-9870, although we are only using the serial ports on NI-9870.
I looked for the NI TimeSync to remove but it isn't listed in our installation
Contents of current installation:
CompactRIO Support 4.0.0
DataSocket for LabVIEW Real-Time 4.9.0
HTTP Client 1.2.0
HTTP Client with SSL Support 1.2.0
I/O Variable Remote Configuration Web Service 1.0
LabVIEW 2011 Adaptive Filter Toolkit 11.0.0
LabVIEW PID and Fuzzy Logic Toolkit 11.0.0
LabVIEW Real-Time 11.0
Language Support for LabVIEW RT 1.0.0.4
NI Application Web Server 2.0
NI System Configuration 5.0.0
NI System Configuration Network Support 5.0.0
NI Web-based Configuration and Monitoring 2.0.0
NI-RIO 4.0.0
NI-Serial RT 3.8.0
NI-VISA 5.1
NI-VISA ENET Passport 5.1
NI-VISA ENET-ASRL Passport 5.1
NI-VISA Remote Passport 5.1
NI-VISA Server 5.1
NI-VISA USB Passport 5.1
Network Streams 1.1
Network Variable Engine 1.8.0
Remote Panel Server for LabVIEW RT 4.0.0
Run-Time Engine for Web Services 4.0.0
SSL Support for LabVIEW RT 4.0.0
System State Publisher 2.0.0
Variable Client Support for LabVIEW RT 1.8.0

Which LabVIEW 2011 system to buy?

I am looking to buy LabVIEW 2011 but don't know which level to buy. I am just getting it to run a program, that was already written, that corresponds with an Instron Stress Machine. If you need to see the program to tell the minimum version of 2011 it will run on, I can attach it to a post.
Thanks for your help,
Will Huntley

Will,
executing existing (compiled) code requires the RunTime Engine (RTE) which is free of charge.
But you will not get it to execute the code if it is still in VI form.
So you have two options:
a) get the finished code in the form of an executable (EXE). This requires the application builder for the person creating the EXE for you.
b) get a development version of LV in order to execute the VI form.
It seems that you are looking for option b) currently and you are correct that there are three different setups available. In order to compare those, please look there. Please see the green LED comparison table.
So as a short summary:
- You will be able to execute existing LV VI's using the Base Development Package even if the code includes certain components not part of this package (e.g. event structure/scripting). Note: You will probably not be able to run code using functions from LV modules/toolkits though (e.g. MathScript RT).
- You will not be able to modify certain components of the code if they are not part of the selected package. E.g. LV 2011 Base Development Package won't let you modify content of event structures (if included in the code).
- The application will possibly require more than just LV to run (driver, toolkits, ...). Many drivers are available for free, but there are also drivers/components requiring license costs.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

LabVIEW 2011 WSN Module?

Similar Messages

Maybe you are looking for