Hi, I've tried to install Deluge on a tmote mini.
Formatting the Flash and installing Deluge works without problems, but I
can't ping the tmote neither over USB when it's plugged in the
programming fixure nor over-the-air. It should work the same way as with
tmote sky described on page 29 and 30
Hi Bernardo,
Looks promising. Would it be possible to make this a wiki?
It would be interesting to have a section with all the different sensors
available on the different mote platforms (for instance first sorted by
mote families, then by sensor boards). This section could state the
TinyOS
It's all looking a lot clearer now, I guess the only question remaining is -
is there any limit to setLocalSleepInterval()? Could I tell it to sleep for
4 hours [setLocalSleepInterval(1440)] ...ignoring the (relatively)
potentially devestating power requirements on trying to send a message to
Dear all,
I am a beginning student of Tinyos. Now I faced a problem while using
TOSSIM showed as below, and my os is open suse and Python version is 2.5.
Can anyone help me?
thank very much
weiping
cjspc9:/opt/tinyos-2.x/apps/Blink # make micaz sim
mkdir -p build/micaz
placing object files in
Hi Roberto,
the cc2420 allows different RF output power levels. The default value is set
to
(1 CC2420_TXCTRL_PADIFF) | (0x1f CC2420_TXCTRL_PAPWR));
I'm wondering to know to which value that correspond to, since I didn't find
it in the datasheet. Also, the possible values are
31
27
23
When applying the Blink application on tmote sky, I find if I add one
more BlinkC.Leds - LedsC; statement to the file BlinkAppC.nc, the
Leds stop blinking. Here is the code of BlinkAppC.nc:
I mean, if one change the code of BlinkAppC.nc to be the following,
the Leds wont blink:
configuration
Hello all,
I am Rafael Marin Perez, and work as a researcher in University of
Murcia (Spain).
We are using the Network Storage Link for USB2.0 (NSLU2) device to
desploy a wireless sensor network (WSN). And we need to reprogramming
the Tmote-sky motes via TCP/IP, because Deluge requiere too much
What hardware (MCU, sensor) are you using ?
MCU - platform
if you are reading
temperature, then there obviously should not be such spikes, so it
looks like there is a problem with reading data from the sensor. I
just re-ran Oscilloscope for all external sensors on telos and it
worked
- what is the search path for components?
I'd like to create, as you write above, my own TemperatureClientC class,
HumidityClientC, for code-reuse and also for code clarity. If I just
create an TemperatureClientC.nc file, where do I have to put it so that
the build process finds it?
You can
Hi,
Is maximum packet size of TinyOS is 32 bytes?Moreover in Surge application
34 byte packet some times. Surge do send the 22 byte packet. What does this
packet signify and can any one tell me the packet format?
Regards,
Adi
On 8/9/07, Michael Schippling [EMAIL PROTECTED] wrote:
It is all,
My suggestion is for TinyOS community to start a WIKI where people can
contribute their experiences. It will be hard for a person to summarize
all information for different hardware platforms.
Personally, I would like to help as well.
Another thing is that the Mailing list is getting a bit
By wiring twice you are saying that the functions provided by the
interface Leds are also called twice. BlinkC calls the leds to toggle,
and two back-to-back toggles makes the led stay the same (at least for
our eyes).
Hugo
On 8/13/07, Min Guo [EMAIL PROTECTED] wrote:
When applying the Blink
Hi,
look in the file tinyos-1.x/tos/types/AM.h
- Mensaje original
De: Adi Mallikarjuna Reddy V [EMAIL PROTECTED]
Para: [EMAIL PROTECTED]
CC: tinyos-help@Millennium.Berkeley.EDU
Enviado: lunes, 13 de agosto, 2007 12:52:04
Asunto: Re: [Tinyos-help] Regarding Packet format
Hi,
Is
Jan,
You can for example (1) put it in your application folder, (2) create
a new folder and include it with CFLAGS in you Makefile, (3) put it in
-Ifolder_name would do the trick?
any of the directories contained in your tos/platform/.platform file
or (4) if it is a driver for a new
Peizhao Hu wrote:
My suggestion is for TinyOS community to start a WIKI where people can
contribute their experiences. It will be hard for a person to summarize
all information for different hardware platforms.
yes, I find this a good approach myself. for example, I've already
created a guide
I don't know about that, but you can find out if you make a component
that implements two interfaces and commands that manipulate the same
variable (initially set to 0). For example have one command set the
variable to 2 and have the other command divide the variable by 2, and
on both commands set
Hi,
The TinyOS gentoo-wiki is a valuable resource for installing TinyOS on
gentoo. However I think its scope is limited to gentoo. So the question
would be, where would we start a general-purpose TinyOS wiki? How about
a wikibook http://en.wikibooks.org/wiki/Main_Page ?
Cheers,
Urs
Ákos Maróy
Urs Hunkeler wrote:
The TinyOS gentoo-wiki is a valuable resource for installing TinyOS on
gentoo. However I think its scope is limited to gentoo. So the question
yes, you're right - I just sent it as an example... we shouldn't post
non-gentoo information on the gentoo wiki..
would be, where
Although I believe 802.15.4 says broadcast packets can be ack'd (to tell
your transmitter that at least one other node received the packet), LPL
disables PacketAcknowledgements before transmitting to the broadcast
address. Ignoring acknowledgements, this allows it to deliver the broadcast
packet
Bernardo Avila Pires wrote:
Greetings!
I have recently written a tutorial, putting together some of the
experience I gathered
I like this section Bernardo:
==
Tinyos adopts some modular programming concepts and principles, such as
programming for interfaces.
Hi,
I have a weird problem. I am running Tmote Sky with TinyOS 1.x app. I am
transmitting serial data with following function:
code
command result_t Comm.transmit(const COMM_Msg msg)
{
TOS_Msg tosMsg;
uint8_t* p;
//Valid msg type if sent by rfm?
if(msg.destAddr != COMM_SERIAL
(msg.type !=
On 8/13/07, Hugo Sousa [EMAIL PROTECTED] wrote:
I don't know about that, but you can find out if you make a component
that implements two interfaces and commands that manipulate the same
variable (initially set to 0). For example have one command set the
variable to 2 and have the other
Roberto,
I've tested all values from 1 to 31 for the PAPWR, and they work.
Based on quick eyeballing of the data, the register setting
corresponds linearly to the amplitude of the output signal, with some
non-linearity at the setting of 1. At the setting of 1, the output
power is about -40dBm.
On Aug 12, 2007, at 9:25 PM, Bin Lei wrote:
In the user manual, AC is defined as code is reachable from at least
one interrrupt handler; while SC is code only reachable from tasks.
But there are many event handler that are not tagged using async, are
they async or sync?
e.g. in Blink example,
On Aug 13, 2007, at 8:14 AM, Ákos Maróy wrote:
Urs Hunkeler wrote:
The TinyOS gentoo-wiki is a valuable resource for installing
TinyOS on
gentoo. However I think its scope is limited to gentoo. So the
question
yes, you're right - I just sent it as an example... we shouldn't post
On Aug 13, 2007, at 1:47 AM, Wei Ping Song wrote:
Dear all,
I am a beginning student of Tinyos. Now I faced a problem while using
TOSSIM showed as below, and my os is open suse and Python version
is 2.5.
Can anyone help me?
thank very much
weiping
cjspc9:/opt/tinyos-2.x/apps/Blink # make
Look to the oft quoted octavetech doc for info about the message and payload:
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf
In general the stuff that gets put into the data payload is defined as
a struct in a .h file in the app's directory. surgeCmd.h would
A brochure dated 25july2007 by them has these words:
===
controller and 802.15.4 radio solutions. It
is available under a commercial license or
for academic use under a GPL license.
=
and a download of 0.9.5 version has GPLv2 in it
It's a real
I reworked UserButtonP.nc, UserButtonC.nc, SwitchToggleC.nc from
tinyos-2.x/tos/platforms/telosb
and their test program
tinyos-2.x/apps/tests/telosb/TestUserButton/TestUserButtonC.nc,
TestUserButtonAppC.nc to get some practice with generic modules and came
across something I don't understand.
Hi,
I have a TinyOS-1.x installation in Ubuntu . The hardware platform is
MICA2 MIB520.
In a test case, I have CntToLedsAndRfm uploaded on one mote A and the
TOSBase uploaded on the mote B mounted at the base station. The LEDs on
mote A blink at different frequencies as specified in the
Hii,
I am using Moteworks to implement multihop network.
I am trying to receive (Intercept) the data at the intermediate node, so
that I can perform some aggregation. But data forwarded to the base station
is different and constant. Below is my intercept function. I think I have
some problem with
I have a heavily modified version of MultihopOscilloscope. Using the
snooping event data is received and stored to Train a Neural Network
for fault detection. Everything works, but snooping is sometimes
erratic. With several nodes TXing, random nodes will not snoop
messages from ALL nodes.
Our goal was that the wiki would be hosted at Harvard. The tinyos.net
site is hosted by Berkeley, and the Debian packages are hosted by
Stanford, so we thought that further distributing the administration
would make it easier for new resources to join and also make it clear
that it's a group
The LEDs should blink on the TOSBase mote if it is getting/sending radio
messages. I would try using Listen or ListenRaw to see if anything
is coming through when the LEDs flash. If no TOSBase flashing, check your
radio freq and power settings during compile. Especially on mica2, the
power is set
On Aug 13, 2007, at 12:51 PM, Joe Polastre wrote:
Our goal was that the wiki would be hosted at Harvard. The tinyos.net
site is hosted by Berkeley, and the Debian packages are hosted by
Stanford, so we thought that further distributing the administration
would make it easier for new resources
Another thing with the TinyOS wiki is about its content management, I
strongly recommend to separate it into sections (i.e.: TinyOS version
1.x, 2.x and future beta x.x :-) and related topic).
I guess many people who use Ubuntu will agree that
http://ubuntuguide.org/wiki/Ubuntu_Edgy wiki is
Please refer to
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-May/016654.html
you need to use the higher number of USB port for UART communication.
well, I don't have the MIB520, so I am not sure whether it helps.
regards;
Peizhao
Hemanth wrote:
Hi,
I have a TinyOS-1.x
I've just written a tutorial with newbie speed of understanding as its
aim, from a new user standpoint, since I am one. Please read and
understand this set of web pages so you can tell me how to improve them
while my short term grasp of its detail is good.
There are 3 motes: A, B, C with node id 0, 1, 2
node A is basestation, node B, C are using BlinkToRadio
In the first, we use the Listen tool to get the packet sent by node B, we
got:
00 00 01 22 06 04 00 06 00 01 00 01
00 00 01 22 06 04 00 06 00 01 00 02
00 00 01 22 06 04 00 06 00 01 00 03
00 00
39 matches
Mail list logo
