gmr

gmr@lists.osmocom.org

51 discussions

gr-gmr1
by Ahmed Moudou 17 Oct '19

17 Oct '19

while compiling the gr-gmr1 code i got a problem while compiling it (the make command ). How can I resolve this problem illustrated in the screenshot below? thanks in advance. cheers

1 0

need help
by fe8769 02 Oct '19

02 Oct '19

Hello Thanks to *mohamed yehia* for great help in understanding in osmo-gmr project . In wireshark I saw "immediate assignment" are displaying a different ARFCN than one I was listen too . That means that TCH3 channel is on another ARFCN . What is the way to follow both ARFCN ? I didn't find the ./gmr_multi_rx utility on git (wiki says : ./gmr_multi_rx --gmr1-dl 941 942 -a RX2 -S B:0 -T 10 -is kc extrat the same way as gr-gsm with rainbow tables ? thanks --

2 1

RACH intercepting
by mohamed yehia 11 Sep '19

11 Sep '19

Dear community members, I'm interested in intercepting L band up-link RACH channel I found the BCCH channel of the spot beam I'm currently in then scan the same ARFCN but in uplink I had a cfile and I tried to read it using gr-gmr1 <https://github.com/osmocom/osmo-gmr/tree/sylvain/gr/gr-gmr1> in the branch sylvain/gr <https://github.com/osmocom/osmo-gmr/tree/sylvain/gr> but i have no results , may be I don't know how to use the read utility in sylvain/gr <https://github.com/osmocom/osmo-gmr/tree/sylvain/gr> I also have another question about the file test.pcap in http://people.osmocom.org/tnt/gmr/ how can I have a file like it and is it l band RACH data or C band. -- *Best Regards , * *Mohamed Yehia Mohamed * Mobile : +2 0102 674 5023

2 1

(no subject)
by Ahmed Moudou 30 Apr '19

30 Apr '19

hi I'am new with ubuntu cd osmo-gmr/utils/gmr_multi_rx make TARGET=uhd cd ../../.. You changed the code osmo-gmr and it was integrated in the Jenkins platform You didn't make the neccesary changes to be done in order to get ready to use the project please send me the necessary changes Cordially

1 0

Hardware
by Andi Kita 26 Feb '19

26 Feb '19

Hello what kind of hardware is supported by osmo-gmr? I have an ettus b200 but when I run a script it comes back with device not compatible or smth similar to it. I have a good option to buy a usrp1 with all the doughterboards. Any help is appreciated. Thank you.

1 0

OsmoDevCon 2019 registration
by Harald Welte 31 Dec '18

31 Dec '18

Dear fellow Osmocom developers, I'm a bit surprised to notice that not more people have signed up for OsmoDevCon 2019. I guess it was mostly an oversight when the date was originally announced, and not a lack of interest? ;) All details about the event are available at the related wiki page at: https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019 Please enter your name at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019#Requested in case you would like to attend. Registering early allows proper planning. Thanks! Looking forward to meeting old and new Osmocom developers in April 2019. Regards, 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)

1 0

Generator matrix used for TCH3 channel encoding
by wireless gmr 17 Dec '18

17 Dec '18

I am interested in finding the generator matrix used for TCH3 channel encoding (GEO-Mobile Radio Interface). I followed the installation steps indicated in OsmocomGMR. There was an example for FACCH3 channel to generate the G matrix. I modified the code for TCH3 (shown below) but the output results does not seems correct. I would really appreciate it if you can tell me what I am doing wrong in the code below. /* GMR-1 G/g matrix geneation forTCH3 */ /* (C) 2011 by Sylvain Munaut <tnt(a)246tNt.com> * All Rights Reserved * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU Affero General Public License as published by * the Free Software Foundation; either version 3 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Affero General Public License for more details. * * You should have received a copy of the GNU Affero General Public License * along with this program. If not, see <http://www.gnu.org/licenses/>. */ #include <errno.h> #include <stdio.h> #include <string.h> #include <osmocom/core/bits.h> #include <osmocom/core/utils.h> #include <osmocom/gmr1/l1/tch3.h> static void copy_bits(ubit_t *dst, int r, ubit_t *bits_e) { int i, j = 0; for(i=0;i<212;i++){ if (i<52 || i > 55){ dst[(208*r)+j] = bits_e[i]; j++; } } } static int pbm_save_bits(const char *filename, ubit_t *m, int x, int y) { FILE *fh; int i, j; fh = fopen(filename, "w"); if (!fh) return -EPERM; fprintf(fh, "P1\n%d %d\n", x, y); for (i=0; i<y; i++) for (j=0; j<x; j++) fprintf(fh, "%d%c", m[(i*x)+j], j==x-1 ? '\n' : ' '); fclose(fh); return 0; } int main(int argc, char *argv[]) { ubit_t mat_G[208*160]; /* 208 lines of 160 pixels */ ubit_t mat_g[208]; /* 208 lines of 1 pixel */ ubit_t bits_e[212]; ubit_t bits_u1[160]; ubit_t bits_s[4]; uint8_t l1[10]; uint8_t l2[10]; int i; int j; int m = 0; memset(mat_G, 0x00, sizeof(mat_G)); memset(mat_g, 0x00, sizeof(mat_g)); memset(bits_s, 0x00, sizeof(bits_s)); memset(l1, 0x00, sizeof(l1)); memset(l2, 0x00, sizeof(l2)); gmr1_tch3_encode(bits_e, l1, l2, bits_s, NULL,m); copy_bits(mat_g, 0, bits_e); for (i=0; i<160; i++) { memset(l1, 0x00, sizeof(l1)); memset(l2, 0x00, sizeof(l2)); memset(bits_u1, 0, sizeof(bits_u1)); bits_u1[i] = 1; osmo_ubit2pbit_ext(l1, 0, bits_u1, 0, 80, 1); osmo_ubit2pbit_ext(l2, 0, bits_u1, 80, 80, 1); gmr1_tch3_encode(bits_e, l1, l2, bits_s, NULL,m); copy_bits(mat_G, i, bits_e); } for (i=0; i<160; i++) { for (j=0; j<208; j++) { mat_G[(i*208)+j] ^= mat_g[j]; } } pbm_save_bits("mat_G.pbm", mat_G, 160, 208); pbm_save_bits("mat_g.pbm", mat_g, 1, 208); printf("\n"); }

