[Tinyos-help] micaz voltage increasing when battery droop

2011-05-24 Thread srsini srsini
Hello,
i try to compute the remaining power in the battry in micaz !! but each time i 
do the test i find that the power is increasing . that's strange , i don't 
understand the matter. PLZ any idea could help.
i use this 

#
 */
module VoltageP
{
  provides interface Atm128AdcConfig;
}
implementation
{
  async command uint8_t Atm128AdcConfig.getChannel()
  {
// select the 1.23V (V_BG). Reference: Table 97, page 244 from the Atmega128
return ATM128_ADC_SNGL_1_23;
  }

  async command uint8_t Atm128AdcConfig.getRefVoltage()
  {
return ATM128_ADC_VREF_OFF;
  }

  async command uint8_t Atm128AdcConfig.getPrescaler()
  {
return ATM128_ADC_PRESCALE;
  }
}
#

Bye___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] MICA 2 Help!!

2011-05-24 Thread fabrice fothe
  Hi every body,
  I'm working on Mica2 for my Bachelor thesis.I have the original node for sending and receiving i also have one Sniffer (MIB 520) like Base Station.My supervisor make a new component MICA2 using the piece from The Crossbow Technology. Now my job it to make the driver of this new component using NESC. There is some one who can tell me the mains steps to follow to write a driver of the MICA2??Thank a lot for responding!!! ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] make micaz sim:problem for Blink app

2011-05-24 Thread vinod kumar
I am working over windows using cygwin.I hve installed everything for
tinyOS.I have checked for python even.It might be because of path settings.
when I type:
make micaz sim
for the Blink app,
Its running to some extent and then showing:
tos-ident-flags:not found
make:python-configure- 2.3 :Command not found
make:ncc:Command not found
make:*** [sim-exe]error 127

---
but I have checked for the presence of python by typing puthon -V on
cygwin prompt
It gave :python 2.3.4
as result
please help me out and if u can give me contacts of people who are also
working over the same thing as I am on an internship.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] DAC on Telosb

2011-05-24 Thread C L
Hello

Has anybody managed to get the DAC working on TelosB?

Or, any experience with this code from David Moss in tinyos-2.x-contrib:
http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x-contrib/rincon/tos/chips/msp430/dac12/

I tried the code - no success.

CL
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] blip/telosb question

2011-05-24 Thread daniele mattiacci
Hi all,
i'm using 2 motes with blip installed:1 works like IPbasestation and he's
attached to the PC, 1 has TCPEcho application running and he's attached to
my PC.
I'm try to develop an application in Java that send IPv6 packet to a mote.I
see by console that IPBaseStation doesn't discarded the packets send by me,
but by telnet console (telnet localhost 6106) i can see that IPBAseStation
doesn't forward my IPv6 packets to a mote with address fec0::2(the
destination in the address is well setted).So what's wrong with my
application?why IPBAsestation doesn't forward the packets in the subnet at
the right mote?

Any help will be appreciate.
Thank you in advance
Daniele.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] blip/telosb question

2011-05-24 Thread daniele mattiacci
I explain better my problem if could help anybody in the answer:
I have done an application that read from a serial port USB0 in ubuntu 10.4,
where there's attached IPBaseStaion the output without do nothing is this:
Stable Library
=
Native lib Version = RXTX-2.1-7
Java lib Version   = RXTX-2.1-7
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
Packet:126
Packet:126
Packet:67
Packet:56
Packet:126
Packet:126
Packet:67 13
Packet:126
Packet:126
Packet:126
Packet:11
Packet:126
Packet:126
Packet:3
Packet:96
Packet:126
Packet:35
Packet:67 36
Packet:38

I read in the class PACKETIZER (support/sdk/java/net/tinyos/packet) this
comment:
To summarise the protocol:
   * - the two sides (A  B) are connected by a (potentially
   *   unreliable) byte stream
   *
   * - the two sides exchange packets framed by 0x7e (SYNC_BYTE) bytes
   *
   * - each packet has the form
   * packet type data bytes 1..n 16-bit crc
   *   where the crc (see net.tinyos.util.Crc) covers the packet type
   *   and bytes 1..n
   *
   * - bytes can be escaped by preceding them with 0x7d and their
   *   value xored with 0x20; 0x7d and 0x7e bytes must be escaped,
   *   0x00 - 0x1f and 0x80-0x9f may be optionally escaped
   *
   * - There are currently 5 packet types:
   *   P_PACKET_NO_ACK: A user-packet, with no ack required
   *   P_PACKET_ACK: A user-packet with a prefix byte, ack
   *   required. The receiver must send a P_ACK packet with the
   *   prefix byte as its contents.
   *   P_ACK: ack for a previous P_PACKET_ACK packet
   *   P_UNKNOWN: unknown packet type received. On reception of an
   *   unknown packet type, the receicer must send a P_UNKNOWN packet,
   *   the first byte must be the unknown packet type.
   *
   * - Packets that are greater than a (private) MTU are silently
   *   dropped.

