From laforge at gnumonks.org  Sun Jan 12 18:53:26 2014
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 12 Jan 2014 19:53:26 +0100
Subject: [RFC] [ADMIN] Making lists subscriber-only?
Message-ID: <20140112185326.GU23594@nataraja>

Dear all,

so far the osmocom.org mailing lists have always been in a 'non-members
are manually moderated' mode.  This has created a lot of work for manual
list moderation, where a lot of the messages caught are simply spam, and
only the occasional valid message is being received.

I'd like to thank the list moderators for taking care of this.

However, in more recent discussions, we were considering to move the
lists to a completely closed mode, i.e. postings would automatically be
rejected from non-members.

The automatic response would contain a description of how to subscribe
in 'nomail' mode, i.e. to subscribe in a way to be able to post to the
list, while still not receiving any incoming traffic.  The latter should
be fine for occasional posters who don't want the bulk e-mail that goes
with a full/regular subscription.

Please provide feedback in case you disagree with that change.  Unless
there is major opposition, we will likely transition to the 'closed'
mode within one month.

Thanks,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140112/20f1d2d9/attachment.bin>

From nik135 at mail.ru  Fri Jan 17 09:16:06 2014
From: nik135 at mail.ru (=?UTF-8?B?YWxleCBrb3JvbGV2?=)
Date: Fri, 17 Jan 2014 13:16:06 +0400
Subject: =?UTF-8?B?dW1kZXNrIHByb2JsZW0=?=
Message-ID: <1389950166.42332561@f325.i.mail.ru>

 Hello, All!

Please, help me resolving problem with umdesk:

1. uhd_find_devices work:

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
??? type: umtrx
??? addr: 192.168.135.35
??? name: UmTRX
??? serial: 75

2. But uhd_usrp_probe fails:

linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown

-- Opening a UmTRX device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Error: resolve: Service not found


I think the problem around eeprom(because led ZPU && FPGA is on), how i can reset it's value to default?


Best regards,
alex korolev
nik135 at mail.ru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140117/9eec543c/attachment.htm>

From alexander.chemeris at gmail.com  Fri Jan 17 09:54:20 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Fri, 17 Jan 2014 13:54:20 +0400
Subject: umdesk problem
In-Reply-To: <1389950166.42332561@f325.i.mail.ru>
References: <1389950166.42332561@f325.i.mail.ru>
Message-ID: <CABmJbFU2+5NaAs-amhYP3+1wU+s6xXJK_mCepxtUyUFTvV51uw@mail.gmail.com>

Alex,

Could you provide the complete command line you use for uhd_usrp_probe?
Googling tells us that "resolve: Service not found" error is a result
of passing an unsupported address type to a resolver.

On Fri, Jan 17, 2014 at 1:16 PM, alex korolev <nik135 at mail.ru> wrote:
> Hello, All!
>
> Please, help me resolving problem with umdesk:
>
> 1. uhd_find_devices work:
>
> --------------------------------------------------
> -- UHD Device 0
> --------------------------------------------------
> Device Address:
>     type: umtrx
>     addr: 192.168.135.35
>     name: UmTRX
>     serial: 75
>
> 2. But uhd_usrp_probe fails:
>
> linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown
>
> -- Opening a UmTRX device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> Error: resolve: Service not found
>
>
> I think the problem around eeprom(because led ZPU && FPGA is on), how i can
> reset it's value to default?
>
>
> Best regards,
> alex korolev
> nik135 at mail.ru



-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From nik135 at mail.ru  Fri Jan 17 10:17:20 2014
From: nik135 at mail.ru (=?UTF-8?B?YWxleCBrb3JvbGV2?=)
Date: Fri, 17 Jan 2014 14:17:20 +0400
Subject: =?UTF-8?B?UmVbMl06IHVtZGVzayBwcm9ibGVt?=
In-Reply-To: <CABmJbFU2+5NaAs-amhYP3+1wU+s6xXJK_mCepxtUyUFTvV51uw@mail.gmail.com>
References: <1389950166.42332561@f325.i.mail.ru>
	<CABmJbFU2+5NaAs-amhYP3+1wU+s6xXJK_mCepxtUyUFTvV51uw@mail.gmail.com>
Message-ID: <1389953840.874913778@f148.i.mail.ru>

 Alexander,

