Hi,Recently i upgraded TinyOS 1.0 to TinyOS 2.0 on windows. But i am getting an error when compiling Blink application for micaz platform. Compilation for Telosb platform works fine. tos-check-env executes without any error.
Following is the error message i get when compiling for micaz.$ make
Hi.When I try to compile a program with 'make pc' I get several errors, whereas if I type 'make tmote' the program compiles and runs OK. The errors I get are related to missing interfaces and components (e.g.: 'interface LocalTime not found'). I guess that it is because tmote associated Makefiles
hello everybody,
in my program idefined my own function as TOS_MsgPtr packet(TOS_MsgPtr msg);
after receiving a complete data packet from the radio,i called for the above function as packet(data) (where data is the received TOS_MsgPtr),.when i tried to compile this file i am get error as
Thanks for ur reply. I will test with this adapters.
On Fri, 22 Sep 2006 Giri Baleri wrote :
The couple of adapters that we have tested/used are:
VendorModel
Keyspan USA-19HS
Belkin F5U109
We have found that not all adapters work reliably with all PC makes and
operating systems.
I am implementing a MAC protocolusing Tinyos. The protocol has a few types of control packets andone type ofdata packet.
However, in current TinyOS 2.0, there is only one type of message_t (once the platform is determined), which has a fixed message structure and size (payload length is 28bytes).
I'm using TOSSIM to simulate 11 motes, and at one stage it seems that
some packets are being sent, but not received in the simulator. If I
turn on the PACKET debug mode, I can see that the bytes of the 'dropped'
packets are interleaved (both transmitting at the same time), but the
send() and
Dear all,
i had a look in the mail archives about the sleep mode for micaz, but it
is not so clear to me how to handle it.
I found that it is necessary to use the HPLPowerManagementM.nc interface, but
if you enable it, you cannot use the timers in your code if the node is in the
sleep
Hi,
I have problem when sending RF msg and continously talking to a digital
sensor conected to UART0. The problem is that I receive bad crc packets,
when transmiting, in a rate of 10%. If I disable de UART interrupts before
sending and then enabled once sendDone , no bad crc msg appear.
Does
Hi all
I need to do DMA based sampling so as to avoid loss
of data from three channels of accelerometer.I have been able to do DMA based
sampling for single channel but unable to do so for more than one
channel.
Can any body suggest how to do go about solving
this problem.
Regards
Raj
Or you can just declare it before you use it,
which is actually the usage shown in the question...
TOS_MsgPtr packet(TOS_MsgPtr msg);
func()
{
packet( msg );
}
TOS_MsgPtr packet(TOS_MsgPtr msg)
{
//stuff
return( msg );
}
Pablo Gil Montaño
Hi,
why does in mica2 the interrupt vectors numbers are 1 less than in the
Atmega128L.pdf datasheet. e.g. interrupt vector for SPI serial transfer
complete, listed as 18 in the datasheet, is declared as 17 in iom128.h
-Bill
___
Tinyos-help mailing
Hi, all
My question is if I want to use the Timer0 in Asynchronous mode to wake up
MCU, how to do that? I know I have to enable the “sei( );”, and set AS0
bit in ASSR (Asynchronous Status Register) the timer0 would run during
sleep. But how to implement Timer 0, and how to define the parameter
On 9/25/06, Сергей Кушнир [EMAIL PROTECTED] wrote:
Hello, David!
I'm sorry asking specifically you, I have wrote about my problem in
threads TinyOS-help TimyOS-devel, but didn't get any answer :(
In our research laboratory in Institute of Radio-Electronics of
Russian Academy of Science we
Hello,I see several posts talking about micaz. Anyway, tinyos 1.x (my version) doesn't support this mote. Does tinyos 2.x support it?José
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
Probalo ya!
On Sep 25, 2006, at 7:30 AM, Bryn Smith wrote:
I'm using TOSSIM to simulate 11 motes, and at one stage it seems that
some packets are being sent, but not received in the simulator. If I
turn on the PACKET debug mode, I can see that the bytes of the
'dropped'
packets are interleaved (both
On Sep 25, 2006, at 1:10 AM, Pablo Gil Montaño wrote:
Hi.
When I try to compile a program with 'make pc' I get several
errors, whereas if I type 'make tmote' the program compiles and
runs OK. The errors I get are related to missing interfaces and
components (e.g.: 'interface LocalTime
TOS 1.1.10 supports micaz.
MS
jose m wrote:
Hello,
I see several posts talking about micaz. Anyway, tinyos 1.x (my version)
doesn't support this mote. Does tinyos 2.x support it?
José
*Preguntá. Respondé. Descubrí.*
I would like to know how to use ACK in TOSSIM. I set ack field in Tos_Msg = 1, but I don't know how to detect whether or not sender receives ack.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
I'm not entirely certain that ACKs work in TOSSIM, like rssi
But in any case the TOS_Msg.ack field is output, not input.
It indicates whether and ACK was received, it doesn't enable them.
To use ACKS you need to call MacControl.enableAck() on the receiving
(or better, both) side, and make
On Sep 25, 2006, at 7:44 PM, Michael Schippling wrote:
I'm not entirely certain that ACKs work in TOSSIM, like rssi
ACKs work in TOSSIM. The default (TR1000) radio stack actually
emulates the ACK bit pattern, etc. I do not know about the CC1000
stack from Harvard or the CC2420 stack
Just wondering if the ACK functionality is also available with TOSSIM that comes with tinyos-1.1.15DecCVS?On 9/26/06, Philip Levis
[EMAIL PROTECTED] wrote:On Sep 25, 2006, at 7:44 PM, Michael Schippling wrote:
I'm not entirely certain that ACKs work in TOSSIM, like rssiACKs work in TOSSIM.
Hi Cory, This is with reference to the volcano monitoring paper of Matt Welsh and his team (mentioned below). In this paper, two problems have been mentioned with regards to FTSP. 1) The problem with the clock driver (apparently seen only on Tmotes) that seems
to return bogus timestamps. 2) FTSP
Hi, Dr. Levis and all,
In your written TEP116 - Packet Protocols, section 3, there is a word The Snoop interface does not assume always-on listening, for example, in the case of TDMA or RTS/CTS data link layer. This means that, although Tinyos has only one message_t structure, it bore in mind the
23 matches
Mail list logo
