Crossbow to Labview

Hi everybody. I am trying to get the data from crossbow to labview. I am using Memsic WSN starters kit (MIB520 Gateway,MICA2 node, MTS400 sensor board ) and I am trying to get data from it into labview. I followed instructions from this webpage http://digital.ni.com/public.nsf/allkb/FD238ED75B22740B86257315004E35FE , but after all steps when I run Read Data and Display Health with Variable Rate.vi I just get an error 8003. Does anybody know what might be a problem and how I could fix it? Thank you.

Hi Nikola100,
Does the error have any explanation with it? The only information I have found regarding that error is if the instrument driver that you downloaded is not compatible with the version of LabVIEW that you have or if you are saving for a previous version. What version of LabVIEW are you using and which Instrument Driver did you download? Also, do you have the NI VISA driver downloaded? Thanks!
Kim
Applications Engineer
National Instruments

Similar Messages

Crossbow with Labview driver

Hi,
I'm using Crossbow wireless moduel with NI Labview 8.2. My system is,
1. Laptop: Crossbow MIB 520 is connected by COM port (virtual COM port, actually it is connected by USB), and Crossbow MICAz is attached to receive signals. The received signals are processed with NI Labview driver from http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=1FB66B354ED149C7E0440003BA230E....
2. Node #1: Corssbow MDA 320 is used for collecting signal from a pressure sensor, and Crossbow MICAz is attached for sending signals.
I want to sample the pressure signals about 100Hz. So I made programs which are installed in MICAz for each node. I check the signals with XSniffer program which is provided Crossbow, it just shows the received signals. So I can see the 100Hz signal with it.
Since the Baud rate for XSniffer is 115200, I changed the Baud rate in the NI Labview dirver which was 57600 to 115200. The Baud rate that I changed is in the zip file, Crossbow XMesh WSN\Private\WSN Connect to Gateway.vi. (Before I change the Baud rate, I could not see the signals in Labview.) However, Labview shows only about 10Hz signal.
Because another program, XSniffer with same system shows 100Hz signal, but Labview dirver does not. So I guess that there might be limitation about accepting data in Labview driver. So my question is,
Are there any sampling limitations for accepting data in NI Labview driver for Crossbow? If so, how can I fix it?
Thanks,
Joonbum Bae.

Did you see this thread? http://forums.ni.com/ni/board/message?board.id=170&message.id=300906
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Crossbow Labview help

I downloaded crossbow's Labview vi's and I tried running the example Read Data and Display Health.vi. I keep getting the error message: Error 8001 occurred at Generic Read Possible Reason(s): Some or all of the samples were not available for some of the nodes specified. Can anyone explain why I keep getting this error? Data comes through when I use MoteView. Thanks for any help.
Solved!
Go to Solution.

Hello,
Here is the LabVIEW Driver which may contain the examples along with some other links you might find useful:
Crossbow XMesh WSN Sensor LabVIEW Plug and Play (project-style) Instrument Driver
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=1FB66B354ED149C7E0440003BA230E...
LabVIEW Drivers for Wireless Sensor Networks
http://zone.ni.com/devzone/cda/tut/p/id/5435
How to Install a Crossbow MIB520 Base Station
http://digital.ni.com/public.nsf/allkb/FD238ED75B22740B86257315004E35FE?OpenDocument
Best,
Patricia B.
National Instruments
Applications Engineer

How to use Crossbow Xmesh WSN LabVIEW drivers for downstream communication with motes

Hello,
I am trying to use LabVIEW Crossbow Xmesh WSN driver for downstreaming commands but driver programs are not working.
I am interested in changing node (Iris mote with MDA300 board) update rate from LabVIEW program running on host PC .
I have used Set node update rate.vi with open stream.vi and start stream.vi in proper sequence and developed a program to change node update rate. When program is run no error is shown but node update rate is not changed.
Pl suggest what I should I do.
What is the function of WSN write VIs (WSN write Raw 1sensor1point). For what type of message this is used.
I want to actuate relay on MDA300 with mote id 2. What VIs (from driver ) I have to use and how to issue command related to it.
Incase any one can help I will be grateful
Roop

Hi Arjun,
I am sending you snap shot of VI developed to change node update rate.and also the heirarchy of drivers VIs used in the program for better understanding .
In case you can figure out why the command message send is unable to communicate with mote .
Also for downstream communication with motes the packet format used is described in Moteworks user manual from MiMSic.com
I think the developer of these drivers can help you out in solving my problem.
Thanks
Roop
Attachments:
sreenshot to arjun ni for checking downstream comm.doc ‏288 KB

How to write commands to Crossbow MDA300 with LabVIEW?

I am able to read data from Nodes using LabVIEW, but I would like to write commands to the nodes using LabVIEW. How can I do that? I am using Iris mote, MDA300, MTS420, MTA 310 sensor boards and MIB520 USB board gateway board and I had got LabVIEW drivers when I purchased the kit. Kindly help.
Attachments:
Crossbow WSN .docx ‏319 KB

Hello,
I am also using the same components which you have used. but i don't have drivers for it. can you please tell me from where i can get them.

Drivers for over the air programming for labview in wireless sensor network

