Talk:TinyOS

Size

One useful bit of information would be the size of TinyOS. All the sites that I checked just say "a few kilobytes." How few? —The preceding unsigned comment was added by Guymacon (talk • contribs) 22:59, 9 June 2006 (UTC)

"Competing technologies"

I'm not sure who came up with the links under "competing technologies," but I don't think they're accurate at all. Protocols and technologies such as Zigbee, X10, WiFi, etc, don't compete with sensor node operating systems. The title of this list should either be changed to "assocated technologies," or modified to actually list other sensor node operating systems, such as SoS (http://nesl.ee.ucla.edu/projects/SOS/), FreeRTOS (http://www.freertos.org/), MantisOS (http://mantis.cs.colorado.edu), eCOS (http://ecos.sourceware.org/), etc. --John 21:01, 13 June 2006 (UTC)

Although this response is months later, I agree and have removed it after growing tired of its erroneous presence here. I am also working on a new look for that template that will hopefully be less spam-filled, but I'm still not interested in seeing it come back here. -- Omicronpersei8 (talk) 21:11, 16 September 2006 (UTC)

Scratch that, I just got the template deleted a little while back. -- Omicronpersei8 (talk) 16:53, 13 October 2006 (UTC)

Contradiction

The article claims that TinyOS is "mostly written in C", and also that it is "a set of NesC and some Java". This seems contradictory to me. Can someone with knowledge of TinyOS clarify? --Allan McInnes (talk) 01:00, 28 August 2006 (UTC)

nesC is a slightly sleeker and smaller version of the C language with fewer features. I'm not exactly sure about the details, but I would assume that the larger processes and anything having to do with graphics is probably thrown out of the nesC language. I do think that all of the code is in "filename.c" format, even if it is meant to be compiled using the nesC compiler. Again - the differences are small. ---- tholex

Actually, from what I've seen nesC is a totally different animal. Check out the "blink an LED" example application here: http://www.tinyos.net/tinyos-1.x/apps/Blink/ here's the main file / entry point: Blink.nc:

 configuration Blink
 {
 }
 implementation
 {
   components Main, BlinkM, SingleTimer, LedsC;
   Main.StdControl -> SingleTimer.StdControl;
   Main.StdControl -> BlinkM.StdControl;
   BlinkM.Timer -> SingleTimer.Timer;
   BlinkM.Leds -> LedsC;
 }

Take a look at the BlinkM.nc (which provides whatever BlinkM is in the above code, I suppose) file for some other examples of differences. -- Ledbettj 19:52, 15 September 2006 (UTC)

The mote code for TinyOS is indeed in nesC, which is not standard C. The mode code is really the main part of the suite, and it's the peripheral utilities included in TinyOS installations that are written in Java and scripting languages, so my vote is on replacing "C" with "nesC". -- Omicronpersei8 (talk) 19:37, 16 September 2006 (UTC)