Hi, I'm having a try with your software. A small suggestion I can give you is about the chapter "Starting OpenBTS" of your howto: a better way to host the transceiver script is to create a new dir under the openbts root (lets call it TransceiverOSMOCOM) that hosts your script. Then to create a link in the apps dir that point to the new transceiver, to follow the model openbts uses. This allows the user to switch between many hardware pieces using the same openbts installation (if compilation flags apply), avoiding to overwrite your script if openbts compilation instructions are literally followed. Just my 2 cents. Dario.
On Sun, Feb 24, 2013 at 3:33 PM, Sylvain Munaut 246tnt@gmail.com wrote:
PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress?
http://bb.osmocom.org/trac/wiki/Software/Transceiver
Cheers,
Sylvain
I'm not succeeding in using the osmocom transceiver.
When openbts starts, the output shown is (a bunch of)
<0011> trx.c:190 TRX CLK Indication 1029029 <0011> trx.c:512 TRX Data 1029080:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029081:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029082:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029083:0:0:a013ce5f9090c67e18229311431a30
When the osmocom mobile tries to attach, the output becomes
<0011> trx.c:512 TRX Data 1029491:0:0:a013ce5f9090c67e18229311431a30 <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029539:0:0:a14dd532a16dc062d07c030e055510 <0011> trx.c:512 TRX Data 1029540:0:0:82b7c400ae9e53e9bd7a0007bf5460 <0011> trx.c:512 TRX Data 1029541:0:0:842dd0834051146707753011978620 <0011> trx.c:512 TRX Data 1029542:0:0:9000ea751006a7f0380b57d421fe50 <0012> l1ctl.c:305 Sync failed, retrying ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029590:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029591:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029592:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029593:0:0:a013ce5f9090c67e18229311431a30 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029641:0:0:8062948a52a104e0402112806004a0 <0011> trx.c:512 TRX Data 1029642:0:0:118a5288440000e102854a018a1600 <0011> trx.c:512 TRX Data 1029643:0:0:408904254000607400058000200220 <0011> trx.c:512 TRX Data 1029644:0:0:44a542052054286588022012a16200 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029692:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029693:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029694:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029695:0:0:a013ce5f9090c67e18229311431a30 <0011> trx.c:512 TRX Data 1029743:0:0:a14dd532a16dc062d07c030e055510 <0011> trx.c:512 TRX Data 1029744:0:0:82b7c400ae9e53e9bd7a0007bf5460 <0011> trx.c:512 TRX Data 1029745:0:0:842dd0834051146707753011978620 <0011> trx.c:512 TRX Data 1029746:0:0:9000ea751006a7f0380b57d421fe50 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync.
Until I get
ALERT 3063667520 TRXManager.cpp:93:clockHandler: TRX clock interface timed out, assuming TRX is dead.
from openbts.
Output from osmocom mobile is
<0003> gsm322.c:2939 Channel synched on wrong ARFCN=XX, syncing on right ARFCN again... <0003> gsm322.c:474 Sync to ARFCN=0 rxlev=<=-110 (No sysinfo yet, ccch mode NONE)
XX is the arfcn of the reference cell. Changing it doesn't change the behavior. I've put this value as param for transceiver, according to the instructions. Any suggestion? Thanks a lot. Dario.
That's obvious. I'm using 2 phones. One as bts, other as subscriber.
On Mon, Feb 25, 2013 at 2:28 PM, Sylvain Munaut 246tnt@gmail.com wrote:
When the osmocom mobile tries to attach, the output becomes
WTF are you trying to do ?
You can't use the phone with both the 'transceiver' and the 'mobile' application at the same time !
Cheers,
Sylvain
This is what happens when using original motorola fw (logs from openbts, cut where reported)
1361800521.515924 3073959680: Starting the system... transceiver: no process found 36 41 1 <0011> trx.c:419 TRX Control recv: |RXTUNE|897000| <0011> trx.c:331 Setting C0 ARFCN to 35 (GSM900) <0011> trx.c:220 TRX Control send: |RSP RXTUNE 0 897000| <0011> trx.c:419 TRX Control recv: |TXTUNE|942000| <0011> trx.c:220 TRX Control send: |RSP TXTUNE 0 942000| <0011> trx.c:419 TRX Control recv: |SETBSIC|2| <0011> trx.c:220 TRX Control send: |RSP SETBSIC 0| <0011> trx.c:419 TRX Control recv: |SETMAXDLY|1| <0011> trx.c:220 TRX Control send: |RSP SETMAXDLY 0 1| <0011> trx.c:419 TRX Control recv: |SETRXGAIN|47| <0011> trx.c:220 TRX Control send: |RSP SETRXGAIN 0 47| <0011> trx.c:419 TRX Control recv: |POWERON|| <0011> trx.c:220 TRX Control send: |RSP POWERON 0| <0011> trx.c:419 TRX Control recv: |SETPOWER|0| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 0| <0011> trx.c:419 TRX Control recv: |SETSLOT|0 5| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 5| <0011> trx.c:512 TRX Data 2348:0:0:abca74273bbd00fef0b5414bd71a00 [cut] <0011> trx.c:512 TRX Data 2385:0:0:10aabdd500aefd7102ab75108bbd50 <0011> trx.c:419 TRX Control recv: |SETSLOT|1 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|2 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|3 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|4 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|5 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|6 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|7 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETPOWER|10| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 10|
system ready
use the OpenBTSCLI utility to access CLI <0011> trx.c:512 TRX Data 2388:0:0:4b90da4280e504e8e00d00a204d060 [cut] <0011> trx.c:512 TRX Data 2861:0:0:4421420408540070a810001a212280 <0011> trx.c:419 TRX Control recv: |SETPOWER|9| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 9| <0011> trx.c:512 TRX Data 2949:0:0:811aa402902001ea40084681028040 [cut] <0011> trx.c:512 TRX Data 4136:0:0:44a542052054286588022012a16200 <0011> trx.c:419 TRX Control recv: |SETPOWER|8| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 8| <0011> trx.c:512 TRX Data 4184:0:0:abca74273bbd00fef0b5414bd71a00 [cut] <0011> trx.c:512 TRX Data 4544:0:0:44a542052054286588022012a16200 ALERT 3063667520 TRXManager.cpp:93:clockHandler: TRX clock interface timed out, assuming TRX is dead. <0011> trx.c:512 TRX Data 4592:0:0:abca74273bbd00fef0b5414bd71a00 <0011> trx.c:512 TRX Data 4593:0:0:6193ebb006fec0f1895b448faaec90 <0011> trx.c:512 TRX Data 4594:0:0:37af2071c41b986e0c9a5218b14110 <0011> trx.c:512 TRX Data 4595:0:0:a01acc5b9814c67a7832b353421a10 Aborted (core dumped)
On Mon, Feb 25, 2013 at 2:35 PM, Sylvain Munaut 246tnt@gmail.com wrote:
That's obvious.
I would think so, but from the logs, it really looks like the same phone is trying to act as both.
Try not using 'mobile' at all and just use any plain old phone. (or the phone with its original firmware).
Cheers,
Sylvain
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 3173 fn_offset=3173 qbits=1420 Synchronize_TDMA LOST 2436! SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 Synchronize_TDMA =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 LOST 1903!
Apart from that, only battery indications are shown.
On Mon, Feb 25, 2013 at 3:03 PM, Sylvain Munaut 246tnt@gmail.com wrote:
This is what happens when using original motorola fw (logs from openbts, cut where reported)
And the osmocon logs ?
Cheers,
Sylvain
Hi.
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 3173 fn_offset=3173 qbits=1420 Synchronize_TDMA LOST 2436! SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 Synchronize_TDMA =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 LOST 1903!
Looks like it can't sync to the reference cell.
Cheers,
Sylvain
I've changed the ref cell, and now I can see
BTS MODE: 2 35
in trx logs. I suppose something is working now, since I can see my imsis in "tmsis" output from openbtscli. I can't register to the network, but I think that now is something related to the "core" (openbts/sipauthregister/asterisk), not radio.
One question more: is the osmocom transceiver able to handle sms as other transceivers?
On Mon, Feb 25, 2013 at 3:36 PM, Sylvain Munaut 246tnt@gmail.com wrote:
Hi.
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 3173 fn_offset=3173 qbits=1420 Synchronize_TDMA LOST 2436! SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 Synchronize_TDMA =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 LOST 1903!
Looks like it can't sync to the reference cell.
Cheers,
Sylvain
Hi,
I can't register to the network, but I think that now is something related to the "core" (openbts/sipauthregister/asterisk), not radio.
Yes, most likely.
One question more: is the osmocom transceiver able to handle sms as other transceivers?
Yes, it can handle SMS. But not calls.
Cheers,
Sylvain
On Mon, Feb 25, 2013 at 4:34 PM, Sylvain Munaut 246tnt@gmail.com wrote:
Yes, it can handle SMS. But not calls.
Why not? Is is something software-related, or hardware limit?
Do you think it would be possible to have one single transceiver that drives 2 phones in order to have more TS?
On Mon, Feb 25, 2013 at 4:51 PM, Sylvain Munaut 246tnt@gmail.com wrote:
Why not?
Because the current code only supports 1 bidirectional timeslot and it's used for the beacon and control channels.
Is is something software-related, or hardware limit?
Either ... Watch the talk, it's explained.
Assumption is the mother of all fuck.
On 25-2-2013 14:33, Dario Lombardo wrote:
That's obvious. I'm using 2 phones. One as bts, other as subscriber.
On Mon, Feb 25, 2013 at 2:28 PM, Sylvain Munaut 246tnt@gmail.com wrote:
When the osmocom mobile tries to attach, the output becomes
WTF are you trying to do ?
You can't use the phone with both the 'transceiver' and the 'mobile' application at the same time !
Cheers,
Sylvain
baseband-devel@lists.osmocom.org
-
Dario Lombardo -
nordin -
Sylvain Munaut