Labview Drivers for Wireless Sensor Networks

[anilhk]

Hi Ryan,

thanks for the early reply ..

Yes I do have the physical crossbow hardware .Can you please let me know more about the VIs which are already present in the Lab , where can I find them .
Also I am not able to view the attachment which you have mentioned.

Regards

Anil

[anilhk]

Hi mfitzsimo
thanks for the reply, I am currently working on crossbow , if I have any querries in Accsense I will surely buzz you .
Currently I am in Houston , Texas and persuing my masters in Computer science .
I am doing this for my research work in Wireless Sensor networks

[Ryan_V[DE]]

Hi Anil,

What school are you attending? If you do not already have them, the VIs can be downloaded here. Be sure to put the top level folder (Crossbow XMesh WSN) into your LabVIEW directory's instr.lib folder. If you are familiar with DAQmx programming, the structure is very much the same. We don't have much in the way of examples, but there are some available here:

C:\Program Files\National Instruments\LabVIEW 8.5\instr.lib\Crossbow XMesh WSN\Examples\

They should give you an idea of how to use the API. Finally, the individual API VI should be available in LabVIEW's Instrument IO palette. Please let me know if you have any more questions.

Regards,

[anilhk]

Hi Ryan

thanks for the info.. i will check the same and revert incase of any issues ..

[anilhk]

Hi Ryan ,

I am currently trying to run the files which I have downloaded , however in my mind I have got few querries .. They might be trival ..but i am not able to get things figured out in my mind .

Once this is connected and starts working , how would my Labview application interact with the hardware .?

How will labview interact with the user ? is ther going to be another interface after the labview which will be used to interact with the users ?

How exactly labview is going to work in this case? . what role VI's are going to play ?

I know these querries might be trival to most of you guys ... but i need to ask them to have a clear undustanding of what i am going to built !

thanks !

Regards

Anil karamchandani

[anilhk]

Hi all

Any info on the above ? .. pls help

[Ryan_V[DE]]

Hi Anil,

In this driver, LabVIEW interacts with the sensor network gateway at the lowest level. It sends and receives packets of information over the serial port. For received data, it buffers it until requested by the user (in the form of a read, etc.). It also provides parsing of the messages and conversion of the raw binary data into engineering units. From that point on, all aspects of your program are up to you. The example I referenced simply displays packets as they come in to the gateway and are forwarded to the host PC. It is quite simple to turn this into a graph to plot trends, or save it to a file. LabVIEW is a full-featured programming languange (and more!) which should allow you to create just about any kind of application you can think of. Perhaps if you give us more information on what it is you are trying to do, I could provide some general suggestions.

Regards,
Ryan

[anilhk]

Hi Ryan / all,

I have downloaded the Labview drivers for the gateway(MIB 520) and sensors(MTS 310) .
In my current setup ,Gateway MIB 520 is connected to my PC where Labview is installed via a COMM port ie serial communication and the sensor MTS 310 is mounted on the Gateway .

The drivers which i had downloaded is kept at the location C:\Program Files\National Instruments\LabVIEW 8.5\instr.lib in the directory Crossbow XMesh WSN

Now when i click on the project Crossbow XMesh WSN.lvproj i see a project explorer window .
In the window when i click on any of the VIs (eg Read Data and Display Health.vi)
and run the same i get an error
Error 8003 occurred at WSN Send Generic Stream Message.vi . Possible reasons :
Engine is not responding .An unexpected terminal error occurred.

May be i am not using the examples in the right manner . can any one guide me thorugh this please
thanks

anil

[anilhk]

guys ,

any luck !

[Nitin_T]

Hi Anil,

You are using the VIs properly. The examples should run without any issues. I would suggest checking the COM port to which you've connected the device. See if it is on COM1, because the software (see Block Diagram) by default selects it. You can select the right COM port and try executing the program once again. I hope this helps! Let me know if there is anything else I can help with or clarify. Have a great day!