Thnaks Hui,
but the thing we do not want TinyDB to do all the data handling with its existing code. I mean can we code our own data aggregation operators in TinyDB and still use it?
If we can do that, it solves our problem.
What we are looking for is some way of operating on the data reported by sensors before transmitting them to the base station.
 Regards,
Torsha

+----------------------------------------------------------------------+
| Torsha Banerjee                                                      |
| Ph.D Student                         Email:[EMAIL PROTECTED]     |
| University of Cincinnati             Lab Phone: (513) 556-3437       |
| CDMC Laboratory                                                      |
| ECECS Dept, PO Box 210030                                            |
| Cincinnati, OH 45221-0030                                            |
+----------------------------------------------------------------------+


On Fri, 12 Jan 2007, Hui KANG wrote:


Did you check TinyDB?

Hui Kang

On 1/10/2007, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:

Hi,
 We are currently working on data aggregation of packets on TinyOS.
Is there any link to websites which gives us overview about how to code
this in nesc i.e.
sensors send packets to source and source does some kind of data
aggregaation like SUM, AVG, MAX and more advanced mathematical operation
on
that data?
Please let me know,
Thanks,
Torsha

+----------------------------------------------------------------------+
| Torsha Banerjee                                                      |
| Ph.D Student                         Email:[EMAIL PROTECTED]     |
| University of Cincinnati             Lab Phone: (513) 556-3437       |
| CDMC Laboratory                                                      |
| ECECS Dept, PO Box 210030                                            |
| Cincinnati, OH 45221-0030                                            |
+----------------------------------------------------------------------+


On Mon, 11 Dec 2006, [EMAIL PROTECTED] wrote:

Send Tinyos-help mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

  1. Re: TOSSIM 2.x doesn't run : pythonpath? (preeti k)
  2. Re: problem with short packet in tmote  ... (Jos? Ulloa Su?rez)


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Dec 2006 19:00:23 +0530
From: "preeti k" <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] TOSSIM 2.x doesn't run : pythonpath?
To: [email protected]
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

oops..! i have not compiled any application on tossim successfully .
I guess that can be the reason python doesn't run the simulation. Still the
msgs that i get for python do not seem obvious.

The last step of compilation (copying python support ) doesn't work
app.xml is created but tossim.py, tossim.dll etc are not created.
Cud this be because of the classpath that i cannot set properly or anything
else?

please let me know

Preeti


On 12/11/06, preeti k <[EMAIL PROTECTED]> wrote:

I set the pythonpath as follows and used both upper and lower cases of
'tossim' in   'from tossim import *'  , i get the following msgs

