Hi! On Mon, 19 Jan 2009, [email protected] wrote:
> Hey, > > I also will try your solution Razvan. Although i think that, some of > this information should be on wiki: > -battery level I added this to the wiki. > -CFLAGS=-DDELUGE_LIGHT_BASESTATION with GoldenImage (maybe its there but > i didn't realized at that time) > -components LedsC; > DelugeC.Leds -> LedsC; I committed these changes in the tree. :-) All the best! Razvan ME >> Hi! >> >> On Mon, 19 Jan 2009, Pratik Gupte wrote: >> >> >>> Hi Razvan, >>> >>> Sorry for the confusion. I'm using the latest version of deluge >>> and TinyOS 2.x from the tinyos CVS on linux (Ubuntu 8.04). I'm >>> re-writing down exactly whatever I have tried: >>> >>> Setting up the basestation (mote 0) >>> /opt/tinyos-2.x/apps/tests/deluge/Basestation >>> >>> make telosb install,0 bsl,/dev/ttyUSB0 >>> >>> Similarly I setup the client node (mote 1) with the Golden Image. >>> >> >> The DELUGE_LIGHT_BASESTATION is disabled in the Makefile from GoldenImage >> so you will not be able to ping the node. >> >> >>> Then I again connect mote 0 and transfer a Blink app with DelugeC >>> component and the Makefile with BOOTLOADER=tosboot >>> then >>> make telosb >>> >> >> The Blink from apps/tests/deluge also has the DELUGE_LIGHT_BASESTATION >> disabled in the Makefile so the mote that will reboot in this image will >> not respond to ping. >> >> >>> then I transfer the above image to mote 0 using >>> tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml >>> >>> Everything works fine and even >>> tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows the Currently running >>> BaseStationAppC and BlinkAppC (stored image 1) as the other volume >>> >>> I power on mote 1 now with batteries and type the following command >>> >>> tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 >>> Command Sent >>> >>> Mote 1 does nothing and it doesn't boot up with the Blink app. >>> >> >> I just verify that the node id works fine. Here is the manual steps: >> >> - plug a mote in ttyUSB0 and burn the deluge/Basestation on it: >> make telosb install,0 >> >> - plug another mote in ttyUSB1 and burn the deluge/GoldenImage with the >> DELUGE_LIGHT_BASESTATION enabled: >> CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install,10 >> bsl,/dev/ttyUSB1 >> >> - compile deluge/Blink with DELUGE_LIGHT_BASESTATION enabled: >> CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install >> >> - upload the deluge/Blink to Basestation: >> tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml >> >> - start the dissemination-and-reboot: >> tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 >> >> - after the dissemination is over the mote on ttyUSB1 will blink. To >> make sure it has the expected node id you have to ping it: >> tos-deluge serial@/dev/ttyUSB1:115200 -p 1 >> >> >> >>> Just to check what Mote 1 has I repeated the above steps and compiled >>> the GoldenImage with CFLAGS=-DDELUGE_BASESTATION for Mote 1 also and >>> finally the command >>> >> >> A mote with DELUGE_BASESTATION will behave as a client. >> >> >>> tos-deluge serial@/dev/ttyUSB0:115200 -p 1 >>> shows only the GoldenImage on Mote 1. >>> >>> 2nd Attempt on the steps on the mail archive >>> http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026204.html >>> Replicating the above steps appropriately, I get the same error as in >>> the above mail and as described as above, i.e. Mote 1 does not receive >>> the new version. >>> >> >> The error you indicate will happen when you try to ping a mote that >> is not compiled with DELUGE_BASESTATION or DELUGE_LIGHT_BASESTATION. I'll >> add some code to print a better message for this. >> >> >>> By "node in air" I meant about the nodes connected through batteries >>> and expecting the disseminated code from the base station. >>> >> >> One more thing: make sure the voltage of the batteries is above 2.7V. A >> mote will not reboot if the voltage is lower than that. >> >> And one last thing: the GoldenImage doesn't have any leds enabled so the >> progress of Deluge will not be indicated in any way. You can enabled them >> by adding the following lines to the GoldenImageAppC.nc: >> >> components LedsC; >> DelugeC.Leds -> LedsC; >> >> All the best! >> Razvan ME >> >> >>> On Mon, Jan 19, 2009 at 1:49 PM, Razvan Musaloiu-E. <[email protected]> >>> wrote: >>> >>>> Hi! >>>> >>>> On Mon, 19 Jan 2009, Pratik Gupte wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> Even I'm facing the same problem with both telosb and micaz motes as per >>>>> instructions on http://docs.tinyos.net/index.php/Deluge_T2 and >>>>> unfortunately >>>>> there were no replies to this post. >>>>> >>>>> Also while going through the tinyos mailing list archives on problem on >>>>> dissemination of deluge T2 >>>>> http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, >>>>> I tried to reproduce the steps in the archive, replacing appropriately >>>>> commands for micaz and mib520 board - >>>>> >>>>> I face the same problem (as the problem in the archive)- Base Station has >>>>> Version 1, but after dissemination the node in air still has version 0. >>>>> >>>>> >>>> I'm a little confused about what doesn't work. What does "node in air" >>>> means? :-) Also: do you have the problem in Windows or Linux? >>>> >>>> I'll retest tomorrow the burn and burn-net. >>>> >>>> -- >>>> Razvan ME >>>> >>>> >>>>> On Mon, Jan 5, 2009 at 6:09 PM, <[email protected]> wrote: >>>>> >>>>> >>>>>> Hey everyone, >>>>>> >>>>>> I've been following the deluge t2 tutorial in wiki, and when i'm trying >>>>>> to disseminate, this problem occurs: >>>>>> >>>>>> Traceback (most recent call last): >>>>>> File "/usr/local/bin/tos-deluge", line 405, in <module> >>>>>> ident(timeout=5) >>>>>> File "/usr/local/bin/tos-deluge", line 153, in ident >>>>>> if am.write(sreqpkt, FM_AMID, timeout=timeout): >>>>>> File "C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py", line 440, in >>>>>> write >>>>>> r = super(AM, self).write(packet, amId, timeout, blocking) >>>>>> File "C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py", line 398, in >>>>>> write >>>>>> return ack.seqno == self.seqno >>>>>> UnboundLocalError: local variable 'ack' referenced before assignment >>>>>> >>>>>> Even though the Windows path have the slashes backwards it still reads >>>>>> the files. >>>>>> >>>>>> I'm using micaz motes, gateway mib520. >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> >>>>>> >>>>>> >> > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
