Hi Philip,
I am currently working on a IEEE 802.15.4/Zigbee implementation.
The part finished so far is the MAC layer.
I interface to AMPromiscuous at the moment and changed some minor things
like the DSN handling in CC2420RadioM.
The biggest part was/is the message-struct TOS_Msg that I inflated to
meet all aspects of the 802.15.4-header and the ACK handling.
This is one of the major parts where Tinyos-1.x lacks.
As I understand it TinyOS wants to be compatible with 802.15.4.
But the truth is that only a very narrow part of the 802.15.4 standard
is supported.
But since I am not using any existing modules that I would have to
restructure and only some state machines and queues I would not have big
problems switching to Tinyos-2.x, right?
For me there are 3 issues:
- I don't want to work with something that's for sure a lot worse than
1.1.14 at the moment.
- I don't want to restructure my code to meet tinyos-2.x and just to do
the same after 1 month again because something major changed.
- TOSSIM should be working at at a similar state as the CC2420-beta in
1.1.14
Martin
Philip Levis wrote:
On Fri, 2006-02-10 at 18:58 +0100, Martin Gercke wrote:
Is there any rule based on which you could suggest who might look into
switching to 2.0 yet and who could have a look but should probably wait
because it's too soon?
For instance concerning the different platforms: mica2, micaz, telosb ...
and maybe concerning something like module-related, specific things ...
can't think of anything but probably there are some things that are
known to be not really "stable" or fixed in design yet so that switching
is not really recommended for now or the near future.
If you want to build on top of a bunch of existing 1.x services (e.g.,
collection, dissemination, time synch, localization), then switching to
2.x is probably not a good idea. While most of those services are going
to appear for 2.x eventually, they aren't there yet.
The only major part of 2.x that's expected to change soon is the
decomposition of the MSP430 USART, so that it can better support
resource arbitration. I also suspect that I'm going to tweak TOSSIM a
bit, but this will mostly involve adding some additional functionality
than changing current abstractions.
Basically, if you want to build systems starting at the HIL level
(sending packets, timers, sampling sensors), then I'd recommend moving
to 2.x. It will make your life a lot easier. If you want to build
systems that touch hardware specific functionality (e.g., crypto on the
CC2420, a new sensor board), then I'd recommend moving to 2.x. If you
would rather use a bunch of existing services (understanding that you'll
probably have to spend a good deal of time getting them to work
together), then I'd stick with 1.x for now.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
