Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - andrew77

Pages: 1 [2]
16
YateBTS / Re: Could not route call to '32843'
« on: May 18, 2015, 12:34:31 PM »
I run:
yate -Df -vvvvv -l /var/log/yate.log

the version is:

/usr/local/bin/yate-config --version
5.4.3
in:
which -a yate-config
/usr/local/bin/yate-config

Connected to 127.0.0.1.
Escape character is '^]'.
YATE 5.4.3-devel1 r5966 (http://YATE.null.ro) ready on andsim-HP-Pavilion-15-Notebook-PC.
debug on
Debug level: 10, objects: off, local: on, threshold: 10
color on
Colorized output: yes
sniffer on
Returned true 'engine.command' delay=0.000113
  thread=0x7f2dcc000990 'RManager Connection'
  data=(nil)
  retval='Message sniffer: on, timer: off
'
  param['line'] = 'sniffer on'
  param['cmd_address'] = '127.0.0.1:53196'
  param['cmd_machine'] = 'false'
  param['cmd_width'] = '80'
  param['cmd_heigth'] = '24'
Message sniffer: on, timer: off
Sniffed 'idle.execute' time=1431970895.908003
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.003696
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'
Sniffed 'idle.execute' time=1431970900.923399
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.004362
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'
Sniffed 'idle.execute' time=1431970905.935216
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.004317
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'
Sniffed 'idle.execute' time=1431970910.950600
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.005848
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'
Sniffed 'idle.execute' time=1431970915.964143
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.000920
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'
Sniffed 'idle.execute' time=1431970920.973844
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
Returned false 'idle.execute' delay=0.005899
  thread=0xf74170 'Engine Worker'
  data=(nil)
  retval='(null)'
  param['module'] = 'nib_cache'
  param['handlers'] = 'javascript:110'

20150518174414.335349 <nib:INFO> onRoute TMSI007b0001 -> 32843
20150518174414.337420 <INFO> Could not route call to '32843' in context 'default', wasted 437 usec
Returned false 'call.route' delay=1.205261
  thread=0x7f2de8004ce0 'Call Router'
  data=(nil)
  retval='(null)'
  param['id'] = 'ybts/1'
  param['module'] = 'ybts'
  param['status'] = 'incoming'
  param['address'] = 'TMSI007b0001'
  param['billid'] = '1431970838-1'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['phy_info'] = 'TA=3 TE=-0.566 UpRSSI=1 TxPwr=30 DnRSSIdBm=-111 time=1431971052.094'
  param['caller'] = '1408089'
  param['imsi'] = '222881661408089'
  param['tmsi'] = '007b0001'
  param['imei'] = '351815050022810'
  param['called'] = '32843'
  param['callednumtype'] = 'unknown'
  param['callednumplan'] = 'isdn'
  param['username'] = '222881661408089'
  param['imei'] = '351815050022810'
  param['emergency'] = 'false'
  param['privacy'] = 'false'
  param['handlers'] = 'javascript:15,regexroute:100,javascript:15,cdrbuild:50,javascript:80,fileinfo:90,subscription:100,sip:100,jingle:100,iax:100,sig:100,analog:100,regfile:100,regexroute:100'
20150518174414.338370 <ybts/1:MILD> Call rejected error='noroute' reason='No route to call target' [0x7f2de8003290]
20150518174414.338508 <ybts/1:INFO> Call 'i0' changed state CallProceeding -> Release [0x7f2de8003290]
20150518174414.338771 <ybts-signalling:INFO> Sending [0x11748b0]
-----
Primitive: L3Message
Info: 0
Connection: 2

<CC>
  <TID TIFlag="true">0</TID>
  <Message type="Release">
    <Cause coding="GSM-PLMN" location="LPN">noroute</Cause>
  </Message>
</CC>
-----


17
YateBTS / Re: Could not route call to '32843'
« on: May 16, 2015, 02:22:31 AM »
As I start Yatebts I get this:


Release 4.0.3 formal build date Apr 12 2015 rev475
20150516081820.275312 <mbts:NOTE> GSMConfig.cpp:80:regenerateBeacon: regenerating system information messages, changemark 1
Starting MBTS...
20150516081820.275861 <ybts-signalling:INFO> Received [0x145f700]
-----
Primitive: Handshake
Info: 0
-----
20150516081820.275971 <ybts:NOTE> State changed WaitHandshake -> Running
20150516081820.276026 <ybts-signalling:INFO> Sending [0x145f700]
-----
Primitive: Handshake
Info: 0
-----
20150516081820.927425 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150516081820.932864 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
20150516081820.937727 <nib:INFO> Finished reading saved registered subscribers. Found 2 registered_subscribers.
20150516081820.938598 <nib:INFO> Checked that only NIB is enabled.
20150516081820.938757 <ALL> Rescanning handler list for 'engine.start' [0x7ffd5d425710] at priority 100
Yate engine is initialized and starting up on andsim-HP-Pavilion-15-Notebook-PC
20150516081820.938925 <INFO> Creating first message dispatching thread
20150516081821.098638 <cpuload:NOTE> Updating CPU core number from 1 to 4
20150516081821.277291 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150516081822.278532 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150516081823.279015 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150516081824.280483 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
20150516081825.281344 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
ALERT 139880744073088 10:18:25.2 TRXManager.cpp:432:powerOff: POWEROFF failed with status -120150516081825.281488 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver

20150516081825.281593 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150516081825.416484 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver-bladerf w/ 1 ARFCNs and Args:
20150516081825.574908 <transceiver:NOTE> bladeRFDevice.cpp:110:open: Opened bladeRF serial=c36781bf545973547fdfed05e6edd3a7 firmware version 1.8.0 (1.8.0)
20150516081825.775101 <transceiver:NOTE> Transceiver.cpp:68:Transceiver: running 1 ARFCNs with oversampling 4
Starting transceiver
20150516081830.307261 <transceiver:NOTE> bladeRFDevice.cpp:243:start: starting bladeRF in super speed mode...
20150516081830.309895 <transceiver:NOTE> bladeRFDevice.cpp:486:readSamples: RX Timestamp adjusted by 1 to 2
20150516081830.319226 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T1
20150516081830.320215 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T2
20150516081830.321375 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T3
20150516081830.322358 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T4
20150516081830.323618 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T5
20150516081830.324670 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T6
20150516081830.325814 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T7
20150516081830.328188 <mbts:MILD> miniggsn.cpp:493:miniggsn_init: could not open GGSN.Logfile.Name log file:ggsn.log
20150516081830.328344 <mbts:MILD> iputils.cpp:456:ip_finddns: GGSN: DNS servers: 8.8.8.8 8.8.4.4
20150516081830.328422 <mbts:MILD> iputils.cpp:363:setprocoption: Can not open file /proc/sys/net/ipv4/ip_forward error: Permission denied
20150516081830.328481 <mbts:MILD> iputils.cpp:363:setprocoption: Can not open file /proc/sys/net/ipv4/ip_nonlocal_bind error: Permission denied
RTNETLINK answers: Operation not permitted
RTNETLINK answers: Operation not permitted
MBTS ready
20150516081830.833991 <ybts-signalling:INFO> Received [0x145f700]
-----
Primitive: RadioReady
Info: 0
-----
20150516081830.834230 <ybts:NOTE> State changed Running -> RadioUp

and "status engine" gives me:

status engine
%%+status:engine
name=engine,type=system,version=5.4.3,revision=5966,nodename=andsim-HP-Pavilion-15-Notebook-PC;plugins=68,inuse=1,handlers=519,hooks=2,messages=0,supervised=false,runattempt=0,lastsignal=0,threads=28,workers=1,mutexes=247,semaphores=0,acceptcalls=accept,congestion=0;sharedpath=/usr/local/share/yate,configpath=/usr/local/etc/yate,usercfgpath=/home/andsim/.yate,modulepath=/usr/local/lib/yate,workpath=/home/andsim
%%-status

even running yatebts as root the result is the same: no route to call...
thanks

18
YateBTS / Re: Could not route call to '32843'
« on: May 12, 2015, 12:00:00 PM »
Yes,

I have this:

[general]
routing=welcome.js

my sim card is registered to a true provider,
with yatebts I connect in "Roaming"

19
YateBTS / Could not route call to '32843' [solved]
« on: May 09, 2015, 06:30:27 AM »
Hello,
I've installed all and yatebts works fine with bladeRF40
but when I try to make a IRV call to 32843 this is the result:

Could not classify call from 'TMSI007b0001', wasted 17 usec
2015-05-09_14:16:01.686657 <nib:INFO> onRoute TMSI007b0001 -> 32843
2015-05-09_14:16:01.688820 <INFO> Could not route call to '32843' in context 'default', wasted 477 usec
2015-05-09_14:16:01.689020 <ybts/1:MILD> Call rejected error='noroute' reason='No route to call target
.....

    <Cause coding="GSM-PLMN" location="LPN">noroute</Cause>
  </Message>
</CC>
-----
2015-05-09_14:16:01.690285 <ybts/1:CALL> Hangup reason='noroute' [0xb6201bb0]

and
when I run yate -sD -vvvvv -l /usr/src/yate/logfiles/yate.log
I get these errors:
.....
2015-05-09_14:15:32.470775 <mbts:MILD> miniggsn.cpp:493:miniggsn_init: could not open GGSN.Logfile.Name log file:ggsn.log
2015-05-09_14:15:32.722404 <mbts:MILD> iputils.cpp:456:ip_finddns: GGSN: DNS servers: 127.0.1.1 0.0.0.0
2015-05-09_14:15:32.723053 <mbts:MILD> iputils.cpp:363:setprocoption: Can not open file /proc/sys/net/ipv4/ip_forward error: Permission denied
2015-05-09_14:15:32.723449 <mbts:MILD> iputils.cpp:363:setprocoption: Can not open file /proc/sys/net/ipv4/ip_nonlocal_bind error: Permission denied
2015-05-09_14:15:32.724141 <mbts:MILD> iputils.cpp:311:ip_tun_open: could not create tunnel sgsntun: ioctl error: Operation not permitted
2015-05-09_14:15:32.724219 <mbts:MILD> miniggsn.cpp:627:miniggsn_init: ggsn: ERROR: Could not open tun device sgsntun
2015-05-09_14:15:32.724548 <mbts:MILD> MAC.cpp:888:macStart:   14:15:32.7,0:GGSN failed to init
....

Anyone can help me to solve this?
thanks




20
YateBTS / Re: Running YateBTS on BladeRF (Video)
« on: April 19, 2015, 12:32:28 PM »
Solved!
Thanks

21
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 16, 2015, 02:34:32 PM »
well!
I'm from Italy :)
I  use eurocircuits (provides also Rogers pcb) as pcb maker and Altium Designer for gerbers at my job.
The use of BladeRF as Tracking generator  is one of my desire, but first I want to use the board as fake BTS (imsi catcher)

I used the filter from triquint (or you can find the same product from Epcos) for a GSM/CDMA detector and works very well, but cannot be used for transmitting chain because of its "un-flatness".
The "top" receiver could be done with two of these filters with a very low noise MIMIC amplifier (such as psa4-5043+) between them, but I'm afraid to amplify too much, I don't want to "burn" the front-end of the board; It would need a Variable gain amplifying, etc...
Regarding the mbts noise, I saw in the forums that many folks have these noise values, I will investigate
Eagle pcb can also be used in Linux!
If you need some advice about the pcb don't hesitate to ask
Enjoy!

22
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 16, 2015, 11:21:05 AM »
yes I know,
the kit is provided with the filter,
I looked for you and I have found this:
http://194.75.38.69/pdfs/VBFZ-925+.pdf

Consider that having a narrower bandwidth there are no means but getting a cavity filter,
 otherwise, if you find someone that can make a small pcb you can use this:
http://www.triquint.com/products/p/856671 this is the best solution with low cost!

I did the test with a dummy load connected in the RX and another in the TX port and the result is this:
mbts noise:  noise rssi: -46
so I think this is the practical lowest  noise floor.
If you consider to really buy this filter (it is for Europe) (http://www.triquint.com/products/p/85667)  (there is also the US version) you have to make  a small pcb  and buy two small Female pcb SMA connectors

23
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 15, 2015, 12:04:18 PM »
Also good antenna and well matched in the downlink band decreases the noise,
I tested another antenna for RX and increased the noise by 10dB!

Have you ever thought to calibrate DC the board before testing in Yate?
https://github.com/Nuand/bladeRF/wiki/DC-offset-and-IQ-Imbalance-Correction

I never did but I want to try

24
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 14, 2015, 02:12:18 PM »
Look at this I tested it (Made in China) but works well, shipped already tuned.(just to have an idea)
http://shop.sysmocom.de/t/gsm-related/duplexers

http://shop.sysmocom.de/products/dx900-kt30

otherwise:
http://www.mfcsales.com/14540.aspx

25
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 14, 2015, 11:12:36 AM »
A duplexer could be the solution of filtering and, further, amplifing
but 1 or 2W I think is too much to start experimenting

if you are going to buy the http://www.w1ghz.org/small_proj/GVA-84_amplifier.pdf I would suggest to use a traditional "through hole" resistor of around 3 or 4 ohm to feed the monolitic GVA (in the  +5V line), even if this doesn't need.
 How much noise do you have? when:
mbts noise

when I increase the rx gain the noise RSSI increase!

26
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 13, 2015, 02:08:04 PM »
Hi
just yesterday I make my yatebts working
I tested my bladerf with a RX antenna matched in the downlink band EGSM900 (Whip halfwave dipole, 2dBi) , so with some High VSWR in the UPlink  (with an antenna for tx not matched for this band but far away from the rx antenna in order not to make interference to the rx path): here are the results:

mbts rxgain
current RX gain is 0 dB
mbts noise
noise RSSI is -26 dB wrt full scale
MS RSSI target is -60 dB wrt full scale
mbts rxgain 30
current RX gain is 0 dB
new RX gain is 30 dB
mbts noise   
noise RSSI is --1 dB wrt full scale
MS RSSI target is -60 dB wrt full scale
Instead, with an antenna for RX fully unmatched for this band I got:
 mbts noise
noise RSSI is -9 dB wrt full scale
MS RSSI target is -60 dB wrt full scale
mbts rxgain
current RX gain is 0 dB
mbts rxgain 47
current RX gain is 0 dB
new RX gain is 30 dB
mbts rxgain   
current RX gain is 30 dB
mbts noise
noise RSSI is --3 dB wrt full scale
MS RSSI target is -60 dB wrt full scale
So, It seems that the measurement makes sense. To get the lowest noise one should use a filter taylored for the band in use (the narrow the bandwith, the lowest will be the noise), in addition RX an TX antenna must be far at least  2D^2/lambda (far-field)  where: D=maximum lenght of the antenna and lambda is the lenghtwave of the signal (Ex for 900 MHz lambda =30cm). Next days I will take  better antennas from my work/lab place  to  investigate futher, I will tell you
bye

27
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 12, 2015, 10:01:40 AM »
solved!
I forget to create a symbolic link in /var/www to nib web
now path in ybts.conf works

28
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 12, 2015, 01:23:35 AM »
OK I will try to configure NIB

Should I install Nib? It seems already installed with YateBTS

Regarding the noise you say, please be more precise, what do you mean? Some noise could be added from your nb AC/DC power supply


29
YateBTS / Re: Running YateBTS on BladeRF (Video)
« on: April 11, 2015, 11:16:26 AM »
Hello guys,
I have a problem when running yate with bladeRF:
I have USB2.0
the installation of yate and yate BTS all gone OK via SVN

this is the output when i run:
 yate -Df -vvvv -l /var/log/yate.log

20150411113607.759068 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150411113607.763468 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
20150411113607.765483 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
20150411113607.766009 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
20150411113607.766748 <nib:INFO> Checked that only NIB is enabled.
Yate engine is initialized and starting up on and-HP-Compaq-2510p-Notebook-PC
20150411113607.767043 <INFO> Creating first message dispatching thread
20150411113608.279609 <cpuload:NOTE> Updating CPU core number from 1 to 2
20150411113608.486824 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150411113609.487476 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150411113610.488483 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150411113611.489554 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
20150411113612.490525 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
20150411113612.490618 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
ALERT 3075032832 13:36:12.4 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.491006 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.595984 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver w/ 1 ARFCNs and Args:
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
20150411113612.596437 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting.
20150411113612.597726 <mbts:GOON> OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting

ybts.conf doesn't show transceiver-bladerf:

Path: string: Path to the transceiver relative to where the MBTS is started.
; Should be one of: ./transceiver-rad1 ./transceiver-usrp1 ./transceiver-uhd
; Defaults to ./transceiver.
;Path=./transceiver

but config.log produced by Yatebts's ./configure seems ok:

checking for bladeRF support using pkg-config
configure:4448: result: 1.2.1-2015.02-1-ppatrusty
configure:4483: checking libusb-1.0/libusb.h usability
configure:4483: gcc -c  -O2 -DLITTLE_ENDIAN  conftest.c >&5
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking libusb-1.0/libusb.h presence
configure:4483: gcc -E  conftest.c
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking for libusb-1.0/libusb.h
configure:4483: result: yes
configure:4749: creating ./config.status

I don't know how to solve this issue

30
YateBTS / [Solved] YateBTS and bladeRF running problem
« on: April 11, 2015, 09:26:55 AM »
Hello guys,
I have a problem when running yate with bladeRF:
I have USB2.0
the installation of yate and yate BTS all gone OK via SVN

this is the output when i run:
 yate -Df -vvvv -l /var/log/yate.log

20150411113607.759068 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150411113607.763468 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
20150411113607.765483 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
20150411113607.766009 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
20150411113607.766748 <nib:INFO> Checked that only NIB is enabled.
Yate engine is initialized and starting up on and-HP-Compaq-2510p-Notebook-PC
20150411113607.767043 <INFO> Creating first message dispatching thread
20150411113608.279609 <cpuload:NOTE> Updating CPU core number from 1 to 2
20150411113608.486824 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150411113609.487476 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150411113610.488483 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150411113611.489554 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
20150411113612.490525 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
20150411113612.490618 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
ALERT 3075032832 13:36:12.4 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.491006 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.595984 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver w/ 1 ARFCNs and Args:
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
20150411113612.596437 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting.
20150411113612.597726 <mbts:GOON> OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting

ybts.conf doesn't show transceiver-bladerf:

Path: string: Path to the transceiver relative to where the MBTS is started.
; Should be one of: ./transceiver-rad1 ./transceiver-usrp1 ./transceiver-uhd
; Defaults to ./transceiver.
;Path=./transceiver

but config.log produced by Yatebts's ./configure seems ok:

checking for bladeRF support using pkg-config
configure:4448: result: 1.2.1-2015.02-1-ppatrusty
configure:4483: checking libusb-1.0/libusb.h usability
configure:4483: gcc -c  -O2 -DLITTLE_ENDIAN  conftest.c >&5
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking libusb-1.0/libusb.h presence
configure:4483: gcc -E  conftest.c
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking for libusb-1.0/libusb.h
configure:4483: result: yes
configure:4749: creating ./config.status

I don't know how to solve this issue

Pages: 1 [2]