Hi All, Can some one tell me how to use IRIS independently without using TOSSIM or TINYVIZ. It is not difficult to do software programming, especially when using very familiar languages such as C or C++ or Java or tcl/tk or Python or AWK and so on. TOSSIM is not capable to do software programming and so is TINYVIZ, but IRIS can do this. So how to use IRIS to do simulation independently? Thanks!
An Feng [email protected] -----Original Message----- From: tinyos-help-request <[email protected]> To: tinyos-help <[email protected]> Sent: Tue, Feb 19, 2013 5:42 pm Subject: Tinyos-help Digest, Vol 118, Issue 47 Send Tinyos-help mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Tinyos-help digest..." Today's Topics: 1. Re: Transmission power for CC2420 packet (Farzad Samie) 2. reduce radio's power consumption (Farzad Samie) 3. raspberry pi + TinyOS (Dane Hamilton) 4. Raspbian and TinyOS (Dane Hamilton) 5. Re: problems with TestSerial : serial link issues (Janos Sallai) 6. Re: Time to transmit in CC2420! (Janos Sallai) 7. Re: Change default transmission power RF230 (IRIS MOTE) (Mitul) 8. DSR (reziii) 9. Re: Packet contents (Michael Schippling) ---------------------------------------------------------------------- Message: 1 Date: Mon, 04 Feb 2013 09:07:32 +0100 From: Farzad Samie <[email protected]> Subject: Re: [Tinyos-help] Transmission power for CC2420 packet To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 03.02.2013 21:13, Swetha wrote: > e range of transmission power in dbm??? You can find all information you need in this file. http://moss.csc.ncsu.edu/~mueller/rt/rt11/readings/projects/g4/datasheet.pdf And yes, 0dbm is the maximum output power. ------------------------------ Message: 2 Date: Mon, 04 Feb 2013 14:58:37 +0100 From: Farzad Samie <[email protected]> Subject: [Tinyos-help] reduce radio's power consumption To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello I'm trying to measure the radio module power (in send/receive state). My platform is telosb (tinyos2.x and radio module is cc2420). I use low power listening interface. I have two nodes: The first one is just a sender; it should only send packet and doesn't need to receive any thing. I've set the transmission power to lowest level on sender, transmit 2 packets per second periodically. So according to datasheet, I expect it to consume about 9mA for a short period and then goes to sleep mode and consumes about a few uA. But after sending these 2 packets, it spends more time (~100ms) in receive mode (consuming about 20mA). I put a resistor (12ohm) in series with voltage supply and measure the voltage drop on it. Here is a figure of signal: https://www.dropbox.com/s/mvd9b2tug0ub2z5/wave1.png That two narrow drops correspond to send modes. But this node is just a sender and won't receive any thing. How can I avoid it from going to receive mode? I found this thread, but it has no solution: http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2011-March/049895.html Many thanks ------------------------------ Message: 3 Date: Fri, 15 Feb 2013 15:37:58 -0500 From: Dane Hamilton <[email protected]> Subject: [Tinyos-help] raspberry pi + TinyOS To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii We are trying to install TinyOS onto a raspberry pi running Raspbian Wheezy for interfacing with TelosB motes. While trying to use the automatic installation of the TinyOS Debian Repository, we are experiencing connection errors. We've updated /etc/apt/sources.list to include only "deb http://tinyos.stanford.edu/tinyos/dists/ubuntu lucid main". Then after running, "sudo apt-get update" we get the following results. Hit http://archive.raspberrypi.org wheezy InRelease Hit http://archive.raspberrypi.org wheezy/main armhf Packages Ign http://tinyos.stanford.edu lucid InRelease Ign http://tinyos.stanford.edu lucid Release.gpg Hit http://tinyos.stanford.edu lucid Release Ign http://archive.raspberrypi.org wheezy/main Translation-en_GB Ign http://archive.raspberrypi.org wheezy/main Translation-en Err http://tinyos.stanford.edu lucid/main armhf Packages 404 Not Found Ign http://tinyos.stanford.edu lucid/main Translation-en_GB Ign http://tinyos.stanford.edu lucid/main Translation-en W: Failed to fetch http://tinyos.stanford.edu/tinyos/dists/ubuntu/dists/lucid/main/binary-armhf/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. We understand that Raspbian is not exactly the same as Ubuntu. What do we need to do to get around this error? Thanks in advance, - Dane Hamilton [email protected] ------------------------------ Message: 4 Date: Fri, 15 Feb 2013 15:47:30 -0500 From: Dane Hamilton <[email protected]> Subject: [Tinyos-help] Raspbian and TinyOS To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" I apologize if I posted this twice. We are trying to install TinyOS onto a raspberry pi running Raspbian Wheezy for interfacing with TelosB motes. While trying to use the automatic installation of the TinyOS Debian Repository, we are experiencing connection errors. We've updated /etc/apt/sources.list to include only "deb http://tinyos.stanford.edu/tinyos/dists/ubuntulucid main". Then after running, "sudo apt-get update" we get the following results. Hit http://archive.raspberrypi.org wheezy InRelease Hit http://archive.raspberrypi.org wheezy/main armhf Packages Ign http://tinyos.stanford.edu lucid InRelease Ign http://tinyos.stanford.edu lucid Release.gpg Hit http://tinyos.stanford.edu lucid Release Ign http://archive.raspberrypi.org wheezy/main Translation-en_GB Ign http://archive.raspberrypi.org wheezy/main Translation-en Err http://tinyos.stanford.edu lucid/main armhf Packages 404 Not Found Ign http://tinyos.stanford.edu lucid/main Translation-en_GB Ign http://tinyos.stanford.edu lucid/main Translation-en W: Failed to fetch http://tinyos.stanford.edu/tinyos/dists/ubuntu/dists/lucid/main/binary-armhf/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. We understand that Raspbian is not exactly the same as Ubuntu. What do we need to do to get around this error? Thanks in advance, - Dane Hamilton [email protected] -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130215/52a4bf72/attachment-0001.htm ------------------------------ Message: 5 Date: Tue, 5 Feb 2013 08:33:42 -0600 From: Janos Sallai <[email protected]> Subject: Re: [Tinyos-help] problems with TestSerial : serial link issues To: jpam <[email protected]> Cc: tinyos forum <[email protected]> Message-ID: <CAPBepE5i3AadLYu=esq9N1qj=0uJuMFRT3BUb8bpSMK_LdYN=w...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Have you programmed the mote with TestSerial? Is it connected to the PC? Are you sure that it's on /dev/ttyUSB0 and not some other port (check motelist output to verify)? Is the little red LED next to the USB connector blinking on the mote when it's connected to the PC? Janos On Tue, Feb 5, 2013 at 6:22 AM, jpam <[email protected]> wrote: > Hello everyone. > > I have the same problem, but I'm using TelosB. > > $ java TestSerial > serial@/dev/ttyUSB0:115200: resynchronising > Sending packet 0 > Sending packet 1 > Sending packet 2 > > ---- > .bashrc file: > > export TOSROOT=/opt/tinyos-svn/src/tinyos-2.x > export PATH=$PATH:/opt/tinyos-svn/bin:$TOSROOT/support/sdk/c:/usr/msp430/bin > export TOSDIR=$TOSROOT/tos > export MAKERULES=$TOSROOT/support/make/Makerules > export CLASSPATH=$TOSROOT/support/sdk/java/tinyos.jar:. > export PYTHONPATH=.:$TOSROOT/support/sdk/python:$PYTHONPATH > export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/msp430/lib:/usr/local/lib > export MOTECOM=serial@/dev/ttyUSB0:telosb > > Any ideas what I'm doing wrong? > > Thanks in advance! > > > > -- > View this message in context: > http://tinyos-help.10906.n7.nabble.com/problems-with-TestSerial-serial-link-issues-tp7323p22525.html > Sent from the TinyOS - Help mailing list archive at Nabble.com. > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > ------------------------------ Message: 6 Date: Thu, 7 Feb 2013 10:30:18 -0600 From: Janos Sallai <[email protected]> Subject: Re: [Tinyos-help] Time to transmit in CC2420! To: wasif masood <[email protected]> Cc: tinyos forum <[email protected]> Message-ID: <capbepe7gozpehz5cx+brjikgbi1drsn3e+fajt4fqmp8yqn...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Wasid, You probably can't reduce that, at least not without digging deep into the radio stack code. Notice that there is a significant delay between issuing send and the packet actually going out. First, the SPI resource needs to be acquired. Then, the packet is uploaded to the TX FIFO of the radio chip. The SPI clock rate is 256kbps, so it takes more time to upload a packet to the radio chip than to actually transmit it! After the packet is uploaded to the FIFO, the backoff timer is started. No matter if you set the initial backoff to 0, it will take some time till the timer is fired. Then, the CCA is carried out, and if the channel is clear, the send strobe is issued. That's when the radio chip starts sending the preamble. If acknowledgements are off, the sendDone event is signaled from a task which was posted from the interrupt context that was triggered by the SFD pin going low after the last byte of the packet is transmitted. If acknowledgements are on, there are further delays: the driver waits for the ack to arrive (or timeouts), and the sendDone event is signaled only after that. To sum it up, this clearly takes several tens of milliseconds. The question is, why do you want to reduce this time? What do you want to achieve and why? Janos On Thu, Feb 7, 2013 at 8:02 AM, wasif masood <[email protected]> wrote: > > Hi All, > > I know this is probably an old topic but I still couldn't find any solution > to that. Well, I am using CC2420Transmit.Send interface which is connected > to CC2420TransmitC. Even at this lowest level of wiring the time elapsed > between the Send and SendDone signal is in 10's of milliseconds (I have > tested it for both Z1 and TelosB). Is there any way I can reduce this time? > Please share your expertise! > > Regards, > Wasif Masood > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ------------------------------ Message: 7 Date: Wed, 13 Feb 2013 05:38:02 -0800 (PST) From: Mitul <[email protected]> Subject: Re: [Tinyos-help] Change default transmission power RF230 (IRIS MOTE) To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii I have tried it and, I think after reducing the transmission power range is of about one small room. Can any one tell me actually how to remove the antenna physically?? -- View this message in context: http://tinyos-help.10906.n7.nabble.com/Change-default-transmission-power-RF230-IRIS-MOTE-tp8631p22583.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ------------------------------ Message: 8 Date: Tue, 5 Feb 2013 09:19:05 -0800 (PST) From: reziii <[email protected]> Subject: [Tinyos-help] DSR To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Hi please help me... I need to DSR routing source code. thanks -- View this message in context: http://tinyos-help.10906.n7.nabble.com/DSR-tp22531.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ------------------------------ Message: 9 Date: Wed, 06 Feb 2013 09:28:52 -0700 From: Michael Schippling <[email protected]> Subject: Re: [Tinyos-help] Packet contents To: Jan Hauer <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed I'm just starting to deal with T2's Listen and ListenRaw (under Ubuntu) and found that ListenRaw has some kind of timing and error issues. If I run it in a shell window it just hangs around and prints no message data, but if I step through it in Eclipse I get a few lines of output before (it appears) that the read() returns a -1 and the main loop exits. However the internal read thread is still running so the process just hangs at that point. I don't think I have the patience to compare its operation to Listen which seems to work OK, so I'm probably going to just drink the kool-aide and move on. I did run across a mention of an extra byte in the message header when using some kind of secure messaging protocol, probably in one of the TEPs (111, 113, 116 seem to deal with messaging). That would offset your payload start, and maybe even mess up the length calculation. In the course of putzing with this I found that the tinyos.jar contains the net/tinyos/packet/Serial.class which is used by Packetizer, but the Serial.java file is missing from my source tree. I can re-compile the source I have if I include the given tinyos.jar but can't actually reconstruct the jar itself. I found a couple of instances on this list of previous complaints about this file being missing, but no offered solutions. I got my source tree from here: git clone -v git://github.com/tp-freeforall/prod tinyos-2.x as per E.Decker's instructions at: https://github.com/tp-freeforall/prod/blob/tp-master/00b_Development_Environment MS On 02/06/2013 02:59 AM, Jan Hauer wrote: > The java listen app should display all bytes. For debugging you could > use the printf library (see apps/tests/TestPrintf) on the BaseStation > and make a hexdump of your entire message_t. Maybe also make sure > message_t payload is big enough (e.g. for cc2420 put "CFLAGS += > -DTOSH_DATA_LENGTH=X", where X is max payload, in Makefile), and, of > course, message_t definition must be the same on sender and > basestation. > > Jan > > On Tue, Feb 5, 2013 at 7:04 PM, Filip Jurne?ka <[email protected]> wrote: >> Thanks, >> >> i've already seen that tutorial and yes, it works fine. The problem I am >> having is most likely somewhere deeper. I am using the hardware in-line >> security. I have specified the requested parameters for the SECCTRL >> registers so that they would add 4-byte CBC-MAC (using some specified key) >> to the message, but when I catch the message with the BS app, it overrides >> the last byte. I was thinking about deeper examination with the ListenRaw >> tool, but didn't get it working as expected. Is the BS/Listen app >> displaying all the received bytes? >> >> Oh and I am specifying the the length of the message to send (via the >> AMSend.send()) to be the size of my payload data. >> >> Filip >> >> On Tue, 05 Feb 2013 18:11:36 +0100, Jan Hauer <[email protected]> >> wrote: >> >>> Hi Filip, >>> >>> the structure of serial AM packets is explained here: >>> http://docs.tinyos.net/tinywiki/index.php/Mote-PC_serial_communication_and_SerialForwarder#BaseStation_and_net.tinyos.tools.Listen >>> About the last byte: check once more that you pass the correct payload >>> length, because in the example it seems that msg len field is 3 (not >>> 4). >>> >>> Jan >>> >>> >>> On Tue, Feb 5, 2013 at 3:05 PM, Filip Jurne?ka >>> <[email protected]> wrote: >>>> Ok, I did that. I know the byte 80 is in fact my defined AM type. Now it >>>> is still an open question for me why does the CBC-MAC override the last >>>> byte in the packet? >>>> >>>> Best, >>>> Filip Jurnecka >>>> >>>> On Tue, 05 Feb 2013 14:58:18 +0100, wasif masood <[email protected]> >>>> wrote: >>>> >>>>> Checkout the CC2420 datasheet for details regarding the 802.15.4 header >>>>> strucutre. >>>>> >>>>> On Tue, Feb 5, 2013 at 2:17 PM, Filip Jurne?ka >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi there. >>>>>> >>>>>> I wonder how the packet delimiters work. Say I have two packets. If >>>>>> sent >>>>>> normally, the BS app displays them as: >>>>>> 00 FF FF 00 01 00 22 80 >>>>>> 00 FF FF 00 01 01 22 80 00 >>>>>> >>>>>> Now I don't know what the first 00 is, but the next FFFF is the >>>>>> broadcast >>>>>> address, the 0001 should be my address, the next 00/01 defines the >>>>>> length >>>>>> of the packet data. What is the 22? What is the 80? Is it the >>>>>> delimiter >>>>>> of >>>>>> the data to follow? Obviously, the last 00 is the data sent. >>>>>> >>>>>> Now it gets more interesting, if I enable the in-line CBC-MAC with 4 >>>>>> bytes >>>>>> output, I get the following. >>>>>> 00 FF FF 00 01 03 22 B7 E2 4C FB >>>>>> 00 FF FF 00 01 04 22 80 71 36 57 EE >>>>>> >>>>>> The question is mainly about the fact that the output is overriding >>>>>> the >>>>>> last byte of the unauthenticated message, i.e. the delimiter or the >>>>>> payload byte. Any ideas why and how to fix it? >>>>>> >>>>>> Best regards, >>>>>> Filip Jurnecka >>>>>> _______________________________________________ >>>>>> Tinyos-help mailing list >>>>>> [email protected] >>>>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Tinyos-help mailing list >>>> [email protected] >>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > ------------------------------ _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help End of Tinyos-help Digest, Vol 118, Issue 47 ********************************************
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
