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

Similar Messages

Read the LabVIEW help file

Forgive me if this is remarkably simple answer.
Id like to be able to read LabVIEW help file on my LapTOP which has no LV installed.
If I can do this from, here as in this forum can it be done?
Thanks

Jeff,
I will work on that.
What I really was after was the DAQmx VI help. That gets installed when DAQmx is installed. I have the VIs (copied from a Windows instrallation). They do not work of course because the core .dll is missing. But that process does not get the help files.
I did search and found that there are programs available on the Mac which can process .chm files. I installed two and then downloaded the file you linked. That has the LV help. After some searching in the NI documents pages I found the DAQmx help and the DAQmx VIs help .chm files. Some links tend not to work, but this has given me access to the stuff I wanted.
For any other crazy Mac users who want to read help files on VIs you cannot run, I have tried CHM Reader, available through the Apple App Store, and iChm, which I found at https://www.macupdate.com/app/mac/28171/ichm . CHM Reader seems to be a bit more robust with the NI files.
Thanks.
Lynn

Error when trying to view examples in LabView help

When pushing button to "open example" or "browse related examples" from within LabView help I get the following error
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://127.1.0.1:3580/National%20Instruments/LabVIEW/LabVIEW/7.1/OpenVIFromHelp?
The following error was encountered:
Connection Failed
The system returned:
(111) Connection refused
My IT-department are unable to help me.
They state that this is a Labview related problem and not at problem originating from our firewall or similar.
In this forum I've found one guy having a similar problem
(http://forums.ni.com/rss/message?board.id=170&message.id=192671 - only the address was ..127.0.0.1.. and not 127.1.0.1),
but unfortunately he never got an usable answer on his question. At least not anything that works for me.
Hope that I'm more lucky now!
In advance: Thank you very much for any help
Jens

I just fought this battle myself, and thought I would along what I found was helpful.
My example finder in LabVIEW 7.1.1 functionality was broken and I found that National was attempting to connect with Example Finder on my local machine using IP address 127.1.0.1, instead of the more common 127.0.0.1 address for localhost. The result was that the Example Finder HTTP:// request was being sent away from my machine using the Microsoft Windows Internet Explorer HTTP Proxy information to my corporate web proxy server. That proxy server was properly refusing to proxy the connection since 127.1.0.1 is a non-routable address.
The error message back from the corporate HTTP proxy server was the helpful item. Once I saw what was happening, I went into the Microsoft Windows control panel for internet options and on the connections tab, LAN setting button, ADVANCED button, entered 127.*.*.* into the field for "DO NOT PROXY THESE ADDRESSES"
Now the Example Finder requests are directed to the NI server on my local machine and the example finder is back to working.
This is the second time I worked this out, but I forgot what was learned the first time.... Guess we are all condemned to repeat our mistakes.

LabVIEW help not opening

This is frustrating. When I try to open LabVIEW help, I get a popup box that says "File not found: mk:@msitstore:<somefilename>." I know this is a windows problem but I cannot find a solution anywhere. I've looked at the security updates and MS knowledgebase. I've reregistered and replaced my hhctrl.ocx file, I've looked at the registry, etc. I've tried every solution I could find and .chm files still won't open, which includes pretty much all the LabVIEW help. What else can I try???

It's definitely a generalized Windows problem. I've been all over the web looking for fixes besides re-registering hhctrl.ocx and was hoping someone here might have tried a different fix. It's looking like I'll need to rebuild Windows to get this fixed (i.e. Delete everything and start over.)
The error I posted shows up whenever I try to open any .chm file. HTML help opens fine. I've tried installing the MS Help Editor program again and it didn't help any. I've tried deleting the help system directories and letting Windows recreate them and that didn't help either.

Adobe Flash Broke my LabVIEW Help

Recently, all of a sudden whenever I opened up LabVIEW Help (such as right-clicking on a function/VI and selecting Help), the Help window would appear, the left pane would be filled in, but the right pane would be blank. The inner part of the title bar would be white, and the Help would simply freeze. The only way to resolve it was to force-kill LabVIEW Help via Task Manager, which also quit LabVIEW (even though it wasn't frozen). I couldn't figure out what was happening until I decided to run FileMon and saw that at the very end of loading the Help window, the Adobe Flash folder was being accessed. OK, this sort of makes sense, since it's displaying an HTML file, but it also doesn't make sense since it wasn't displaying Flash content. But why would that freeze the Help window? Flash worked just fine in my browser. I did a complete uninstall of Flash, and my LabVIEW Help magically started working again.
Anybody else seen this? FYI: I had Flash 10 installed. There had been an update to Flash a couple of weeks ago, I think, but I'm almost (99%) positive that I had used Help during that time without seeing this freeze. Haven't the courage yet to try installing it again.

Thanks for the feedback. I had to install Flash again since Pandora uses it (and I love Pandora). This time LabVIEW Help did not freeze up, and when I had FileMon running I saw that the LabVIEW executable was not accessing the Adobe folder (whereas before it was doing it right before the Help window froze up). Bizarre.

LabVIEW Help Important Information Copyright page broken links

None of the files or folders listed in the LabVIEW Help >> Important Information >>Copyright page are existing in my W7 64 bits LV 2013 installation:

It's been a while since I installed 2013...
But since you are mentioning it, I get the same page for LV 2014 Help, and sure enough, none of it matches anything I can find in the Program Files/National Instruments folder (obviously since it is shared by all versions).
I HAD an installation error when installing 2014.

Labview help menu

Hi,
I am not able to search the labview help Menu ( CNTRL + ? ) under the HELP drop down. When I press it, nothing happens. I tried re-installing Labview completely and it did not make any difference. I am using Labview 8.2
Thanks,
bira_pxi

Hi Jon,
Did you try browsing to the directory where LabVIEW is installed and just attempt to open the help file without going through LabVIEW? The help file in Linux for LabVIEW is just an html file, and sometimes if html files are not registered with a default application in the kernel, LabVIEW will not be able to open the file, and there will not be error thrown. LabVIEW opens the help file with whatever browser that's the default.
Let me know what you find out there. Thanks!
Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support

Problems in accessing forum and LabVIEW help

Today I experience heavy problems accessing the forum (slow and sloooower…) as well as the online LabVIEW help just giving:
Internal Server Error - Read
The server encountered an internal error or misconfiguration and was unable to complete your request.
Reference #3.45911160.1390920616.8e98ad6
Yesterday I experienced problems searching in the online help: While it seems to work in LV2011 help the same words weren't found in the LV2009 help!
What's going on here?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Hi,
no, it's not fixed at all. The problems of searching the online LabVIEW help still persist!
Searching for "snippet" in the LV2009 help results in this:
(German for "no search results")
Searching the exact same word in the LV2011 help gives the expected results:
So I guess the search is still broken for the older LV2009 online help…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Does LabView Help exist in ereader format?

I am looking for LabVIEW help in an ereader format. Not to concerned with which format. I can easily convert the format using Calibre.
I tried converting the chm files but that was turning into a major effort.
Appreciate the help.
Mike

Export the help to a PDF, using this Knowledgebase article:
http://digital.ni.com/public.nsf/allkb/ABBE63AD0050200386256FAA0063E049
As a companion, I would reccommend getting the e-book version of "LabVIEW for Everyone"
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

LabView help won't open

I have been trying to open the search LabView help and the help won't open. A window appears but then it won't load. I haven't done anything different to my computer, this just started happening suddenly. The whole program then usually crashes when I try to close the help after a while.
Any ideas?
Message Edited by flyer88 on 01-28-2009 03:29 PM

Does this happen no matter when you try to open LabVIEW help? Even if you click the LabVIEW Help button on the Getting Started page?
Does Context Help (Help >> Show Context Help) still work?
What version of LabVIEW are you using?
Also, can you open LabVIEW Help or any other help file externally? LabVIEW Help can be found in Program Files >> National Instruments >> LabVIEW x.x
Will
Certified LabVIEW Architect, Certified Professional Instructor
Choose Movement Consulting
choose-mc.com

Can I disable F1 for LabVIEW help?

When my VIs are running, I want to disable the help window popping up when the user presses the F1 key. I don't care whether it pops up when I'm editing.

Hi,
You can also programmatically discard the event that is generated when the F1 key is pressed by using filter events in an Event structure. Discard the event by passing a True value to the 'Discard?' input on the Event Filter Node for a Key Down ? event>. The Vkey to be monitored being "F1".
Regards,
Cyril Bouton
Active LabVIEW Developper

DESPERATELY NEED LabVIEW help ASAP for hire

Need LabVIEW expert ASAP for help with outputting a digital signal. $50-$75 to start - probably would only take an hour though. Would like service by Monday the 24th if possible. Over the phone or on site (Ann Arbor, MI) will work. Please contact [email protected] or [email protected]
We are working with a USB 6501 DAQ board, LabVIEW 8.5, and need to send a 3.5-5 V DC signal for controlled second time intervals (on/off). For example, send signal for 15 seconds. Turn off for 45. Do this for 3 outputs and repeat this process as many times as controlled by the user.

I hope this isn't homework

Improving the LabVIEW Help: Working with Data Types

Have you ever had trouble figuring out how to work with the waveform data type, the dynamic data type, or some of the other more complex data types in LabVIEW? As a tech writer on the LabVIEW team, I'd like to improve our documentation about working with data. What would you like to see? What would be helpful? Have you ever given up on a particular data type because it didn't work? Have you ever created a replacement data type because you preferred not to use a LabVIEW data type?
Lacy Klosterman Rohre | Marketing Editor | National Instruments | 512.683.6376 | ni.com/newsletter

I've been programming LabVIEW since around 3.1 / 4.0. Over the years and versions, I've found it necessary to approach a lot of the new datatypes and algorithms with some healthy skepticism because I don't think we're usually given a "fair and balanced" overview. Some of the things that are highly promoted that bring "ease of use" for beginners (and I *do* understand the importance of that when you're growing your LabVIEW user base) can carry significant performance penalties that are mentioned in more of a whisper, if at all. I'd just like a more full disclosure of the tradeoffs -- the good, the bad, and the ugly.
Waveforms -- very rarely use them, unless required for analysis functions. I have a vague notion (between a belief and a memory) that they used to carry a significant performance penalty compared to arrays, but that the gap is now much smaller. Still, I'm most comfortable with my old habit of using data arrays. Some of this came about because a lot of my work uses counters where I may have a variable "dt" value or where my AI is clocked by a counter and the "dt" isn't internally generated.
Dynamic signals -- have never used them. Have no clear idea what good they're supposed to be, and they seem to be tied in primarily with Express VI's, which I have also studiously avoided.
Variants -- Use them only slightly. Performance issues are a question mark. Exception: have learned that the implementation of Variant properties allows their use as an efficient way to create associates for string lookup tables.
Digital Waveform -- have typically avoided it except when graphing digital data during debug. Haven't found any compelling reasons to use it. I do like the notion of a compress/expand capability for sparse digital data, but haven't exercised it enough to trust the implementation.
Recap: I don't need more simple "how-to's" in the help. I need a LOT more "why bother's" that include both pros and cons.
-Kevin P.

Labview help for first robotics team 3959

I am from team 3959 in the first robotics competition and we are stumped on something and have been for a while. We are trying to make a code for a shooter(ran by a vex pro jaguar) that launches frisbees(go to the first website for more info.) and a servo code(a vex pro servo) both in a Teleop.vi but although they have no code in common they conflict. the shooter code works fine as does the servo but if used at the same time the shooter runs a full neutral. I have added pictures of both codes to show. one is labeled working servo the other is a jaguar code. please if anyone could possibly help it would be great
-Joseph (proud head programming student of 3959)
Attachments:
labview.docx ‏352 KB

Questions about FRC should be posted in the FIRST Robotics Competition Community.
Please don't use Word documents for screenshots. Paste the screenshot into mspaint and save as a PNG, or even better, upload your code as an attachment. I'm an experienced FRC mentor and I still can't figure out what's going on in your screenshot because so much is crossed out and circled. Possibly the problem is that the servo code runs in a loop - why is it in a while loop? There's already a while loop further up in the code; if you put a loop like that inside your code, it will prevent the main loop from repeating until the inside loop finishes, which means anything else that is supposed to run repeatedly will run only once (until the servo loops stops; then it will run again one time and the servo loop will restart, etc.)

Dice vi in labview needed.Can all the experts in labview help?

i need to use labview to create a dice vi.This dice vi needs to test an interfacing hardware downloaded with a dice program(written in vhdl).
i really need help in writing the vi and using the daq card to interface with the hardware.I'm using a pci-6503 with cb-50lp, and labview 6i.
Here are the specifications for the vi:
1.Needs 7 dig_read_to_lines to show the leds(display 7-seg to show the numbers of dice after each 'throw');
2.needs 2 dig_write_to_lines to tell the hardware to when to start and when to reset.When start is first pressed, the 7-seg will display a continuous running random number, and when the start is pressed the 2nd time, the 7-seg will stop to display a random number.T
he reset when pressed will make the 7-segment back to 0.
3.both the read and write can also using read_to_port or Write_to_port(i'm not very sure how).
The problem is to combine both read and write togather so that the vi can continuously read the hardware and display random running numbers and at the same time able to start,stop and reset as desired.I've tried doing it,but unsuccessful,becos either the numbers don't run continuous or the numbers don't start,stop andt reset as desired.
Pls help and if anyone can show me a model dice vi,it'll definitely help alot.Its quite important.

Here is how you can set up your VI. I would recommend using the read and write to digital port VIs. Use the DIO advanced VIs to get the results that you need. You will see that the read/write to digital port VI basically use two steps - Port Config, and Read/Write Port VI.
Here is my idea. Outside of a loop run Port Config VI and configure one port for read and one port for write. Then in the loop you will read and/or write to digital ports depending on certian conditions such as start, stop, reset, etc (use case statements). You can use the line mask to read or write the lines of interest in Read/Write Port VI.
So when the start button is pressed the program will write out a value to the write port and start the read from digital port.
Then when the the st
op button is pressed, the program will stop reading from the digital port. Finally when the reset is pressed, you can not set the read port to zero, but you can set the indicator on the front panel to zero (maybe use a local variable). The read port will simply return the value at the port and does not set the port to a certain value (it is a read port and not a write port).

Crossbow Labview help

Similar Messages

Maybe you are looking for