i run "uhd_usrp_probe" without any arguments.

"usrp_burn_mb_eeprom --key=ipaddr" return same error.

previously these tools will work .

transceived also don't work:

Config Settings
?? Log Level............... NOTICE
?? Device args.............
?? TRX Base Port........... 5700
?? TRX Address............. 127.0.0.1
?? Channels................ 1
?? Samples-per-Symbol...... 4
?? External Reference...... Disabled
?? Diversity............... Disabled

-- Opening a UmTRX device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
ALERT 3046254816 06:17:41.8 UHDDevice.cpp:608:open: UHD make failed, device type=umtrx,addr=192.168.135.35,name=UmTRX,serial=75
ALERT 3046254816 06:17:41.8 osmo-trx.cpp:364:main: Failed to create radio device

Shutting down transceiver...

Is there a way to reset the eeprom saved  values ?? to it's default values?

ps. in my example of umdesk ethernet led in front side is not working.
How i can turn it on?


???????, 17 ?????? 2014, 13:54 +04:00 ?? Alexander Chemeris <alexander.chemeris at gmail.com>:
>Alex,
>
>Could you provide the complete command line you use for uhd_usrp_probe?
>Googling tells us that "resolve: Service not found" error is a result
>of passing an unsupported address type to a resolver.
>
>On Fri, Jan 17, 2014 at 1:16 PM, alex korolev < nik135 at mail.ru > wrote:
>> Hello, All!
>>
>> Please, help me resolving problem with umdesk:
>>
>> 1. uhd_find_devices work:
>>
>> --------------------------------------------------
>> -- UHD Device 0
>> --------------------------------------------------
>> Device Address:
>>     type: umtrx
>>     addr: 192.168.135.35
>>     name: UmTRX
>>     serial: 75
>>
>> 2. But uhd_usrp_probe fails:
>>
>> linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown
>>
>> -- Opening a UmTRX device...
>> -- Current recv frame size: 1472 bytes
>> -- Current send frame size: 1472 bytes
>> Error: resolve: Service not found
>>
>>
>> I think the problem around eeprom(because led ZPU && FPGA is on), how i can
>> reset it's value to default?
>>
>>
>> Best regards,
>> alex korolev
>>  nik135 at mail.ru
>
>
>
>-- 
>Regards,
>Alexander Chemeris.
>CEO, Fairwaves LLC / ??? ???????
>http://fairwaves.ru


? ?????????,
alex korolev
nik135 at mail.ru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140117/44153981/attachment.htm>

From alexander.chemeris at gmail.com  Fri Jan 17 12:50:05 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Fri, 17 Jan 2014 16:50:05 +0400
Subject: umdesk problem
In-Reply-To: <1389953840.874913778@f148.i.mail.ru>
References: <1389950166.42332561@f325.i.mail.ru>
	<CABmJbFU2+5NaAs-amhYP3+1wU+s6xXJK_mCepxtUyUFTvV51uw@mail.gmail.com>
	<1389953840.874913778@f148.i.mail.ru>
Message-ID: <CABmJbFV4eRTScFVT-JoWV5FO5qM-3=D-k5H39qJ3eSN-Rh_wpw@mail.gmail.com>

Alex,

On Fri, Jan 17, 2014 at 2:17 PM, alex korolev <nik135 at mail.ru> wrote:
> i run "uhd_usrp_probe" without any arguments.

Please make sure that it is using correct UHD library.

If you're using an Ethernet switch - try changing it. Some people
reported issues with some switch models. You could also try changing
an Ethernet card - we had issues with some JMicron based NICs.

UmTRX doesn't support 100Mbit cards and supports only a subset of 1GbE
specs, so some cards and switches may be confused.

What may help to debug the issue is a Wireshark capture of what
happens on this Ethernet connection.

> "usrp_burn_mb_eeprom --key=ipaddr" return same error.
>
> previously these tools will work.

What have you changed for it to stop working?

> Is there a way to reset the eeprom saved values to it's default values?

No, there is no way to reset to defaults, other than writing values again.

Which values did you change?

> ps. in my example of umdesk ethernet led in front side is not working.
> How i can turn it on?

