I would get things working without lpl, and then compute your power
budget.  It really depends on the application whether that's a good
idea.

On Fri, Mar 2, 2012 at 1:03 PM, Alex FP <[email protected]> wrote:
> Dear  Stephen.
>
> Thanks for your clarification, now I understand better the way of working of
> Blip 2.0.
>
> Then, for the moment is no way to know where is passing the packets.
>
> One question more. What would you recommend to me  in order to save battery
> energy. I mean, only putting this line in the makefile?:
>
> CFLAGS += -DCC2420_LOW_POWER_LISTENING
> CFLAGS += -DLOW_POWER_LISTENING -DLPL_DUTY_PERIOD=0
>
> Or must I have other consideration for RPL?
>
>
>
> Thanks a lot for your support again.
>
> Yours faithfully,
>
> Alex
>
> On Thu, Mar 1, 2012 at 7:45 PM, Stephen Dawson-Haggerty
> <[email protected]> wrote:
>>
>> Hi Alex -- I disabled traceroute in this version of blip -- the motes
>> don't send the ICMP time exceeded messages which are necessary for it.
>>  Two reasons -- (1) sometimes routing loops lead to a lot of dropped
>> packets and so a lot of errors, which just make things works, and (2)
>> I didn't want to use the code space.  Sorry about that!
>>
>> Best,
>> Steve
>>
>> On Thu, Mar 1, 2012 at 7:57 AM, Alex FP <[email protected]> wrote:
>> > Dear John.
>> >
>> > Thanks for you support, I appreciate so much your help.
>> >
>> >
>> > I am using the UDPEcho app + Ppproute app , and until this moment I've
>> > testing with two hops (from fec0::100 to fec0::4)
>> >
>> >
>> > PC(fec0::100)-->node1(fec0::1,sink_node)-->node7(fec0::7)-->node4(fec0::4);
>> > fec0::100 and fec0::1 with USB connection.
>> >
>> > This test is in a considerable distance, I am making pings to fec0::4
>> > and I
>> > am getting the reply from it; and when  the node7 is removed, which is
>> > in
>> > the middle (fec0::7) the communication is lost.
>> >
>> > But I don't understand why when in the PC write the  traceroute6 command
>> > don't appears each node where pass the packets?
>> >
>> >
>> >
>> > root@acp:/opt/tinyos-2.x.svn/apps# tracert6 fec0::4
>> > traceroute to fec0::4 (fec0::4) from fec0::100, 30 hops max, 60 byte
>> > packets
>> >  1  * * *
>> >  2  * * *
>> >  3  fec0::4 (fec0::4)  97.768 ms  * 83.826 ms
>> >
>> >
>> >
>> > root@acp:/opt/tinyos-2.x.svn/apps# tracert6 fec0::7
>> >
>> > traceroute to fec0::7 (fec0::7) from fec0::100, 30 hops max, 60 byte
>> > packets
>> >  1  * * *
>> >  2  * * fec0::7 (fec0::7)  57.774 ms
>> >  3  fec0::7 (fec0::7)  61.834 ms  * 56.148 ms
>> >
>> >
>> > I am doing something bad or must use other command?
>> >
>> >
>> > Yours faithfully,
>> >
>> > Alex
>> >
>> >
>> >
>> > On Wed, Feb 29, 2012 at 9:42 PM, JeongGil Ko <[email protected]> wrote:
>> >>
>> >> Alex,
>> >>
>> >> Looks like you are on the right page :)
>> >>
>> >> -John
>> >>
>> >> ------
>> >> JeongGil Ko
>> >> Ph.D. Candidate
>> >> Department of Computer Science
>> >> Johns Hopkins University
>> >> http://www.cs.jhu.edu/~jgko
>> >>
>> >> On Feb 29, 2012, at 3:26 PM, Alex FP wrote:
>> >>
>> >> > Dear John.
>> >> >
>> >> > Thanks again for your answer.
>> >> >
>> >> > I was checking UDPEchoC.nc and appears:
>> >> > .....
>> >> > #ifdef RPL_ROUTING
>> >> >   components RPLRoutingC;
>> >> > #endif
>> >> > ....
>> >> >
>> >> > Also in its  UDPEchoC's Makefile.  Here is specified is using  RPL,
>> >> > and
>> >> > is enable with this line:
>> >> >
>> >> > PFLAGS += -DRPL_ROUTING -DRPL_STORING_MODE -I$(TOSDIR)/lib/net/rpl
>> >> >
>> >> > Then, must I understand is working y default the RPL? But before this
>> >> > must I add to the UDPEcho's Makefile this:
>> >> >
>> >> > CFLAGS+=-DRPL_ROOT_ADDR=3
>> >> >
>> >> > Where 3 is the ID of the mote that is installed the Ppproute app on
>> >> > it.
>> >> >
>> >> > .. And also make match the channels in both Ppproute's Makefile and
>> >> > UDPEcho's  Makefile  (for telosb), for example:
>> >> >
>> >> > CFLAGS += -DCC2420_DEF_CHANNEL=25
>> >> >
>> >> > All this is correct?
>> >> >
>> >> >
>> >> > Best regards,
>> >> >
>> >> > Alex.
>> >>
>> >
>> >
>> > _______________________________________________
>> > Tinyos-help mailing list
>> > [email protected]
>> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>>
>>
>> --
>> stephen dawson-haggerty
>> http://cs.berkeley.edu/~stevedh
>> uc berkeley wireless and embedded systems lab
>> berkeley, ca 94720
>
>



-- 
stephen dawson-haggerty
http://cs.berkeley.edu/~stevedh
uc berkeley wireless and embedded systems lab
berkeley, ca 94720

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to