Re: [Openbts-discuss] Bogus timestamp from JSONEventsClient

[Michael I. <mic...@ra...>]

Hi Simon,

I took a peek and think my change will fix your issue:
 - https://github.com/RangeNetworks/NodeManager/commit/8c8a6e8f7a93543b60b85cea9fb2b3479cd57584

I’m going to re-link OpenBTS to point to this update in NodeManager but, in the mean time, you can try changing that line manually in your environment to see if it resolves things.

Regards,
-Michael

> On Apr 5, 2016, at 7:29 PM, Neel Pandeya <nee...@et...> wrote:
> 
> Hello Simon Pålstam:
> 
> These timestamps that you're seeing could be the result of overruns, or maybe just of bad signed math, but I don't think they are USRP-related values, and they're not coming from UHD, as far as I can tell.
> 
> Do these strange timestamps occur just once or twice or infrequently, or regularly?
> 
> --Neel Pandeya
> 
> 
> > ---------- Forwarded message ----------
> > From: ​​​​Simon Pålstam <sim...@st...>
> > Date: 29 March 2016 at 05:28
> > Subject: [Openbts-discuss] Bogus timestamp from JSONEventsClient
> > To: ope...@li...
> >
> >
> > Hi I'm using JSONEventsClient to get physical measurements from OpenBTS but
> > I don't know how to interpret the timestamps I get. To me it seems to be an
> > overflow, is there anyone who has an idea what might cause this?
> >
> > This is what my measurements look like:
> >
> > {
> > "data" : {
> > "burst" : {
> > "RSSI" : -34.0095,
> > "RSSP" : -6.00945,
> > "actualMSPower" : 5,
> > "actualMSTimingAdvance" : 0,
> > "timingError" : -1.04978
> > },
> > "channel" : {
> > "ARFCN" : 120,
> > "IMSI" : "240078585304473",
> > "carrierNumber" : 0,
> > "timeslotNumber" : 1,
> > "typeAndOffset" : "TCH/F",
> > "uplinkFrameErrorRate" : 0.0585415
> > },
> > "reports" : {
> > "neighboringCells" : [],
> > "servingCell" : {
> > "RXLEVEL_FULL_dBm" : -48,
> > "RXLEVEL_SUB_dBm" : -48,
> > "RXQUALITY_FULL_BER" : 0.0028,
> > "RXQUALITY_SUB_BER" : 0
> > }
> > }
> > },
> > "name" : "PhysicalStatus",
> > "timestamp" : "18446744072250882950",
> > "version" : "0.1"
> > }
> >
> > The timestamp on the measurement is as you can see 18446744072250882950, and
> > the associated UNIX time is 1458830211.
> >
> > Thanks for any help
> >
> > /Simon
> >
> > ------------------------------------------------------------------------------
> > Transform Data into Opportunity.
> > Accelerate data analysis in your applications with
> > Intel Data Analytics Acceleration Library.
> > Click to learn more.
> > http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
> > _______________________________________________
> > Openbts-discuss mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openbts-discuss
> >
> >
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss