Check openbsc.cfg
auth policy accept-all
Thanks fro replying @skyinlife.
I already run it with accept-all. Here’s a snippet of network config from my openbsc.cfg
https://pastebin.com/kbzN6JP8
I think the issue may be with osmo-trx where I see some Receive Error Alerts. Looking like this:
https://pastebin.com/isPMY4Ad
Try it
wget sourceforge.net/projects/libdbi-drivers/files/libdbi-drivers/libdbi-drivers-0.8.3
tar -xvzf libdbi-drivers-0.8.3.tar.gz
cd libdbi-drivers-0.8.3
vi drivers/sqlite3/dbd_sqlite3.c
Edit _dbi_internal_error_handler => _dbd_internal_error_handler
./autogen.sh
./configure --disable-docs --with-sqlite3 --with-sqlite3-dir=/usr/bin --with-dbi-incdir=/usr/local/include
make
make install
ldconfig
After remake all
73, de UT0VA
@skyinlife thanks for trying to help.
I built the driver but there were a few errors, for example:
drivers/sqlite3/dbd_sqlite3.c line 273:
int dbd_goto_row(dbi_result_t *result, unsigned long long rowidx)
but
/usr/include/dbi/dbd.h
defines the same function (line 42) as
int dbd_goto_row(dbi_result_t *result, unsigned long long rowidx, unsigned long long currowidx);
If we read the c code in dbd_sqlite3.c line 273
int dbd_goto_row(dbi_result_t *result, unsigned long long rowidx, unsigned long long currowidx) {
result->currowidx = rowidx;
return 1;
}
it looks like it assigns rowidx to currowidx, which is already expected to be a member of a “result” class, so I don’t understand why we have to ask for it on the input side.
May be there is a version mismatch or something, I don’t know… Just including it in in C file function to match the header definition allows make to complete without errors but than “make check” fails.
So, I am kind of lost at this point.
What makes me wonder is that osmo-trx terminal shows zero activity on any phone trying to register. It’s almost as if the phone does not even want to to register to “Test PLMN 1-1” or LimeSDR receiver is totally deaf. May be there is some network white-listing on the phone, or something else…
I’ll try a few other things if nothing works I’ll try it with OpenBSC.
73!
ps. I had some fun time working from UB4IZA club back in the 90s. 
1 Like
Hm…
wrong antenna on RX input maybe ?
I am just using a rubber-duckie from 440 Mhz hand-held radio for both Tx and Rx on LimeSDR, not ideal but that’s the best I have and the phone is like a a meter away from Rx antenna.
If someone could share (copy in pastebin) their terminal outputs from osmo-nitb, osmo-bts-trx, and osmo-trx from the moment when they are started and up to and including when a phone registers to their network I’d much appreciate it. It would help me to debug the issue.
FYI manage to purchase GSM dual band 900/1800 SMA GSM antenna for less than 6$ in my local shop…
My question was which Lime RX input you are using?
RX1_H Channel 1 RX - frequencies above 1.5GHz
RX2_H Channel 2 RX - frequencies above 1.5GHz
RX1_L Channel 1 RX - frequencies below 1.5GHz
RX2_L Channel 2 RX - frequencies below 1.5GHz
RX1_W Channel 1 RX - wideband
RX2_W Channel 2 RX - wideband
I am using RX1_L for RX. I removed MN18 inductor on it to open up HF bands and this has been my main RX input so far. I know it works well based on GQRX experience.
Thanks for the tip on GSM antenna. Will consider getting it as soon as I have this thing running.
@9a4db and @skyinlife – question for you guys and for whoever may have inputs.
I assume you managed to have OsmoTRX/OpenBSC stack running with LimeSDR such that phones not only see the network but also register with it. If so, did you use this fork of osmo-trx or some other source? Tnx.
Please look above to IgnasJ script, that one is working for me too.
This will have reduced performance on higher frequencies. If not fitting the part gave equal performance on every frequency, it would not be fitted…
Have first hand experience on that subject too…
Own two LimeSDR boards, one mine from Crowd campaign, with removed coil on RX1_W by me
and second hand purchased from user here, who mixed up the parcels.
So on the end, instead of non mod, received board with RX1_L coil MN18 removed.
Interesting fact is that both boards are working ok on above IgnasJ configuration.
Must measure that once…
Which band?
I wouldn’t have thought the performance degradation should be an issue for bench testing, but it’s worth noting that performance will have been altered for higher frequencies, with even the original GSM band of 900MHz being a long way from 30MHz and below.
1,8 GHz
Can not measure now because my calibrated Agilent set and one of Lime boards
are on my second site… But in Feb may be able to measure and post here.
@andrewback – yes, I am aware of the degradation on high freq due to MN18 removal, but at 900 Mhz I think it’s not that pronounced yet to become a major factor mainly because MS is very close to the RX antenna.
@9a4db – good point, I can see the sources IgnasJ used in install.sh he attached. Will try that on my Ubuntu 17.04.
Hi,
I am using LimeSDR and I would like to setup a mini GSM base station. I am following the instructions by IgnasJ
However, I am getting trouble starting tranceiver:
TERMINAL 1:
ronan@ronan-MS-N014:~/Downloads$ osmo-nitb -c openbsc.cfg -l hlr.sqlite3 -P -C
<0005> abis_nm.c:2800 (bts=0,trx=0) Changing adm. state Unlocked -> Unlocked [vty]
<001e> telnet_interface.c:104 telnet at 127.0.0.1 4242
<0005> bsc_init.c:465
WARNING: You are running an ‘accept-all’ network on a BTS that is not barred. This configuration is likely to interfere with production GSM networks and should only be used in a RF shielded environment such as a faraday cage!
<0020> input/ipaccess.c:848 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports
<0017> smpp_smsc.c:1001 SMPP at 0.0.0.0 2775
<0025> control_if.c:854 CTRL at 127.0.0.1 4249
DB: Database initialized.
DB: Database prepared.
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3002
<0005> abis_nm.c:507 BTS0 feature ‘EGPRS’ reported via OML does not match statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:507 BTS0 feature ‘OML Alerts’ reported via OML does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20180115
<0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx
<0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:311 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63
<0020> input/ipaccess.c:243 Sign link vanished, dead socket
<0020> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
TERMINAL 2:
ronan@ronan-MS-N014:~/Downloads$ osmo-bts-trx -c osmo-bts.cfg
((*))
|
/ \ OsmoBTS
<0017> control_if.c:854 CTRL at 127.0.0.1 4238
<0010> telnet_interface.c:104 telnet at 127.0.0.1 4241
<0012> input/ipaccess.c:886 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002
<000b> trx_if.c:599 Open transceiver for phy0.0
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<0001> oml.c:229 O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX.
<0001> oml.c:680 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:1049 ADM state already was Unlocked
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108205-0=1108205 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108421-1108300=121 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108638-1108435=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108855-1108652=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1109072-1108870=202 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1109289-1109086=203 > 1!
<0001> bts.c:210 Shutting down BTS 0, Reason No clock from osmo-trx
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 1112227-1109693=2534 > 1!
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> bts.c:205 BTS is already being shutdown.
<000b> trx_if.c:172 No response from transceiver for phy0.0
Shutdown timer expired
ronan@ronan-MS-N014:~/Downloads$
TERMINAL 3:
ronan@ronan-MS-N014:~/Downloads$ sudo osmo-trx -e
[sudo] password for ronan:
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in, but not supported by CPU
Config Settings
Log Level… NOTICE
Device args…
TRX Base Port… 5700
TRX Address… 127.0.0.1
GSM Core Address…127.0.0.1
Channels… 1
Tx Samples-per-Symbol… 4
Rx Samples-per-Symbol… 4
EDGE support… Enabled
Reference… Internal
C0 Filler Table… Disabled
Multi-Carrier… Disabled
Tuning offset… 0
RSSI to dBm offset… 0
Swap channels… 0
– Make connection: ‘LimeSDR-USB [USB 2.0] 9060B00470E28’
– Reference clock 30.720 MHz
– Device name: LimeSDR-USB
– Reference: 30.72 MHz
– Init LMS7002M(0)
– Ver=7, Rev=1, Mask=1
– LMS7002M calibration values caching Disable
– Transceiver active with 1 channel(s)
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:791:driveControl: Changing TSC from 0 to 7
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:244:start: Starting the transceiver
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=389640 time_end=385560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=389640 time_end=385560
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0.120517, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0.120517, Previous time: 0.359668
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=415140 time_end=412080
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=415140 time_end=412080
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.383206
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.383206
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=440640 time_end=417180
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping
On the LimeSuiteGUI I also was able to perform loopback test and the example.ini.
This test:
https://wiki.myriadrf.org/LimeSDR-USB_Quick_Test
Waveform is different from the guide. Loopback check is good but the receive check (2nd check on the guide) is different:
Is the hardware here defective?
As suggested, I used simpler like CubicSDR software to check. But it seems I could not even get the nearest radio station. But my android phone can,
I had that issue today until changing:
~/.osmocom/osmo-bts.cfg
from:
phy 0
instance 0
osmotrx rx-gain 1
to:
phy 0
instance 0
osmotrx rx-gain 49 ← this seems to be the max allowed
Now two phones are camped on OpenBSC a couple of rooms away from the LimeSDR. Just going from experience in OpenBSC where rxgain default is 52 and is dialed back to 10 for USRP sensitivity.
Once you have a couple of phones camped you can find their extension in nitb and send sms texts back and forth:
# telnet 0 4242
OpenBSC> show subscriber imsi 901700000005100
ID: 3, Authorized: 0
Extension: 35079
LAC: 1/0x1
IMSI: 901700000005100
TMSI: 89AD2E7B
Expiration Time: Sun, 11 Feb 2018 14:55:55 -0500
Paging: not paging Requests: 0
Use count: 1
OpenBSC> show subscriber imsi 901700000005090
ID: 4, Authorized: 0
Extension: 39083
LAC: 1/0x1
IMSI: 901700000005090
TMSI: 3EDFA534
Expiration Time: Sun, 11 Feb 2018 14:53:42 -0500
Paging: not paging Requests: 0
Use count: 1
Here’s a DZ09 smartwatch ($11 on ebay!) with an expired H2O sim joining the network:
<0002> gsm_04_08.c:1415 LOCATION UPDATING REQUEST: MI(IMSI)=310410721544479 type=NORMAL
<0001> gsm_04_08.c:150 (bts 0 trx 0 ts 0 pd 05) Sending 0x18 to MS.
<0000> abis_rsl.c:2125 (bts=0,trx=0,ts=0,ss=2) SAPI=0 DATA INDICATION
<0000> gsm_04_08.c:4007 Dispatching 04.08 message, pdisc=5
<0002> gsm_04_08.c:573 IDENTITY RESPONSE: MI(IMEI)=354883070044060
<0002> gsm_04_08.c:530 → LOCATION UPDATE ACCEPT
<0001> gsm_04_08.c:150 (bts 0 trx 0 ts 0 pd 05) Sending 0x02 to MS.
<0002> gsm_04_08.c:900 → MM INFO
<0001> gsm_04_08.c:150 (bts 0 trx 0 ts 0 pd 05) Sending 0x32 to MS.
<0002> gsm_subscriber.c:341 Subscriber 310410721544479 ATTACHED LAC=1
<0000> abis_rsl.c:2125 (bts=0,trx=0,ts=0,ss=2) SAPI=0 DATA INDICATION
<0000> gsm_04_08.c:4007 Dispatching 04.08 message, pdisc=5
<0002> gsm_04_08.c:1429 TMSI Reallocation Completed. Subscriber: 310410721544479
<0002> gsm_04_08.c:329 Location Updating completed for 310410721544479
OpenBSC> show subscriber imsi 310410721544479
ID: 5, Authorized: 0
Extension: 27525
LAC: 1/0x1
IMSI: 310410721544479
TMSI: 61A287CF
Expiration Time: Sun, 11 Feb 2018 15:32:17 -0500
Paging: not paging Requests: 0
Use count: 1
1 Like