Could there be a timing issue when waiting for Acks? It might be that the telos responds a little slower and the iris gives up waiting too soon -- if I have the order of execution right anyway...
MS Urs Hunkeler wrote: > Hi Miklos, > > I repeated the tests. Here are the results. > > Cheers, > Urs > > > > ------------------------------------- > > TelosB -> TelosB (working): > 15:55:40 "rx" 33509947 21696 0 14 [ 0x61 0x88 0x00 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:55:40 "rx" 33511595 23088 0 5 [ 0x02 0x00 0x00 ] > 15:55:41 "rx" 34430793 25039 0 14 [ 0x61 0x88 0x01 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:55:41 "rx" 34432441 26446 0 5 [ 0x02 0x00 0x01 ] > 15:55:42 "rx" 35350148 26890 0 14 [ 0x61 0x88 0x02 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:55:42 "rx" 35351796 28282 0 5 [ 0x02 0x00 0x02 ] > 15:55:43 "rx" 36272035 31274 0 14 [ 0x61 0x88 0x03 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:55:43 "rx" 36273684 32666 0 5 [ 0x02 0x00 0x03 ] > 15:55:44 "rx" 37198957 40691 0 14 [ 0x61 0x88 0x04 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:55:44 "rx" 37200606 42084 0 5 [ 0x02 0x00 0x04 ] > > TelosB -> Iris (working): > 15:57:42 "rx" 145352641 59712 0 5 [ 0x02 0x00 0x00 ] > 15:57:43 "rx" 146272720 62550 0 14 [ 0x61 0x88 0x01 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:57:43 "rx" 146273487 63055 0 5 [ 0x02 0x00 0x01 ] > 15:57:44 "rx" 147192075 64402 0 14 [ 0x61 0x88 0x02 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:57:44 "rx" 147192843 64907 0 5 [ 0x02 0x00 0x02 ] > 15:57:45 "rx" 148113963 3249 0 14 [ 0x61 0x88 0x03 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:57:45 "rx" 148114731 3754 0 5 [ 0x02 0x00 0x03 ] > 15:57:46 "rx" 149040857 12639 0 14 [ 0x61 0x88 0x04 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:57:46 "rx" 149041624 13144 0 5 [ 0x02 0x00 0x04 ] > 15:57:47 "rx" 149964826 19104 0 14 [ 0x61 0x88 0x05 0x22 0x00 0x00 0x00 > 0x01 0x00 0x3f 0x34 0x01 ] > 15:57:47 "rx" 149965593 19609 0 5 [ 0x02 0x00 0x05 ] > > Iris -> TelosB (not working): > 5:58:17 "rx" 178146566 20364 0 14 [ 0x41 0x88 0x51 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:18 "rx" 179076190 32484 0 14 [ 0x61 0x88 0x52 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:18 "rx" 179077820 33860 0 5 [ 0x02 0x00 0x52 ] > 15:58:19 "rx" 179996770 35560 0 14 [ 0x61 0x88 0x53 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:19 "rx" 179998401 36935 0 5 [ 0x02 0x00 0x53 ] > 15:58:20 "rx" 180915155 36441 0 14 [ 0x61 0x88 0x54 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:20 "rx" 180916787 37817 0 5 [ 0x02 0x00 0x54 ] > 15:58:21 "rx" 181833949 37732 0 14 [ 0x61 0x88 0x55 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:21 "rx" 181835580 39108 0 5 [ 0x02 0x00 0x55 ] > 15:58:22 "rx" 182756735 43014 0 14 [ 0x61 0x88 0x56 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:58:22 "rx" 182758368 44391 0 5 [ 0x02 0x00 0x56 ] > > Iris -> Iris (working): > 15:59:49 "rx" 262660345 58240 0 14 [ 0x41 0x88 0x51 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:50 "rx" 263589969 4824 0 14 [ 0x61 0x88 0x52 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:50 "rx" 263590737 5328 0 5 [ 0x02 0x00 0x52 ] > 15:59:51 "rx" 264510550 7901 0 14 [ 0x61 0x88 0x53 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:51 "rx" 264511318 8405 0 5 [ 0x02 0x00 0x53 ] > 15:59:52 "rx" 265428936 8783 0 14 [ 0x61 0x88 0x54 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:52 "rx" 265429704 9287 0 5 [ 0x02 0x00 0x54 ] > 15:59:53 "rx" 266347730 10073 0 14 [ 0x61 0x88 0x55 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:53 "rx" 266348498 10577 0 5 [ 0x02 0x00 0x55 ] > 15:59:54 "rx" 267270519 15356 0 14 [ 0x61 0x88 0x56 0x22 0x00 0x00 0x00 > 0x05 0x00 0x3f 0x34 0x05 ] > 15:59:54 "rx" 267271285 15862 0 5 [ 0x02 0x00 0x56 ] > > ------------------------------------- > > > Miklos Maroti wrote: >> Dear Urs, >> >> This is very strange. Can you program a second IRIS mote with the >> apps/tests/rf230/RF230Sniffer program to record all communications and >> dump that to a PC? Just upload it, connect it to a PC and on the PC >> run the java net.tinyos.util.DiagMsg command? You can specify the >> communication port in the usual format with -comm <source>. This will >> dump all traffic to the console together with microsecond precision >> timestamps. >> >> Would be nice to compare the message traces of the 4 setups. >> >> Best, >> Miklos >> >> On Wed, Apr 22, 2009 at 3:18 PM, Urs Hunkeler <[email protected]> wrote: >>> Hi, >>> >>> I have written a very simple test app to verify the proper operation of >>> the acknowledgment mechanism in TinyOS (see below). The program running >>> on a mote with an ID > 0 sends every second a packet to the mote 0 and >>> toggles LED 0. If it receives an Ack, it also toggles LED 1. It appears >>> that: >>> >>> TelosB -> TelosB: ack received >>> TelosB -> Iris : ack received >>> Iris -> Iris : ack received >>> >>> But: >>> Iris -> TelosB: NO ack >>> >>> Is there an incompatibility between the two chips? Any other known >>> issues? Ideas on how to solve this problem? >>> >>> Cheers, >>> Urs > > > _______________________________________________ > 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