It means that i can discard this packet?Because i would like to know if
there's a manner to read the IPv6 packet sended by the tun0 interface.I'm
really confused.Thanks for any help,
Daniele.


2011/5/24 daniele mattiacci d.mat...@gmail.com

 Hi all,
 i'm using 2 motes with blip installed:1 works like IPbasestation and he's
 attached to the PC, 1 has TCPEcho application running and he's attached to
 my PC.
 I'm try to develop an application in Java that send IPv6 packet to a mote.I
 see by console that IPBaseStation doesn't discarded the packets send by me,
 but by telnet console (telnet localhost 6106) i can see that IPBAseStation
 doesn't forward my IPv6 packets to a mote with address fec0::2(the
 destination in the address is well setted).So what's wrong with my
 application?why IPBAsestation doesn't forward the packets in the subnet at
 the right mote?

 Any help will be appreciate.
 Thank you in advance
 Daniele.

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Microsecond Timestamping

2011-05-24 Thread Janos Sallai
Sean:

Look at how the wiring is done in the test app in
apps/tests/rfxlink/TestPacketTimeSync. TimeSyncMessageC and
ActiveMessageC provide multiple PacketTimeStamp interfaces,
PacketTimeStampRadio (TMicro precision on the telos/micaz) and
PacketTimeStampMilli (TMilli precision). You'll need to wire the
former.

Janos

