Thanks, Omprakash - that was what I was looking for. Another few lines
fixed the missing group ID:
task uartSendTask() {
[...init variables...]
am_group_t group;
[...read RadioAMPacket fields...]
group = call RadioAMPacket.group(msg);
[...write UartAMPacket source address...]
call UartAMPacket.setGroup(msg, group);
[...call UartSend...]
Problem solved. Thanks.
Andreas
On 21/01/2008, at 13:44, Omprakash Gnawali wrote:
I committed a change to the BaseStation that makes it copy the source
field from the radio to the serial packet. Is that what you wanted?
- om_p
On Jan 21, 2008 2:33 AM, Andreas Reinhardt
<[EMAIL PROTECTED]> wrote:
When I run BaseStation on telosB motes, it outputs a blank group
field
and a sender address equal to the byte swapped version of the
destination address value. However, I might try and see whether I can
combine the benefits of both.
Andreas
On 21/01/2008, at 10:05, Kevin Klues wrote:
Is there some limitation in the already existing tinyos-2.x/apps/
BaseStation ?
Kevin
On Jan 20, 2008 11:59 PM, Andreas Reinhardt
<[EMAIL PROTECTED]> wrote:
I was considering implementing a transparent gateway mote that
would
simply forward all packets received on the radio to the USB port.
Like
a T2 version of TOSbase. As I want to maintain the serial packet
format, instead of operating on raw byte data, I was looking for a
way
to keep all header fields intact. Or is there another simple way to
instantiate 256 instances of AMSend?
Andreas
On 15/01/2008, at 16:08, Kevin Klues wrote:
Can I ask why you are trying to dynamically change the value of
the AM
type at runtime via this interface? The traditional way to
"change"
the AM type is to include multiple instances of
SerialAMSenderC() in
your configuration, each instantiated with a different AM type.
When
you want to send a message with a particular AM type, you choose
the
proper instance of the AMSend interface provided by one of these
components.
I'm not sure exactly why what you were trying to do originally
wouldn't work in theory, but I suspect it has something to do with
not
using the proper components in your configuration.
Kevin
On Jan 15, 2008 1:53 AM, Andreas Reinhardt
<[EMAIL PROTECTED]> wrote:
Hi,
Using tmotes on tinyos-2.x, I am looking for a solution to
manually
set the AMtype field of an AMPacket that I send out over the
serial
port. When I set it using the AMPacket.setType(..) method prior
to
calling AMSend.send(), it seems it is always reset by
SerialActiveMessageP.nc. But even if I uncomment line 63 in the
AMSend.send() method of that file, things don't change:
// [... ]header->group = TOS_AM_GROUP;
//header->type = id; // Commented out
header->length = len; [...]
However, if I enter any arbitrary number here (such as: header-
type =
4;), it appears correctly in the data stream over the serial
port.
How
can that be - browsing the source code doesn't show up any other
methods handling the packet in the meantime.
Any other solutions are appreciated.
Thanks,
Andreas
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
~Kevin
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
~Kevin
_______________________________________________
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
