From: Dimitar P. <dp...@sw...> - 2010-12-09 12:32:09
|
Hi Guys, Another basic question, sorry about that. I am testing example-runicast with the unicast layer debug enabled and I see (at the receiver mote) System online. 1.0: uc: recv_from_broadcast, receiver 1.0 1.0: unicast_send to 2.17 1.0: uc: sent_by_broadcast, receiver 2.17 runicast message received from 2.17: MyString, seqno 0 1.0: uc: recv_from_broadcast, receiver 1.0 1.0: unicast_send to 2.17 1.0: uc: sent_by_broadcast, receiver 2.17 runicast message received from 2.17: MyString, seqno 1 1.0: uc: recv_from_broadcast, receiver 1.0 1.0: unicast_send to 2.17 1.0: uc: sent_by_broadcast, receiver 2.17 runicast message received from 2.17: MyString, seqno 2 1.0: uc: recv_from_broadcast, receiver 1.0 1.0: unicast_send to 2.17 1.0: uc: sent_by_broadcast, receiver 2.17 runicast message received from 2.17: MyString, seqno 3 1.0: uc: recv_from_broadcast, receiver 1.0 1.0: unicast_send to 2.17 1.0: uc: sent_by_broadcast, receiver 2.17 runicast message received from 2.17: MyString, seqno 0 ... I have verified that the confirmation is happening properly at runicast level. (at the transmitter mote we get) System online. 2.17: sending runicast to address 1.0 2.17: runicast: sending packet 0 2.17: unicast_send to 1.0 2.17: uc: sent_by_broadcast, receiver 1.0 runicast: sent_by_stunicast c->rxmit 0 num_tx 1 2.17: runicast: sent_by_stunicast packet 0 (0) resent 1 2.17: uc: recv_from_broadcast, receiver 2.17 2.17: runicast: recv_from_stunicast from 1.0 type 1 seqno 0 2.17: runicast: got ACK from 1.0, seqno 0 (0) 2.17: runicast: ACKed 0 runicast message sent to 1.0, retransmissions 1 ... I am confused about the seqno which is cycling 0, 1, 2, 3, 0, 1 ... How should I interpret this number? Is this just a packet number and having nothing to do with the runicast retransmissions? Best Regards Dimitar ----- Original Message ----- From: "Dimitar Penev" <dp...@sw...> To: "Contiki developer mailing list" <con...@li...> Sent: Thursday, December 09, 2010 1:11 PM Subject: Re: [Contiki-developers] sniffer using ATZB-24-A2 ? > Hi David, > > Thank you for the suggestions! I am going to check what will suit us best. > > A quick note. Testing runicast example I have enabled debug at > core/net/rime/unicast.c > and I am getting: > > 1.0: uc: recv_from_broadcast, receiver 1.0 > 1.0: unicast_send to 2.17 > 1.0: uc: recv_from_broadcast, receiver 2.17 > runicast message received from 2.17: MyString, seqno 0 > > The 3rd line doesn't looks logical to me and I saw in the code > "recv_from_broadcast" > instead of "sent_by_broadcast" which is probably a typo in the svn trunk? > > /*---------------------------------------------------------------------------*/ > static void > sent_by_broadcast(struct broadcast_conn *broadcast, int status, int > num_tx) > { > struct unicast_conn *c = (struct unicast_conn *)broadcast; > > PRINTF("%d.%d: uc: recv_from_broadcast, receiver %d.%d\n", > ... > > BTW can you guys suggest good book explaining the radio protocol stuff > around Contiki? > > Best Regards > Dimitar Penev > > > ----- Original Message ----- > From: "David Kopf" <da...@em...> > To: "Dimitar Penev" <dp...@sw...>; "Contiki developer mailing > list" > <con...@li...> > Sent: Wednesday, December 08, 2010 6:42 PM > Subject: Re: [Contiki-developers] sniffer using ATZB-24-A2 ? > > >> Hi >> >> A quick way to see packets is to print them out in the radio driver >> (look for DEBUG>1 in rf230bb.c). You can enable debug in any of the core >> net routines like tcp, uip, nd6, sicslowmac but change the printf >> definitions to keep the strings from filling RAM: >> #include <avr/pgmspace.h> >> #define PRINTF(FORMAT,args...) printf_P(PSTR(FORMAT),##args) >> >> A real sniffer with Wireshark would give you dissectors for all the >> protocols, saving a lot of time. I don't know of any AVR platforms that >> have a serial tunslip interface. I use the Raven USB stick with 15DOT4 >> tools. I think the econotag sniffer uses a serial interface, I have not >> tried it yet. >> >> >> On Wed, 2010-12-08 at 16:54 +0200, Dimitar Penev wrote: >>> Hi Guys, >>> >>> We have just manage to exchange some packets between two avr-zigbit >>> modules >>> (ATZB-24-A2) using example-unicast >>> Really exciting stuff :) >>> >>> Can we somehow implement a snifer using ATZB-24-A2 hardware (using >>> serial >>> interface for printing) so we see what is going on at the lower layers? >>> Probably there is a ready made code we can use? >> >> >> > > > ------------------------------------------------------------------------------ > This SF Dev2Dev email is sponsored by: > > WikiLeaks The End of the Free Internet > http://p.sf.net/sfu/therealnews-com > _______________________________________________ > Contiki-developers mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/contiki-developers > |