Hi, I was asking about TelosB with TinyOS 2.0. Thanks.
On Dec 20, 2007 12:30 AM, Avinash Sridharan [EMAIL PROTECTED]
wrote:
Could be you be more specific about the platform and the version of TinyOS
you are using ?
-Avinash
On Dec 18, 2007 8:23 PM, Tie Luo [EMAIL PROTECTED] wrote:
Dear
Dear All,
Is the current MAC protocol in TinyOS B-MAC or X-MAC? I searched on
tinyos.net and it seems to be B-MAC. I just want to confirm. Thanks.
--
Regards,
Tie
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
Hi, I saw that there are 2.0 release, 2.0 beta2, 2.0 prerelease2, and
2.0devel-Branch. So what is the latest version?
To update to the latest version, which 'module-name' should I specify in the
CVS command? Thanks alot!
--
Tie
___
Tinyos-help
] wrote:
On Nov 21, 2006, at 5:54 AM, Tie Luo wrote:
Dear All,
If component A signals an event, and component B (which uses an
interface implemented by A) defines an event handler as follows:
async event void interfaceA.eventName(...) {} //void body
Another component C users interfaceA
PacketAcknowledgments.requestAck() enables acknowledgement.
But as a caveat, even if the ack is enabled and error==SUCCESS, it does not
guarantee the message has been sent to receiver. After the transmitter
sends out the message it will wait for a period of ACK_WAIT (some constant
defined like
For CC2420, ifAUTOCRC is set, will the hardware reject CRC-error packet automatically?
If true, thenis it possible to receive those packets but with AUTOCRC still being set? Because we do not want to generate CRC using software.Many thanks to comments.
-- Regards,Tie
If this is really a bug, where should be modified in Tinyos 2?
On 11/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,I tried to use the inputdivider function to set the prescaler for thetimer and it didnt work. I check the implementation and I believe I should
be change fromasync command
I work on real motes and thus did not use tossim.
But I guess tossim can simulate interference since it use a SNR model while it does not simulate collision, which is rather difficult.Tie
On 11/10/06, Yinying Yang [EMAIL PROTECTED] wrote:
Hi,
Does collision or interfere happens in TOSSIM?
Should not happen somewhere goes wrong :p
p.s. I am using T2; there is no TOS_Msg.
On 11/10/06, Lei Tang [EMAIL PROTECTED] wrote:
Hi, everyoneI'm working with MICAz now to mark received packet with a timestamp. This
posting of Joe suggested the TOS_Msg.time could be used for this purpose.
Levis [EMAIL PROTECTED] wrote:
On Nov 10, 2006, at 5:17 AM, Tie Luo wrote: I work on real motes and thus did not use tossim.
But I guess tossim can simulate interference since it use a SNR model while it does not simulate collision, which is rather difficult.TOSSIM in TinyOS 1.x and in T2 both simulate
tell me more about how to use it? Or give me a document I can look through?Sorry for bothering you again.Thank you.
Lei
On 11/10/06, Tie Luo [EMAIL PROTECTED] wrote:
Are you going to get the time when the msg being sent, or the time that you received it?
For the former, you can use metadata
always occur at the start symbol and thus prevent reception?
Regards,
Tie
On 11/11/06, Philip Levis [EMAIL PROTECTED] wrote:
On Nov 10, 2006, at 7:14 PM, Tie Luo wrote: Thank you for your clarification. I think to detect collision in reality becomes difficult, since
both collisions and channel error
We are using micaz motes with T2. Since we may set intervals as small as 1 ms, we are concerned about the timer accuracy.
We read TEP and knew that timer0 uses external crystal and has the best accuracy, does the millisecond timer component use timer 0 rather than 1-3? If not, how to use
Hello, what is the relationship between the return value of CCA.get() andSTXONCCA.strobe()?
Thanks.
On 11/9/06, Philip Levis [EMAIL PROTECTED] wrote:
On Nov 8, 2006, at 11:50 AM, Avinash Sridharan wrote: Hi All,I wanted to know as to what is the duration of sensing when using
CC2420 when the
Hello, a quick question. What is the return value of STXON.strobe() if radio is currently receiving a message?
The CC2420 datasheet says that it causes radio to enter TX state and can send, but seen from my experiments it does not.
Rgds,
Tie
On 11/6/06, Tie Luo [EMAIL PROTECTED] wrote:
Thank you
Hi,
According to CC2420 datasheet, the 127 byte packet size limit does not count in the PHY header, therefore the max payload length should be 127 - 10 (MAC header, excluding length field) - 2 (MAC footer) = 115 bytes,
i.e. TOSH_DATA_LENGTH can be definedto be115.
Dr. Levis, could you confirm? -
Shouldn't there be another 2 bytes for MAC footer? So should the limit be 109 bytes?
BTW, want to confirm whether the 6 bytes physical layerheader is counted in the 127 bytes.
Thanks,
Tie
On 10/22/06, Raghu Ganti [EMAIL PROTECTED] wrote:
Yes, on the MicaZ, it is limited by 127, the headers are 16
micaz and telosb use CC2420 as their transceiver, and in cc2420 data sheet the data rate is said to be 250kbps.
I did a measurement and found the rate was much lower; less than 150kbps.
Who else also did such measurements? Would like to hear your results.
p.s. the accuracy of timer is also
are first checking first that the radio was not
transmitting, and then checking if the command strobe cause the radioto begin transmitting.--Jonathan W. Hui[EMAIL PROTECTED]
http://www.cs.berkeley.edu/~jwhui/On 11/4/06, Tie Luo [EMAIL PROTECTED] wrote: I have been confused for a long time. Can
Thanks MIchael.
I have read your experiment report. According to my experiments, I got much less msg loss and lower delay. But I modified the lower-layer tinyos code a bit. I did not do rigorous tests and not record the data. There are still two parameters that our experiments cannot give good
I found a checkpoint report ofUC Berkeley EECS150 2006 which says the following:
After changing the frequency programmed in the FSCTRL configuration register, described above, it is necessary to issue the SRFOFF command strobe.
If this is not done, channel changing will not always work.
Is it
I have been confused for a long time. Can anybody help?
T2: CC2420TransmitP.nc void attemptSend():
1 status = m_cca ? call STXONCCA.strobe() : call STXON.strobe();
2 if ( !( status CC2420_STATUS_TX_ACTIVE ) ) {
3 status = call SNOP.strobe();
4 if ( status CC2420_STATUS_TX_ACTIVE )
CC2420Transmit.send() is to send without CCA, but it still backoff if channel is congested.
Is itfeasible to send immediately regardless of channel status?
platform: micaz, T2
Thanks a lot.-- Regards,Tie
___
Tinyos-help mailing list
Hi,
I think motes will power up and down automatically to save energy, and I have two questions:
1) How to disable this function?
2) Will all variables be re-initialzed when a mote is powered down and later up by itself?
platform: micaz, T2
Many thanks.-- Regards,Tie
and thus TX is still not active?
On 11/2/06, Philip Levis [EMAIL PROTECTED] wrote:
On Nov 1, 2006, at 1:35 AM, Tie Luo wrote: Line 6: if congestion is true, even m_cca==false can enter
S_SAMPLE_CCA state, which is wrong.Why is this wrong? If it's congested, continue sampling for a clearchannel. Line
Hi, in T2, there are some codes like the following:
#ifdef PLATFORM_MICAZ
#endif
However, I searched in all files under tos/ directory and did not found the definition of this macro.
Does the nesC compiler dynamically define this macro during compilation?
Thanks.
-- Regards,Tie
I am confused by the following code in CC2420TransmitP.nc (T2):
void attemptSend() {
bool congestion = TRUE;
...
1 status = m_cca ? call STXONCCA.strobe() : call STXON.strobe();2 if ( !( status CC2420_STATUS_TX_ACTIVE ) ) {3 status = call SNOP.strobe();4 if ( status CC2420_STATUS_TX_ACTIVE )
synchronous ACKs.
Tie
On 10/28/06, Philip Levis [EMAIL PROTECTED] wrote:
On Oct 27, 2006, at 10:13 PM, Tie Luo wrote: Dear all, I am using AMSnoopingReceiverC, but the node seems only receive
message destined to the node itself, and cannot receive messages for others. I saw in CC2420ActiveMessageC.nc
From the last email it appears that CC2420 does provide snooping functionality, doesn't it?
If unfortunately, itdoes not, then how tosnoop on micaz? Synchronous ACK is not necessaryto us.
Really need help. Thanks a lot.
Tie
On 10/28/06, Tie Luo [EMAIL PROTECTED] wrote:
Thanks
CC2420 is not able to snoop? And, I indeed do not needsynchronous ACKs. Tie On 10/28/06, Philip Levis
[EMAIL PROTECTED] wrote: On Oct 27, 2006, at 10:13 PM, Tie Luo wrote: Dear all,
I am using AMSnoopingReceiverC, but the node seems only receivemessage destined to the node
way would be to delete this line, butreally there should be an interface to do so (if there is not already).
Again, the CC2420 datasheet is very helpful, and is located at:http://www.chipcon.com/files/CC2420_Data_Sheet_1_4.pdf- Ryan Stinnett
Tie Luo wrote: By looking at the source code, I found
Dear all,
I am using AMSnoopingReceiverC, but the node seems only receive message destined to the node itself, and cannot receive messages for others.
I saw in CC2420ActiveMessageC.nc there is a comment:
Note that snooping may not work, due to CC2420 early packet rejection if acknowledgements are
if (callCC2420Config.sync()==SUCCESS) var=1;
and in RadioConfig.syncDone(error_t err)I reset var=2 regardless of the value of err.
However,sometimes the var is always 1,even if Icheckvar periodically.
This shows syncDone may not be called. Is that a bug? I recall previously a similar bug
Many thanks to David for your excellent inputs.
According towhat you said as quoted below:
Using the MacControl or CsmaControl interfaces, you can completely disable CCA (clear channel assessment). This will make your motes transmit as fast as possible, but requires one mote to secure the channel
is receiving/transmitting packets. Which
not releasing resource bug are you referring to?Are you using the SPI bus for anything else? E.g., large storageoperations?PhilOn Oct 25, 2006, at 2:11 AM, Tie Luo wrote: if (call
CC2420Config.sync()==SUCCESS) var=1; and in RadioConfig.syncDone(error_t err) I
a millisecond of TXACTIVE.
Hope that clears things up,
-David
-Original Message-From: Tie Luo [mailto:
[EMAIL PROTECTED]] Sent: Wednesday, October 25, 2006 7:09 AMTo: David MossCc:
tinyos-help@millennium.berkeley.eduSubject: Re: [Tinyos-help] CSMA-CA on CC2420micaz
Many thanks to David for your
Embedded below.
On 10/26/06, Philip Levis [EMAIL PROTECTED] wrote:
On Oct 25, 2006, at 9:32 AM, Tie Luo wrote: If radio is busy, I think CC2420Config.sync will fail, or may
return SUCCESS and signal syncDone at some time later. I do not understand what you said if sync were to never signal done
net.tinyos.message.SerialPacket temp.listener.messageReceived
(msg.get_header_dest(), received); ^
On 10/23/06, Tie Luo [EMAIL PROTECTED] wrote:
After update the whole tinyos 2.x in October, using the develop branch, the apps/BaseStation does not work. In particular, using a Java program to open
alot.
On 10/23/06, Philip Levis [EMAIL PROTECTED] wrote:
On Oct 22, 2006, at 8:23 PM, Tie Luo wrote: After update the whole tinyos 2.x in October, using the develop
branch, the apps/BaseStation does not work. In particular, using a Java program to open and write a message to the BaseStation via serial
When using apps/BaseStation to communicate with tools/Listen.java, Listen.java prints '/dev/ttyS0:57600 - bad packet'
What is the simplest wayto fix the problem incurred by the updated serial protocol?
On 10/23/06, Tie Luo [EMAIL PROTECTED] wrote:
Please ignore my previous email on Java program
Hi, TEP 113 was last modified on 2006-06-14, but my tinyos July version works. Only after I updated from the lastest develop branch version, Java program does not communicate with motes via serial port.
On 10/23/06, Philip Levis [EMAIL PROTECTED] wrote:
On Oct 22, 2006, at 8:23 PM, Tie Luo wrote
. :(
On 10/23/06, KANG HUI [EMAIL PROTECTED] wrote:
Hi, Tie,I met the same problem. Say, for Osciscope, I can get the messagesuccessfully, but Listen.java
prints 'bad packet.'Can you receive the message?HuiOn Mon, 23 Oct 2006, Tie Luo wrote: When using apps/BaseStation to communicate with tools
:
On Oct 23, 2006, at 7:26 AM, Tie Luo wrote: Hi, TEP 113 was last modified on 2006-06-14, but my tinyos July
version works.Only after I updated from the lastest develop branch version, Java program does not communicate with motes via serial port.There was recently some work on the mica serial stack
After update the whole tinyos 2.x in October, using the develop branch, the apps/BaseStation does not work. In particular, using a Java program to open and write a message to the BaseStation via serial port will return error. While the same code can run on the previous version of tinyos.
I have
Yes the problem is sendDone does not get called.
I also found the latest version has fixed this bug, but when I update using CVS I could not get the lastet file; the files got downloaded are still in July.Then I specified 'tinyos-2_0_devel-BRANCH' as modulename in
cvs -z3 -d:pserver:[EMAIL
platform: micaz, tinyos 2.x (Revision: 1.1.2.22)
I have updated to the latest TInyosdelevelop branch. Although some bug on switching channels was fixed (release resource after sync()), there are still problems.
A mote can send message after switching to a new channel, but the other mote cannot
1. What is the channel switch latency of CC2420?
2. Are the channels orthogonal to each other?
Thanks in advance!-- Regards,Tie
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
I uses CC2420Config.setChannel(16) and then CC2420Config.sync(), but it does not work. What are possible reasons? How long will it take for micaz to switch channels? Thanks!
Tie
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
In 802.15.4, the frame format is defined as:| PHY preamble | SFD | length | MAC_header | MAC_payload | MAC_footer
Therefore the previous three (or two) fieldsseem toform the PHY header.
But in tinyos 2.x there is:
async command error_t PhySend.send(message_t* msg, uint8_t len) {
... //
Tie Luo sent was specific to telos motesoh well...MSJay Taneja wrote:
I know that the Telos/Tmote implementations generally use 28 byte payloads because the 16-bit micro has some difficulties dealing with odd bytelength fields. The Mica family, on the other hand, has 8-bit
micros. I am not quite
/opt/tinyos-2.x/tos/types/message.h:7:#define TOSH_DATA_LENGTH 28/opt/tinyos-2.x/tos/chips/cc2420/CC2420.h:70:#define TOSH_DATA_LENGTH 28/opt/tinyos-2.x/tos/chips/xe1205/XE1205.h:102:#define TOSH_DATA_LENGTH 28
I did not find anywhere defining it to be 29.
p.s. If anyone point out the caveats of
I searched for this problem but did not find the answer.
I want to build a program with defining a macro. Generally,
make -Dmacro
will work for cc,gcc,CC etc. compilers, but on TInyOS,
make -Dmacro platformdoes not work.
How to do this job?
Thanks.
-- Regards,Tie
how does Tinyos process integer division? Specifically,
uint_16_t result = 3 / 5 * 5;
then is result3 or 0?-- Regards,Tie
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
I did find How to calculating energy consumption in TOSSIM in mail archive, butI want to calculate energy consumption on real motes.
I also found there was a similar question in archive, but the answer is too general.Could anyone tell the pariticular interfaces and componets? Many thanks.--
PacketAckknowledgements.requestAck (msg)
On 10/16/06, LE KHAC HIEU [EMAIL PROTECTED] wrote:
Hi,I want to enable automatic ACK in MicaZ with tinyos-2.x. Could someoneplease give me a hint.
Thanks,-Hieu___Tinyos-help mailing
It can be found in TinyOS source code that TOSH_DATA_LENGTH is defined to be 28, but I found in this mail archive people are saying 29, which one is correct?
Another question is, since 802.15.4 supports up to 127-byte packet, does that mean we can redefine TOSH_DATA_LENGTH to be larger, say 100,
://focus.ti.com/lit/ds/symlink/cc2420.pdf--Jonathan Hui[EMAIL PROTECTED]On 9/28/06, Tie Luo [EMAIL PROTECTED]
wrote: Dr Hui, at first I thank you very much for your explanation. Based on your answer to 1.2, buf[ length ]is crc.But why buf[ length ] 7 being one indicates a good crc?
On 9/28/06, Jonathan
interface CCFifo specifies 'uint8_t length' as a parameter in all its commands, but in its implementation CC2420SpiImplP.nc, it actuall calls SpiPacket.send(), which specifies 'uint16_t length' as a parameter. So, can I modify uint8_t in CCFifo to be uint16_t such that I can send a long packet?
We spent a lot of time but are still confused by the following:
1)CC2420ReceiveP.nc, in event void RXFIFO.readDone(uint8_t* rx_buf, uint8_t rx_len, error_t error )
1.1) line 197:
if ( length 10 ) {...} (where length is header[0])
Q: why use constant 10? Does it mean sizeof(cc2420_header_t)? If
Dr Hui, at first I thank you very much for your explanation.Based on your answer to1.2,buf[ length ] is crc. But why buf[ length ] 7beingone indicates a good crc?
On 9/28/06, Jonathan Hui [EMAIL PROTECTED] wrote:
On 9/28/06, Tie Luo [EMAIL PROTECTED] wrote: 1) CC2420ReceiveP.nc
, in event void
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).
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
I have the same concern about the CSMA implementation in TinyOS 2.0.
Details are especially preferred. Thanks in advance.
On 9/21/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,My question follows the same line as that of Daniel, but I'm working onMICA2 motes, not MICAZ.
What is not very clear
This questionisw.r.tMAC/PHY in TinyOS 2.0.
By theory, MAC should sense the channel until it becomes idle for some time (e.g. DIFS) and then sendsthe packet. But we did not findhow to control carrier sensing
and backoff (the Backoff interface just provides two events - initial() congestion() -
/~jwhui/
On 9/12/06, Tie Luo [EMAIL PROTECTED] wrote: This question is w.r.t MAC/PHY in TinyOS 2.0. By theory, MAC should sense the channel until it becomes idle for some time
(e.g. DIFS) and then sends the packet.But we did not find how to control carrier sensing and backoff (the Backoff interface
I believe both TEP 104(Radio Physical Layer) andTEP 105 (Radio Link Layer)areinteresting parts and deserve effort, especially for those working on physical and MAC layers rather than higher layers.
Can I take a look at the latest draft on TEP105 (since 104 is not available), although it may be
Although the precision_tag TMicro is defined and interface TimerTMicro is possible, we did not find any component the implement that type of timer. The TimerMilliC.nc does exist (we use TinyOS 2.0) but a corresponding
TimerMicroC.nc does NOT exist.
So, how to get a timer that operate on a
Dear Dr. Levis,
Why TEP 104 105 are not released?
I am referring to http://www.tinyos.net/tinyos-2.x/doc/
Any others who can help answer are also appreciated.
-- Regards,Tie
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
Hi, how to detect packet collision in tinyos 2.0? Specifically,a collision can occur either during receiving a packet, or when the two packets come at the same time.
AMReceive only provides event void receive(), which is called whena good packet has been received.
Thanks a lot in advance.--
Similar question that I have. Will feel happy if hearing comments.
Tie
On 9/8/06, Madhu Mudigonda [EMAIL PROTECTED] wrote:
Hello ,
I'm actually working on a project to implementMAC layer. I'm using telosb motes with CC2420 radio. Can anybody suggest some useful literature to understand things?
then you can start making some modifications so youcan get a new protocol.
Regards,
Miguel Erazo
Tie Luo [EMAIL PROTECTED] wrote:
Hi Guys,
Anyone can give a rough outline or simply a pointer to developing a new (CSMA-based) MAC in TinyOS?
Thanks a ton!!-- Regards,Tie
Hi Guys,
Anyone can give a rough outline or simply a pointer to developing a new (CSMA-based) MAC in TinyOS?
Thanks a ton!!-- Regards,Tie
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
Many thanks to Xiaofan Jiang, Karthik Dantu, R. Steve McKown!
Your suggestion works. :-)
Rgds,
Tie
On 9/1/06, R. Steve McKown [EMAIL PROTECTED] wrote:
On Thursday 31 August 2006 10:18 am, Tie Luo wrote: Hi Guys, When I was installing TinyOS
2.0, I encountered a problem in Step 3 (install native
73 matches
Mail list logo