1 0

OsmoDevCon 2018 schedule planning
by Harald Welte 06 Dec '17

06 Dec '17

Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc(a)lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] Like every year in early December, it is time to discuss as schedule for OsmoDevCon in the upcoming year. Note: Ths is about OsmoDevCon, the more private meeting of developers, *NOT* about OsmoCon, the public conference. == When, Who, Where == I propose the following date for OsmoDevCon 2018: April 20 - April 23rd, 2018 * Who: Active developers/contributors of Osmocom projects (as usual) * Where: IN-Berlin, Berlin (as usual) Please let me know ASAP if that proposed date works for everyone who'd want to attend. We can still change it now, but I would want to nail down the date pretty soon. == Format == After the experiment of reducing from 4 to 3 days last year (due to OsmoCon), we will again go for *four days* in 2018. However, we should clearly divide the days in a way that e.g. "GSM/3G" topics are on two days, while SDR+Other topics are on the other days, so people not interested in some topics can skip one or two days, as needed. We could even divide it further like: * 1 day 3GPP RAN (osmo-bts, osmo-bsc, osmo-pcu, virt_phy, fake_trx, ...) * 1 day 3GPP CN (osmo-msc, osmo-hlr, osmo-sip-connector, nextepc, etc.) * 2 days misc Regards, and looking forward to meeting you [again] in 2018, 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)

1 1

Planning for OsmoCon + OsmoDevCon
by Harald Welte 14 Oct '17

14 Oct '17

