Premkumar Arumugam | 28 Jul 14:33 2014
Picon

Processor and radio module speed

Hello,
 I am using TelosB motes and TinyOS for my experiment.  I would like to know the hardware limit of this mote (MSP 430 and CC2420). I was carrying some initial experiment to understand the hardware limit, I considered two mote, one was the pinging mote and the other was the base station to receive the packet. The pinging mote transmits packet for every 50ms (which is in 1 minute, there will be 1200 packets) and in next experiment the pinging mote transmitted packet for every 200ms (1 minute=300 packets). Comparatively 200ms performed better packet delivery ratio. The distance between the mote is 1m and the packet length is 100 bytes.
 
Why this difference?
 
Is this because of transmission interval between the packet or the number of bytes to be transmitted??
 
Experts, please share your suggestions?

Thanks,
Prem
<div>

<div class="MsoNormal">Hello, </div>

<div class="MsoNormal">
<span>&nbsp;</span>I am using TelosB
motes and TinyOS for my experiment.<span>&nbsp; </span>I
would like to know the hardware limit of this mote (MSP 430 and CC2420). I was
carrying some initial experiment to understand the hardware limit, I considered
two mote, one was the pinging mote and the other was the base station to
receive the packet. The pinging mote transmits packet for every 50ms (which is
in 1 minute, there will be 1200 packets) and in next experiment the pinging
mote transmitted packet for every 200ms (1 minute=300 packets). Comparatively
200ms performed better packet delivery ratio. The distance between the mote is
1m and the packet length is 100 bytes.</div>

<div class="MsoNormal">&nbsp;</div>

<div class="MsoNormal">Why this difference?</div>

<div class="MsoNormal">&nbsp;</div>

<div class="MsoNormal">Is this because of transmission interval between the packet
or the number of bytes to be transmitted??</div>

<div class="MsoNormal">&nbsp;</div>

<div class="MsoNormal">Experts, please share your suggestions?</div>

<div class="MsoNormal"><br></div>

<div class="MsoNormal">Thanks,</div>

<div class="MsoNormal">Prem<br>
</div>

</div>
José Silva Oliveira Araujo | 28 Jul 09:07 2014
Picon
Picon

problem with printf: printing when using PrintfC and not when using SerialPrintfC

Hi all,

 

I am having a problem with my tinyos 2.x and telos nodes. I was trying to read the printfs that I am calling in my application but for some weird reason I only get the output

 

Thread[Thread-1,5,main]serial <at> /dev/ttyUSB2:115200: resynchronizing when issuing “java net.tinyos.tools.PrintfClient -comm serial <at> /dev/ttyUSBX:telos” (getting stuck there) if I use “components SerialPrintfC;”. However, when I use “components PrintfC;” it works. Same happens for the printf test and tutorial examples from tinyos.

 

Now the reason for me to prefer to use SerialPrintfC instead of PrintfC is because if I use PrintfC in the application that I am interested to run, I am getting the following compilation errors which breaks the compilation:

 

/home/wsn/local/src/tinyos-2.x/tos/lib/printf/PrintfP.nc:130: redefinition of `printfflush'

/home/wsn/local/src/tinyos-2.x/tos/lib/printf/printf.h:72: previous declaration of `printfflush'

 

Anybody has any tips on what this problem may be caused by and how to fix it?

 

Thanks for the help!

José Araújo

_____________________________

PhD student

Department of Automatic Control

KTH Royal Institute of Technology

http://people.kth.se/~araujo/

https://code.google.com/p/kth-gisoo/

 

