the counter state coming out
of every atomic section to determine whether the clock fired while you were
in it. Does that scare you? It should. I recommend finding an alternative to
building a real time software clock.
Regards,
Ben Buckner
___
Tinyos
On Jun 15, 2007, at 4:16 PM, Ben Buckner wrote:
From: Ian Welch [EMAIL PROTECTED]
Subject: [Tinyos-help] Timer and Atomic Help
Hello,
I'm implementing a clock on my mote and it seems to drift, I
think the
issue is to to too many or too long atomic sections. I was
wondering
, counter driven 6
kHz ADC, and frequency measurement at the same time, so they can be fairly
flexible. Just remember to restore all the counter registers after you're
done with them.
See
http://www.avrfreaks.net/index.php?module=Freaks%20Devicesfunc=displayDevo
bjectid=55
For hardware details.
Ben
Hello all,
We are using mica2 and mts300 sensor boards and we have a problem using
functions like
memset and memcpy. We are using tinyos 2.x and we wanted to know is there
any way of doing that?Do we need to include a specific header file? Any
help will be much appreciated.
thanks in
Bill-
From the legendary Octavetech protocol document that you linked:
P_PACKET_ACK (0x41) - User packet. ACK required. Includes a prefix byte.
Receiver must send a P_ACK response with prefix byte as contents.
Regards,
Ben B.
Date: Mon, 23 Apr 2007 13:55:54 -0400
From: Bill Leal [EMAIL
Hi,
I have trouble sending msg from laptop (using c++) code to tmote. All the
code is at the bottom. I have no problem reading the data from the serial
but sending it back dooesn't seam to work. Anyone knows why? Thanks.
Indy
[...]
memcpy(output_buffer, msgOUT, sizeof(msgOUT));
Out
up the
framing logic, but you never know how logically the actual code has been
implemented.
Ben
-Original Message-
From: Michael Schippling [mailto:[EMAIL PROTECTED]
Sent: Monday, April 09, 2007 10:16 PM
To: Ben Buckner
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help
Yes. My mistake.
We would want to make sure the CRC bytes don't have the 7E or 7D bytes.
The
corrected procedure would be as here:
1. create the message packet including everything but the Sync bytes (7E)
2. run the CRC algorithm on the escaped data packet
3. attach the CRC in little
Date: Fri, 10 Nov 2006 12:04:26 +0100 (CET)
From: walid hamdi [EMAIL PROTECTED]
Subject: [Tinyos-help] Programmer is not responding!
Hello Tinyosians!
I was running the programming board perfectly, made
some modifications in the TOSBase application just to
send a message on the Radio.
As i
-Original Message-
Date: Tue, 31 Oct 2006 19:16:49 -0600
From: Leon Zhou [EMAIL PROTECTED]
Subject: [Tinyos-help] How to wake up a MICA2 sensor
To: tinyos-help@Millennium.Berkeley.EDU
Hi,
We're doing a temperature detection project with MICA2 and TinyOS.
In order to save power, our
Functions in NesC are still functions. You don't use call or post with
them, and you invoke them just like you do in C. To my knowledge, it doesn't
matter whether the functions are called in tasks or not. There are really
only two contexts in which code executes in NesC/TinyOS, which are tasks
for the framing bytes, 0x7E, which come at the beginning and the end of the
packet.
For details, see the often-referenced
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Pack
ets.pdf
Regards,
Ben Buckner
-Original Message-
Date: Wed, 18 Oct 2006 14:47:59 -0600
From
It depends on which communications components you're using, but if I had to
guess, I'd say you might have something wrong with the packet sequencing.
Some of the routing components/protocols (Bcast for instance) use a sequence
number to make sure copies of the same packet aren't received multiple
Jiggling or reconnecting the mote often fixes that - another thing to look
at is to make sure you don't have the mote power turned on when you program
it. That can be very bad. The serial port probably isn't the problem or the
programming would have failed much earlier in the process.
Hi Imanol.
The documentation for the protocol is
pretty sparse in general, but this link should be enough to get it done with
the appropriate amount of beating your head on the wall, http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf
Not sure Im
multiple times, much less expect it as a normal radio
reactivation procedure. Main-EWMAMultiHopRouter.StdControl, so as I
understand it, the Main init call should have already fanned out to the
multihop component's init() at boot.
Any comments, explanations, speculations?
Thanks,
Ben Buckner
16 matches
Mail list logo
