Messages

1

YateBTS / Re: Cant detect cellular network

« on: November 06, 2018, 10:31:34 AM »

These are the common reasons for the phone not to see the network:

- Hardware or USB errors corrupting the beacon transmission. If this were happening you would get a lot of warnings. (The "TOA error" message at the "ALL" debug level is not a warning. It is part of a routine timing calculation.)

- Weak signal. What kind of antenna are you using?  Also, set Radio.PowerManager.MaxAttenDB and Radio.PowerManager.MinAttenDB both to 0 maximize output power.

- Excessive CPU loading corrupting the beacon transmission. The log shows a few places where the radio ran late and dropped the signal, but not so much that it should be a problem. What does "top" show for yate when you are running YateBTS?

- Bad frequency calibration. Have you enabled NTP on your computer and BladeRF frequency calibration in YateBTS?

- Interference. What country are you in? What band and ARFCN have you configured? The config file you sent shows Radio.C0 = 0. Did you fix that before running?

2

YateBTS / Re: Excessive TOA errors

« on: November 06, 2018, 06:44:21 AM »

These messages mean that the equalizer detected a timing error in the uplink signal. But for an idle channel that does not mean anything. That is why these messages are at the "ALL" debug level.

You see that the peak/mean ratios are small, less than 10. That is an idle channel and the TOA estimator is just looking at noise.

These message do no indicate any particular problem with your system.

3

YateBTS / Re: SMSCB

« on: May 25, 2018, 05:47:27 AM »

You can create and remove SMSCB messages with Yate call.control messages, either from a Javascript or from the rmanager command line.

See https://wiki.yatebts.com/index.php/GSM/LTE_LabKit_AppNote:_Controlling_the_LabKit_with_Javascript#SMSCB for details.

4

YateBTS / Re: raspberry is to weak for the BTS?

« on: March 22, 2018, 05:55:08 AM »

We have not done any work on optimizing this software for ARM.

What model Raspberry is this?

5

YateBTS / Re: LTE - Cannont connet to Yate on Port 1049

« on: March 22, 2018, 04:44:09 AM »

Can you give more details on the "Any time you try to enable LTE for a 2nd time, you get a port connection error" problem?
Is this a red message in the LMI about port 1049? (That message may be normal, but clears itself after a few seconds.)
When you say "enable LTE for a 2nd time", what is the sequence of events?

Also, we have a resolution for the problem of some phones not seeing the network. Please contact me privately to arrange an update for your LTE software.

6

YateBTS / Re: BladeRF kalibration

« on: February 05, 2018, 10:16:11 AM »

Xarion -

"kal" is not part of the YateBTS software, so nobody on this forum is likely to know.

Current versions of YateBTS calibrate their clocks with NTP.

-- David

7

YateBTS / Re: GPRS failed on HUAWEI

« on: February 05, 2018, 10:13:42 AM »

Is there an APN called "internet" defined in the HUAWEI phone?

8

YateBTS / Re: Newbie questions about YateBTS

« on: January 17, 2018, 11:42:05 AM »

YateBTS supports GPRS at rates up to about 50 kbit/sec. It works wit the Nuand BladeRF radio. It does not support any of the Ettus radios.

9

YateBTS / Re: Problems with libusb!!

« on: November 29, 2017, 06:50:59 AM »

The timestamp jumps usually mean that the CPU is not keeping up with the radio signal. If they are not too severe, YateBTS will still work. If your phone sees the beacon, then it might be OK. You say "a lot" of timestamp jumps? How often do they happen?

10

YateBTS / Re: YateBTS support for Ettus B210

« on: November 29, 2017, 06:41:40 AM »

YateBTS does not support the Ettus B210.

11

YateBTS / Re: Registration failed on network 2

« on: July 13, 2015, 12:02:47 AM »

From you log, this looks like a hardware problem with the radio or with the USB cable.

12

YateBTS / Re: Registration failed on network 2

« on: June 25, 2015, 04:13:26 AM »

Nurwalid -

Take a look at the section on RACH activity on http://wiki.yatebts.com/index.php/Radio_Related_Problems.

If you enable RACH logging and try to register, do you see RACH bursts?

If you remove and replace the handset battery between tests does that change the behavior or the RACH activity?

Regards,
David

13

YateBTS / Re: bladeRF calibration

« on: March 31, 2015, 10:46:28 AM »

The values for rxvag1, rxvga2, txvga1 and txvga2 are set by YateBTS from the configuration file. The default values in that file should work without changes.

If you are using a Lab Kit, then we calibrated the frequency for you already. If not, for most BladeRF radios we have seen, the frequency offset setting in YateBTS is in the range 165-170.

There are also calibrations for DC offset, but single-carrier GSM is not very sensitive to DC offset.

14

YateBTS / Re: filter for RX antenna

« on: March 31, 2015, 10:39:15 AM »

Take a look at http://wiki.yatebts.com/index.php/Radio_Related_Problems for some pointers on normal values for power and noise levels.

That said, the normal range of a lab kit should not be more than about 20 meters. It is intended for desktop testing and development work, not large-area coverage.

As for frequency calibration, anything within 200 Hz of the standard should work with no problem.

15

YateBTS / Re: USRP on YateBTS

« on: March 24, 2015, 08:50:56 AM »

Hello Nurwalid -

I am not aware of any use of YateBTS with the Ettus N210. We support only the Nuand BladeRF radio.

Regards,
David