Is it possible to run multiple copies of TOSSIM (one for each application under test) connected to one serialforwarder so that they can talk to each other?
- Conor
On 11/8/06, walid hamdi [EMAIL PROTECTED] wrote:
This was my first problem at all!!:)This won´t be possible:-(Tossim runs a
If you'd like SerialForwarder (or any command, for that matter) to run in the background so that you can still use your command line, put an ampersand () at the end of the command. To bring it back to the foreground, type fg. If it's already running in the foreground and you don't want to stop it,
If the D2 light is the red one, then it probably means that your batteries are low. When the batteries on my Mica2 motes run low, the red light flashes and they act unreliably (read: unable to program them, and the radios work only sporadically).
- COn 10/25/06, Michael Schippling [EMAIL
Perhaps you need to pass different strings to unique() in order to get different values out of it? What I am implying is that all three of the timers you wire below may resolve to the same timer because you give them all the same name.
...not that I have any idea how unique() works, of course. -
Is the radio on? Has it had enough time to power up? Is it tuned correctly? Have you done the Truffle Shuffle?
- Conor
On 9/11/06, David Moss [EMAIL PROTECTED] wrote:
Still working with this problem -
I downloaded TinyOS 2.x beta2 to three computers now, and have tried compiling/installing
Unless you specifically enable interrupts inside of an atomic section (I'm not even sure why you'd want to do such a thing), then no interrupts will occur because they are disabled within atomic sections. - Conor
On 9/7/06, Adam [EMAIL PROTECTED] wrote:
Then, which is the case in TinyOS 1.x? From
Interrupts are disabled within async{} blocks. Therefore, no events can be fired, and nothing will happen except for what's in your async code (unless the batteries die or your mote falls into a pool of molten lava).
- ConorOn 9/6/06, Adam [EMAIL PROTECTED] wrote:
(1) Inside the tinyOS
No. The only way to break out of the async nature of interrupt handlers (and functions called by them) is to post a task, thus allowing the synchronous interrupt-handling call tree to terminate. - C
On 9/6/06, Adam [EMAIL PROTECTED] wrote:
It is a great question - I am looking at
I get this sometimes. Sometimes it's just low battery voltage, sometimes it has to do with Cygwin not being able to get full sense of the COM ports, and sometimes it's because there's a stale copy of UISP running in the background which needs to get killed.
- ConorOn 9/5/06, Neal Patwari [EMAIL
I completely agree with you on the lack of respect for documentation's role in software development. Much like in a math proof or a professional chef's recipe, many important steps and assumptions are not documented because it's assumed that whoever's looking at the code can understand it
You can think of squelch as earplugs for the radio. If you put earplugs in your ears, you're only going to be able to hear things that are fairly loud and/or fairly close to you. The bigger the earplug, the louder the sound must be for you to hear it. So, raising the squelch value on the radio
Holy moly, that's quite different than the CC1000 architecture for the Mica2 in TinyOS-1.1.15!I'm using the RadioReceiveCoordinator interface for the CC1000 in my app; can you give me any direction as to how I might switch from the standard CC1000 stack to the Rincon code?
- ConorOn 8/28/06,
The graphs are generated as part of the documentation, and can be found in GIF format in the nesdoc documentation directory. Additionally, the source code which describes the configuration and formatting of the graphs (in the 'dot' language) should be in the same directory. Documentation for dot
If I understand what you're doing correctly, then the problem may be in the book-keeping. If the RF channel is in use and your mote tries to send, that send is going to fail, and you're never going to get a RadioCoordinator event (because there is no sending going on). Therefore, your handler for
Perhaps if you use the QueuedReceive mechanism, you'll not loose as many packets? Or, if you really want to be sure you're getting the packets and you don't want to touch the radio stack, try using the RadioCoordinator interface, which allows you to be notified every time a byte is recieved.
-
Hi. I'm writing a bit of Java code to run on a PC connected to mote network. I'm currently using TinyOS-1.x, but at some point I'm sure I'll move to TinyOS-2.x. For my java code, should I connect to a Serial Forwarder to receive packets, or should I use MoteIF to connect directly?
The
Hi Alexandre. No worries about asking questions -- we're all novices at some point!
In TinyOS, a read from a sensor is generally split into two phases: the
request, and the read. You make the request for a reading from
your ADC (or whatever the sensor's connected to) and then go off and do
other
and modifications necessary for compilation of TinyOS code to Cricket binaries.It's based on Cricket v2.3.2 and contains modifications for speedups and extended documentation. The documentation is an ongoing project.
If anyone would like it, I'm happy to email it; just let me know you'd like a copy. - Conor
Are you able to use your serial port at all under Cygwin?I've found that using something like Hyperterminal to open and close the COM port under Windows before trying to use it in Cygwin clears up any problems.
As for USB-Serial adapters, I haven't had any luck with them. - ConorOn 7/18/06, raj
>From pages 13 14 of the ATMega128 manual, there are two types of interrupts: ones which are triggered and remain triggered until they are enabled and handled, and ones which only remain triggered as long as the trigger signal is present (and which may not actually have interrupt flags). I am
infamous ones in our group was the
something.o file not found in theC:\Windows\Temp directory.Did you have to change a lot to get it working?Sankar.On Thu, 13 Jul 2006 15:58:57 -0500, Conor Todd
[EMAIL PROTECTED]wrote: We're using Crickets too, and we have no problems with the tinyos
The documentation for TinyOS says that interrupts are DISABLED within atomic sections of code, such that no asynchronous will even occur, since asynchronous events are generated by interrupts. - Conor
On 7/12/06, jose m [EMAIL PROTECTED] wrote:
Hello,- The atomic sentence, DISABLE interrupts or
Sometimes, under WinXP, I have to use something like Hyperterminal to
initially open and close the COM port to which the MIB510 is attached
before programs under Cygwin can do it. It might just be my
laptop, though.
- ConorOn 7/10/06, Sankar Gorthi [EMAIL PROTECTED] wrote:
As you can see, the
to understand that there's a
variably-sized hunk of data on the end of an AM type?
Thanks very much!
- Conor Todd
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos
A suggestion and a question regarding David's post:
Suggestion: How about a community-maintained wiki on tinyos.net? Then,
as each of us acquires expertise in the various bits of TinyOS, we can
document it for others.
Question: What is a TEP? Googling for this term led to a variety of
25 matches
Mail list logo
