Thanks for your quick reply, I've tried to patch CsmaCA802_15_4::canProceed method, but the problem isn't disappeared.
I've noticed that the problem is present only on SCS802_15_4::startDevice method and not in SSCS802_15_4::startPANCoord method. In addition there are little different between these methods, so I've tried to modify SCS802_15_4::startDevice method, replacing: scan_BO = sscsTaskP.startDevice_BO + 1; with: scan_BO = sscsTaskP.startDevice_BO; In this way output error vanishes but I'm not really sure that this is a true solution because I don't have deeply studied code yet Best regards. Busanelli Stefano Il giorno gio, 22/03/2007 alle 09.35 -0400, Ahmad Khayyat ha scritto: > This reminds me about a bug in the original wpan implementation. Not > sure if it is fixed in Iyappan patch as I am using ns-2.29. > > In the method: > bool CsmaCA802_15_4::canProceed(double wtime, bool afterCCA) > > The following declaration exists: > > UINT_16 t_bPeriods,t_CAP; > > For large BO/SO values, UINT_16 is insufficient. I replaced it with > UINT_32 and many problems with large BO/SO values were resolved. I used > to get poor delivery ratio but now it is reasonable. > I have no idea whether this has anything to do with your problem, but > you might want to give it a try. There is a good chance it does. Make > sure you update the type casts related to these two variables in this > method, too. > > - Ahmad > > > On Thu, 22 Mar 2007 10:47:37 +0100 > Stefano Busanelli <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > > I'm using ns-allinone-2.31 package, that includes 802.15.4 > > implementation made by Zheng subsequently patched by Iyappan. > > > > If I set to 14 both Beacon Order (BO) and Superframe Order (SO) values > > of a generic device (not coordinator), ns returns this error message: > > > > <!>[0.300000](node 1) unable to start as a device: active channel scan > > failed - > > > > This happens using scss methods and independently from the values > > assumed by others flags, like "assoPermit" or "isFFD". > > > > Instead if I set BO=14 and SO=13, all works well. > > > > Am i making some mistakes or the "legal" pair (BO=14,SO=14) is not > > admitted in current implementation of 802.15.4? > > > > I'm looking forward to receive your prompt reply. > > > > Best regards > > > > Busanelli Stefano > >
