Hi.
I am running Tmote Sky (Msp430) with TinyOS 1.x.
I have two questions.
1. Can I use a Watchdog on this platform? If so, How. Moteiv's site is down
and cannot get any info.
2. When 2 nodes sends a package 'exactly' at the same time to the 3rd node,
the 3rd node seem to crash. I tried
Hi,
Is it possible to retreive the the 'signal' call to default event?
I have a following event implemented as:
default event void Core.sigEvent(uint8_t val)
{
...//DO STUFF
}
and I call it as a normal signal call
somefunction()
{
...
signal Core.sigEvent(val);
...
}
But, I don't get the
Hi,
I have a weird problem. I am running Tmote Sky with TinyOS 1.x app. I am
transmitting serial data with following function:
code
command result_t Comm.transmit(const COMM_Msg msg)
{
TOS_Msg tosMsg;
uint8_t* p;
//Valid msg type if sent by rfm?
if(msg.destAddr != COMM_SERIAL
(msg.type !=
Thanks for your answer lads.
I've checked the whole system and there is no duplicate of the file EASAP.nc.
When I remove the definition in EASAP.nc interface, the compiler complains
(naturally):
interface has no command or event named `findNode'.
And there is no definition in EASAPImp
I got it...
I forgot a simple thing:
includes EASAP;
at the top of the interface declaration of EASAP.nc.
Which led to, as you said Michael, the compiler to 'help' with declaring the
function because 'struct node' is unknown for the interface...
Thanks lads.
Inderjit
Hi, I have a small problem compiling my module.
I have an interface (EASAP.nc):
interface EASAP
{
...
command struct Node* findNode(uint8_t id);
...
}
And in my module ( EASAPM.nc)
{
...
command struct Slot* EASAPImp.findSlot(uint8_t slot)
{
...
}
...
Hi,
Is it possible to pass a preprocessor command from terminal i.e $make XXX
BASE. And in the code there are pre-processor definitions like:
#ifdef BASE
...
#endif
What I'm trying to do is that there are some different routines for a BASE
station and the other motes. BASE transmitts the
by adding
line-feeds or something...it should be raw I/O.
Hopefully you've seen the octavetech doc:
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf
MS
Inderjit Singh wrote:
Thanks Ben,
I tried something very simple:
1. I get the byte stream from usb sent from
by adding
line-feeds or something...it should be raw I/O.
Hopefully you've seen the octavetech doc:
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf
MS
Inderjit Singh wrote:
Thanks Ben,
I tried something very simple:
1. I get the byte stream from usb sent from
Thanks Ben,
I tried something very simple:
1. I get the byte stream from usb sent from the TMote like:
7e 42 xx xx xx xx 7e
2. I remove the 7e from the stream and send it back as it is (42 xx xx
xx xx). But I still don't get it. C/C++ should be able to handle this
no?
Is there any doc on
Do you mean I don't remove the 0x7e bytes on each end?
Inderjit
On 4/12/07, Ben Buckner [EMAIL PROTECTED] wrote:
Oh, you have to provide the framing structure with any packet you send to
the mote. The protocol doesn't change.
Ben
-Original Message-
From: Inderjit Singh [mailto
Thanks Ben,
I tried something very simple:
1. I get the byte stream from usb sent from the TMote like:
7e 42 xx xx xx xx 7e
2. I remove the 7e from the stream and send it back as it is (42 xx xx
xx xx). But I still don't get it. C/C++ should be able to handle this
no?
Is there any doc on
Hi,
I relatively new in TinyOS so please bare with me.
I am programming tmote sky with TinyOs 1.x. I loosing sent packet from the
computer in tmote while doing this:
-
CONFIGURATION:
configuration TDMAC
{
}
implementation
{
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
CODE :nesC and tinyOS
configuration TimeSync
{
}
implementation
{
Hi.
I'm trying to create a component as following:
THE INTEFACE:
interface TimeSync
{
command result_t synchronize(uint16_t time);
command uint16_t getTime();
command bool timeSet();
}
THE COMPONENT:
configuration TimeSyncC
{
provides interface TimeSync;
provides interface StdControl;
}
Sorry, my mistake. The interface is correct. It's was on the other component
that was lacking the uses interface. Sorry about that. A beginner's error I
presume.
Inderjit
On 4/10/07, Inderjit Singh [EMAIL PROTECTED] wrote:
Hi.
I'm trying to create a component as following:
THE INTEFACE
Hi,
Does anyone have a complete description on how and when the CRC should be
calculated when sent from the computer to tmote sensor using serial
(UARTComm) communication. I'm trying to write c/c++ code to 'inject data' to
the WSN but thre are a lot of confusion on how the crc and the data
Cheers,
tony
Inderjit Singh wrote:
Hi,
Does anyone have a complete description on how and when the CRC should
be calculated when sent from the computer to tmote sensor using serial
(UARTComm) communication. I'm trying to write c/c++ code to 'inject
data' to the WSN but thre are a lot
Sorry, my mistake. The interface is correct. It's was on the other component
that was lacking the uses interface. Sorry about that. A beginner's error I
presume.
Inderjit
On 4/10/07, Inderjit Singh [EMAIL PROTECTED] wrote:
Hi.
I'm trying to create a component as following:
THE INTEFACE
19 matches
Mail list logo