On Tue, May 24, 2011 at 12:37 AM, Xiaowei seanwill...@gmail.com wrote:
 Dear Janos,

 Thank you very much for your reply! By the way, if you remember, you
 actually gave me the same clue several weeks ago! It's so frustrating that I
 still haven't figured it out.

 I looked into TestPacketTimeSync, you are using PacketTimeStamp.timestamp to
 get the time when packets are sent and received, is that right?
 So I tried to use interface PacketTimeStamp in my app just like you  did in
 TestPacketTimeSync by:

 adding App.PacketTimeStamp-ActiveMessageC; in my configuration file,
 adding uses interface PacketTimeStampTMicro, uint16_t; in module file,
 and call the timestamp command like this
     if (call PacketTimeStamp.isValid(msg)==TRUE){
                 sendtime = call PacketTimeStamp.timestamp(msg);
 When I compile the code, it says no match for the wiring
 App.PacketTimeStamp-ActiveMessageC.
 In your Packet timestamping TEP written with Miklos, you mentioned it does
 not prescribe how packet timestamping should be implemented: it only
 describes the interfaces and the required functionality. Feel like I'm not
 using PacketTimeStamp interface in the correct way.

 Then I tried to use your CC2420XActiveMessageC by downloading the
 trunk/cc2420x folder, put it under my tos/chips folder, and in the
 configuration wire App.PacketTimeStamp-CC2420XActiveMessageC. Got the
 compile error cannot find `CC2420XActiveMessageC'.

 I'm using CounterTMicro, uint16_t to record time of microsecond presicion,
 and disabled csma  by setting the default value of ccaOn = TRUE to ccaOn
 = FALSE in tinyos-2.1.0/tos/chips/cc2420/csma/CC2420CsmaP.nc. The rest I'm
 trying to do is to record the actual time when packets are transmitted(when
 the first bit hits the air, or at least as close to the moment as possible)
 and received. Can this be achieved in tinyos 2.1.0 with telosb mote in an
 easy, light-weighted way?

 Really appreciate your time of looking into this!

 Sean

 On Sun, May 22, 2011 at 12:11 AM, Janos Sallai sal...@isis.vanderbilt.edu
 wrote:

 Sean:

 The default cc2420 radio stack doesn't support TMicro timestamping.
 There's an alternative implementation, however, which does. Take a
 look at apps/tests/rfxlink/TestPacketTimeSync. The readme file
 explains how to compile for the telos. You'll need the latest sources
 from google code.

 For your convenience, here's a direct link to the readme file.

 http://code.google.com/p/tinyos-main/source/browse/trunk/apps/tests/rfxlink/TestPacketTimeSync/README.txt?spec=svn5544r=5544

 Janos

 On Sat, May 21, 2011 at 7:14 PM, Xiaowei seanwill...@gmail.com wrote:
  Hi all,
 
  I'm doing some experiment to record the exact time when packets start
  transmission at the sending mote and being received at the receiving
  mote
  with telosb motes in TinyOS 2.1.0.
  These are the components and interface I'm using:
  components Msp430CounterMicroC;
  App.Counter - Msp430CounterMicroC
  uses interface CounterTMicro, uint16_t;
 
  To get rid of random delay, I also disabled csma by setting:
  the default value of ccaOn = TRUE to ccaOn = FALSE in
  tinyos-2.1.0/tos/chips/cc2420/csma/CC2420CsmaP.nc
 
  At the sending mote, I called Counter.get() in sendDone event handler,
  and
  at the receiving mote I called Counter.get() in receive event handler.
  It
  seems that the time recorded is not the exact time when the packet is
  sent
  over the air.
 
  So I tried to use interface PacketTimeStampTMicro, uint16_t, but got
  the
  no match error for the line App.PacketTimeStamp-ActiveMessageC when
  compiling the code, couldn't figure out why. Tried include message.h in
  module file, didn't work.
 
  There's also another interface RadioTimeStamping that provides event
  transmittedSFD and receivedSFD, which satisfies my requirement. But it's
  said that RadioTimeStamping is not supported in TinyOS 2.1. I tried to
  use
  it by wire 'App.RadioTimeStamping-CC2420TransmitC.TimeStamp', got
  compile
  error cannot find TimeStamp.
 
  I have been stuck in this problem for a while, anyone knows how to do
  this
  (Basically, get the time when packets actually being transmitted to the
  air
  and being received)?
 
  Any help is greatly appreciated.
 
  Sean
 
 
 
  ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 



___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] DAC on TelosB

2011-05-24 Thread Sandip Bapat
I have indeed managed to get the DAC to work on the TelosB. I will send you 
some 
test code via a separate email. 


Sandip

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] micaz voltage increasing when battery droop

2011-05-24 Thread Michael Schippling
As I understand it, the mica platforms measure battery voltage
by taking a reading from a fixed 1.23v chip. Since the ADC
reference (full-scale-value) _is_ the battery itself, the
reading from the chip will _increase_ as the battery droops.

You may be seeing this effect, but I thought the Voltage
components for each platform handled this in their read
methods and also converted the result to milli-volts.

MS

srsini srsini wrote:
 Hello,
 i try to compute the remaining power in the battry in micaz !! but each 
 time i do the test i find that the power is increasing . that's strange 
 , i don't understand the matter. PLZ any idea could help.
 i use this 
 
 #
  */
 module VoltageP
 {
   provides interface Atm128AdcConfig;
 }
 implementation
 {
   async command uint8_t Atm128AdcConfig.getChannel()
   {
 // select the 1.23V (V_BG). Reference: Table 97, page 244 from the 
 Atmega128
 return ATM128_ADC_SNGL_1_23;
   }
 
   async command uint8_t Atm128AdcConfig.getRefVoltage()
   {
 return ATM128_ADC_VREF_OFF;
   }
 
   async command uint8_t Atm128AdcConfig.getPrescaler()
   {
 return ATM128_ADC_PRESCALE;
   }
 }
 #
 
 Bye
 
 
 
 
 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Parsing Serial Messages

2011-05-24 Thread Saif Ahmad
How can I parse the data I read through the serial port as all of it is in
hex?
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] using 6lowpan on telosb tprca2400ca trp2410ca

2011-05-24 Thread daniele mattiacci
Hi all,
i'm using 2 motes with blip installed:1 works like IPbasestation and he's
attached to the PC, 1 has TCPEcho application running and he's attached to
my PC.
I'm try to develop an application in Java that send IPv6 packet to a mote.I
see by console that IPBaseStation doesn't discarded the packets send by me,
but by telnet console (telnet localhost 6106) i can see that IPBAseStation
doesn't forward my IPv6 packets to a mote with address fec0::2(the
destination in the address is well setted).So what's wrong with my
application?why IPBAsestation doesn't forward the packets in the subnet at
the right mote?

Any help will be appreciate.
Thank you in advance
Daniele.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] using 6lowpan on telosb tprca2400ca trp2410ca

2011-05-24 Thread daniele mattiacci
I explain better my problem if could help anybody in the answer:
I have done an application that read from a serial port USB0 in ubuntu 10.4,
where there's attached IPBaseStaion the output without do nothing is this:
Stable Library
=
Native lib Version = RXTX-2.1-7
Java lib Version   = RXTX-2.1-7
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
Packet:126
Packet:126
Packet:67
Packet:56
Packet:126
Packet:126
Packet:67 13
Packet:126
Packet:126
Packet:126
Packet:11
Packet:126
Packet:126
Packet:3
Packet:96
Packet:126
Packet:35
Packet:67 36
Packet:38

I read in the class PACKETIZER (support/sdk/java/net/tinyos/packet) this
comment:
To summarise the protocol:
   * - the two sides (A  B) are connected by a (potentially
   *   unreliable) byte stream
   *
   * - the two sides exchange packets framed by 0x7e (SYNC_BYTE) bytes
   *
   * - each packet has the form
   * packet type data bytes 1..n 16-bit crc
   *   where the crc (see net.tinyos.util.Crc) covers the packet type
   *   and bytes 1..n
   *
   * - bytes can be escaped by preceding them with 0x7d and their
   *   value xored with 0x20; 0x7d and 0x7e bytes must be escaped,
   *   0x00 - 0x1f and 0x80-0x9f may be optionally escaped
   *
   * - There are currently 5 packet types:
   *   P_PACKET_NO_ACK: A user-packet, with no ack required
   *   P_PACKET_ACK: A user-packet with a prefix byte, ack
   *   required. The receiver must send a P_ACK packet with the
   *   prefix byte as its contents.
   *   P_ACK: ack for a previous P_PACKET_ACK packet
   *   P_UNKNOWN: unknown packet type received. On reception of an
   *   unknown packet type, the receicer must send a P_UNKNOWN packet,
   *   the first byte must be the unknown packet type.
   *
   * - Packets that are greater than a (private) MTU are silently
   *   dropped.

It means that i can discard this packet?Because i would like to know if
there's a manner to read the IPv6 packet sended by the tun0 interface.I'm
really confused.Thanks for any help,
Daniele.
2011/5/24 daniele mattiacci d.mat...@gmail.com

 Hi all,
 i'm using 2 motes with blip installed:1 works like IPbasestation and he's
 attached to the PC, 1 has TCPEcho application running and he's attached to
 my PC.
 I'm try to develop an application in Java that send IPv6 packet to a mote.I
 see by console that IPBaseStation doesn't discarded the packets send by me,
 but by telnet console (telnet localhost 6106) i can see that IPBAseStation
 doesn't forward my IPv6 packets to a mote with address fec0::2(the
 destination in the address is well setted).So what's wrong with my
 application?why IPBAsestation doesn't forward the packets in the subnet at
 the right mote?

 Any help will be appreciate.
 Thank you in advance
 Daniele.



___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Microsecond Timestamping

2011-05-24 Thread Xiaowei
Hi Janos,

To test your apps/tests/rfxlink/TestPacketTimeSync, I downloaded the whole
folder TestPacketTimeSync to my directory /opt/tinyos-2.1.0/apps, and
cc2420x to /opt/tinyos-2.1.0/tos/chips. When I compile TestPacketTimeSync,
there's always error like no match, cannot find***. Is it supposed to be
used like this, or I'm doing it in a wrong way?

In fact, what I need to do is to get microsecond timestamp for packet
transmission and reception, I'm trying to do in in the following way:
download cc2420x from google code, put it under
/opt/tinyos-2.1.0/tos/chips,
add App.PacketTimeStamp-CC2420XActiveMessageC to my configuration,
add uses interface PacketTimeStampTRadio, uint32_t  to my module,
then call PacketTimeStamp.timestamp() to get microsecond timestamp value.
Any file else I have to bring in or modify?

Thanks a lot..

Sean

By the way, I'm using tinyos 2.1.0, is there any easy and feasible way to do
microsecond timestamping in other versions?

Sean

On Tue, May 24, 2011 at 3:28 PM, Xiaowei seanwill...@gmail.com wrote:

 Hi Janos,

 I tried to use CC2420TransmitC.ByteIndicator and
 C2420ReceiveC.PacketIndicator to determine the start of transmission and
 reception of a packet, didn't work.

 Then I write the following to my sender telosb mote,
   async event void CaptureSFD.captured( uint16_t time ){
 sendtime = call Counter.get();
   }

 will Counter.get() record the time when packets actually start being
 transmitted?
 I tried this out, but the result is not so good. I'm not sure whether it's
 because this doesn't work as I expected at all or it's some other reason.

 Thank you for your reply!

 Sean


 On Tue, May 24, 2011 at 11:15 AM, Janos Sallai sal...@isis.vanderbilt.edu
  wrote:

 Sean:

 Look at how the wiring is done in the test app in
 apps/tests/rfxlink/TestPacketTimeSync. TimeSyncMessageC and
 ActiveMessageC provide multiple PacketTimeStamp interfaces,
 PacketTimeStampRadio (TMicro precision on the telos/micaz) and
 PacketTimeStampMilli (TMilli precision). You'll need to wire the
 former.

 Janos

 On Tue, May 24, 2011 at 12:37 AM, Xiaowei seanwill...@gmail.com wrote:
  Dear Janos,
 
  Thank you very much for your reply! By the way, if you remember, you
  actually gave me the same clue several weeks ago! It's so frustrating
 that I
  still haven't figured it out.
 
  I looked into TestPacketTimeSync, you are using
 PacketTimeStamp.timestamp to
  get the time when packets are sent and received, is that right?
  So I tried to use interface PacketTimeStamp in my app just like you  did
 in
  TestPacketTimeSync by:
 
  adding App.PacketTimeStamp-ActiveMessageC; in my configuration file,
  adding uses interface PacketTimeStampTMicro, uint16_t; in module
 file,
  and call the timestamp command like this
  if (call PacketTimeStamp.isValid(msg)==TRUE){
  sendtime = call PacketTimeStamp.timestamp(msg);
  When I compile the code, it says no match for the wiring
  App.PacketTimeStamp-ActiveMessageC.
  In your Packet timestamping TEP written with Miklos, you mentioned it
 does
  not prescribe how packet timestamping should be implemented: it only
  describes the interfaces and the required functionality. Feel like I'm
 not
  using PacketTimeStamp interface in the correct way.
 
  Then I tried to use your CC2420XActiveMessageC by downloading the
  trunk/cc2420x folder, put it under my tos/chips folder, and in the
  configuration wire App.PacketTimeStamp-CC2420XActiveMessageC. Got the
  compile error cannot find `CC2420XActiveMessageC'.
 
  I'm using CounterTMicro, uint16_t to record time of microsecond
 presicion,
  and disabled csma  by setting the default value of ccaOn = TRUE to
 ccaOn
  = FALSE in tinyos-2.1.0/tos/chips/cc2420/csma/CC2420CsmaP.nc. The rest
 I'm
  trying to do is to record the actual time when packets are
 transmitted(when
  the first bit hits the air, or at least as close to the moment as
 possible)
  and received. Can this be achieved in tinyos 2.1.0 with telosb mote in
 an
  easy, light-weighted way?
 
  Really appreciate your time of looking into this!
 
  Sean
 
  On Sun, May 22, 2011 at 12:11 AM, Janos Sallai 
 sal...@isis.vanderbilt.edu
  wrote:
 
  Sean:
 
  The default cc2420 radio stack doesn't support TMicro timestamping.
  There's an alternative implementation, however, which does. Take a
  look at apps/tests/rfxlink/TestPacketTimeSync. The readme file
  explains how to compile for the telos. You'll need the latest sources
  from google code.
 
  For your convenience, here's a direct link to the readme file.
 
 
 http://code.google.com/p/tinyos-main/source/browse/trunk/apps/tests/rfxlink/TestPacketTimeSync/README.txt?spec=svn5544r=5544
 
  Janos
 
  On Sat, May 21, 2011 at 7:14 PM, Xiaowei seanwill...@gmail.com
 wrote:
   Hi all,
  
   I'm doing some experiment to record the exact time when packets start
   transmission at the sending mote and being received at the receiving
   mote
   with telosb motes in TinyOS 2.1.0.
   These are the 

[Tinyos-help] blip/telosb problem

2011-05-24 Thread daniele mattiacci
Hi all,
i'm using 2 motes with blip installed:1 works like IPbasestation and he's
attached to the PC, 1 has TCPEcho application running and he's attached to
my PC.
I'm try to develop an application in Java that send IPv6 packet to a mote.I
see by console that IPBaseStation doesn't discarded the packets send by me,
but by telnet console (telnet localhost 6106) i can see that IPBAseStation
doesn't forward my IPv6 packets to a mote with address fec0::2(the
destination in the address is well setted).So what's wrong with my
application?why IPBAsestation doesn't forward the packets in the subnet at
the right mote?