[cross-post to many lists, please follow-up-to openbsc(a)lists.osmocom.org] Dear all, time is flying, and I would like to start early with discussions and planning about OsmoCon and OsmoDevCon in 2018. It helps to start early. Side note: We have some pending issues about the events from last year at http://osmocom.org/projects/osmo-dev-con/issues - I've incorporated them in the text below. == OsmoDevCon == For OsmoDevCon, I think it's easy: We keep it as-is. Same procedure as every year, which means: * same venue, same catering options * same concept of 'anyone contributing to Osmocom can apply for registration until all seats are taken' * same idea of inviting some few speaker[s] doing other FOSS mobile communications work to join us The parts that we need to change, IMHO: * don't reduce from 4 to 3 days like last year. Have full 4 days again * sort topics per day / half-day, i.e. have "GSM/UMTS Cellular Infrastructure" days for BTS/BSC/NITB/MSC/HLR/SGSN/GGSN & Co, but then have other days for other projects. This would enable people not interested in the [continued evolvement] of the cellular projects be able to skip those days, or to simply meet in an adjacent room for parallel hacking sessions/discussions * try to be a bit more structured with the schedule in general. The existing approach works for people who attend all the event all day long, but not so well for people with other plans / limited time Any further change requests or topics to discuss? Please note that Pablo Neira has offered to kindly host an OsmoDevCon in Seville (Spain). I've attended a number of netfilter workshops he organized there, and he's doing a great job! However, given the large number of attendees from Berlin (and Germany in general), I think this would make things more complicated, and more expensive for most attendees. If you disagree with that assessment: I'm open for having the discussion, I just thought it's more practical/economic to do it in Berlin. === 10 year Anniversary Party === Given that 2018 marks the 10 year anniversary of Dieter and me hacking with the Siemens BS-11 in 2008, I think the 2018 incarnation deserves some special celebration of some form. I have no concrete idea yet, but for sure we should so something, and it should be at/around OsmoDevCon. And for sure we should have a BS-11 around :) == OsmoCon == The public OsmoCon was welcomed and was a success. However, let's start this discussion with a review of last years event. === Registration === * Registrations came in way too late. Two weeks ahead of the event, we were considering to cancel it. And then within the last few days, we had to turn people down due to limited seating capacity * To make planning more reliable, we see on other option but to significantly raise the registration fee combined with an equally significant discount for early booking === Duration === * Many people requested multiple days rather than just one, in order to make more out of (long distance) travels. This is obvious, but as we had no idea how many people would attend at all (or if we have to cancel due to lack of attendance), planning multiple days in the first incarnation would have been high risk and a multitude of work * I would suggest to expand to two or even three days this week, possibly one days with tutorials and the other day with tech talks * Slightly less crammed schedule due to multiple days === Venue === We recognize this yearso venue was not the best option, due to * Bad ventilation in the basemenet * Difficult to find * No space next to the conference room where people can meet / hang out in parallel to talks (not everyone attends every talk) I still like the "understatement" of the venue. I'd prefer any hostel / non-profit / hackerspace / university over luxurious hotels any time. Going to an expensive venue means more or less automatically more expensive ticket fees, which again is more likely to exclude pure community members without a commercial activity related to Osmocom. So any future venue would ideally: * be able to hold slightly more people than this year * have a second room or large lobby in which people can meet for extended coffee breaks in parallel to some talks, as needed * be slightly easier to find (and we have to put up some signs outside and in the lobby) * have better WiFi and/or wired connectivity === Programme / Format === * less crammed over multiple days * some more "interactive" formats were requested, for users to provide feedback to developers * there was some discussion about topics / speakers in redmine last year, but not too much participation [until it was too late]. * I'd suggest a more formal CfP process with a submission deadline that allows us to publish a preliminary schedule long ahead of the event === Video Recordings === I think they were a big success, and it was a very big surprise that the CCC Video Operations Center was volunteering to help such a small and niche-interest event like OsmoCon. We should make sure that we can repeat this for 2018. == Dates / Frequency == Having OsmoCon and OsmoDevCon back to back becomes somewhat long, if OsmoCon is 2-3 days and OsmoDevCon is 4 days. Basically we're looking at a full week for those of you who would like to attend both events. But then, I think the number of people attending both events is actually not all that big. Without checking the details, I think not more than half of the OsmoDevCon attendees were attending OsmoCon. I would expect that tendency to remain or even increase. I still think it's good to keep them back-to-back. In terms of frequency, I would actually suggest we move to a 6-month cycle rather than a 12-month cycle. There's a lot of development going on at all time. I understand that not everyone is able to attend two events just on Osmocom, especially if it's a spare time / hobby type activity. That's ok, I think there's no problem with attending either of the two only, and catching up by video recordings and/or mail on the other. The qeustion is: Should that second event be developer-oriented or user-oriented? Or again both? Any comments here? Ok, that was a somewhat lengthy e-mail. Please make sure to provide any feedback you may have as early as possible, to increase the chances of your feedback being reflected in the planning. Happy hacking, 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)

1 0

git.osmocom.org cgit improvements
by Harald Welte 20 Mar '17

20 Mar '17

Hi all, today I've deployed some cgit improvements on https://git.osmocom.org/, in the hope that it makes this tool even more useful: 1) syntax highlighting of source code (requested by Hoernchen) The source code is now highlighted by pygments. I don't really understand why somebody would want to look at source code a lot in a browser, but well, it was as easy as to enable the existing pygments based filter plugin. 2) rendering of "about" page from README.md As you might have noticed, I've introduced a README.md in a number of repositoires, and cgit is now rendering an about page for every repository, e.g. at http://git.osmocom.org/libosmo-abis/about/ 3) gerrit change-ID hyperlink generation All gerrit Change-IDs in commit messages are now automatically converted to hyperlinks to the respective gerrit change, see e.g. the below example: http://git.osmocom.org/openbsc/commit/?id=6dd0fc685b7149f67a5fe17a5bce55c44… Please note that this works for the "Change-Id" line of the actual change, but also for change-ids in the free text (e.g. "this depends on change-id ... in libosmocore") 4) Osmocom ticket/issue hyperlink generation Any Line that matches the "^((Relate|Close|Fixe)[ds]):" prefix is scanned for occurrences of "OS#(\d+)" which are then amended with hyperlinks to the respective issue on osmocom.org Please note the OS# prefix is mandatory, so things like "OS#1614, 1615" will not work, as can be seen at http://git.osmocom.org/osmo-pcu/commit/?id=0a8fae8d141c2cfa4387ffe9b35402d5… Please format your commit messages accordingly. Regards, 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)

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

gmr