Hi,
thanks for answering.
I am trying to test a few localization algorithms in Tossim (and
visualize them) and I thought that the new Tossim would be better for
this task, since it allows everything to be in the same process. But it
seems that it may be to early to do that in Tossim 2.x (at least for
me). But I found TinyViz and Tossim 1.x to be too slow and heavy.
What would be your oppinion? I was planning to implement the whole
thing in C++ and Qt.
ali
Philip Levis wrote:
On Dec 11, 2006, at 9:08 AM, A. Banani wrote:
Hi,
I am currently testing Tossim with TinyOs 2.x under Gentoo Linux as
described in the tutorial no. 11. I have written a small program
which uses the RadioCountToLeds object files and would like to
analyze the states of the leds.
I was now wondering if the debug messages are the only way to do that
or are there any other ways of checking the motes leds (or other
motes properties)?
One drawback of the C++ approach is that you can't (as easily) query
variables. In the case of the Leds, your nesC code can always call
Leds.get() and Leds.set(). From an output standpoint, the best way is
to use a dbg() statement indicating their state.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
