Hi all,
Just wanted to share an issue and a quick workaround I found for it in case
anyone else has the same problem. I believe a cmd2 update is causing
pySim-shell to fail. After installing it on a fresh install of Ubuntu
Server 20.04 and getting the following error when I run "python3
pySim-shell -p0":
>Using PC/SC reader interface
>Autodetected card type: sysmoUSIM-SJS1
>AIDs on card:
> USIM: a0000000871002ffffffff8907090000
>Traceback (most recent call last):
> File "pySim-shell.py", line 512, in <module>
> app = PysimApp(card, rs, opts.script)
> File "pySim-shell.py", line 59, in __init__
> super().__init__(persistent_history_file='~/.pysim_shell_history',
allow_cli_args=False, use_ipython=True, auto_load_commands=False,
command_sets=basic_commands, >startup_script=script)
>TypeError: __init__() got an unexpected keyword argument 'use_ipython'
If you run into this you can fix it by uninstalling cmd2 and reinstalling
cmd2 with "pip3 install cmd2==1.5".
Best,
Bryan
> I don't understand. This callback will be called with data you need to
write
> to the network. In case of MTP Level3 you will need to wrap that around
the
> msgb you got.
I means: is the interaction with mtp3 layer implemented (is sending sccp
data by mtp3 implemented by the library?)?
Also, what about the reception of data from mtp3 layer. is that implemented
in the sccp lib.
I am asking these questions because I see the code of mtp3 in the lib but no
significant call is present in the sccp part of the lib.
Thank you for your help.
On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote:
> [translated from german]
> is it certain that we switch a channel to PDCH only when
> gprs mode != none?
A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we
send a PDCH ACT message.
We send a PDCH ACT message
- during init (CHANNEL OML's state changed to enabled -> send PDCH ACT),
- and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH.
So the question is, when we receive a channel release ack, could that be
the PDCH release and we switch PDCH right back on by accident? No, because
we only receive a chan rel ack when the *TCH/F* is being released.
That is because the PDCH release is initiated "internally" from the PDCH
DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches
on, which existed before dyn PDCH:
if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) {
LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n",
gsm_lchan_name(lchan));
return 0;
}
In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but
not in the rsl_rx_dyn_pdch().
This is analogous to the ip.access way -- the ip.access nanobts replies to
a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel
release ack.
Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH
for clarity? (But we shouldn't actually send a release ack, to stay
compatible.)
Even though it works as-is, we should indeed add another flag check:
- We do check the flags that no ACT/DEACT is already pending;
- And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE;
- But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE.
This should never happen, but it would make sense to ensure that.
~Neels
Hello Osmocom community,
(Cc'ing Eric per instructions from Harald)
I am looking to acquire an SDR device for the purpose of running
osmo-bts-trx. My initial goal is to get to the bottom of some
mysteries observed in OS#6579; because it is CSD, getting a
non-virtual test setup requires an SDR-based BTS rather than the
otherwise wonderful sysmoBTS. And of course there will likely be
other fixes and improvements that can be made in osmo-bts-trx. :)
Harald recommended that I get a BladeRF 2.0 xA4 for this purpose,
plus a Leo Bodnar GPSDO. However, before I commit to buying that hw
with an aggregate cost of around $800, I wanted to get some community
input to make sure it is the right choice for the job at hand.
(There is also the possibility that Sysmocom will sponsor this hw for
me, which is wonderful - but still, I don't want to waste money even
if it's someone else's!)
Harald told me that Eric has worked on BladeRF, and instructed me to
ask both Eric and the wider community. My basic question is: how
stable and reliable is this BladeRF 2.0 in the BTS application? I
presume I will need to run osmo-trx-bladerf, but I find it alarming
that there is absolutely no documentation for this variant: the wiki
and the user manual cover osmo-trx-uhd and osmo-trx-lms, but not one
mention of BladeRF.
It is my understanding that BladeRF always runs on 38.4 MHz clock; if
the external clock frequency is some other, the PLL inside BladeRF
will discipline the local 38.4 MHz VCXO to "follow" the external
reference, but the SDR will still run at 38.4 MHz. Thus I see no way
to avoid fractional resampling, i.e., configuring the external GPSDO
to put out 26 MHz or 52 MHz won't do anything to eliminate that
fractional resampling need. Hence the question: does this fractional
resampling constitute a real problem, or is it a sufficiently minor
defect such that one can live with it in a lab environment? Will
there be any gotchas to be aware of, such as MS struggling to connect
to the test network?
Finally, how does this BladeRF compare to various LimeSDR options? It
seems like LimeSDR has always been the popular choice in the "cheap"
department, whereas for BladeRF I see not one mention anywhere as I
already noted. How do these two options compare? I recall hearing
that while LimeSDR was once very popular, people were also having
problems with it. Is BladeRF now better in terms of stability, or not
really? And if BladeRF really is a better choice than LimeSDR for the
purpose of running an SDR BTS on something cheaper than Ettus hw, then
how did we get into the peculiar situation of having documentation
that covers LimeSDR but not BladeRF?
Please help this SDR-ignorant gal figure out which hardware I should
buy. Whether I cover the cost on my own or take up Harald's offer of
cost reimbursement, either way I need to be sure I buy the right thing...
Oh, one more detail: whichever USB-interfaced SDR I get, I plan on
using a Raspberry Pi 5 to drive it, running stock Raspbian. Does
anyone have any experience with using RPi devices to drive SDRs for
use as BTS? Is RPi5 powerful enough to run all of the computationally
demanding parts, including that fractional resampling? Is stock
Raspbian good enough in terms of sw dependencies?
TIA,
Mychaela
