Hello
i installed all the package of openBTS and it was working properly, but
last time i take the server and connect the Umtrx module, the ping command
work properly, uhd_find_devices also work but i have this masseage: transceiver
; no process found... and after a long message comes telling me that the
network is unreachable. Just last week all this was working properly.
Can someone tell me ho to fix it please? or do i need to flash again the
module Umtrx?
*Manoel Aposaz.*
*The limite of our Greatest achievement will depend on the depth of our
imagination and our relation with God.*
Tel : 77 113 24 83.
Kleiv...
Hi. Since link2voip.com went kaput, I've been without a SIP trunking
provider. Does anyone have any recommendations?
I'd prefer a pay-as-you-go service over one with a monthly fee, since I use
it sporadically for development.
Thanks,
Robin
Hello, All!
1. I'm also (as Andrew Back) interested about calibration methods, but I can not find calibration technology description.
How i can calibate device?
2. test_pps_input program failed with message:
Using Device: Single USRP:
Device: UmTRX Device
Mboard 0: UMTRX-REV0
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: LMS6002D (0xfa07) - 0
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: LMS6002D (0xfa09) - 0
Attempt to detect the PPS and set the time...
-- 1) catch time transition at pps edge
Error: RuntimeError: Board 0 may not be getting a PPS signal!
No PPS detected within the time interval.
See the application notes for your device.
Where i can get information about pps signal state and gps lock? (from device)
3. I found that eob (end of burst) metadata does not work, signal at spectrum analyzer is present, after sendind eob.
How i can mute tx?
thanks for answers ! :-)
С уважением,
alex korolev
nik135(a)mail.ru
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
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
Hello, Alexander!
A few days ago, you wrote that you know about the problem (issue) , tell me how to solve it ?
С уважением,
alex korolev
nik135(a)mail.ru
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
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(a)mail.ru
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(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello,
I battled with osmo-bts-trx this afternoon; it didn't want to build with
old (at least not any I tried) nor recent libosmocore, so I ended up
using a chainsaw and cutting pieces out of it. The outcome is here:
https://github.com/shimaore/osmo-bts
You can see what I had to remove here:
https://github.com/shimaore/osmo-bts/commit/b5ac1c000e6d7bea57f7c1d8d47f43f…
This version builds with libosmocore etc `master` revisions.(*)
Once compiled this gives me a piece of software that starts and prints
out messages on the console, and apparently connects to the transceiver
on one side, and to osmo-bsc on the other side.
Anyhow, sending this out in hope this might save someone else a few
hours. :}
S.
(*) The `abis` and `rsl` code are completely different in recent
libosmocore, I suspect this build uses the old `abis` code embedded
inside osmo-bts. The sysmo-bts code was updated, but not the
trx-bts code.
--
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/
