Hi everyone,
1st Scenario :
I have a sensing application to send 100 samples of data over to XmeshBase 5
seconds periodically. When using Xsniffer, I can view the packets it is trying
to send to XmeshBase. Thus, there is nothing wrong with the upstream packet.
Initially the DataType column would indicate Bcast (Blue color ) since it is in
Broadcasting mode and have not yet establised a mesh connection. At the same
time, i'm running Xserve, it just shows the null values.
After waiting for a very long period of time say 10-40 Minutes , I managed to
see the DataType to change to Base and the color has turned light green which
signifies that a mesh has been formed. It is only at this moment that i can
actually see the raw data being updated in Xserve.
2nd Scenario :
I load up a pre-built Tutorial 4 Crossbow Xmesh application found in
apps/tutorials folder , myApp ,which is a lite version of XMTS310 , not
including the extras like health pckt , power management ..etc and i load it
to the same mote ... and after about 10-30 Seconds, it establishes a mesh like
magic... I didnt believe it and tried a few times and it is so stable.
My question is, where am i missing ? I actually wrote my sensing application
based on myApp ... using the Mhopsend feature to send my packet. The only known
difference is that for my application, I am using HighFrequencySampling to
sample my data as compared to packing the data into an XdataMsg structure found
in myApp which is sampling just a few values.
However, I do not suspect that this is the problem as i even tried to sample
just 10 samples using my HFS application, still, i have to wait a long time to
establish a network.. I even tried to use a call Mhopsend.getBuffer, but there
seem to be no difference if i have it or not.
Please lend me your advice..
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