<div>
<div class="WordSection1">
<p class="MsoNormal">Hi all,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I am having a problem with my tinyos 2.x and telos nodes. I was trying to read the printfs that I am calling in my application but for some weird reason I only get the output<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thread[Thread-1,5,main]serial <at> /dev/ttyUSB2:115200: resynchronizing when issuing &ldquo;java net.tinyos.tools.PrintfClient -comm serial <at> /dev/ttyUSBX:telos&rdquo; (getting stuck there) if I use &ldquo;components SerialPrintfC;&rdquo;. However, when I use &ldquo;components
 PrintfC;&rdquo; it works. Same happens for the printf test and tutorial examples from tinyos.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Now the reason for me to prefer to use SerialPrintfC instead of PrintfC is because if I use PrintfC in the application that I am interested to run, I am getting the following compilation errors which breaks the compilation:
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">/home/wsn/local/src/tinyos-2.x/tos/lib/printf/PrintfP.nc:130: redefinition of `printfflush'<p></p></p>
<p class="MsoNormal">/home/wsn/local/src/tinyos-2.x/tos/lib/printf/printf.h:72: previous declaration of `printfflush'
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Anybody has any tips on what this problem may be caused by and how to fix it?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thanks for the help!<p></p></p>
<p class="MsoNormal">Jos&eacute; Ara&uacute;jo<p></p></p>
<p class="MsoNormal">_____________________________<p></p></p>
<p class="MsoNormal">PhD student<p></p></p>
<p class="MsoNormal">Department of Automatic Control<p></p></p>
<p class="MsoNormal">KTH Royal Institute of Technology<p></p></p>
<p class="MsoNormal"><a href="http://people.kth.se/~araujo/"><span>http://people.kth.se/~araujo/</span></a><p></p></p>
<p class="MsoNormal"><a href="https://code.google.com/p/kth-gisoo/"><span>https://code.google.com/p/kth-gisoo/</span></a><p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
jobishjohn ips | 28 Jul 08:46 2014
Picon

Regarding PacketAcknowledgements interface

I am a beginner and uses TinyOS 2.1.2.I am using TelosB motes.
I was experimenting about the PacketAcknowledgements interface.
My code in brief (module file) is:
-------------------------------------------------------
    event void Boot.booted()
    {
        call timer.startPeriodic(1000);
        call radiocontrol.start();
    }   
    event void timer.fired()
    {
        nx_uint16_t * pntr =  (nx_uint16_t *) call AMSend.getPayload(&wtmsg,sizeof(testdata));       
        (*pntr) = testdata;
        if(call PacketAcknowledgements.requestAck(&wtmsg)==SUCCESS)
            call Leds.led0Toggle();
        call AMSend.send(destid, &wtmsg, sizeof(testdata));
    }
    event void radiocontrol.stopDone(error_t error){}
    event void radiocontrol.startDone(error_t error){}
    event void AMSend.sendDone(message_t *msg, error_t error)
    {
        if ( (msg == &wtmsg) && (call PacketAcknowledgements.wasAcked(msg)==SUCCESS))
                  call Leds.led1Toggle();
        else
                 ack_success = FAIL;
    }
---------------------------------------------------------------
Even with destination mote in the off state(no power), I get a SUCCESS(led1 toggles) for PacketAcknowledgements.wasAcked(msg).
Where I am doing the mistake? I have connected, PacketAcknowledgements -> ActiveMessageC in my configuration file.

Can any one please help me to find out my mistake..!!!

Thanks
Jobish John
<div><div dir="ltr">
<div>
<div>I am a beginner and uses TinyOS 2.1.2.I am using TelosB motes.<br>I was experimenting about the PacketAcknowledgements interface.<br>My code in brief (module file) is:<br>-------------------------------------------------------<br>
&nbsp;&nbsp;&nbsp; event void Boot.booted()<br>&nbsp;&nbsp;&nbsp; {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call timer.startPeriodic(1000);<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call radiocontrol.start();<br>&nbsp;&nbsp;&nbsp; }&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; event void timer.fired()<br>&nbsp;&nbsp;&nbsp; {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; nx_uint16_t * pntr =&nbsp; (nx_uint16_t *) call AMSend.getPayload(&amp;wtmsg,sizeof(testdata));&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; (*pntr) = testdata;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; if(call PacketAcknowledgements.requestAck(&amp;wtmsg)==SUCCESS)<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call Leds.led0Toggle();<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call AMSend.send(destid, &amp;wtmsg, sizeof(testdata));<br>&nbsp;&nbsp;&nbsp; }<br>
&nbsp;&nbsp;&nbsp; event void radiocontrol.stopDone(error_t error){}<br>&nbsp;&nbsp;&nbsp; event void radiocontrol.startDone(error_t error){}<br>&nbsp;&nbsp;&nbsp; event void AMSend.sendDone(message_t *msg, error_t error)<br>&nbsp;&nbsp;&nbsp; {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; if ( (msg == &amp;wtmsg) &amp;&amp; (call PacketAcknowledgements.wasAcked(msg)==SUCCESS))<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call Leds.led1Toggle();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; else<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ack_success = FAIL;<br>&nbsp;&nbsp;&nbsp; }<br>---------------------------------------------------------------<br>Even with destination mote in the off state(no power), I get a SUCCESS(led1 toggles) for PacketAcknowledgements.wasAcked(msg).<br>
Where I am doing the mistake? I have connected, PacketAcknowledgements -&gt; ActiveMessageC in my configuration file.<br><br>Can any one please help me to find out my mistake..!!!<br><br>
</div>Thanks<br>
</div>Jobish John<br>
</div></div>
Abinaya Inbamani | 27 Jul 06:32 2014
Picon

not able to receive the packets...

Hi i am using MIB520 , iris mote(XM2110) and MDA100 sensor board...
I am trying to use Moteview tool ....i have configured all my motes correctly....but i am not able to receive packetes...can anyone please help...
Steps which i followed...
opened moteview, file->connect to WSN
Mode..acquire live data->local
i chose the com  port and interface board correctly...in advanced server settings i enabled spawn seprate shell...
in sensor board tab i chose the Application name as XMDA100 as i am using that board...
now when i started to run xserve ....i am not able to receive the packets...wht can be the issue...
Can anyone kindly help..
<div><div dir="ltr">Hi i am using MIB520 , iris mote(XM2110) and MDA100 sensor board...<div>I am trying to use Moteview tool ....i have configured all my motes correctly....but i am not able to receive packetes...can anyone please help...</div>
<div>Steps which i followed...</div>
<div>opened moteview, file-&gt;connect to WSN</div>
<div>Mode..acquire live data-&gt;local</div>
<div>i chose the com &nbsp;port and interface board correctly...in advanced server settings i enabled spawn seprate shell...</div>
<div>in sensor board tab i chose the Application name as XMDA100 as i am using that board...</div>
<div>now when i started to run xserve ....i am not able to receive the packets...wht can be the issue...</div>
<div>Can anyone kindly help..</div>
</div></div>
Alex | 25 Jul 09:47 2014
Picon

Does blip and coap in tinyos 2.1.2 support micaz or iris platform


Hi,


    I have installed tinyos 2.1.2 under Ubuntu 12.04. I can make PppRouter and UDPEcho on telosb platform. Does blip and coap in tinyos 2.1.2 support micaz or iris platform?

    There are errors if I make micaz under PppRouter dictionary and errors on other applications. 


Ubuntu 12.04     MSP430-GCC 4.6.3    NESCC 1.3.5

telosb
micaz
iris

PppRouter
OK
ERROR
ERROR

UDPEcho
OK
OK
ERROR

TCPEcho
ERROR
ERROR
ERROR

CoapBlip
ERROR
ERROR
ERROR







**************************************************************************************************************************
root <at> ubuntu:/opt/tinyos-2.1.2/apps/PppRouter# make micaz blip
[INFO] compiling PppRouterC to a micaz binary
nescc -o build/micaz/main.exe  -Os -DRPL_ROUTING -DRPL_STORING_MODE -I../../tos/lib/net/rpl -I../../tos/lib/ppp -I../../tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -gcc=avr-gcc -Wnesc-all -fnesc-include=tos -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -fnesc-cfile=build/micaz/app.c -fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22 -DCC2420_HW_ACKNOWLEDGEMENTS -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I../../tos/lib/net/ -I../../tos/lib/printf/ -I../../tools/tinyos/c/blip/ -I../../tos/lib/net/blip/ -I../../tos/lib/net/blip/interfaces/ -I../../tos/lib/net/blip/nwprog/ -I../../tos/lib/net/blip/shell/ -I../../tos/lib/net/blip/serial/ -I../../tos/lib/net/blip/platform/ -I../../tos/lib/net/blip/icmp/ -I../../tos/lib/net/blip/dhcp/ -I../../tos/platforms/micaz -I../../tos/platforms/mica -I../../tos/platforms/micaz/chips/cc2420 -I../../tos/chips/cc2420 -I../../tos/chips/cc2420/alarm -I../../tos/chips/cc2420/control -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/link -I../../tos/chips/cc2420/lowpan -I../../tos/chips/cc2420/lpl -I../../tos/chips/cc2420/packet -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/spi -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/security -I../../tos/platforms/micaz/chips/at45db -I../../tos/platforms/mica2/chips/at45db -I../../tos/platforms/mica/chips/at45db -I../../tos/chips/at45db -I../../tos/chips/atm128 -I../../tos/chips/atm128/adc -I../../tos/chips/atm128/pins -I../../tos/chips/atm128/spi -I../../tos/chips/atm128/i2c -I../../tos/chips/atm128/timer -I../../tos/lib/timer -I../../tos/lib/serial -I../../tos/lib/power -I../../tos/lib/diagmsg -mmcu=atmega128 -fnesc-target=avr -fnesc-no-debug -DPLATFORM_MICAZ -Wall -Wshadow --param max-inline-insns-single=100000 -I../../tos/system -I../../tos/types -I../../tos/interfaces -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x53cdf274L -DIDENT_UIDHASH=0x67782f81L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring-check.xml PppRouterC.nc -lm  ../../tools/tinyos/c/blip/lib6lowpan/iovec.c ../../tools/tinyos/c/blip/lib6lowpan/in_cksum.c ../../tools/tinyos/c/blip/lib6lowpan/ip_malloc.c ../../tools/tinyos/c/blip/lib6lowpan/utility.c ../../tos/lib/net/blip/table.c
../../tos/system/LedC.nc:32:25: error: PlatformLed.h: No such file or directory
In file included from ../../tos/lib/ppp/PppC.nc:78,
                 from ../../tos/lib/ppp/PppDaemonC.nc:56,
                 from PppRouterC.nc:16:
In component `LedC':
../../tos/system/LedC.nc:88: component PlatformLedC not found
../../tos/system/LedC.nc:89: no match
In file included from ../../tos/lib/timer/MuxAlarmMilli32C.nc:47,
                 from ../../tos/lib/ppp/LcpAutomatonC.nc:72,
                 from ../../tos/lib/ppp/LinkControlProtocolC.nc:89,
                 from ../../tos/lib/ppp/PppDaemonC.nc:65,
                 from PppRouterC.nc:16:
In component `MuxAlarmMilli32C_':
../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component AlarmMilli32C not found
../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component `AlarmMilli32C' is not generic
../../tos/lib/timer/MuxAlarmMilli32C_.nc:56: no match
../../tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
../../tos/chips/cc2420/link/PacketLinkC.nc:38:2: warning: #warning "*** USING PACKET LINK LAYER"
make: *** [exe] Error 1
root <at> ubuntu:/opt/tinyos-2.1.2/apps/PppRouter# make iris blip
[INFO] compiling PppRouterC to a iris binary
nescc -o build/iris/main.exe  -Os -DRPL_ROUTING -DRPL_STORING_MODE -I../../tos/lib/net/rpl -I../../tos/lib/ppp -I../../tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -gcc=avr-gcc -Wnesc-all -fnesc-include=tos -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -fnesc-cfile=build/iris/app.c -fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22 -DCC2420_HW_ACKNOWLEDGEMENTS -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I../../tos/lib/net/ -I../../tos/lib/printf/ -I../../tools/tinyos/c/blip/ -I../../tos/lib/net/blip/ -I../../tos/lib/net/blip/interfaces/ -I../../tos/lib/net/blip/nwprog/ -I../../tos/lib/net/blip/shell/ -I../../tos/lib/net/blip/serial/ -I../../tos/lib/net/blip/platform/ -I../../tos/lib/net/blip/icmp/ -I../../tos/lib/net/blip/dhcp/ -I../../tos/platforms/iris -I../../tos/platforms/micaz -I../../tos/platforms/mica -I../../tos/platforms/iris/chips/rf230 -I../../tos/chips/rf230 -I../../tos/lib/rfxlink/layers -I../../tos/lib/rfxlink/util -I../../tos/platforms/iris/chips/at45db -I../../tos/platforms/mica2/chips/at45db -I../../tos/platforms/mica/chips/at45db -I../../tos/chips/at45db -I../../tos/platforms/iris/chips/ds2401 -I../../tos/platforms/mica2/chips/ds2401 -I../../tos/chips/ds2401 -I../../tos/chips/atm1281 -I../../tos/chips/atm1281/adc -I../../tos/chips/atm1281/timer -I../../tos/chips/atm128 -I../../tos/chips/atm128/adc -I../../tos/chips/atm128/pins -I../../tos/chips/atm128/spi -I../../tos/chips/atm128/i2c -I../../tos/chips/atm128/timer -I../../tos/lib/timer -I../../tos/lib/serial -I../../tos/lib/power -I../../tos/lib/diagmsg -mmcu=atmega1281 -fnesc-target=avr -fnesc-no-debug -DPLATFORM_IRIS -Wall -Wshadow --param max-inline-insns-single=100000 -I../../tos/system -I../../tos/types -I../../tos/interfaces -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x53cdf282L -DIDENT_UIDHASH=0x3a3c71e1L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/iris/wiring-check.xml PppRouterC.nc -lm  ../../tools/tinyos/c/blip/lib6lowpan/iovec.c ../../tools/tinyos/c/blip/lib6lowpan/in_cksum.c ../../tools/tinyos/c/blip/lib6lowpan/ip_malloc.c ../../tools/tinyos/c/blip/lib6lowpan/utility.c ../../tos/lib/net/blip/table.c
In file included from ../../tos/lib/timer/MuxAlarmMilli32C.nc:47,
                 from ../../tos/lib/ppp/LcpAutomatonC.nc:72,
                 from ../../tos/lib/ppp/LinkControlProtocolC.nc:89,
                 from ../../tos/lib/ppp/PppDaemonC.nc:65,
                 from PppRouterC.nc:16:
