How do you compare NesCT + TinyOS 1.x with TinyOS 2.0 + TOSSIM ?
I know that TinyOS 2.0 is around for a while, but i really did not look into it. My latest information about TOSSIM includes the addition of a scripting language written in Python. You can trace the variables during simulation runtime with this feature. Luckily, OMNeT++ already has this feature. We don’t need to worry about this. TinyOS 2.0 also brings multiple instantiation of a single component. Suppose you have a nesC file with some implementation. Just like the relationship between a class and object, you can have multiple copies of same nesC component in memory.