Common guys this is not the right way to ask help. Understand that if the
guys out there weren't helpful TINYOS wouldn't have made this far. Sometimes
people are busy with their own stuff. As we must know the people working on
TinyOS are working full time on their jobs too. Be patient and keeping
looking for your answers on the archives and I am sure most of the problems
what we face might have been answered before. So keep faith in this forum,be
patient and stop cribbing about your questions not being answered.
I apologize on behalf of all the TinyOS community to the great ppl out there
who help us.
Thanking You
MMA
On 09/06/07, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
Send Tinyos-help mailing list submissions to
tinyos-help@Millennium.Berkeley.EDU
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. syntax of LoggerRead.read () question (Gary Pan)
2. Documentation regarding exact contents of the MAC Protocol
Data Unit frame (Pedro Almeida)
3. Need help on receiving multiple messages in tinyos-2.x (Murtuza)
4. Generic Modules with Numeric Types? (J. Ryan Stinnett)
5. Funneling-MAC source code release (Gahng-Seop Ahn)
6. Re: Generic Modules with Numeric Types? (David Gay)
7. RE: [tinyos-1.x] No replies!! (Micfox Micfox)
----------------------------------------------------------------------
Message: 1
Date: Fri, 8 Jun 2007 12:16:27 -0700 (PDT)
From: Gary Pan <[EMAIL PROTECTED]>
Subject: [Tinyos-help] syntax of LoggerRead.read () question
To: TinyOS <tinyos-help@millennium.berkeley.edu>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hellow all.
I used the example from /SenseLightToLog/SimpleCmdMsg.nc line 116 and
tried to read log from EEPROM. But I am not sure if I use the correct syntax
and I got no result back.
Here is part of line 116 of SimpleCmdMsg.nc
call LoggerRead.readNext(((struct LogMsg *)log_msg.data)->log)
log_msg is defined as:
TOS_Msg log_msg
Besides, in file SimpleCmd.h the structure of LogMsg is defined as:
typedef struct LogMsg {
uint16_t sourceaddr;
uint8_t log[16];
} LogMsg;
In my application case, I make my own structure as follows:
typedef struct BodyMsg
{
uint16_t source;
uint16_t time;
uint16_t reading;
} BodyMsg;
typedef struct CmdMsg
{
int8_t action;
union {
BodyMsg body_msgs;
uint8_t log[6];
} Data;
} CmdMsg;
I want to point the read log data to the portion of log[6].
So I use the syntax like this:
TOS_Msg SendPkt;
call LoggerRead.read( cur_line, ((struct CmdMsg *)SendPkt.data)->
Data.log );
After that I send out the data read from log like this:
struct CmdMsg *Cmd_ptr;
Cmd_ptr = (struct CmdMsg *) SendPkt_ptr->data;
Cmd_ptr -> action = LOAD;
call SendLog.send( BASE_STATION, sizeof(struct CmdMsg), SendPkt_ptr );
But I did not get the logging data sent out. And I did not know if I
have read the data from EEPROM or not. I think I have stored the data to the
EEPROM correctly.
Can anyone point my out the mistake? Right now I am guessing
Gary
---------------------------------
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20070608/5cffa3de/attachment-0001.html
------------------------------
Message: 2
Date: Fri, 8 Jun 2007 20:21:28 +0100
From: "Pedro Almeida" <[EMAIL PROTECTED]>
Subject: [Tinyos-help] Documentation regarding exact contents of the
MAC Protocol Data Unit frame
To: tinyos-help@millennium.berkeley.edu
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hello;
I'm trying to look for documentation where I can understand the exact
contents, byte by byte, of the MPDU. I've looked into the TEPs and the
source files themselves, butI wasn't completely clear.
I'm using now the TestNetwork demo, where I receive 32 bytes per message,
of
which I know little about, except for the contents of the message_t
itself:
typedef nx_struct TestNetworkMsg {
nx_am_addr_t source;
nx_uint16_t seqno;
nx_am_addr_t parent;
nx_uint16_t metric;
nx_uint16_t data;
nx_uint8_t hopcount;
nx_uint16_t sendCount;
nx_uint16_t sendSuccessCount;
} TestNetworkMsg;
That are not, by far, 32 bytes.
So far I understood the MPDU is made of
2 bytes - Frame Control
1 byte - Data Sequence Number
4 to 20 bytes - Address Information
n bytes - Data Payload
2 bytes - Frame Check Sequence
which adds 5 bytes of the SHR and 1 byte of the PHR. So what exactly are
those 32 bytes??? Which ones are the payload (MSDU) and which ones are not
(and what are they?)?
An example of the 32 bytes is as follows:
7E 45 00 FF FF 00 00 13 00 EE 00 01 00 00 00 07 80 EE 00 07 00 80 00 00 00
00 20 00 00 53 63 7E
Help!
Thank you!!!
Pedro
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20070608/ad0b8e1f/attachment-0001.htm
------------------------------
Message: 3
Date: Fri, 8 Jun 2007 14:58:16 -0500
From: Murtuza <[EMAIL PROTECTED]>
Subject: [Tinyos-help] Need help on receiving multiple messages in
tinyos-2.x
To: tinyos-help@millennium.berkeley.edu,
[EMAIL PROTECTED]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hello friends,
I have 2 different questions.
1. I wanted to know how can I receive messages of different payload format
i.e the payload are of different sizes and structures from different motes
to a common mote. I have seen the code for BaseStation. It does a similar
thing. But the doubt which bogs me is the AM type of a message. Can anyone
tell me the meaning of AM type. I understand that different message types
have different AM types. And we can differentiate different message based
on
this. Two packets coming from different kinds of motes running different
applications can be distinguished using AM types. Am I right ? If I am
then
how can we make sure that the AM types are always distinct.
And if my concept of AM Type is entirely wrong then please do not curse
me
and tell me what it really means. I would be more than thankful if you do
so.
2. When i receive messages from motes to the base station I get a messages
that do not match the tinyos message_t structure. For example I ran a
simple
test in which the source mote sends its TOS_NODE_ID and a serial number of
the message over the radio. The TOS_NODE_ID of this node was 3. The
structure of the message payload was as shown below.
typedef nx_struct test{
nx_am_addr_t nodeid;
nx_uint16_t num;
}test;
I got this as the output displayed on my computer.
00 FF FF 00 03 04 22 06 00 03 00 01
00 FF FF 00 03 04 22 06 00 03 00 02
00 FF FF 00 03 04 22 06 00 03 00 03
The output of the BlinkToRadio application. But why is it that the output
sent by the motes is not according to the message_t structure.
typedef nx_struct cc1000_header {
nx_am_addr_t addr;
nx_uint8_t length;
nx_am_group_t group;
nx_am_id_t type;
} cc1000_header_t;
Why is it that there is always the TOS_NODE_ID inserted after the
destination ID. In the header the
first field is the destination address right. Then its the length. But
why is it that i always get
the source node ID.
Thanking You
MMA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20070608/357bcf4a/attachment-0001.html
------------------------------
Message: 4
Date: Fri, 08 Jun 2007 22:23:13 -0500
From: "J. Ryan Stinnett" <[EMAIL PROTECTED]>
Subject: [Tinyos-help] Generic Modules with Numeric Types?
To: tinyos-help@millennium.berkeley.edu
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I'm building several modules that act as wrappers around a data
structure, similar to the PoolC from T2 in tos/system. However, rather
than storing an array of an arbitrary types and working with pointers to
them as PoolC does, I'm only working with numeric types like uint8_t,
uint16_t, float, etc. My first plan was to make a single generic module
and use a typedef parameter to specify the type, like PoolC does.
However, I want to be able to use arithmetic operations within the
module. This results in compilation errors, which I'm assuming are
because a struct or other non-numeric type could be passed in for the
typedef parameter. At the same, all the information to evaluate whether
only numeric types are passed in is available at compile time. Is there
any way to make this work, or should I just make different modules for
each numeric type?
Thanks,
Ryan
------------------------------
Message: 5
Date: Fri, 08 Jun 2007 23:43:16 -0400
From: Gahng-Seop Ahn <[EMAIL PROTECTED]>
Subject: [Tinyos-help] Funneling-MAC source code release
To: tinyos-help@millennium.berkeley.edu
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
we are pleased to announce that the funneling-MAC TinyOS
source code is now available at:
http://www.cs.dartmouth.edu/~sensorlab/funneling-mac/
The funneling-MAC is a localized and sink-oriented MAC
capable of mitigating the funneling effect and boosting
application fidelity in sensor networks. The technical paper
has been presented at SenSys 2006.
The funneling-MAC web page also includes publications
and other documentation.
Best regards,
Gahng-Seop Ahn
Emiliano Miluzzo
Andrew Campbell
------------------------------
Message: 6
Date: Fri, 8 Jun 2007 21:59:02 -0700
From: "David Gay" <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] Generic Modules with Numeric Types?
To: "J. Ryan Stinnett" <[EMAIL PROTECTED]>
Cc: tinyos-help@millennium.berkeley.edu
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>From the nesC documentation (somewhat hidden in /usr/share/ncc/doc,
admittedly):
It is also possible to declare, using the special @integer() and @number()
attributes, that a type parameter is of an integral (respectively
numerical)
type. In that case, all the operations allowed on integers (respectively,
integers and floating-point numbers) are allowed:
generic module Sort(typedef t @number()) { }
implementation {
...
void f() {
t x1, x2;
...
if (x1 < x2)
...
}
David Gay
------------------------------
Message: 7
Date: Sat, 09 Jun 2007 00:59:46 -0400
From: "Micfox Micfox" <[EMAIL PROTECTED]>
Subject: RE: [Tinyos-help] [tinyos-1.x] No replies!!
To: [EMAIL PROTECTED], tinyos-help@Millennium.Berkeley.EDU
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=gb2312; format=flowed
Yes, I totally agreed with you. I also have at least 4 questions not
answered at all!!! In some way, I preferred the situation that the
mailing
list can be more responsive instead of the tinyos being open-source!!!
>From: "Vipin Kashyap" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: tinyos-help@Millennium.Berkeley.EDU
>Subject: [Tinyos-help] [tinyos-1.x] No replies!!
>Date: Fri, 8 Jun 2007 23:32:54 +0530 (IST)
>
>Hi !
>
>It is very disappointing that my last three posts, one of them posted as
>early as 04 Jun, have evoked no response.
>
>Firstly, the documentation available on the subject is, to say the least,
>very basic and at best hovers around demo apps like blink and
>senselighttolog/rfm etc. There is hardly any help available on sampling
>analog adc channels for obtaining data from external sensors other than
>those on-board mica2/z. It would be really nice if at least one such
>sample app could be part of the tinyos/apps dir.
>
>Since the whole tinyos project is open-source effort, I did expect the
>documentation to be a weak link. But I expected that at least the mailing
>lists would be frequented by the project core team to come to the rescue
>of
>newbie developers.
>
>Open-source or not, one must appreciate that in today's world, we all
work
>against deadlines, whether professionals or students. And at a time when
>we are racing against time, the lack of support can be quite distressing.
>
>I sincerely hope that those concerned will take note and make the
>tinyos-help list more responsive. I also hope that I am not antagonising
>anyone by saying what i just did.
>
>Thanks & Regards,
>
>--
>Vipin Kashyap
>
>
>_______________________________________________
>Tinyos-help mailing list
>Tinyos-help@Millennium.Berkeley.EDU
>https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
------------------------------
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
End of Tinyos-help Digest, Vol 50, Issue 58
*******************************************
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