In component `MuxAlarmMilli32C_':
../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component AlarmMilli32C not found
../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component `AlarmMilli32C' is not generic
../../tos/lib/timer/MuxAlarmMilli32C_.nc:56: no match
In file included from ../../tos/lib/net/blip/IPNeighborDiscoveryC.nc:16,
                 from ../../tos/lib/net/blip/IPStackC.nc:47,
                 from PppRouterC.nc:43:
In component `IPAddressC':
../../tos/lib/net/blip/IPAddressC.nc:34: component Ieee154AddressC not found
../../tos/lib/net/blip/IPAddressC.nc:38: cannot find `Ieee154Address'
In component `IPNeighborDiscoveryC':
../../tos/lib/net/blip/IPNeighborDiscoveryC.nc:23: cannot find `Ieee154Address'
In file included from ../../tos/lib/net/blip/IPStackC.nc:48,
                 from PppRouterC.nc:43:
In component `IPDispatchC':
../../tos/lib/net/blip/IPDispatchC.nc:46: component Ieee154BareC not found
../../tos/lib/net/blip/IPDispatchC.nc:47: component RadioPacketMetadataC not found
../../tos/lib/net/blip/IPDispatchC.nc:59: cannot find `SplitControl'
../../tos/lib/net/blip/IPDispatchC.nc:60: cannot find `BarePacket'
../../tos/lib/net/blip/IPDispatchC.nc:61: cannot find `BareSend'
../../tos/lib/net/blip/IPDispatchC.nc:62: cannot find `BareReceive'
../../tos/lib/net/blip/IPDispatchC.nc:68: cannot find `PacketLink'
make: *** [exe] Error 1


