Menu
▾
▴
Re: [Openbts-discuss] UMTS Bad Waveform
|
From: Tim B. <tbl...@ou...> - 2015-02-12 22:19:42
|
Thanks Tom. I was able to get in and activate the notice logging to help troubleshoot the bad waveform issue (still ongoing even with the default configurations). The log contains a repeating message that I cannot make heads or tails out of. Here is a sample: NOTICE 139993601550080 14:17:35.5 UMTSCommon.cpp:112:FN: TIME RAN BACKWARDS: prevFN=1181 prev.sec=1423779455 usec=388059 currentFN=1164 now.sec=1423779455 usec=533998 deltaSec=0 deltaUSec=1203 elapsedUSec=1203 elapsedFrames=0 NOTICE 139993602615040 14:17:35.5 UMTSCommon.cpp:117:FN: basetime.sec=1423779455 usec=532795 NOTICE 139993601550080 14:17:35.5 UMTSCommon.cpp:117:FN: basetime.sec=1423779455 usec=532795 NOTICE 139993602615040 14:17:35.5 UMTSCommon.cpp:118:FN: prevdeltaSec=0 prevdeltaUSec=175178 prevelapsedUSec=175178 prevelapsedFrames=17 NOTICE 139993601550080 14:17:35.5 UMTSCommon.cpp:118:FN: prevdeltaSec=0 prevdeltaUSec=175178 prevelapsedUSec=175178 prevelapsedFrames=17 NOTICE 139993602615040 14:17:35.5 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1164 newFN=1211 diff=-47 BaseTime.sec=1423779455 .usec=535618 t=1423779455.54 NOTICE 139993601550080 14:17:35.5 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 47 frames fnbefore=1164 mPrevWriteTime=0:1135 fnafter=1211 NOTICE 139993601550080 14:17:35.6 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 14 frames fnbefore=1213 mPrevWriteTime=0:1215 fnafter=1227 NOTICE 139993602615040 14:17:35.6 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1227 newFN=1264 diff=-37 BaseTime.sec=1423779455 .usec=697310 t=1423779455.70 NOTICE 139993602615040 14:17:35.8 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1279 newFN=1264 diff=15 BaseTime.sec=1423779455 .usec=852629 t=1423779455.85 NOTICE 139993602615040 14:17:36.1 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1292 newFN=1264 diff=28 BaseTime.sec=1423779456 .usec=137444 t=1423779456.14 NOTICE 139993602615040 14:17:36.1 UMTSCommon.cpp:112:FN: TIME RAN BACKWARDS: prevFN=1292 prev.sec=1423779456 usec=137443 currentFN=1264 now.sec=1423779456 usec=143018 deltaSec=0 deltaUSec=5574 elapsedUSec=5574 elapsedFrames=0 NOTICE 139993602615040 14:17:36.5 UMTSCommon.cpp:117:FN: basetime.sec=1423779456 usec=137444 NOTICE 139993602615040 14:17:36.5 UMTSCommon.cpp:118:FN: prevdeltaSec=1 prevdeltaUSec=4294252110 prevelapsedUSec=284814 prevelapsedFrames=28 NOTICE 139993602615040 14:17:36.5 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1264 newFN=1311 diff=-47 BaseTime.sec=1423779456 .usec=533232 t=1423779456.53 NOTICE 139993601550080 14:17:36.5 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 47 frames fnbefore=1264 mPrevWriteTime=0:1265 fnafter=1311 NOTICE 139993601550080 14:17:37.0 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 50 frames fnbefore=1313 mPrevWriteTime=0:1315 fnafter=1363 NOTICE 139993602615040 14:17:37.5 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1410 newFN=1364 diff=46 BaseTime.sec=1423779457 .usec=532174 t=1423779457.53 NOTICE 139993601550080 14:17:37.5 UMTSCommon.cpp:112:FN: TIME RAN BACKWARDS: prevFN=1410 prev.sec=1423779457 usec=532174 currentFN=1364 now.sec=1423779457 usec=532479 deltaSec=0 deltaUSec=305 elapsedUSec=305 elapsedFrames=0 NOTICE 139993602615040 14:17:37.5 UMTSCommon.cpp:112:FN: TIME RAN BACKWARDS: prevFN=1410 prev.sec=1423779457 usec=532174 currentFN=1364 now.sec=1423779457 usec=533663 deltaSec=0 deltaUSec=1489 elapsedUSec=1489 elapsedFrames=0 NOTICE 139993601550080 14:17:37.5 UMTSCommon.cpp:117:FN: basetime.sec=1423779457 usec=532174 NOTICE 139993602615040 14:17:37.5 UMTSCommon.cpp:117:FN: basetime.sec=1423779457 usec=532174 NOTICE 139993601550080 14:17:37.5 UMTSCommon.cpp:118:FN: prevdeltaSec=0 prevdeltaUSec=460259 prevelapsedUSec=460259 prevelapsedFrames=46 NOTICE 139993602615040 14:17:37.5 UMTSCommon.cpp:118:FN: prevdeltaSec=0 prevdeltaUSec=460259 prevelapsedUSec=460259 prevelapsedFrames=46 NOTICE 139993602615040 14:17:37.5 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1364 newFN=1411 diff=-47 BaseTime.sec=1423779457 .usec=536198 t=1423779457.54 NOTICE 139993601550080 14:17:37.5 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 47 frames fnbefore=1364 mPrevWriteTime=0:1365 fnafter=1411 NOTICE 139993601550080 14:17:37.9 UMTSL1CC.cpp:1676:l1WaitToSend: waitToSend waited 34 frames fnbefore=1413 mPrevWriteTime=0:1415 fnafter=1447 NOTICE 139993602615040 14:17:37.9 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1450 newFN=1464 diff=-14 BaseTime.sec=1423779457 .usec=926933 t=1423779457.93 NOTICE 139993602615040 14:17:38.1 UMTSCommon.cpp:85:setFN: clock set FN: oldFN=1482 newFN=1464 diff=18 BaseTime.sec=1423779458 .usec=107219 t=1423779458.11 NOTICE 139993602615040 14:17:38.1 UMTSCommon.cpp:112:FN: TIME RAN BACKWARDS: prevFN=1482 prev.sec=1423779458 usec=107219 currentFN=1471 now.sec=1423779458 usec=187172 deltaSec=0 deltaUSec=79953 elapsedUSec=79953 elapsedFrames=7 ------------------------------ > Date: Thu, 12 Feb 2015 11:56:16 -0800 > Subject: Re: [Openbts-discuss] UMTS Bad Waveform > From: to...@ts... > To: tbl...@ou... > > The master configuration is a sqlite3 database file in the following location. > > '/etc/OpenBTS/OpenBTS-UMTS.db' > > You can view and modify it manually with the sqlite manipulator of > your choice. There's few browsers out there. I personally use > sqlitebrower, but that's mainly because it's readily available more so > than being an actual preference. > > -TT > > On Thu, Feb 12, 2015 at 11:40 AM, Tim Blake <tbl...@ou...> wrote: > > Tom, > > > > Is there a way to manually change the config? The node isn't even launching > > now and the CLI is no help without it running. It's either manually > > changing the config or reverting back to an original install at this point. > > > > Tim > > > > > > ------------------------------ > > > >> Date: Thu, 12 Feb 2015 11:26:19 -0800 > >> Subject: Re: [Openbts-discuss] UMTS Bad Waveform > >> From: to...@ts... > >> To: tbl...@ou... > >> CC: ope...@li... > >> > >> On Thu, Feb 12, 2015 at 11:09 AM, Tim Blake <tbl...@ou...> wrote: > >> > I have verified that with the default band and UARFCN settings, the > >> > waveform > >> > looks correct. However, changing the band and channel via devconfig > >> > results > >> > in incorrect waveform production. > >> > >> OK. I didn't think about the general configuration failing. Was there > >> really no feedback in an error message (or assertion failure)? > >> > >> -TT |