Any help will be appreciate.
Thank you in advance
Daniele.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Urgent: Display Mote Data

2011-05-24 Thread daniele mattiacci
hi all,
apologize if i write here but i think i have some problem, i send an email
to the tinyos-help, but the email doesn't return on my email address, does
anyone receive my request called blip/telosb question?

2011/5/23 Saif Ahmad saif...@gmail.com

 How can I display communication messages and data exchanged between nodes
 and BS using tinyos 2.1.1 on my Laptop.

 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] [tinyos-help]Problem with make micaz

2011-05-24 Thread Vamsidhar Addanki
hi there

when i type make micaz in my ubuntu vmware player, i receive a huge list of 
errors. I do not face such problems with make telosb.
I use tinyos 2.1.1.
please help me out
 
.
.
.
.
.
In file included from /opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:12,
 from /opt/tinyos-2.1.1/tos/platforms/mica/PlatformC.nc:47,
 from /opt/tinyos-2.1.1/tos/system/MainC.nc:50,
 from BlinkAppC.nc:45:
In C file:
/opt/tinyos-2.1.1/tos/system/scale.h:13: syntax error before `scale32'
/opt/tinyos-2.1.1/tos/system/scale.h:16: syntax error before `x_mod_b'
/opt/tinyos-2.1.1/tos/system/scale.h:18: syntax error before `*='
In file included from /opt/tinyos-2.1.1/tos/platforms/mica/PlatformC.nc:47,
 from /opt/tinyos-2.1.1/tos/system/MainC.nc:50,
 from BlinkAppC.nc:45:
In component `MeasureClockC':
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:39: syntax error before 
`cycles'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:41: syntax error before 
`Init'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:48: syntax error before 
`start'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:51: warning: type 
defaults to `int' in declaration of `TCCR1B'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:51: `CS10' undeclared 
here (not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:51: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:52: warning: type 
defaults to `int' in declaration of `ASSR'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:52: `AS0' undeclared here 
(not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:52: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:53: warning: type 
defaults to `int' in declaration of `TCCR0'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:53: `CS01' undeclared 
here (not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:53: `CS00' undeclared 
here (not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:53: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:58: warning: type 
defaults to `int' in declaration of `start'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:58: `TCNT1' undeclared 
here (not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:58: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:59: syntax error before 
`for'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:59: warning: type 
defaults to `int' in declaration of `wraps'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:59: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:59: syntax error before 
`)'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:65: warning: type 
defaults to `int' in declaration of `start'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:65: redefinition of 
`start'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:58: previous declaration 
of `start'
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:65: `next' undeclared 
here (not in a function)
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:65: warning: data 
definition has no type or storage class
/opt/tinyos-2.1.1/tos/platforms/mica/MeasureClockC.nc:69: syntax error before 
`now'
MeasureClockC: `Init.error_t' not implemented
MeasureClockC: `Atm128Calibrate.uint32_t' not implemented
MeasureClockC: `Atm128Calibrate.uint32_t' not implemented
MeasureClockC: `Atm128Calibrate.uint8_t' not implemented
MeasureClockC: `Atm128Calibrate.uint16_t' not implemented
MeasureClockC: `Atm128Calibrate.uint16_t' not implemented
In component `PlatformC':
/opt/tinyos-2.1.1/tos/platforms/mica/PlatformC.nc:45: `Atm128Calibrate' not 
connected
In file included from /opt/tinyos-2.1.1/tos/system/MainC.nc:50,
 from BlinkAppC.nc:45:
In component `RealMainP':
/opt/tinyos-2.1.1/tos/system/RealMainP.nc: In function `main':
/opt/tinyos-2.1.1/tos/system/RealMainP.nc:68: interface has no command or event 
named `init'
/opt/tinyos-2.1.1/tos/system/RealMainP.nc:69: interface has no command or event 
named `runNextTask'
/opt/tinyos-2.1.1/tos/system/RealMainP.nc:75: interface has no command or event 
named `init'
/opt/tinyos-2.1.1/tos/system/RealMainP.nc:76: interface has no command or event 
named `runNextTask'
/opt/tinyos-2.1.1/tos/system/RealMainP.nc: At top level:
/opt/tinyos-2.1.1/tos/system/RealMainP.nc:93: syntax error before `PlatformInit'
In file included from BlinkC.nc:41,
 from BlinkAppC.nc:45:
In interface `Timer':
/opt/tinyos-2.1.1/tos/lib/timer/Timer.nc:53: syntax error before `dt'
/opt/tinyos-2.1.1/tos/lib/timer/Timer.nc:62: syntax error before `dt'

Re: [Tinyos-help] Urgent: Display Mote Data

2011-05-24 Thread Michael Schippling
Yup. I seen both messages...

For communication examples, look at the Listen and Oscilloscope
Java programs, and search for the MIG message generator doc.

MS

daniele mattiacci wrote:
 hi all, 
 apologize if i write here but i think i have some problem, i send an 
 email to the tinyos-help, but the email doesn't return on my email 
 address, does anyone receive my request called blip/telosb question?
 
 2011/5/23 Saif Ahmad saif...@gmail.com mailto:saif...@gmail.com
 
 How can I display communication messages and data exchanged between
 nodes and BS using tinyos 2.1.1 on my Laptop.
 
 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 mailto:Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 
 
 
 
 
 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Microsecond Timestamping

2011-05-24 Thread Janos Sallai
Sean:

You'll need to grab the _whole_ tinyos-2.x tree from google code.
Updating only _some_ directories will not work. Once you have the
latest tree, follow the instructions in the README file.

Janos

On Tue, May 24, 2011 at 11:31 PM, Xiaowei seanwill...@gmail.com wrote:
 Hi Janos,

 To test your apps/tests/rfxlink/TestPacketTimeSync, I downloaded the whole
 folder TestPacketTimeSync to my directory /opt/tinyos-2.1.0/apps, and
 cc2420x to /opt/tinyos-2.1.0/tos/chips. When I compile TestPacketTimeSync,
 there's always error like no match, cannot find***. Is it supposed to be
 used like this, or I'm doing it in a wrong way?

 In fact, what I need to do is to get microsecond timestamp for packet
 transmission and reception, I'm trying to do in in the following way:
 download cc2420x from google code, put it under
 /opt/tinyos-2.1.0/tos/chips,
 add App.PacketTimeStamp-CC2420XActiveMessageC to my configuration,
 add uses interface PacketTimeStampTRadio, uint32_t  to my module,
 then call PacketTimeStamp.timestamp() to get microsecond timestamp value.
 Any file else I have to bring in or modify?

 Thanks a lot..

 Sean

 By the way, I'm using tinyos 2.1.0, is there any easy and feasible way to do
 microsecond timestamping in other versions?

 Sean

 On Tue, May 24, 2011 at 3:28 PM, Xiaowei seanwill...@gmail.com wrote:

 Hi Janos,

 I tried to use CC2420TransmitC.ByteIndicator and
 C2420ReceiveC.PacketIndicator to determine the start of transmission and
 reception of a packet, didn't work.

 Then I write the following to my sender telosb mote,
   async event void CaptureSFD.captured( uint16_t time ){
     sendtime = call Counter.get();
   }

 will Counter.get() record the time when packets actually start being
 transmitted?
 I tried this out, but the result is not so good. I'm not sure whether it's
 because this doesn't work as I expected at all or it's some other reason.

 Thank you for your reply!

 Sean

 On Tue, May 24, 2011 at 11:15 AM, Janos Sallai
 sal...@isis.vanderbilt.edu wrote:

 Sean:

 Look at how the wiring is done in the test app in
 apps/tests/rfxlink/TestPacketTimeSync. TimeSyncMessageC and
 ActiveMessageC provide multiple PacketTimeStamp interfaces,
 PacketTimeStampRadio (TMicro precision on the telos/micaz) and
 PacketTimeStampMilli (TMilli precision). You'll need to wire the
 former.

 Janos

 On Tue, May 24, 2011 at 12:37 AM, Xiaowei seanwill...@gmail.com wrote:
  Dear Janos,
 
  Thank you very much for your reply! By the way, if you remember, you
  actually gave me the same clue several weeks ago! It's so frustrating
  that I
  still haven't figured it out.
 
  I looked into TestPacketTimeSync, you are using
  PacketTimeStamp.timestamp to
  get the time when packets are sent and received, is that right?
  So I tried to use interface PacketTimeStamp in my app just like you
  did in
  TestPacketTimeSync by:
 
  adding App.PacketTimeStamp-ActiveMessageC; in my configuration file,
  adding uses interface PacketTimeStampTMicro, uint16_t; in module
  file,
  and call the timestamp command like this
      if (call PacketTimeStamp.isValid(msg)==TRUE){
                  sendtime = call PacketTimeStamp.timestamp(msg);
  When I compile the code, it says no match for the wiring
  App.PacketTimeStamp-ActiveMessageC.
  In your Packet timestamping TEP written with Miklos, you mentioned it
  does
  not prescribe how packet timestamping should be implemented: it only
  describes the interfaces and the required functionality. Feel like I'm
  not
  using PacketTimeStamp interface in the correct way.
 
  Then I tried to use your CC2420XActiveMessageC by downloading the
  trunk/cc2420x folder, put it under my tos/chips folder, and in the
  configuration wire App.PacketTimeStamp-CC2420XActiveMessageC. Got the
  compile error cannot find `CC2420XActiveMessageC'.
 
  I'm using CounterTMicro, uint16_t to record time of microsecond
  presicion,
  and disabled csma  by setting the default value of ccaOn = TRUE to
  ccaOn
  = FALSE in tinyos-2.1.0/tos/chips/cc2420/csma/CC2420CsmaP.nc. The rest
  I'm
  trying to do is to record the actual time when packets are
  transmitted(when
  the first bit hits the air, or at least as close to the moment as
  possible)
  and received. Can this be achieved in tinyos 2.1.0 with telosb mote in
  an
  easy, light-weighted way?
 
  Really appreciate your time of looking into this!
 
  Sean
 
  On Sun, May 22, 2011 at 12:11 AM, Janos Sallai
  sal...@isis.vanderbilt.edu
  wrote:
 
  Sean:
 
  The default cc2420 radio stack doesn't support TMicro timestamping.
  There's an alternative implementation, however, which does. Take a
  look at apps/tests/rfxlink/TestPacketTimeSync. The readme file
  explains how to compile for the telos. You'll need the latest sources
  from google code.
 
  For your convenience, here's a direct link to the readme file.
 
 
  http://code.google.com/p/tinyos-main/source/browse/trunk/apps/tests/rfxlink/TestPacketTimeSync/README.txt?spec=svn5544r=5544
 

[Tinyos-help] Packet structure telosb and tmotesky

2011-05-24 Thread Jorge R. Beingolea G.
hi...
I am using TmoteSky and Telosb with Oscilloscope aplication and need
your help ...

i have o next frame:

00 FF FF 00 07 1C 00 93 00 00 01 00 00 07 00 B8 0E 27 0E 28 0E 28 0E 28 
0E 28 0E 28 0E 28 0E 28 0E 28 0E 23

and I do not have the description of the fields of the frame, it
happens that I want to make the translation of the frame with one
another application, however, this necessary to know the structure of
the frame...

you can help me?

thanks

Jorge

-- 
MSc. Jorge Rodolfo Beingolea G.
Pervasive and High Performance Computing Group
Laboratory of Integrated Systems - LSI
Polytechnic School of the University of Sao Paulo - Brazil
Telf: 00 55 11 3091- 9741  Fax: 00 55 11 3091- 5665
Celu: 00 55 11 7155- 3685

Esta mensagem é destinada exclusivamente ao seu destinatário e pode conter 
informações confidenciais, protegidas por sigilo profissional ou cuja 
divulgação seja proibida por lei. O uso não autorizado de tais informações é 
proibido e está sujeito às penalidades cabíveis.

This message is intended exclusively for its addressee and may contain 
information that is confidential and protected by a professional privilege or 
whose disclosure is prohibited by law. Unauthorized use of such information is 
prohibited and subject to applicable penalties.

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Urgent: Display Mote Data

2011-05-24 Thread daniele mattiacci
thank you and sorry again

2011/5/25 Michael Schippling sc...@santafe.edu

 Yup. I seen both messages...

 For communication examples, look at the Listen and Oscilloscope
 Java programs, and search for the MIG message generator doc.

 MS

 daniele mattiacci wrote:

 hi all, apologize if i write here but i think i have some problem, i send
 an email to the tinyos-help, but the email doesn't return on my email
 address, does anyone receive my request called blip/telosb question?

 2011/5/23 Saif Ahmad saif...@gmail.com mailto:saif...@gmail.com


How can I display communication messages and data exchanged between
nodes and BS using tinyos 2.1.1 on my Laptop.

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
mailto:Tinyos-help@millennium.berkeley.edu


 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



 


 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] micaz voltage increasing when battery droop

2011-05-24 Thread 崔晓宗
Battery Voltage. The returned value represents the difference
 * between the battery voltage and V_BG (1.23V). The formula to convert
 * it to mV is: 1223 * 1024 / value.


2011/5/25 Michael Schippling sc...@santafe.edu

 As I understand it, the mica platforms measure battery voltage
 by taking a reading from a fixed 1.23v chip. Since the ADC
 reference (full-scale-value) _is_ the battery itself, the
 reading from the chip will _increase_ as the battery droops.

 You may be seeing this effect, but I thought the Voltage
 components for each platform handled this in their read
 methods and also converted the result to milli-volts.

 MS

 srsini srsini wrote:
  Hello,
  i try to compute the remaining power in the battry in micaz !! but each
  time i do the test i find that the power is increasing . that's strange
  , i don't understand the matter. PLZ any idea could help.
  i use this
 
  #
   */
  module VoltageP
  {
provides interface Atm128AdcConfig;
  }
  implementation
  {
async command uint8_t Atm128AdcConfig.getChannel()
{
  // select the 1.23V (V_BG). Reference: Table 97, page 244 from the
  Atmega128
  return ATM128_ADC_SNGL_1_23;
}
 
async command uint8_t Atm128AdcConfig.getRefVoltage()
{
  return ATM128_ADC_VREF_OFF;
}
 
async command uint8_t Atm128AdcConfig.getPrescaler()
{
  return ATM128_ADC_PRESCALE;
}
  }
  #
 
  Bye
 
 
  
 
  ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 ___
 Tinyos-help mailing list
 Tinyos-help@millennium.berkeley.edu
 https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




-- 
Regards,
Xiaozong Cui
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help