Hi all ,
In my earlier post, I had requested for information regarding the drivers for Wireless sensor network( WSN) in Labview. I was successfully able to configure my WSN using Labview. thanks to all for the support and help.
However I have a new querry now. I have developed a WSN testbed with more than 1 mote and more than 1 sensor. all the motes are spread out and they communicate with the base mote. the base mote is connected to the gateway and the gateway is connected to the PC where labview and moteview are installed.
Now I need to confure the motes ( ie load a software on the mote which is not connected to the PC) . Is it possible with labview ?
I mean does labview support this kind of a structure .? Say for ex i have a mote with id = 10 and that mote is one hope away from the base mote ? can i still configure that mote remotely ?
thanks!

Hey anilhk,
When you say "load the software on the mote" do you mean actually reflashing the firmware on the sensor? If so, there is currently no functionality for this in the Crossbow driver. LabVIEW is certainly capable of doing this, but in order to get the functionality, you may have to program it yourself. The Crossbow driver source code is available to view and using the programming documentation from Crossbow you could make modifications to the driver for your own use.
Regards,
Chris Delvizis
National Instruments

Using Crossbow NI Driver, MDA320

I just downloaded the LabView driver for Crossbow (Crossbow XMesh WSN). I am trying to use one of the example programs, "Read data and display health with variable rate". My Crossbow motes use the MDA320 sensor board. When I first bring up the program in LabView, the MTS300 sensor board is selected by default. The block diagram indicates everything is connected OK. On the block diagram, when I switch to MDA320, multiple sensors, multiple points, the block diagram connection from the Crossbow read function to "data" indicates an error. The error is related to attempting to send three data fields (MDA320) instead of 5 (MTS300). Also, the front panel looks as if it is exclusively for data coming from an MTS300. Does this example program run as-is with an MDA320? Any help would be appreciated. Tim.

Hey Tporter,
The MDA320 only returns 3 measurements rather than the 5 measurements returned by the MTS300. The error you are seeing is related to the cluster data type expecting 5 elements when it is only receiving 3 elements from the MDA320 Read.
To fix this we simply need to delete the data cluster control and the broken wire. Then right click the data output terminal on the Read VI and select Create » Indicator. This will create a cluster with the correct number of elements.
Message Edited by Chris_D on 09-05-2008 10:44 AM
Regards,
Chris Delvizis
National Instruments
Attachments:
mda320.jpg ‏11 KB

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

How to run downloaded drivers on Fresh Install of Labview 6.1 on a Mac G4 OS 9

I have just completed a fresh install of Labview 6.1 on an Macintosh G4 running OS9. I can run it and it seems to work just fine. I downloaded some drivers for an oscilloscope (HP 546XX) to run with an HP 54603b. When I installed, I went to open the 'Get Started.VI' I get a freeze and have to force quit out of labview. I am not sure how to resolve this. I am pretty sure that it is independent of the device, since I can open the vi's at least on another computer with no hardware attached. So I guess to boil my situation down. I have 2 questions:
-How do I get a fresh install on a mac G4 OS 9 to run downloaded drivers from the internet
-How do I ensure that I have the hardware configured on
a macintosh to run properly.
I really have little experience with macs so I am not really sure what my options are or what could be the problem so any assistance would be much appreciated.

Hmmm. I wonder if NI-VISA isn't installed correctly on this machine.
When LabVIEW loads a VI that uses a VISA name control on the front panel, it queries VISA for the installed devices. Sometimes this takes a few seconds, but maybe in your case, something has been corrupted and it's hanging.
To try to narrow this down, first run the separate program "VISAConfig". This should list your devices. If this works, this means it's pretty likely that VISA is installed correctly.
Next, run LabVIEW. On an empty front panel, select the "Controls->I/O->VISA Resource Name" and place it on the front panel. When you click on the arrow on this control, you should see a list of your devices. If this works, then that indicates that LabVIEW is successfully talking
to the VISA software.
If both of those succeeded, then we have to take a closer look at this particular instrument driver. Can you drop other VIs (say, Initialize or Close) without hanging?
If either of the first two steps fail, I'd suggest that you reinstall the VISA software. You may want to try the latest version of NI-VISA (from ni.com), but first confirm that it supports LabVIEW 6.1.
I hope this helps.
Brian

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Some fonts are not shown correctly in LabVIEW 2012

I found a bug related with fonts in LabVIEW2012 f3 KR.
- When I select NI7SEG in font selection dialog, right font is not shown in the example box.
- Draw text at point.vi shows same problem for some fonts while other fonts are working.
I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google.
So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK.
* OS: Windows 7 32bit KR

Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
- Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
- LabVIEW 2010 but on same PC shows correct fonts.
Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
(1st group)
Arial Unicode MS...
Bookshelf Symbol 3....
Windings 3
(2nd group)
@Arial Unicode MS...
@Terminal
(3rd group)
Arial...
Consolas...
Courier...
Licida Console...
NI7SEG...
Verdana

Comunicação entre Labview e ANSI's.

Estou definindo Projeto de Graduação e estou interessado em trabalhar na integração entre Labview e ANSI's na análise de elementos finitos. Gostaria de saber se alguém possui alguma informação sobre o tema.

Voce poderia ser mais especifico com relacao a informacao que voce esta precisando?
Atenciosamente
Filipe A.
Applications Engineer
National Instruments

Crossbow to Labview

Similar Messages

Maybe you are looking for