This LED is not implemented yet.
This is for a future software upgrade. :)

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From nik135 at mail.ru  Fri Jan 17 14:30:47 2014
From: nik135 at mail.ru (=?UTF-8?B?YWxleCBrb3JvbGV2?=)
Date: Fri, 17 Jan 2014 18:30:47 +0400
Subject: =?UTF-8?B?UmVbNF06IHVtZGVzayBwcm9ibGVt?=
In-Reply-To: <CABmJbFV4eRTScFVT-JoWV5FO5qM-3=D-k5H39qJ3eSN-Rh_wpw@mail.gmail.com>
References: <1389950166.42332561@f325.i.mail.ru>
	<1389953840.874913778@f148.i.mail.ru>
	<CABmJbFV4eRTScFVT-JoWV5FO5qM-3=D-k5H39qJ3eSN-Rh_wpw@mail.gmail.com>
Message-ID: <1389969047.766977550@f251.i.mail.ru>

 Alexander,


???????, 17 ?????? 2014, 16:50 +04:00 ?? Alexander Chemeris <alexander.chemeris at gmail.com>:
>What may help to debug the issue is a Wireshark capture of what
>happens on this Ethernet connection. ok, i try this.
>> previously these tools will work.
>
>What have you changed for it to stop working?
./usrp_burn_mb_eeprom --key=gpsdo --val=internal

this command will success, i'm reboot device and uhd_usrp_probe and usrp_burn_mb_eeprom broke.

ps. where i can read about dbg port?

Regards,

alex korolev
nik135 at mail.ru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140117/259d12e1/attachment.htm>

From alexander.chemeris at gmail.com  Fri Jan 17 14:51:55 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Fri, 17 Jan 2014 18:51:55 +0400
Subject: umdesk problem
In-Reply-To: <1389969047.766977550@f251.i.mail.ru>
References: <1389950166.42332561@f325.i.mail.ru>
	<1389953840.874913778@f148.i.mail.ru>
	<CABmJbFV4eRTScFVT-JoWV5FO5qM-3=D-k5H39qJ3eSN-Rh_wpw@mail.gmail.com>
	<1389969047.766977550@f251.i.mail.ru>
Message-ID: <CABmJbFV++q0COhvtriBP3JYTqtTo49j5JtOurZGtCQzk2mMGfw@mail.gmail.com>

On Fri, Jan 17, 2014 at 6:30 PM, alex korolev <nik135 at mail.ru> wrote:
> ???????, 17 ?????? 2014, 16:50 +04:00 ?? Alexander Chemeris
> <alexander.chemeris at gmail.com>:
>> previously these tools will work.
>
> What have you changed for it to stop working?
>
> ./usrp_burn_mb_eeprom --key=gpsdo --val=internal
>
> this command will success, i'm reboot device and uhd_usrp_probe and
> usrp_burn_mb_eeprom broke.

Ok, this is a known issue. We have to disable this setting for UmTRX
completely, as it doesn't make sense.
I'll give you some guidance a bit later.

> ps. where i can read about dbg port?

USB debug port is a virtual UART port with 230400 baud rate. Connect
it to your Linux and you will see a serial-to-USB device. Usually it's
/dev/ttyUSBx.

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From alexander.chemeris at gmail.com  Mon Jan 20 09:23:08 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Mon, 20 Jan 2014 13:23:08 +0400
Subject: umdesk problem
In-Reply-To: <1389970937.24066676@f103.i.mail.ru>
References: <1389950166.42332561@f325.i.mail.ru>
	<1389969047.766977550@f251.i.mail.ru>
	<CABmJbFV++q0COhvtriBP3JYTqtTo49j5JtOurZGtCQzk2mMGfw@mail.gmail.com>
	<1389970937.24066676@f103.i.mail.ru>
Message-ID: <CABmJbFU=u=WO+2Y7H5m9FzRby+53B27dVZJgtArkj-6hPLcU8w@mail.gmail.com>

On Fri, Jan 17, 2014 at 7:02 PM, alex korolev <nik135 at mail.ru> wrote:
> Ok, thanks. explain me please, gps sync always active? and test_pps_input
> must always work?

Yes, GPS sync is activated automatically as soon as it receives a GPS signal.

>>> ps. where i can read about dbg port?
>>
>> USB debug port is a virtual UART port with 230400 baud rate. Connect
>> it to your Linux and you will see a serial-to-USB device. Usually it's
>> /dev/ttyUSBx.
>
> I can use usual USB cable?

Yes, you should use a normal micro-USB cable.

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From andreas at eversberg.eu  Fri Jan 24 09:29:50 2014
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Fri, 24 Jan 2014 10:29:50 +0100
Subject: RF power problems with current master of osmo-trx
Message-ID: <52E2328E.2090709@eversberg.eu>

hi,

i experience problems with osmo-trx/umtrx. when i start osmo-trx, i get 
the following output:

openbsc osmo-trx # /files/projects/gsm/osmo-trx/Transceiver52M/osmo-trx
linux; GNU C++ version 4.5.4; Boost_104900; UHD_003.004.000-1b07671

Config Settings
    Log Level............... NOTICE
    Device args.............
    TRX Base Port........... 5700
    TRX Address............. 127.0.0.1
    Channels................ 1
    Samples-per-Symbol...... 4
    External Reference...... Disabled
    Diversity............... Disabled

-- Opening a UmTRX device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
-- Setting UmTRX 4 SPS
-- Transceiver active with 1 channel(s)

i use current master. (an older version with branch umtrx_dual_test 
works with two TRX.) when i use RSSI test phone, i see that the RF power 
is high on TS0 and TS1 only. also it takes many tries to sync to it. i 
receive BCCH infos with some dropouts, but RACH is not received.

i have no slotmask define at osmo-bts. any idea what causes it?

regards,

andreas





From alexander.chemeris at gmail.com  Fri Jan 24 10:58:49 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Fri, 24 Jan 2014 14:58:49 +0400
Subject: RF power problems with current master of osmo-trx
In-Reply-To: <52E2328E.2090709@eversberg.eu>
References: <52E2328E.2090709@eversberg.eu>
Message-ID: <CABmJbFW30qiJYM9GauTFYjb8LwQupH9zKp6TsZHyK+C2_8ZjEA@mail.gmail.com>

Hi Andreas,

We use the current master of osmo-trx in production and lab environments
without any issues, so there should be something wrong with your setup.

Could you please provide more details about your setup and experiments you
did?
E.g. what PC so you run it on, what is the CPU utilization, have you tried
to run it with real-time priority, what exactly you feed into the osmo-trx
and what do you see on your monitoring phone, how exactly long is "longer",
etc

We noticed, that Linux kernel 3.3 had issues with 1GbE chips from Intel, so
we switched to the kernel version 3.8, which works stable. We use kernels
from the stock Ubuntu Server 12.04.
24 ???. 2014 ?. 13:47 ???????????? "Andreas Eversberg" <andreas at eversberg.eu>
???????:

> hi,
>
> i experience problems with osmo-trx/umtrx. when i start osmo-trx, i get
> the following output:
>
> openbsc osmo-trx # /files/projects/gsm/osmo-trx/Transceiver52M/osmo-trx
> linux; GNU C++ version 4.5.4; Boost_104900; UHD_003.004.000-1b07671
>
> Config Settings
>    Log Level............... NOTICE
>    Device args.............
>    TRX Base Port........... 5700
>    TRX Address............. 127.0.0.1
>    Channels................ 1
>    Samples-per-Symbol...... 4
>    External Reference...... Disabled
>    Diversity............... Disabled
>
> -- Opening a UmTRX device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> -- Setting UmTRX 4 SPS
> -- Transceiver active with 1 channel(s)
>
> i use current master. (an older version with branch umtrx_dual_test works
> with two TRX.) when i use RSSI test phone, i see that the RF power is high
> on TS0 and TS1 only. also it takes many tries to sync to it. i receive BCCH
> infos with some dropouts, but RACH is not received.
>
> i have no slotmask define at osmo-bts. any idea what causes it?
>
> regards,
>
> andreas
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140124/b4754f6e/attachment.htm>

From andreas at eversberg.eu  Sat Jan 25 06:22:56 2014
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Sat, 25 Jan 2014 07:22:56 +0100
Subject: RF power problems with current master of osmo-trx
In-Reply-To: <CABmJbFW30qiJYM9GauTFYjb8LwQupH9zKp6TsZHyK+C2_8ZjEA@mail.gmail.com>
References: <52E2328E.2090709@eversberg.eu>
	<CABmJbFW30qiJYM9GauTFYjb8LwQupH9zKp6TsZHyK+C2_8ZjEA@mail.gmail.com>
Message-ID: <52E35840.1010808@eversberg.eu>

Alexander Chemeris wrote:
>
> Could you please provide more details about your setup and experiments 
> you did?
> E.g. what PC so you run it on, what is the CPU utilization, have you 
> tried to run it with real-time priority, what exactly you feed into 
> the osmo-trx and what do you see on your monitoring phone, how exactly 
> long is "longer", etc
>
> We noticed, that Linux kernel 3.3 had issues with 1GbE chips from 
> Intel, so we switched to the kernel version 3.8, which works stable. 
> We use kernels from the stock Ubuntu Server 12.04.
>
dear alexander,

sorry, but this was my fault. here is the reason why i have only RF 
power on two slots:

- i configured TS 0 with CCCH and TS1..TS7 with SDCCH8
- i set bts type at osmo-nitb to "nanobts", which rejects SDCCH8 on TS2..TS7
- no "Set Chan Attr" was sent from osmo-nitb to osmo-bts for TS2..TS7, 
so osmo-bts did not send SETTSC to osmo-trx.

the thing is that the transceiver will only send bursts to umtx, if 
SETTSC was given. (makes sense)

i found out that sending no butsts from osmo-trx to the transceiver will 
cause no RF output. this is why osmo-bts sends dummy bursts for the 
first TRX, so there is RF power on all TS all the time. on other TRX, 
osmo-bts send bursts, only if the logical channel (the bursts belong to) 
is activated. this is the way it is done to reduce noise on the 
spectrum. i can see it one the osmocombb-RSSI application. once a 
channel was activeated, there will be RF power on the specific TS, even 
when osmo-bts does not send bursts anymore. i guess that some filler 
table of osmo-trx causes it. i think it would be nice if osmo-trx would 
stop transmitting, when there are no more bursts comming from osmo-bts. 
(at least after a while.)

best regards,

andreas




From tom at tsou.cc  Sat Jan 25 07:36:10 2014
From: tom at tsou.cc (Tom Tsou)
Date: Sat, 25 Jan 2014 02:36:10 -0500
Subject: RF power problems with current master of osmo-trx
In-Reply-To: <52E35840.1010808@eversberg.eu>
References: <52E2328E.2090709@eversberg.eu>
	<CABmJbFW30qiJYM9GauTFYjb8LwQupH9zKp6TsZHyK+C2_8ZjEA@mail.gmail.com>
	<52E35840.1010808@eversberg.eu>
Message-ID: <CAATyM+ZLP_sU1haftCAeFFbksc+Pe5gLKhsU7TT-g8_jRNs0mA@mail.gmail.com>

On Sat, Jan 25, 2014 at 1:22 AM, Andreas Eversberg <andreas at eversberg.eu> wrote:
> once a channel was activeated,
> there will be RF power on the specific TS, even when osmo-bts does not send
> bursts anymore. i guess that some filler table of osmo-trx causes it. i
> think it would be nice if osmo-trx would stop transmitting, when there are
> no more bursts comming from osmo-bts. (at least after a while.)

Yes, this is the behaviour of the filler table, which will resend the
previous frame until a new frame arrives. Sending an idle frame will
disable output, which is how the filler table is managed in OpenBTS.
You can disable the filler table with this patch.

diff --git a/Transceiver52M/Transceiver.cpp b/Transceiver52M/Transceiver.cpp
index e5ab476..9077465 100644
--- a/Transceiver52M/Transceiver.cpp
+++ b/Transceiver52M/Transceiver.cpp
@@ -197,19 +197,13 @@ void Transceiver::pushRadioVector(GSM::Time &nowTime)
   TransceiverState *state;
   std::vector<signalVector *> bursts(mChans);
   std::vector<bool> zeros(mChans);
