4 th issue.. [Tinyos-help] Tinyos - Tossim Help [ANITHA KALAIVANAN ]
hey try tinyviz to see the output..........
first of all set PATH... i.e. export
PATH=$PATH:/opt/tinyos-1.x/tools/java/net/tinyos/sim
then try this command......
tinyviz -run build/micaz/main.exe 10
all the best...


On 3/15/10, [email protected] <
[email protected]> wrote:
>
> 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. calrification of the steps of CTP (Islam Hegazy)
>   2.  multiple components AMSenderC (Binh Luong)
>   3. Timer precision problem during proting to platform (Attila Strba)
>   4. Tinyos - Tossim Help (ANITHA KALAIVANAN)
>   5. web server function on TinyOS (Wenjia Liu)
>   6. Testing X-MAC with WUSTL/MLA framework
>      (tinyos-2.x-contrib/wustl/upma) (Vincent Gay)
>   7. Braodcast-Unicast in IRIS (lena psara)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 14 Mar 2010 15:30:35 -0600
> From: "Islam Hegazy" <[email protected]>
> Subject: [Tinyos-help] calrification of the steps of CTP
> To: "TinyOS help" <[email protected]>
> Message-ID: <d94f86448de345fa8b40e2ef412c5...@ict628e>
> Content-Type: text/plain; charset="windows-1256"
>
> Hi all,
>
> After reading the CTP paper and understanding the implementation in TinyOS,
> I conducted a numerical example to understand the behaviour of ETX. I had
> the following observations:
> 1) Beacon-driven link quality (BLQ) tends to increase the value of ETX,
> while data-driven link quality (DLQ) tends to decrease the value of ETX.
> 2) BLQ is unidirectional from the incoming beacons, while DLQ is
> bidirectional from data packets and ACKs.
> 3) BLQ is calculated for all neighbours, while DLQ is calculated for my the
> next hop neighbour only.
> 4) ACK is on 1-to-1 basis, which means that a node sends a single data
> packet and waits for the ACK before sending a new data packet.
> 5) ACK does not include the seq. number of the data packet since it is a
> 1-to-1 scheme.
> 6) Snoop and intercept do not update the neighbour entries in the routing
> tables.
>
> Are my observations about CTP correct?
>
> Regards
> Islam
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100314/6329a6cf/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Sun, 14 Mar 2010 14:56:00 -0700 (PDT)
> From: Binh Luong <[email protected]>
> Subject: [Tinyos-help]  multiple components AMSenderC
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
>
> Hi all,
>
> Normally when we want to send a message we declare our configuration and
> module as follows:
>
> (in configuration)
> components new AMSenderC(AM_MSG);
>
> MyAppC.AMSend -> AMSenderC;
> MyAppC.Packet -> AMSenderC;
> MyAppC.AMPacket -> AMSenderC;
>
> (in module)
> module MyAppC
> {
> uses {
>    .....
>    interface Packet;
>    interface AMPacket;
>    interface AMSend;
>    ......
> }
> }
>
> That means for AMSenderC we need to use the 3 interfaces: Packet, AMPacket
> and AMSend
>
> Now my question is: When I have several types of message then I will need
> several AMSenderC(s). So do I have to declare for each AMSenderC its own
> necessary interfaces Packet, AMPacket and AMSend or can I just use the 3
> interfaces (Packet, AMPacket and AMSend) for all types of messages ?
>
> Thanks in advance
> Regards,
> Binh
> --
> View this message in context:
> http://old.nabble.com/multiple-components-AMSenderC-tp27898445p27898445.html
> Sent from the TinyOS - Help mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 14 Mar 2010 15:50:52 -0700 (PDT)
> From: Attila Strba <[email protected]>
> Subject: [Tinyos-help] Timer precision problem during proting to
>        platform
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Guys,
>
>
> I am trying to port the TinyOS to the Dolphin EO3000I chip from EnOcean and
> I have a poblem with the Timer precission.
>
> As I read from the TEP 102, it is written that the HLP timer interface
> should provide either 32kHz or 1ms or 1us tick precision. The Dolphin runs
> on 16MHz clock. The Timer0 I am trying to use is 16bit, uses the same clock
> source and it has the possibility to use either 2,4,8 prescaler. But that's
> all, so in best case using prescaler 8 I would get 0.5us pro 1 tick.
>
>
> My question is what to do with this? I am far away from the values TEP102
> considers. The transformation components are only for the width adjustment
> right? (i.e. TransformAlarmC).
> Or should I manually adjust the values I get through the HPL
> interface  using constants (multiplication of the input values by 2) such
> way that I get 1us interface?
>
> Any help is highly apritiated,
>
> greetings
>
> Attila
>
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 14 Mar 2010 13:03:57 +0530
> From: ANITHA KALAIVANAN <[email protected]>
> Subject: [Tinyos-help] Tinyos - Tossim Help
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> We have installed tinyos 2.x in ubuntu jaunty . We are not working with
> motes but trying to simulate it using TOSSIM. We had tried to simulate a
> few
> of the sample applications like Blink, RadiotoLeds,  though we were able to
> compile the codes succesfully ,its execution had ended up with error. The
> main.exe file cannot be executed because of the following error.- CANNOT
> EXECUTE BINARY FILE
>
> ki...@kiran-laptop:/opt/tinyos-1.x/apps/Blink/build/micaz$ ./main.exe
> bash: ./main.exe: cannot execute binary file
>
> So we  installed wine application which is used to run exe files and tried
> to execute it through wine commands , but it shows an error- BAD EXE FORMAT
>
> ki...@kiran-laptop:/opt/tinyos-1.x/apps/Blink/build/micaz$ wine main.exe
> wine: could not load
> L"Z:\\opt\\tinyos-1.x\\apps\\Blink\\build\\micaz\\main.exe": Bad EXE format
>
> So, we tried working on Tinyos1.x through Xubuntos Virtual Image. But the
> command Make pc gives the following error
>
> ki...@kiran-laptop:/opt/tinyos-1.x/apps/Blink$ make pc
> mkdir -p build/pc
>    compiling Blink to a pc binary
> ncc -o build/pc/main.exe -g -O0 -pthread -fnesc-nido-tosnodes=1000
> -fnesc-simulate -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all
> -target=pc
> -fnesc-cfile=build/pc/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"Blink\"
> -DIDENT_USER_ID=\"kiran\" -DIDENT_HOSTNAME=\"kiran-laptop\"
> -DIDENT_USER_HASH=0xf062a24fL -DIDENT_UNIX_TIME=0x4b9c8ee9L
> -DIDENT_UID_HASH=0x96ff53f9L Blink.nc -lm
> In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43,
>                 from /opt/tinyos-1.x/tos/system/tos.h:144:
> /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here
> (not in a function)
> /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES'
> not integer constant
> make: *** [exe0] Error 1
>
> Can you please help us find a solution to this problem.
>
> Also,  we tried to work with TinyViz but it shows the same error as
> mentioned above.
>
> Please help us find a solution to these problems....
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100314/7d4722d7/attachment-0001.htm
>
> ------------------------------
>
> Message: 5
> Date: Sun, 14 Mar 2010 17:15:22 -0400 (EDT)
> From: Wenjia Liu <[email protected]>
> Subject: [Tinyos-help] web server function on TinyOS
> To: Tinyos help <[email protected]>
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset=utf-8
>
> Hello there,
>
> Can tinyos support web server function? I am planning to design a web based
> system then users can read the data on web page...
>
> Thanks,
> Wenjia
>
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 15 Mar 2010 11:14:31 +0100
> From: Vincent Gay <[email protected]>
> Subject: [Tinyos-help] Testing X-MAC with WUSTL/MLA framework
>        (tinyos-2.x-contrib/wustl/upma)
> To: [email protected]
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> if you intend to test the low-power MAC protocols from WUSTL's UPMA
> framework, especially X-MAC, please note that you have to pay attention to
> the length of the CCA check's routine. You must set up the
> DEFAULT_CCA_LENGTH in
> */opt/tinyos-2.x-contrib/wustl/upma/chips/cc2420/PowerCycleP.nc
> *accordingly to the platform you are doing tests with.
>
> By default, the setup is 8ms which corresponds to the maximum gap between
> two strobed preambles on TelosB platform. However, on MicaZ platform, I
> have
> observed that this gap roughly ranges from 12ms to 20ms. In that case, if
> you don't want to end up with an alarming number of dropped packets, the
> DEFAULT_CCA_LENGTH should preferably set up to 20ms for instance. That way,
> you ensure that a receiving node will poll the channel for long enough to
> detect a preamble's transmission from the sender during the preambling
> phase.
>
> Regards
> Vincent
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100315/336703f0/attachment-0001.htm
>
> ------------------------------
>
> Message: 7
> Date: Mon, 15 Mar 2010 03:20:27 -0700 (PDT)
> From: lena psara <[email protected]>
> Subject: [Tinyos-help] Braodcast-Unicast in IRIS
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear all,
>
> I have a problem with unicasting packets using IRIS Zigbee Mote while the
> broadcasting is working well. I am not experienced in nesC programming and
> TinyOS so please if you know help me.
> The main functionality is that the mote is waiting for receiving something
> from serial port and then post a task for  transmission over radio and vice
> versa.
>
> First of all, in the configuration file:
>
> for both sending over radio and sending through UART i use the SendMsg
> interface.
>
> .........
> MyAppM.RadioDataSend -> Comm.SendMsg[0];
> MyAppM.RadioDataReceive -> Comm.ReceiveMsg[0];
> MyAppM.UartDataSend -> Comm2.SendMsg[0];
>
>
> In the module file:
>
> module MyAppM{
>
>    provides{
>        interface StdControl;
>    }
>
>    uses{
>        interface StdControl as CommControl;
>        interface Timer;
>        interface Leds;
>        interface Serial;
>        interface SendMsg as UartDataSend;
>        interface SendMsg as RadioDataSend;
>        interface ReceiveMsg as RadioDataReceive;
>    }
> }
>
> implementation {
>
> ........
> uint16_t address;
> .......
>
> //in the task for sending over radio:
> void task SendData_radio()
> {
>    if(sending_packet1) return;
>    atomic sending_packet1 = TRUE;
>
>    if(address == 0){
>
>       //send message to all motes-BROADCAST
>       if (call RadioDataSend.send(TOS_BCAST_ADDR, sizeof(Msg_radio),
> &msg_buffer_radio) != SUCCESS)
>       sending_packet1 = FALSE;
>    } else {
>    if (call RadioDataSend.send(address), sizeof(Msg_radio),
> &msg_buffer_radio) != SUCCESS)
>    sending_packet1 = FALSE;
>    }
>   return;
> }
>
>
> .........
>
> I think that the problem is in the above task...I am waiting for your help.
> Thanks
>
> Best Regards,
> Lena
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100315/600113df/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> End of Tinyos-help Digest, Vol 83, Issue 46
> *******************************************
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to