**************************************************************************************************************************

--
Thanks for your attention.

Best regards.




<div>
<div>
<div>
<br><div>Hi,</div>
<div><br></div>
<div><br></div>
<div>&nbsp; &nbsp; I have installed tinyos 2.1.2 under Ubuntu 12.04. I can make PppRouter and UDPEcho on telosb platform. Does blip and coap in tinyos 2.1.2 support micaz or iris platform?</div>
<div><br></div>
<div>&nbsp; &nbsp; There are errors if I make micaz under PppRouter dictionary and errors on other applications.&nbsp;</div>
<div><span><br></span></div>
<div><br></div>
<div><span>Ubuntu 12.04 &nbsp; &nbsp; MSP430-GCC 4.6.3 &nbsp; &nbsp;NESCC 1.3.5</span></div>
<div><table border="1" cellpadding="2" cellspacing="0">
<tr>
<td valign="top"><div><br></div></td>
<td valign="top"><div>telosb</div></td>
<td valign="top"><div>micaz</div></td>
<td valign="top"><div>iris</div></td>
<td valign="top"><div><br></div></td>
</tr>
<tr>
<td valign="top"><div>PppRouter</div></td>
<td valign="top"><div>OK</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div><br></div></td>
</tr>
<tr>
<td valign="top">UDPEcho</td>
<td valign="top"><div>OK</div></td>
<td valign="top"><div>OK</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div><br></div></td>
</tr>
<tr>
<td valign="top"><div>TCPEcho</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top">ERROR</td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div><br></div></td>
</tr>
<tr>
<td valign="top"><div>CoapBlip</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div>ERROR</div></td>
<td valign="top"><div><br></div></td>
</tr>
<tr>
<td valign="top"><div><br></div></td>
<td valign="top"><div><br></div></td>
<td valign="top"><div><br></div></td>
<td valign="top"><div><br></div></td>
<td valign="top"><div><br></div></td>
</tr>
</table></div>
<div><br></div>
<div>*************************************************************<span>*************************************************************</span>
</div>
<div><span><div>root <at> ubuntu:/opt/tinyos-2.1.2/apps/PppRouter# make micaz blip</div>
<div>[INFO] compiling PppRouterC to a micaz binary</div>
<div>nescc -o build/micaz/main.exe &nbsp;-Os -DRPL_ROUTING -DRPL_STORING_MODE -I../../tos/lib/net/rpl -I../../tos/lib/ppp -I../../tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -gcc=avr-gcc -Wnesc-all -fnesc-include=tos -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -fnesc-cfile=build/micaz/app.c -fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22 -DCC2420_HW_ACKNOWLEDGEMENTS -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I../../tos/lib/net/ -I../../tos/lib/printf/ -I../../tools/tinyos/c/blip/ -I../../tos/lib/net/blip/ -I../../tos/lib/net/blip/interfaces/ -I../../tos/lib/net/blip/nwprog/ -I../../tos/lib/net/blip/shell/ -I../../tos/lib/net/blip/serial/ -I../../tos/lib/net/blip/platform/ -I../../tos/lib/net/blip/icmp/ -I../../tos/lib/net/blip/dhcp/ -I../../tos/platforms/micaz -I../../tos/platforms/mica -I../../tos/platforms/micaz/chips/cc2420 -I../../tos/chips/cc2420 -I../../tos/chips/cc2420/alarm -I../../tos/chips/cc2420/control -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/link -I../../tos/chips/cc2420/lowpan -I../../tos/chips/cc2420/lpl -I../../tos/chips/cc2420/packet -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/spi -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/security -I../../tos/platforms/micaz/chips/at45db -I../../tos/platforms/mica2/chips/at45db -I../../tos/platforms/mica/chips/at45db -I../../tos/chips/at45db -I../../tos/chips/atm128 -I../../tos/chips/atm128/adc -I../../tos/chips/atm128/pins -I../../tos/chips/atm128/spi -I../../tos/chips/atm128/i2c -I../../tos/chips/atm128/timer -I../../tos/lib/timer -I../../tos/lib/serial -I../../tos/lib/power -I../../tos/lib/diagmsg -mmcu=atmega128 -fnesc-target=avr -fnesc-no-debug -DPLATFORM_MICAZ -Wall -Wshadow --param max-inline-insns-single=100000 -I../../tos/system -I../../tos/types -I../../tos/interfaces -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x53cdf274L -DIDENT_UIDHASH=0x67782f81L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring-check.xml PppRouterC.nc -lm &nbsp;../../tools/tinyos/c/blip/lib6lowpan/iovec.c ../../tools/tinyos/c/blip/lib6lowpan/in_cksum.c ../../tools/tinyos/c/blip/lib6lowpan/ip_malloc.c ../../tools/tinyos/c/blip/lib6lowpan/utility.c ../../tos/lib/net/blip/table.c</div>
<div>../../tos/system/LedC.nc:32:25: error: PlatformLed.h: No such file or directory</div>
<div>In file included from ../../tos/lib/ppp/PppC.nc:78,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/PppDaemonC.nc:56,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from PppRouterC.nc:16:</div>
<div>In component `LedC':</div>
<div>../../tos/system/LedC.nc:88: component PlatformLedC not found</div>
<div>../../tos/system/LedC.nc:89: no match</div>
<div>In file included from ../../tos/lib/timer/MuxAlarmMilli32C.nc:47,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/LcpAutomatonC.nc:72,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/LinkControlProtocolC.nc:89,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/PppDaemonC.nc:65,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from PppRouterC.nc:16:</div>
<div>In component `MuxAlarmMilli32C_':</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component AlarmMilli32C not found</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component `AlarmMilli32C' is not generic</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:56: no match</div>
<div>../../tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"</div>
<div>../../tos/chips/cc2420/link/PacketLinkC.nc:38:2: warning: #warning "*** USING PACKET LINK LAYER"</div>
<div>make: *** [exe] Error 1</div>
<div>root <at> ubuntu:/opt/tinyos-2.1.2/apps/PppRouter# make iris blip</div>
<div>[INFO] compiling PppRouterC to a iris binary</div>
<div>nescc -o build/iris/main.exe &nbsp;-Os -DRPL_ROUTING -DRPL_STORING_MODE -I../../tos/lib/net/rpl -I../../tos/lib/ppp -I../../tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -gcc=avr-gcc -Wnesc-all -fnesc-include=tos -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -fnesc-cfile=build/iris/app.c -fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22 -DCC2420_HW_ACKNOWLEDGEMENTS -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I../../tos/lib/net/ -I../../tos/lib/printf/ -I../../tools/tinyos/c/blip/ -I../../tos/lib/net/blip/ -I../../tos/lib/net/blip/interfaces/ -I../../tos/lib/net/blip/nwprog/ -I../../tos/lib/net/blip/shell/ -I../../tos/lib/net/blip/serial/ -I../../tos/lib/net/blip/platform/ -I../../tos/lib/net/blip/icmp/ -I../../tos/lib/net/blip/dhcp/ -I../../tos/platforms/iris -I../../tos/platforms/micaz -I../../tos/platforms/mica -I../../tos/platforms/iris/chips/rf230 -I../../tos/chips/rf230 -I../../tos/lib/rfxlink/layers -I../../tos/lib/rfxlink/util -I../../tos/platforms/iris/chips/at45db -I../../tos/platforms/mica2/chips/at45db -I../../tos/platforms/mica/chips/at45db -I../../tos/chips/at45db -I../../tos/platforms/iris/chips/ds2401 -I../../tos/platforms/mica2/chips/ds2401 -I../../tos/chips/ds2401 -I../../tos/chips/atm1281 -I../../tos/chips/atm1281/adc -I../../tos/chips/atm1281/timer -I../../tos/chips/atm128 -I../../tos/chips/atm128/adc -I../../tos/chips/atm128/pins -I../../tos/chips/atm128/spi -I../../tos/chips/atm128/i2c -I../../tos/chips/atm128/timer -I../../tos/lib/timer -I../../tos/lib/serial -I../../tos/lib/power -I../../tos/lib/diagmsg -mmcu=atmega1281 -fnesc-target=avr -fnesc-no-debug -DPLATFORM_IRIS -Wall -Wshadow --param max-inline-insns-single=100000 -I../../tos/system -I../../tos/types -I../../tos/interfaces -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x53cdf282L -DIDENT_UIDHASH=0x3a3c71e1L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/iris/wiring-check.xml PppRouterC.nc -lm &nbsp;../../tools/tinyos/c/blip/lib6lowpan/iovec.c ../../tools/tinyos/c/blip/lib6lowpan/in_cksum.c ../../tools/tinyos/c/blip/lib6lowpan/ip_malloc.c ../../tools/tinyos/c/blip/lib6lowpan/utility.c ../../tos/lib/net/blip/table.c</div>
<div>In file included from ../../tos/lib/timer/MuxAlarmMilli32C.nc:47,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/LcpAutomatonC.nc:72,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/LinkControlProtocolC.nc:89,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/ppp/PppDaemonC.nc:65,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from PppRouterC.nc:16:</div>
<div>In component `MuxAlarmMilli32C_':</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component AlarmMilli32C not found</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:55: component `AlarmMilli32C' is not generic</div>
<div>../../tos/lib/timer/MuxAlarmMilli32C_.nc:56: no match</div>
<div>In file included from ../../tos/lib/net/blip/IPNeighborDiscoveryC.nc:16,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from ../../tos/lib/net/blip/IPStackC.nc:47,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from PppRouterC.nc:43:</div>
<div>In component `IPAddressC':</div>
<div>../../tos/lib/net/blip/IPAddressC.nc:34: component Ieee154AddressC not found</div>
<div>../../tos/lib/net/blip/IPAddressC.nc:38: cannot find `Ieee154Address'</div>
<div>In component `IPNeighborDiscoveryC':</div>
<div>../../tos/lib/net/blip/IPNeighborDiscoveryC.nc:23: cannot find `Ieee154Address'</div>
<div>In file included from ../../tos/lib/net/blip/IPStackC.nc:48,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from PppRouterC.nc:43:</div>
<div>In component `IPDispatchC':</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:46: component Ieee154BareC not found</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:47: component RadioPacketMetadataC not found</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:59: cannot find `SplitControl'</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:60: cannot find `BarePacket'</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:61: cannot find `BareSend'</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:62: cannot find `BareReceive'</div>
<div>../../tos/lib/net/blip/IPDispatchC.nc:68: cannot find `PacketLink'</div>
<div>make: *** [exe] Error 1</div>
<div><br></div></span></div>
<div><span><br></span></div>
<div>*************************************************************<span>*************************************************************</span>
</div>
<br><div>--<br><div>
<span class="Apple-tab-span">	</span>Thanks for your attention.</div>
<div><br></div>
<div>Best regards.</div>
</div>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
Thomas Pötsch | 24 Jul 17:02 2014
Picon
Picon

msp430-gcc 4.6.3 increases image size

Hi all,

after upgrading from msp430-gcc 4.5.3 to 4.6.3 I noticed that the image size 
of PppRouter has increased by 1300 byte!! The same holds for other apps as 
well.
Am I doing something wrong or is this an issue of the new version of the 
compiler?

Best regards,
Thomas
Skander Bahloul | 24 Jul 09:44 2014
Picon

Problem exception in thread main java.long.NoClassDefFoundError:net/tinyos/sim/simdriver

Dear TinyOS community,

I try to run Tinyviz ( command ./tinyviz). I had this error:
exception in thread main java.lang.NoClassDefFoundError:net/tinyos/sim/simdriver

Could you help me please!

Best regards,


-----------------------------------------------------------------------------------
Skander BAHLOUL



<div>
<div>Dear TinyOS <span class="sac">community</span>,<br>
</div>
<div><br></div>
<div>I try to run Tinyviz ( command ./tinyviz). I had this error:<br>
</div>
<div>exception in thread main java.lang.NoClassDefFoundError:net/tinyos/sim/simdriver</div>
<div><br></div>
<div>Could you help me please!<br>
</div>
<div><br></div>
<div>Best regards,<br>
</div>
<div><br></div>
<div><br></div>
<div>-----------------------------------------------------------------------------------<br><span data-mce-style="color: #0000ff;">Skander BAHLOUL</span><br>
</div>
<div><br></div>
<div><br></div>
<div><br></div>
</div>
trung phạm | 23 Jul 14:51 2014
Picon

Tymo Dymo Create node

Hi !!

I have a problem , and i hope i will have some your advice

I can make telosb with dymonetworkC
and i use WSIM and WSNET to create 3 node 
I can send information 3 node together
But i want to see parameter , and what tools i can see that ?
Any idea for me ?

Thanks you so much !!
<div><div dir="ltr">
<span>Hi !!</span><br><br><span>I have a problem , and i hope i will have some your advice</span><br><br><div>I can make telosb with dymonetworkC</div>
<div>and i use WSIM and WSNET to create 3 node&nbsp;</div>
<div>I can send information 3 node together</div>
<div>But i want to see parameter , and what tools i can see that ?</div>
<div>Any idea for me ?<br><br>Thanks you so much !!</div>
</div></div>
Alex | 21 Jul 11:56 2014
Picon

tinyos2.1.2 & pppRouter


Hi,

    Has anyone successfully installed msp430-gcc version 4.6.3 or above and compiled PppRouter successfully?

    Which version of Ubuntu are you using?



--
Thanks for your attention.

Best regards.


<div>
<div>
<br><div>Hi,</div>
<div><br></div>
<div>&nbsp; &nbsp; Has anyone successfully installed msp430-gcc version 4.6.3 or above and compiled PppRouter successfully?</div>
<div><br></div>
<div>&nbsp; &nbsp; Which version of Ubuntu are you using?</div>
<br><br><br><div>--<br><div>
<span class="Apple-tab-span">	</span>Thanks for your attention.</div>
<div><br></div>
<div>Best regards.</div>
</div>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
Alex | 21 Jul 10:43 2014
Picon

ice-insight



Hi, 

Has anyone ever used ice-insight? I am using ice-insight and encountered a problem. 

I used avr jtagice mkii and input "ice-insight ./build/micaz/main.exe" and it replied:
************************************************************************************************************
$ ice-insight ./build/micaz/main.ihex
AVaRICE version 2.4, Jan  8 2007 16:54:40


Defaulting JTAG bitrate to 1 MHz. Make sure that the target
frequency is at least 4 MHz or you will likely encounter failures
controlling the target.


JTAG ICE communication failed: Inappropriate ioctl for device
************************************************************************************************************

It is very kind of you if you give me some hint on it.

--
Thanks for your attention.

Best regards.


<div>
<div>
<br><br><div>Hi,&nbsp;</div>
<div><br></div>
<div>Has anyone ever used ice-insight? I am using ice-insight and encountered a problem.&nbsp;</div>
<div><br></div>
<div>I used avr jtagice mkii and input "ice-insight ./build/micaz/main.exe" and it replied:</div>
<div>************************************************************************************************************</div>
<div>
<div>$ ice-insight ./build/micaz/main.ihex</div>
<div>AVaRICE version 2.4, Jan &nbsp;8 2007 16:54:40</div>
<div><br></div>
<div><br></div>
<div>Defaulting JTAG bitrate to 1 MHz. Make sure that the target</div>
<div>frequency is at least 4 MHz or you will likely encounter failures</div>
<div>controlling the target.</div>
<div><br></div>
<div><br></div>
<div>JTAG ICE communication failed: Inappropriate ioctl for device</div>
</div>
<div>************************************************************************************************************</div>
<div><br></div>It is very kind of you if you give me some hint on it.<br><br><div>--<br><div>
<span class="Apple-tab-span">	</span>Thanks for your attention.</div>
<div><br></div>
<div>Best regards.</div>
</div>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
Vinod Supnekar | 19 Jul 14:33 2014
Picon

Fwd: How to find parameters like THROUPUT, DELIVERY RATIO , EFFICIENCY with of AODV in TOSSIM



 In TOSSIM , i am not able to compare the results of AODV and modified AODV(paper reffered and implemented  by me).

  Everything is running fine!!!!

But to complete my thesis , i need to show factual results as you know more.

So , i request to you buddies to give me some idea about " How to find parameters like THROUPUT, DELIVERY RATIO ,EFFICIENCY with of AODV in TOSSIM ".

 It will be really helpful for me to complete my last 10 % work and  help in my submission.

Thank you.





--
Regards,

Vinod  Supnekar
MTech Software Engg.
VJTI.Mumbai.
Mob.9773583026.
<div><div dir="ltr">
<br><div class="gmail_quote"><div dir="ltr">
<div class="gmail_quote">
<br><div dir="ltr">&nbsp;In TOSSIM , i am not able to compare the results of AODV and modified AODV(paper reffered and implemented &nbsp;by me).<div>

<br><div>&nbsp; Everything is running fine!!!!</div>
<div><br></div>
<div>But to complete my thesis , i need to show factual results as you know more.</div>
<div><br></div>
<div>So , i request to you buddies to give me some idea about " How to find parameters like THROUPUT, DELIVERY RATIO ,EFFICIENCY with of AODV in TOSSIM ".<br clear="all"><div><br></div>
<div>
&nbsp;It will be really helpful for me to complete my last 10 % work and &nbsp;help in my submission.</div>

<div><br></div>
<div>Thank you.</div>
<span><span><div dir="ltr"><br></div></span></span>
</div>
</div>
</div>
</div>
<span><div>
<br>
</div></span>
</div></div>
<br><br clear="all"><div><br></div>-- <br><div dir="ltr">Regards,<div>
<br><div>Vinod &nbsp;Supnekar</div>
<div>MTech Software Engg.</div>
<div>VJTI.Mumbai.</div>

<div>Mob.9773583026.</div>
</div>
</div>
</div></div>

Gmane