+  std::vector<bool> filler(mChans, true);

   for (size_t i = 0; i < mChans; i ++) {
     state = &mStates[i];

     while ((burst = mTxPriorityQueues[i].getStaleBurst(nowTime))) {
       LOG(NOTICE) << "dumping STALE burst in TRX->USRP interface";
-
-      TN = burst->getTime().TN();
-      modFN = burst->getTime().FN() % state->fillerModulus[TN];
-
-      delete state->fillerTable[modFN][TN];
-      state->fillerTable[modFN][TN] = burst->getVector();
-      burst->setVector(NULL);
       delete burst;
     }

@@ -220,9 +214,8 @@ void Transceiver::pushRadioVector(GSM::Time &nowTime)
     zeros[i] = state->chanType[TN] == NONE;

     if ((burst = mTxPriorityQueues[i].getCurrentBurst(nowTime))) {
-      delete state->fillerTable[modFN][TN];
-      state->fillerTable[modFN][TN] = burst->getVector();
       bursts[i] = burst->getVector();
+      filler[i] = false;
       burst->setVector(NULL);
       delete burst;
     }
@@ -230,6 +223,11 @@ void Transceiver::pushRadioVector(GSM::Time &nowTime)

   mRadioInterface->driveTransmitRadio(bursts, zeros);

+  for (size_t i = 0; i < mChans; i++) {
+    if (!filler[i])
+      delete bursts[i];
+  }
+
   return;
 }



From andreas at eversberg.eu  Sat Jan 25 07:57:29 2014
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Sat, 25 Jan 2014 08:57:29 +0100
Subject: RF power problems with current master of osmo-trx
In-Reply-To: <CAATyM+ZLP_sU1haftCAeFFbksc+Pe5gLKhsU7TT-g8_jRNs0mA@mail.gmail.com>
References: <52E2328E.2090709@eversberg.eu>	<CABmJbFW30qiJYM9GauTFYjb8LwQupH9zKp6TsZHyK+C2_8ZjEA@mail.gmail.com>	<52E35840.1010808@eversberg.eu>
	<CAATyM+ZLP_sU1haftCAeFFbksc+Pe5gLKhsU7TT-g8_jRNs0mA@mail.gmail.com>
Message-ID: <52E36E69.8090704@eversberg.eu>

Tom Tsou wrote:
> Sending an idle frame will
> disable output, which is how the filler table is managed in OpenBTS.
hi tom,

so when i stop sending the bursts, the filler table will continue to 
transmit bursts. do i understand it correctly: if i send a single idle 
burst (frame??) after sending bursts, the filler table is disabled until 
new bursts are sent?

what does an idle frame look like? is it a burst without bits? (only the 
6 byte header?)

best regards,

andreas




From nik135 at mail.ru  Mon Jan 27 11:53:41 2014
From: nik135 at mail.ru (=?UTF-8?B?YWxleCBrb3JvbGV2?=)
Date: Mon, 27 Jan 2014 15:53:41 +0400
Subject: =?UTF-8?B?dW10cnggJ2dwc2RvJyBpc3N1ZQ==?=
Message-ID: <1390823621.481832846@f412.i.mail.ru>

 Hello, Alexander!

?
A few days ago, you wrote that you know about the problem (issue) , tell me how to solve it ?


? ?????????,
alex korolev
nik135 at mail.ru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/umtrx/attachments/20140127/21b71195/attachment.htm>

From alexander.chemeris at gmail.com  Mon Jan 27 22:03:06 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Tue, 28 Jan 2014 02:03:06 +0400
Subject: umtrx 'gpsdo' issue
In-Reply-To: <1390823621.481832846@f412.i.mail.ru>
References: <1390823621.481832846@f412.i.mail.ru>
Message-ID: <CABmJbFWg_d5+ueFjYnpC8x+1HQG2oyMzRyPHjadE=RdpNPz5Cg@mail.gmail.com>

Hi Alex,

A high-level description of the issue and a solution by Stephane Alnet is here:
https://github.com/fairwaves/UHD-Fairwaves/issues/3

I've added him to CC, may be can share a patch for his hack.

If someone could create a patch for a proper solution of the issue, I
would merge that into UHD-Fairwaves. E.g. we could completely remove
"gpsdo" setting from the UmTRX EEPROM, as it doesn't make any sense.

On Mon, Jan 27, 2014 at 3:53 PM, alex korolev <nik135 at mail.ru> wrote:
> Hello, Alexander!
>
>
> A few days ago, you wrote that you know about the problem (issue) , tell me
> how to solve it?
>
>
> ? ?????????,
> alex korolev
> nik135 at mail.ru



