The most common way is to attach a series resistor into the power feed.
This is easiest to accomplish by soldering a 1ohm resistor to a
double-sided piece of circuit board and stuffing it between the battery
terminal and holder contact. After that, measure the voltage over the
resistor with an
Hi Guys,
I have any problem with current consumption on telosb. I made some
tests and the normal energy consumption is 19,5 mA when radio interface
cc2420 is up, while when cc2420 is down the consumption is 0,125 mA.
How can i lower the max Value?
i try to set the power to the lowest level
You sure it's 1.1.1.3? I've only seen 3 numbers...like 1.1.3 or 1.1.13
If it's 1.1.3, I'd continue to upgrade to something over ..10 just for
your own sanity. But that has nothing to do with your CLASSPATH...
I think the warning is for '.' (period) not dash, unless there is some
unicode foo I
I just looked at the tmote specs and it shows a bit higher current
when _receiving_ (!!?), but in the range you have measured. Judicious
use of the radio is the issue, also look up Low Power Listening and
see if it is of any use.
MS
Leonardo wrote:
Hi Guys,
I have any problem with current
Currently TOSSIM only supports micaz. And there is no sensor support other
then a simple fake DemoSensorC.
Chad
On 11/7/07, Quan Yuan [EMAIL PROTECTED] wrote:
Hello,
I just tried to compile files under \tinyos-
2.x\apps\tests\mts300\PhotoTemp.
However, how could I connect PhotoTemp
The tmote Oscilloscope program strikes me as another of the expertly
obfuscated TOS demo apps that is nearly impossible to follow or
modify...IMHO.
I think the business end of the data collection/aggregation happens
in the tinyos-1.x/tos/lib/Oscope/OscopeM.nc file, and you may be
able to
Dear all,
for my project I need to work on the .c file generated from nc application.
And I need to call a function called, for example, as for the Oscilloscope
application:
result_t OscilloscopeM$Timer$fired(void)
{
..
}
first I cannot call it from another program. Even it is declared, the
Hi everybody!
I have downloaded tinyos 1.1.1.3 and when I run toscheck inorder to if there is
something wrong with the program, I get this answer
toscheck completed with errors:
WARNING: CLASSPATH may not include ´-´ that is, the symbol for the current
working directory. Please add ´-´ to
What should I use if I want to receives bytes of data from UART0 in Tmote
Sky?
Currently, I use tx() function. But I only got 1 byte of data which is the
last byte of data sent from my CmuCAM3.
Then I found a function UartStream and UartByte. Can they can be to solve my
problem?
What is the
Hello,
I just tried to compile files under \tinyos-2.x\apps\tests\mts300\PhotoTemp.
However, how could I connect PhotoTemp to TOSSIM in TinyOS 2? It seems that
make mica2 sim does not work.
Thank you.
Quan
___
Tinyos-help mailing list
Hi Mejda,
I'm also interested in using jennic chip mainly because of its long
communication range. I'm considering porting tinyos to the Jennic or
connecting jennic chip to crossbow mica family motes. But my concern is
that time synchronization accuracy may not be as good as that of other
Hi,
I am trying to implement the simulation of TinyOS applications in
TOSSIM. I changed to the directory 'xbow/apps/CntToLedsAndRfm', and
built a TOSSIM version of this application with /make pc/. I did make it
successfully at the first time. However, after I changed the parameter
in
Hi,
I need some help to modify the Oscilloscope application so that it reads
only the TSR sensor and not the entire set of sensors. I also need to have
one reading per packet sent. The current Oscilloscope application sends 10
readings per packet for the six sensors and this makes the
I just wanted to point out that after having some problems programming
telosb in the virtual machine I realized that it is necessary to install the
tinyos-tools package in the host system. I'm not pretty sure, but it seems
that the host system should detect the telosb device in order to make it
Hi!
If we try to compile a file with the command make pc to simulate it with
TOSSIM (tinyos1.x), it doesn't works..the output is:
Unknown target pc
Known targets for TinyOS directory /opt/MoteWorks/tos are:
iris m2100 m2110 m4100 m9100 mica mica2 mica2b mica2dot micaz micazb micazc
msp430 rcb230
Hi,
I am working on routing implementation in TinyOS. Although I found some
protocols in
TinyOS 1.x, yet I do not find many papers published in this field, compared
with simulations.
Can anyone refer some published papers in routing implementation?
Thank you very much.
Best Regards,
Tao Wu
Hello all ,
I just setup XubunTOS virtual machine with VMware on windows XP and
apparently have my working environment ok for working with TinyOS
I just want to know now if the USB interface with which to comunicate to
motes will be enabled with this setup and if I will be able to play around
Hi,
I have not yet tried time synchronization using jennic chip, but i'm planning
to do it.
With best Regards.
- Message d'origine
De : Tomonori Nagayama (長山 智則） [EMAIL PROTECTED]
À : mejda chouaieb [EMAIL PROTECTED]
Cc : Anton [EMAIL PROTECTED]; tinyos-help@Millennium.Berkeley.EDU
please search the mailing list with keyword RSSI, I did post some
related question about this.
To be brief, RSSI from the CC2420 chip tell you about the Noise ratio
surrounding, where RSSI value from the received packet tell you about
the quality of the wireless medium.
in your packet you
it looks like TinyOS 2.X is slightly better. :-)
regards;
Peizhao
Michael Schippling wrote:
The tmote Oscilloscope program strikes me as another of the expertly
obfuscated TOS demo apps that is nearly impossible to follow or
modify...IMHO.
I think the business end of the data
it is a common problem with the nesC binary. Make sure you have it
installed. please check on mailing list archive for more information.
regards;
Peizhao
汪付强 wrote:
tinyos forum：
hello！
When I compile blink code in tinyos, I got the error message that ncc is
not found:
mkdir -p
tinyos forum：
hello！
When I compile blink code in tinyos, I got the error message that ncc is not
found:
mkdir -p build/micaz
compiling Blink to a micaz binary
ncc -o build/micaz/main.exe -Os -finline-limit=10 -Wall -Wshadow
-DDEF_TOS_AM_GROUP=0x7d
-Wnesc-all -target=micaz
To achieve what you want to do in TinyOS. You just need to modify the
following for single reading per packet.
// Oscilloscope.h
typedef nx_struct oscilloscope {
nx_uint16_t version; /* Version of the interval. */
nx_uint16_t interval; /* Samping period. */
nx_uint16_t id; /* Mote id of
Dear All Tmote Sky Users;
Anyone has a backup of all moteiv support information from the web site?
As the sudden shutdown of MoteIV support web site, we lost all this
information. It will be really graceful to have a copy for future
reference. :-)
--
regards;
Peizhao
Just checking, did BasestationCC2240 get removed from 2.0.1 when updating to
2.0.2? I just installed 2.0.2 and that directory seemed to go away...
Kurt
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
if your PirC() from PirC.nc is correct for your PIR sensor, the
Oscilloscope application should run fine without any changes.
regards;
Peizhao
yvonne er wrote:
Hi everyone,
I am using TinyOS 2.x and MicaZ to acquire data readings from my
passive infra-red (PIR) sensor. I used this command
26 matches
Mail list logo