$ export PYTHONPATH=/opt/tinyos-2.x/support/sdk/python/tinyos
$ python
Python 2.3.4 (#1, Jun 13 2004, 11:21:03)
[GCC 3.3.1 (cygming special)] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
from *tossim* import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/opt/tinyos-2.x/support/sdk/python/tinyos/tossim/TossimApp.py",
line 45,
 in ?
    from tinyos.tossim.TossimNescDecls import *
ImportError: No module named tinyos.tossim.TossimNescDecls
from *TOSSIM* import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named TOSSIM


I then tried and set the pythonpath as /opt/..../python(ie without the
last tinyos dir)

$ export PYTHONPATH=/opt/tinyos-2.x/support/sdk/python

$ python
Python 2.3.4 (#1, Jun 13 2004, 11:21:03)
[GCC 3.3.1 (cygming special)] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
from *tossim* import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named tossim
from *TOSSIM* import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named TOSSIM
from *tinyos.tossim* import *
* t=TOSSIM([])*
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: name 'TOSSIM' is not defined
*t=tossim([])*
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: name 'tossim' is not defined

I don't know whats going wrong , either ways it doesn't seem to work for
me
can someone help me out?
Preeti


On 12/11/06, preeti k <[EMAIL PROTECTED]> wrote:

I set the python path to

$ export PYTHONPATH=$TOSROOT/support/sdk/python
but it doesn't seem to work.

i get the error as follows (its quite long)


$ make micaz sim-cygwin
mkdir -p build/micaz
  placing object files in build/micaz
  writing XML schema to app.xml
  compiling BlinkAppC to object file sim.o
ncc -c -DUSE_DL_IMPORT -fpic -o build/micaz/sim.o -g -O0 -tossim
-fnesc-nido-tos
nodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\)
-finline-limit=
100000 -Wall -Wshadow -Wnesc-all -target=micaz
-fnesc-cfile=build/micaz/app.c -b
oard=micasb  -Wno-nesc-data-race BlinkAppC.nc   -fnesc-dump=components
-fnesc-du
mp=variables -fnesc-dump=constants -fnesc-dump=typedefs
-fnesc-dump=interfacedef
s -fnesc-dump=tags -fnesc-dumpfile=app.xml
In file included from /opt/tinyos-2.x/tos/lib/tossim/sim_mac.c:34,
                 from /opt/tinyos- 2.x/tos/lib/tossim/tos.h:89:
/opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:14: warning: declaration of
`link' sha
dows global declaration
/usr/include/sys/unistd.h:97: warning: location of shadowed declaration
/opt/tinyos- 2.x/tos/lib/tossim/sim_gain.c:20: warning: declaration of
`link' sha
dows global declaration
/usr/include/sys/unistd.h:97: warning: location of shadowed declaration
/opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: In function
`sim_gain_allocate_link':

/opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:134: warning: declaration of
`link' sh
adows global declaration
/usr/include/sys/unistd.h:97: warning: location of shadowed declaration
/opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: At top level:
/opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:141: warning: declaration of
`link' sh
adows global declaration
/usr/include/sys/unistd.h:97: warning: location of shadowed declaration
In file included from /opt/tinyos- 2.x
/tos/chips/atm128/timer/sim/HplAtm128Timer0
AsyncC.nc:58,
                 from /opt/tinyos-2.x
/tos/platforms/mica/AlarmCounterMilliP.nc:3
0,
                 from /opt/tinyos-2.x/tos/platforms/mica/sim/HilTimerMilliC.nc:4

1,
                 from /opt/tinyos-2.x/tos/system/TimerMilliP.nc:41,
                 from /opt/tinyos-2.x/tos/system/TimerMilliC.nc:40,
                 from BlinkAppC.nc:46:
In component `HplAtm128CompareC':
/opt/tinyos-2.x/tos/chips/atm128/timer/sim/HplAtm128CompareC.nc: In
function `ti
mer0_compare_handle':
/opt/tinyos-2.x/tos/chips/atm128/timer/sim/HplAtm128CompareC.nc:195:
warning: de
claration of `time' shadows global declaration
/usr/include/time.h:49: warning: location of shadowed declaration
cc1: warning: -fpic ignored for target (all code is position
independent)
  compiling Python support into pytossim.o and tossim.o
g++ -c -DUSE_DL_IMPORT -shared -fpic -o build/micaz/pytossim.o -g -O0
/opt/tiny
os-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.3
-I/opt/tinyos-2.x
/tos/lib/tossim -DHAVE_CONFIG_H
cc1plus: warning: -fpic ignored for target (all code is position
independent)
g++ -c -DUSE_DL_IMPORT -shared -fpic -o build/micaz/tossim.o -g -O0
/opt/tinyos
-2.x/tos/lib/tossim/tossim.c -I/usr/include/python2.3 -I/opt/tinyos-2.x
/tos/lib/
tossim
cc1plus: warning: -fpic ignored for target (all code is position
independent)
  linking into shared object ./_TOSSIM.dll
g++ -fpic -shared -W1,--enable-auto-image-base  build/micaz/pytossim.o
build/mic
az/sim.o build/micaz/tossim.o -L/usr/lib/python2.3/config -lpython2.3-lstdc++ -
o _TOSSIM.dll
build/micaz/sim.o(.text+0x239): In function `fillInOutput':
/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:97: undefined reference to
`_hashtable_
search'
build/micaz/sim.o(.text+0x309):/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:127:
und
efined reference to `_hashtable_search'
build/micaz/sim.o(.text+0x2f04): In function `sim_log_init':
/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:154: undefined reference to
`_create_ha
shtable'
build/micaz/sim.o(.text+0x2f86): In function `sim_log_add_channel':
/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:166: undefined reference to
`_hashtable
_search'
build/micaz/sim.o(.text+0x3050):/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:181:
un
defined reference to `_hashtable_insert'
build/micaz/sim.o(.text+0x3100): In function `sim_log_remove_channel':
/opt/tinyos-2.x/tos/lib/tossim/sim_log.c:207: undefined reference to
`_hashtable
_search'
build/micaz/tossim.o(.text+0x9c9): In function `_ZN4MoteC2EP8nesc_app':
/opt/tinyos-2.x/tos/lib/tossim/tossim.c:125: undefined reference to
`_create_has
htable'
build/micaz/tossim.o(.text+0xa01): In function `_ZN4MoteC1EP8nesc_app':
/opt/tinyos-2.x/tos/lib/tossim/tossim.c:125: undefined reference to
`_create_has
htable'
build/micaz/tossim.o(.text+0xb62): In function
`_ZN4Mote11getVariableEPc':
/opt/tinyos-2.x/tos/lib/tossim/tossim.c:172: undefined reference to
`_hashtable_
search'
build/micaz/tossim.o(.text+0xcaa):/opt/tinyos- 2.x/tos/lib/tossim/tossim.c:188:
u
ndefined reference to `_hashtable_insert'
collect2: ld returned 1 exit status
make: *** [sim-exe] Error 1


Any clue what can be done about this?

Preeti


On 12/8/06, Daniele Munaretto <[EMAIL PROTECTED] > wrote:

You should define your python path, because this error is due to the
wrong path.
Hoping this can be helpful and a good hint,
cheers
Daniele


preeti k wrote:
I looked at this thread of the tinyos-help.
I seem to have the same problem wrt python
After "from tinyos.tossim import *"
  runs but the new command "t=tossim([])" doesn't.
Can you help me out? May I know what changes and to which script
should be made?

Thanks



Dear Dr.Levis,
Finally i solved, there was an error in a script. Thanks very much
for your
help.
Instead i don't understand why, when i switch back to 1.x, i cannot
compile
apps no more, while in 2.x yes. I'm following the instructions for
changing the
paths but nothing...in the attached file there is the compiling
result.
Cheers
Daniele


        -----Original Message-----
        From: Munaretto, Daniel
        Sent: Tue 9/12/2006 10:02 AM
        To: Philip Levis

        Cc:
        Subject: RE: [Tinyos-help] TOSSIM 2.x doesn't run



        Dear Dr.Levis,

          thanks very much for your help. But after "from
tinyos.tossim import
*", that runs, the new command "t=Tossim([])" doesn't work. Changing
Tossim
with TOSSIM or tossim it is the same:
        "NameError: name 'tossim' is not defined".


        Cheers
        Daniele

                -----Original Message-----

From: Philip Levis [mailto:[EMAIL <mailto:%5bEMAIL> PROTECTED]

       Sent: Mon 9/11/2006 6:08 PM
                To: Munaretto, Daniel

Cc: [email protected] 
<mailto:[email protected]

                Subject: Re: [Tinyos-help] TOSSIM
2.x doesn't run




                On Sep 11, 2006, at 6:42 AM, Munaretto, Daniel
wrote:


              > Dear all,
              >    following the tutorial and archive cause of
some problems,
i
              > compiled Blink apps as:

              >
              > make micaz sim- cygwin

              >
              > in order to run then TOSSIM.

But after writing
              > "from TOSSIM import *"

              > in python environment, the bash displays "no
module named
TOSSIM".

              > Does it mean that with the sim- cygwin command i
cannot run
TOSSIM
              > in tinyos-2.x?

                You need to add
tinyos-2.x /support/sdk/python to your
PYTHONPATH
                variable.


                Phil







-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20061211/4296d896/attachment.html

------------------------------

Message: 2
Date: Mon, 11 Dec 2006 11:31:30 -0300
From: Jos? Ulloa Su?rez  <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] problem with short packet in tmote  ...
To: Lista Tinyos <[email protected]>
Cc: Hemanth H <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi, i found  your question  posted  in the TinyOS Mail List. Nowaday
we've been experiencing the same problem with a short packet.
Can you help me if you have found the answer?, or guide us with your
experience in with this problem.
In this link somebody have the same problem:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-January/014213.html



My tinyos version is 1.1.11-3is
Thank you very much.



__
Jose Ulloa S

Hemanth H escribi�:
Hi

I am using SurgeTelos application to sample an sensor at 100 samples
per second. I am sending the sampled data through the multihop to the
base node.(the base node is also sampling data and sending thru UART
to the comp). I am using about 3 hops max currently and only 4 nodes .
I have made the following changes to the SurgeMsg packet format. First
have changed the seqno from 32 bit to 16 bit. Then I have increased
the no of readings from 1 to 6 in a packet.

I have also made changes to the MultiHopLQI library. First I have
increased MHOP_QUEUE_SIZE from 2 to 20 and MHOP_HISTORY_SIZE from 4 to
40. I did get significant performance improvement with this change. I
have not changed the MAC and retained it as it is.

I am using the oscilloscope application to display tha data. I have
used MIG to modify the oscilloscope app. and I am also displaying the
debug information .

Now with this configuration I run all the nodes at RF power 1 so that
the testing is easier.

I am facing the following problem

1 I am having high error rates, How can I improve performance without
changing the MAC for now.
2 When I run the setup and the oscilloscope application the setup runs
for several seconds properly and then I get an error as follows.
The packets of the base node are not having any problems but all other
packets through the radio are having problems. i.e I am only getting
the header but the body is missing.

Can anybody tell me what I am doing wrong.



726
receive error for net.tinyos.oscil.OscopeMsg (AM type 17): invalid
length messag
e received (too short)
receive error for net.tinyos.oscil.OscopeMsg (AM type 17): invalid
length messag
e received (too short)
message recieved

Oscope message recieved
Message <OscopeMsg>
 [sourceaddr=0x0]
 [originaddr=0x0]
 [seqno=0x0]
 [originseqno=0x1]
 [hopcount=0x0]
 [type=0x0]
 [data=0x53 0x3f 0x50 0x44 0x59 0x3b ]
 [parentaddr=0x7e]
 [seq_no=0x2d7]

Output from the Listen application

00 21 08 EF FF FF 7E 00 11 7D
1C 00 00 00 00 00 7E 00 11 7D 00 00 00 00 00 00 04 00 00 00 00 00 3B
08 48 08 42
08 4B 08 3D 08 52 08 7E 00 9D 08
00 21 08 23 FF FF 7E 00 11 7D
00 21 08 F0 FF FF 7E 00 11 7D
00 21 08 25 FF FF 7E 00 11 7D
1C 00 00 00 00 00 7E 00 11 7D 00 00 00 00 00 00 04 00 00 00 00 00 33
08 4F 08 3F
08 52 08 3E 08 52 08 7E 00 9F 08
00 21 08 26 FF FF 7E 00 11 7D
00 21 08 F2 FF FF 7E 00 11 7D
1C 00 00 00 00 00 7E 00 11 7D 00 00 00 00 00 00 04 00 00 00 00 00 7E
08 2C 08 4A
08 47 08 4F 08 4A 08 7E 00 A0 08
00 21 08 F3 FF FF 7E 00 11 7D
1C 00 00 00 00 00 7E 00 11 7D 00 00 00 00 00 00 04 00 00 00 00 00 42
08 4E 08 4A
08 4F 08 43 08 4D 08 7E 00 A1 08
00 21 08 28 FF FF 7E 00 11 7D
00 21 08 F5 FF FF 7E 00 11 7D
1C 00 00 00 00 00 7E 00 11 7D 00 00 00 00 00 00 04 00 00 00 00 00 46
08 57 08 40
08 58 08 3F 08 50 08 7E 00 A2 08

regards
hemanth
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help





------------------------------

_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

End of Tinyos-help Digest, Vol 44, Issue 35
*******************************************
)
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to