-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From stephane at shimaore.net  Tue Jan 28 19:49:06 2014
From: stephane at shimaore.net (stephane at shimaore.net)
Date: Tue, 28 Jan 2014 20:49:06 +0100
Subject: umtrx 'gpsdo' issue
In-Reply-To: <CABmJbFWg_d5+ueFjYnpC8x+1HQG2oyMzRyPHjadE=RdpNPz5Cg@mail.gmail.com>
References: <1390823621.481832846@f412.i.mail.ru>
	<CABmJbFWg_d5+ueFjYnpC8x+1HQG2oyMzRyPHjadE=RdpNPz5Cg@mail.gmail.com>
Message-ID: <20140128194906.GA2315@shimaore.net>

Hi,

> A high-level description of the issue and a solution by Stephane Alnet is here:
> https://github.com/fairwaves/UHD-Fairwaves/issues/3
> I've added him to CC, may be can share a patch for his hack.

It's going to be pull-request #4 :)
  https://github.com/fairwaves/UHD-Fairwaves/pull/4

This doesn't fix the issue (i.e. you can still prevent your UmTRX from
booting by improperly setting the `gpsdo` parameter) but it provides a
workaround so that you can re-set the parameter to its default value.

HTH,
S.

-- 
St?phane Alnet -- Telecom Artisan. OpenSource Advocate.
Development and integration for FreeSwitch, OpenSIPS, CouchDB, Node.js.
Mobile: +33643482771 - http://shimaore.net/ - https://github.com/shimaore/



From alexander.chemeris at gmail.com  Tue Jan 28 20:15:51 2014
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Wed, 29 Jan 2014 00:15:51 +0400
Subject: umtrx 'gpsdo' issue
In-Reply-To: <20140128194906.GA2315@shimaore.net>
References: <1390823621.481832846@f412.i.mail.ru>
	<CABmJbFWg_d5+ueFjYnpC8x+1HQG2oyMzRyPHjadE=RdpNPz5Cg@mail.gmail.com>
	<20140128194906.GA2315@shimaore.net>
Message-ID: <CABmJbFXT-2EHxHnaLRui0Ck8ENmeDVnZxw-qEj1QRD8Hts8AVA@mail.gmail.com>

On Tue, Jan 28, 2014 at 11:49 PM,  <stephane at shimaore.net> wrote:
> Hi,
>
>> A high-level description of the issue and a solution by Stephane Alnet is here:
>> https://github.com/fairwaves/UHD-Fairwaves/issues/3
>> I've added him to CC, may be can share a patch for his hack.
>
> It's going to be pull-request #4 :)
>   https://github.com/fairwaves/UHD-Fairwaves/pull/4
>
> This doesn't fix the issue (i.e. you can still prevent your UmTRX from
> booting by improperly setting the `gpsdo` parameter) but it provides a
> workaround so that you can re-set the parameter to its default value.

Merged, thanks!


-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ??? ???????
http://fairwaves.ru



From andrew at carrierdetect.com  Wed Jan 29 17:28:46 2014
From: andrew at carrierdetect.com (Andrew Back)
Date: Wed, 29 Jan 2014 17:28:46 +0000
Subject: LO leakage and I/Q balance calibration procedures.
Message-ID: <CADj1OPBNFkeT1Wd4KfxgX6iaP0Pi0A1hpYnDk=F+aX4rndgG3g@mail.gmail.com>

Hello,

Is there documentation somewhere, even if just an archived e-mail, of
the processes you need to follow to carry out calibration for LO
leakage and I/Q balance?

Cheers,

Andrew

-- 
Andrew Back
http://carrierdetect.com



From andrew at carrierdetect.com  Thu Jan 30 17:27:08 2014
From: andrew at carrierdetect.com (Andrew Back)
Date: Thu, 30 Jan 2014 17:27:08 +0000
Subject: umtrx_vcxo.py always reporting 2048.
Message-ID: <CADj1OPCzj_0jAtpap6gtCk88E0CoPM9pELoA3jLwcN4=xkprow@mail.gmail.com>

Hello,

I'm attempting to perform TCXO DAC calibration. However, whenever I
run umtrx_vcxo.py it reports the current DAC value to be 2048,
regardless of whether the GPS antenna is unplugged, or it is plugged
in and GPS has a lock.

I've updated the FPGA and ZPU firmware with those found at:

  http://people.osmocom.org/ipse/umtrx-v2/current/

But this doesn't seem to have made any difference.

Is there anything else I can try?

Cheers,

Andrew

-- 
Andrew Back
http://carrierdetect.com