- osmocom-analog - lists.osmocom.org

Future Directions in Nursing Education and Paper Writing Services
by taylorswiftmerch146＠gmail.com 03 Mar '26

03 Mar '26

As nursing education continues to evolve, driven by advancements in healthcare delivery and technological innovation, the role of nursing paper writing services will likely expand to meet the changing needs of students and educators. Future directions in nursing education and paper writing [url=https://www.writinkservices.com/nurs-fpx-4060-assessment-1-health-promo… fpx 4060 assessment 1 health promotion plan ps[/url] services may include: Integration of artificial intelligence and machine learning technologies to enhance the efficiency and effectiveness of paper writing services.Collaboration between academic institutions and paper writing services [url=https://www.writinkservices.com/nurs-fpx-6103-assessment-2-applying-the… fpx 6103 assessment 2 applying the tripartite model[/url] to promote academic integrity and ethical writing practices.Expansion of services to support emerging areas of nursing practice, such as telehealth, informatics, and population health.Conclusion: Navigating the Future of Nursing EducationIn conclusion, the evolution of nursing education reflects a commitment to excellence, innovation, and continuous improvement in preparing nurses to meet the complex healthcare needs of society. Nursing paper writing services play a vital role in supporting this mission by providing students with the resources and support they need to succeed academically. As we look to the future, nursing educators, students, and paper writing [url=https://www.writinkservices.com/nurs-fpx-4030-picot-questions-and-evide… fpx 4030 picot questions and evidence based approach[/url] services must continue to collaborate and innovate to ensure that nursing education remains responsive to the evolving needs of healthcare delivery and patient care.

2 2

Conquer the Infinite Descent: Is Slope the Ultimate Test of Your Reflexes?
by improved.emu.tvmt＠protectsmail.net 17 Jan '26

17 Jan '26

Hey there, fellow gamers! Are you ready to test your skills, push your reflexes to the absolute limit, and maybe even scream a little (or a lot) in frustration? If so, then you absolutely NEED to know about Slope, the ridiculously addictive and deceptively simple game that’s been quietly captivating players for years. Forget complex storylines and sprawling open worlds for a minute. Slope throws you right into the action with a single, exhilarating objective: survive the endless descent. Sounds easy, right? Trust me, it's anything but. So, grab your favorite gaming beverage, settle in, and let's dive into the world of Slope! We'll explore what makes this game so captivating, how to play, some sneaky tips to improve your score, and ultimately, whether it's worth adding to your ever-growing list of must-play games. 1. What Exactly Is Slope? The Lowdown on This High-Speed Challenge Slope, developed by Rob Kay and released in 2014, is a simple yet incredibly engaging endless runner game. You control a ball rolling down an increasingly steep and challenging slope. Your mission? To avoid falling off the edges and smashing into the red blocks scattered throughout the course. The beauty of Slope lies in its minimalist design. The stark, neon-lit graphics, coupled with the pulsating electronic soundtrack, create a hypnotic and immersive experience. It's a game that's easy to pick up but incredibly difficult to master, offering a constant stream of adrenaline-pumping challenges. Think of it as a futuristic, neon-infused version of a classic downhill ski race, only instead of skis, you're a ball, and instead of snow, you're navigating a treacherous, ever-changing landscape of platforms and obstacles. Website: https://slopefree.org 2. How to Play Slope: A Beginner's Guide to Endless Freefall Okay, so you're intrigued. Let's get down to brass tacks – how do you actually play this thing? Thankfully, the controls are incredibly intuitive: Desktop/Laptop: Use the left and right arrow keys to steer the ball. Alternatively, you can use the 'A' and 'D' keys for the same effect. Mobile Devices: Tilt your device left and right to control the ball's movement. That's it! Sounds simple, right? Here's the catch: Speed: The ball accelerates as you descend, making it increasingly difficult to react to upcoming obstacles. Obstacles: Red blocks are your nemesis. Touching them results in instant game over. Gaps: You'll encounter gaps in the platforms that require precise maneuvering to avoid falling into the abyss. Dynamic Environment: The course is constantly changing, throwing new challenges and obstacles your way as you progress. The game continues until you inevitably crash (and you will crash... a lot). Your score is determined by the distance you travel before meeting your demise. 3. Pro Tips and Tricks: Mastering the Art of the Descent Ready to go from a Slope newbie to a seasoned pro? Here are some essential tips and tricks to help you dominate the game: Focus on Smooth Movements: Avoid jerky or sudden movements. Smooth, controlled steering is key to maintaining your balance and navigating tight turns. Anticipate Obstacles: Scan ahead and try to anticipate upcoming obstacles. This will give you more time to react and adjust your trajectory. Use the Entire Platform: Don't be afraid to use the edges of the platforms to your advantage. You can often "cut" corners by steering close to the edge, allowing you to maintain speed and avoid obstacles. Practice Makes Perfect: This might sound cliché, but it's absolutely true. The more you play, the better you'll become at anticipating obstacles and controlling the ball. Learn the Patterns (Sort Of): While the course is dynamically generated, certain patterns and obstacle combinations tend to repeat. Pay attention to these patterns and learn how to navigate them effectively. Don't Be Afraid to Slow Down (Sometimes): While speed is important, sometimes it's better to slow down slightly to avoid a particularly tricky obstacle. Listen to the Music: The pulsating soundtrack can actually help you anticipate changes in the course. Pay attention to the rhythm and use it as a cue to prepare for upcoming challenges. Take Breaks: Slope can be incredibly frustrating at times. If you're feeling overwhelmed, take a break and come back to it later with a fresh perspective. Embrace the Failures: Crashing is part of the learning process. Don't get discouraged by setbacks. Learn from your mistakes and keep practicing. Find Your Rhythm: Everyone has their own unique style of play. Experiment with different techniques and find what works best for you. 4. Ready to Take the Plunge? Your Call to Action! So, what are you waiting for? Head over to Slope and start playing! Challenge your friends, beat your own high score, and see how far you can descend into the neon abyss. Let us know in the comments below what your high score is! We want to know if you are having fun, or if you have any new strategy for playing the game! Website: https://slopefree.org

1 0

AMPS: Using one radio for TX, other for RX
by tangamugrosa＠gmail.com 06 Jan '26

06 Jan '26

Greetings group members Given the huge price of the Lime SDR, I was trying to find alternative methods for setting up an AMPS test rig. I found this command that operated half of the time rx and half tx, but it was of no use. At one point I saw "Signal received" on the console but it did not show further signs of life. My questions are, please: - Is there any future with this approach? - if nor, woukd be possible to use the hackrf to transmit, and a RTL-SDR to receive? Thank you very much test@test-ThinkPad-T470:~$ SOAPY_SDR_LOG_LEVEL=DEBUG sudo amps -v 1 -k 313 -F yes --sdr-soapy --sdr-device-args "driver=hackrf" --sdr-samplerate 5000000 -s 200000 --sdr-tx-gain 15 --sdr-rx-gain 0 -S sid=1 --sdr-timestamps 0 --sdr-lo-offset 0 And the output; DOPTIONS INFO options.c:128 Config file '/root/.osmocom/analog/amps.conf' seems not to exist, using command line options only. DOPTIONS INFO options.c:280 Command line option '-v' ('--verbose'), parameter '1' DOPTIONS INFO options.c:280 Command line option '-k' ('--kanal'), parameter '313' DOPTIONS INFO options.c:280 Command line option '-F' ('--flip-polarity'), parameter 'yes' DOPTIONS INFO options.c:296 Command line option '--sdr-soapy' DOPTIONS INFO options.c:294 Command line option '--sdr-device-args', parameter 'driver=hackrf' DOPTIONS INFO options.c:294 Command line option '--sdr-samplerate', parameter '5000000' DOPTIONS INFO options.c:280 Command line option '-s' ('--samplerate'), parameter '200000' DOPTIONS INFO options.c:294 Command line option '--sdr-tx-gain', parameter '15' DOPTIONS INFO options.c:294 Command line option '--sdr-rx-gain', parameter '0' DOPTIONS INFO options.c:280 Command line option '-S' ('--sysinfo'), parameter 'sid=1' DOPTIONS INFO options.c:294 Command line option '--sdr-timestamps', parameter '0' DOPTIONS INFO options.c:294 Command line option '--sdr-lo-offset', parameter '0' Selected System ID (SID) 1 belongs to: Chicago, IL (Cellular One) DDSP DEBUG dsp.c:150 Generating sine table for SAT signal. DAMPS NOTICE amps.c:583 You selected 'combined control & paging & voice channel'. This is a hack, but the only way to use control channel and voice channel on one transceiver. Some phones may reject this, but all my phones don't. DAMPS DEBUG amps.c:597 Creating 'AMPS' instance for channel = 313 of band A (sample rate 200000). DSENDER DEBUG sender.c:77 (chan 313) Creating 'Sender' instance DJITTER INFO jitter.c:129 (313) Reset jitter buffer. DJITTER INFO jitter.c:113 (313) Created jitter buffer. (samperate=8000, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DJITTER INFO jitter.c:129 (313) Reset jitter buffer. DJITTER INFO jitter.c:113 (313) Created jitter buffer. (samperate=200000, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DDSP DEBUG dsp.c:202 (chan 313) Init DSP for transceiver. DSENDER DEBUG sender.c:308 (chan 313) Maximum deviation: 8.0 kHz, Maximum modulation: 10.0 kHz DSENDER DEBUG sender.c:309 (chan 313) Deviation at speech level: 2.9 kHz DDSP DEBUG dsp.c:218 Use 20.0000 samples for full bit duration @ 200000. DDSP DEBUG dsp.c:234 Bit window length: 20 DDSP DEBUG dsp.c:235 -> Samples in window to analyse level left of edge: 5..9 DDSP DEBUG dsp.c:236 -> Samples in window to analyse level right of edge: 10..14 DDSP DEBUG dsp.c:175 Generating smooth ramp table. DDSP DEBUG dsp.c:259 Sat detection interval is 66 ms. DDSP DEBUG dsp.c:927 (chan 313) SAT detector reset: Initial state. DAMPS DEBUG amps.c:399 (chan 313) State change: (NULL) -> IDLE DAMPS INFO amps.c:685 (chan 313) Entering IDLE state, sending Overhead/Filler frames on combined control & paging & voice channel. DDSP DEBUG dsp.c:927 (chan 313) SAT detector reset: Change to FOCC. DDSP INFO dsp.c:944 (chan 313) Change mode to FOCC DDSP DEBUG dsp.c:967 (chan 313) Reset FSK frame transmitter, due to setting DSP mode. DAMPS NOTICE amps.c:638 Created channel #313 (System A) of type 'CC/PC/VC' = combined control & paging & voice channel Base station on channel 313 ready (combined control & paging & voice channel), please tune transmitter to 879.390 MHz and receiver to 834.390 MHz. (-45.000 MHz offset) DLCC DEBUG endpoint.c:1376 Creating new endpoint instance. DLCC DEBUG endpoint.c:1209 setting automatic remote peer selection DSDR DEBUG sdr.c:149 Open SDR device DSDR INFO sdr.c:168 Require bandwidth of each channel is 2 * (8.0 deviation + 10.0 modulation) = 36.0 KHz DSDR INFO sdr.c:307 We shift center frequency 18 KHz down (half bandwidth), to prevent channel from overlapping with DC level. DSDR INFO sdr.c:133 TX Spectrum: 1 ---------------------------------------+--------------------------------------- DSDR INFO sdr.c:135 Frequency 1 = 879.3900 MHz DSDR INFO sdr.c:357 Total bandwidth (two sidebands) for all TX Frequencies: 108000 Hz DSDR INFO sdr.c:365 Using center frequency: TX 879.354000 MHz DSDR DEBUG sdr.c:370 Frequency #0: TX offset: 0.036000 MHz DSDR INFO sdr.c:391 Using gain: TX 15.0 dB DSDR INFO sdr.c:433 We shift center frequency 18 KHz down (half bandwidth), to prevent channel from overlapping with DC level. DSDR INFO sdr.c:133 RX Spectrum: 1 ---------------------------------------+--------------------------------------- DSDR INFO sdr.c:135 Frequency 1 = 834.3900 MHz DSDR INFO sdr.c:469 Total bandwidth (two sidebands) for all RX Frequencies: 108000 Hz DSDR INFO sdr.c:477 Using center frequency: RX 834.354000 MHz DSDR DEBUG sdr.c:482 Frequency #0: RX offset: 0.036000 MHz DSDR INFO sdr.c:492 Using gain: RX 0.0 dB DSDR INFO sdr.c:525 Using local oscillator offset: 0 Hz DSOAPY INFO soapy.c:109 Using device args "driver=hackrf" DSOAPY DEBUG soapy.c:83 SDR device args: key='driver' value='hackrf' DSOAPY INFO soapy.c:113 Using stream args "" DSOAPY INFO soapy.c:117 Using tune args "" [INFO] Opening HackRF One #0 16bc62dc2e8526a7... DSOAPY DEBUG soapy.c:176 We have 1 RX channel, selecting channel #0 DSOAPY DEBUG soapy.c:305 We have 1 TX channel, selecting channel #0

1 0

SDR reccomendation
by nishackle＠gmail.com 24 Dec '25

24 Dec '25

Hi All, I hate reaching out like this, but I'm at the limit of my knowledge. I've got some AMPS handsets i'd like to make use of-back to my PBX if possible. The problem is, i've not been able to get AMPS to work with any of the SDR's I have. I have a HackRF, A URAN1 and a Pluto. I can open the URAN as a USRP device with the following: amps --sdr-soapy \ --sdr-device-args "driver=uhd" \ --sdr-channel 0 \ --sdr-samplerate 1000000 \ --sdr-bandwidth 250000 \ --sdr-rx-gain 20 \ --sdr-tx-gain 30.0 \ -k 334 -T CC/PC/VC \ -k 336 -T VC \ -p -s 192000 -o --fast-math Which appears to work, but the radio doesn't ever actually transmit, the SDR works, because I use it with OpenBTS to make a GSM station. I spent a $400 on a secondhand limeSDR mini, but that turned up broken in the post. Is there an easily obtainable SDR that anyone else has got working? Thanks, Nick

2 1

Can someone mind checking over my 1g base station?
by plaskg.90＠gmail.com 14 Nov '25

14 Nov '25

Hello all, With the help of Harald I have been able to construct a wired base station for the TACS network! I wondered if someone here can check over what I have so far done, to see if I have made any mistakes (which is quite likely!). Manly, I have used some 2w attenuators in the system between the phone and the splitter/combiner and I am worried that the phones I have will transmit at a higher power (I have a Motorola 4800x, Motorola independent (DynaTAC) and a Vodafone VT1) and burn out the attenuators (which would severely damage the transmitter on the phone). I will be happy to send anyone photos of my setup (I don’t believe I can attach them here). Again, I am still quite new to RF in general, so help much appreciated. :)

2 1

Re: LimeSDR Mini 2.0
by Mario García-Oliva 25 May '25

25 May '25

Hey. Did you manage to try out Osmocom-Analog with the LimeSDR 2? Had any issues with it?

1 0

LimeSDR Mini 2.0
by MKS 31 Dec '24

31 Dec '24

Hello, are there any known issues in using the LimeSDR Mini 2.0? I see that the original LimeSDR Mini is supported - there is published documentation on using osmocom-analog with it. Can I follow the same installation procedures using the LimeSDR Mini 2.0 as shown for the LimeSDR Mini? Thanks

1 0

Having trouble transmitting with USRP
by h416984j＠gmail.com 27 Nov '24

27 Nov '24

Hi, I have been interested in trying out Osmocom-analog's AMPS implementation. I purchased an Ettus B210 clone device and built osmocom-analog from source as described on osmocom-analog.eversberg.eu. Everything went well until I started the program and tried to transmit, I received no Tx (output) and the built-in graphs and visualizers had strange output unlike what was expected: https://imgur.com/a/Ghr1cju. I used Ubuntu 22.04 and UHD driver 4.7.0. I am truly at a loss at what is causing the strange output, I also tried launching with soapy and several other arguments. Additionally, the LimeSDR Mini V2 I had previously acted the same way as well, so I'm unsure what the problem is. Any advice will be appreciated, and more information can be provided. Thank you. Full log with debug enabled shared below: sudo amps --sdr-uhd --channel 334 --channel 332 --fast-math --sdr-rx-gain -12 --sdr-tx-gain 6 --samplerate 999999 -v 1 DOPTIONS INFO options.c:128 Config file '/root/.osmocom/analog/amps.conf' seems not to exist, using command line options only. DOPTIONS INFO options.c:296 Command line option '--sdr-uhd' DOPTIONS INFO options.c:294 Command line option '--channel', parameter '334' DOPTIONS INFO options.c:294 Command line option '--channel', parameter '332' DOPTIONS INFO options.c:296 Command line option '--fast-math' DOPTIONS INFO options.c:294 Command line option '--sdr-rx-gain', parameter '-12' DOPTIONS INFO options.c:294 Command line option '--sdr-tx-gain', parameter '6' DOPTIONS INFO options.c:294 Command line option '--samplerate', parameter '999999' DOPTIONS INFO options.c:280 Command line option '-v' ('--verbose'), parameter '1' Selected System ID (SID) 40 belongs to: Salinas, CA (GTE Mobile) San Francisco, CA (GTE Mobile) San Jose, CA (GTE Mobile) San Rosa, CA (GTE Mobile) Santa Barbara, CA (GTE Mobile) DDSP DEBUG dsp.c:150 Generating sine table for SAT signal. DAMPS DEBUG amps.c:597 Creating 'AMPS' instance for channel = 334 of band B (sample rate 999999). DSENDER DEBUG sender.c:77 (chan 334) Creating 'Sender' instance DJITTER INFO jitter.c:129 (334) Reset jitter buffer. DJITTER INFO jitter.c:113 (334) Created jitter buffer. (samperate=8000, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DJITTER INFO jitter.c:129 (334) Reset jitter buffer. DJITTER INFO jitter.c:113 (334) Created jitter buffer. (samperate=999999, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DDSP DEBUG dsp.c:202 (chan 334) Init DSP for transceiver. DSENDER DEBUG sender.c:308 (chan 334) Maximum deviation: 8.0 kHz, Maximum modulation: 10.0 kHz DSENDER DEBUG sender.c:309 (chan 334) Deviation at speech level: 2.9 kHz DDSP DEBUG dsp.c:218 Use 99.9999 samples for full bit duration @ 999999. DDSP DEBUG dsp.c:234 Bit window length: 100 DDSP DEBUG dsp.c:235 -> Samples in window to analyse level left of edge: 25..49 DDSP DEBUG dsp.c:236 -> Samples in window to analyse level right of edge: 50..74 DDSP DEBUG dsp.c:175 Generating smooth ramp table. DDSP DEBUG dsp.c:259 Sat detection interval is 66 ms. DDSP DEBUG dsp.c:927 (chan 334) SAT detector reset: Initial state. DAMPS DEBUG amps.c:399 (chan 334) State change: (NULL) -> IDLE DAMPS INFO amps.c:685 (chan 334) Entering IDLE state, sending Overhead/Filler frames on combined control & paging channel. DDSP DEBUG dsp.c:927 (chan 334) SAT detector reset: Change to FOCC. DDSP INFO dsp.c:944 (chan 334) Change mode to FOCC DDSP DEBUG dsp.c:967 (chan 334) Reset FSK frame transmitter, due to setting DSP mode. DAMPS NOTICE amps.c:638 Created channel #334 (System B) of type 'CC/PC' = combined control & paging channel Base station on channel 334 ready (combined control & paging channel), please tune transmitter to 880.020 MHz and receiver to 835.020 MHz. (-45.000 MHz offset) DAMPS NOTICE amps.c:558 Channel number 332 belongs to a control channel, but your channel type 'voice channel' requires it to be on a voice channel number. Some phones may reject this, but all my phones don't. DAMPS DEBUG amps.c:597 Creating 'AMPS' instance for channel = 332 of band A (sample rate 999999). DSENDER DEBUG sender.c:77 (chan 332) Creating 'Sender' instance DJITTER INFO jitter.c:129 (332) Reset jitter buffer. DJITTER INFO jitter.c:113 (332) Created jitter buffer. (samperate=8000, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DJITTER INFO jitter.c:129 (332) Reset jitter buffer. DJITTER INFO jitter.c:113 (332) Created jitter buffer. (samperate=999999, target_window=60ms, max_window=1000ms, flag:latency=true flag:repeat=true) DDSP DEBUG dsp.c:202 (chan 332) Init DSP for transceiver. DSENDER DEBUG sender.c:308 (chan 332) Maximum deviation: 8.0 kHz, Maximum modulation: 10.0 kHz DSENDER DEBUG sender.c:309 (chan 332) Deviation at speech level: 2.9 kHz DDSP DEBUG dsp.c:218 Use 99.9999 samples for full bit duration @ 999999. DDSP DEBUG dsp.c:234 Bit window length: 100 DDSP DEBUG dsp.c:235 -> Samples in window to analyse level left of edge: 25..49 DDSP DEBUG dsp.c:236 -> Samples in window to analyse level right of edge: 50..74 DDSP DEBUG dsp.c:175 Generating smooth ramp table. DDSP DEBUG dsp.c:259 Sat detection interval is 66 ms. DDSP DEBUG dsp.c:927 (chan 332) SAT detector reset: Initial state. DAMPS DEBUG amps.c:399 (chan 332) State change: (NULL) -> IDLE DAMPS INFO amps.c:692 (chan 332) Entering IDLE state (sending silence / no RF) on voice channel. DDSP DEBUG dsp.c:927 (chan 332) SAT detector reset: Disable FVC. DDSP INFO dsp.c:962 (chan 332) Change mode from FVC to OFF DDSP DEBUG dsp.c:967 (chan 332) Reset FSK frame transmitter, due to setting DSP mode. DAMPS NOTICE amps.c:638 Created channel #332 (System A) of type 'VC' = voice channel Base station on channel 332 ready (voice channel), please tune transmitter to 879.960 MHz and receiver to 834.960 MHz. (-45.000 MHz offset) DSDR DEBUG sdr.c:149 Open SDR device DSDR INFO sdr.c:168 Require bandwidth of each channel is 2 * (8.0 deviation + 10.0 modulation) = 36.0 KHz DSDR INFO sdr.c:345 We move center frequency between the two channels in the middle, to prevent them from overlapping with DC level. DSDR INFO sdr.c:133 TX Spectrum: 2 1 ---------------------------------------+--------------------------------------- DSDR INFO sdr.c:135 Frequency 1 = 880.0200 MHz DSDR INFO sdr.c:135 Frequency 2 = 879.9600 MHz DSDR INFO sdr.c:357 Total bandwidth (two sidebands) for all TX Frequencies: 960 00 Hz DSDR INFO sdr.c:365 Using center frequency: TX 879.990000 MHz DSDR DEBUG sdr.c:370 Frequency #0: TX offset: 0.030000 MHz DSDR DEBUG sdr.c:370 Frequency #1: TX offset: -0.030000 MHz DSDR INFO sdr.c:391 Using gain: TX 6.0 dB DSDR INFO sdr.c:457 We move center frequency between the two channels in the middle, to prevent them from overlapping with DC level. DSDR INFO sdr.c:133 RX Spectrum: 2 1 ---------------------------------------+--------------------------------------- DSDR INFO sdr.c:135 Frequency 1 = 835.0200 MHz DSDR INFO sdr.c:135 Frequency 2 = 834.9600 MHz DSDR INFO sdr.c:469 Total bandwidth (two sidebands) for all RX Frequencies: 96000 Hz DSDR INFO sdr.c:477 Using center frequency: RX 834.990000 MHz DSDR DEBUG sdr.c:482 Frequency #0: RX offset: 0.030000 MHz DSDR DEBUG sdr.c:482 Frequency #1: RX offset: -0.030000 MHz DSDR INFO sdr.c:492 Using gain: RX -12.0 dB DSDR INFO sdr.c:525 Using local oscillator offset: -1000000 Hz DUHD INFO uhd.c:59 Using device args "" DUHD INFO uhd.c:60 Using stream args "" DUHD INFO uhd.c:61 Using tune args "" DUHD INFO uhd.c:64 Creating USRP with args ""... [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~ jammy1 [INFO] [B200] Detected Device: B210 [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Setting master clock rate selection to 'automatic'. [INFO] [B200] Asking for clock rate 16.000000 MHz... [INFO] [B200] Actually got clock rate 16.000000 MHz. [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] Actually got clock rate 31.999968 MHz. [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] OK [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] OK [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] OK DUHD NOTICE uhd.c:422 Given RX gain -12.000 is not supported, we use 0.000 [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] OK [INFO] [B200] Asking for clock rate 31.999968 MHz... [INFO] [B200] OK | | | /|===|\ -=O=- / |\ /| \ ~ | AMPS / | X | \ ~ / |===| \ / | |\ \ / /| | \ \ ~ |--| / / |===| \ \ /|\/|\ / / | | \ \ / |--| \ / / | | \ \ / | |\ \ / / |===| \ \ __ / /|--| \ \ / / | | \ \ \_ / / | | \ \ / / | | \ \ \ / / | | \ \______/ / | | \| \| \========================================================================= \_______|/\|______ _***_*__**_***___**_*_| X | |MMMM| \__ |\/| \______/* ** * * * ** * |/ \|______________|MMMM| _____ \_|/\| * * * * ** * * * * * * |\ /|*____/ ~ ~ ~ ~ / ~ ~\_______I__I_________*______*_*___*__*___*__*_*_| X |/ ~ ~ _________ _______\ _ _ _ _ _ _ _ _ _ _ |/_\/ ~ ______/ _ _ _ _ _ _ _ _/~ ~ ____/ ~ ~ ~ _ _ _ _ _ _ _ /_____/ ~ ____________ __/~\______________ _ _ _ _ _/ ~ ~ __________/ ~ ~ ~ ~ ~ ~ \____________________________/ / ~ ~ ~ ~ ~ DSDR DEBUG sdr.c:707 Create threads! DFRAME INFO frame.c:2723 Transmit: Word 1 - System Parameter Overhead DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2736 SID1: 20 (First part of the system identi fication field) DFRAME DEBUG frame.c:2734 EP: 0 = No (Extended Protocol Capabilit y Indicator) DFRAME DEBUG frame.c:2734 AUTH: 0 = No (Support of authentication p rocedures described in TIA/EIA-136-510) DFRAME DEBUG frame.c:2734 PCI: 0 = No (Set to 1 if Control Channel can assign digital traffic channels) DFRAME DEBUG frame.c:2736 NAWC: 4 (Number of additional words comin g field) DFRAME DEBUG frame.c:2734 OHD: 6 = Word 1 of system parameter messa ge (Overhead Message Type field) DFRAME DEBUG frame.c:2736 P: 1530 (Parity field) DFRAME INFO frame.c:2723 Transmit: Word 2 - System Parameter Overhead DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2734 S: 1 = Yes (Serial number field) DFRAME DEBUG frame.c:2734 E: 1 = Yes (Extended address field) DFRAME DEBUG frame.c:2734 REGH: 1 = Yes (Registration field for hom e stations) DFRAME DEBUG frame.c:2734 REGR: 1 = Yes (Registration field for roa ming stations) DFRAME DEBUG frame.c:2734 DTX Support: 0 = DTX Not Supported (Indicates th e nature of DTX supported on an analog voice) DFRAME DEBUG frame.c:2734 N-1: 20 = 21 (N is the number of paging channels in the system) DFRAME DEBUG frame.c:2734 RCF: 1 = Yes (Read-control-filler field) DFRAME DEBUG frame.c:2734 CPA: 1 = Yes (Combined paging/access fie ld) DFRAME DEBUG frame.c:2734 CMAX-1: 20 = 21 (CMAX is the number of acce ss channels in the system) DFRAME DEBUG frame.c:2734 END: 0 = No (End indication field) DFRAME DEBUG frame.c:2734 OHD: 7 = Word 2 of system parameter messa ge (Overhead Message Type field) DFRAME DEBUG frame.c:2736 P: 437 (Parity field) DFRAME INFO frame.c:2723 Transmit: Registration ID Message DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2736 REGID: 196474 (Registration ID field) DFRAME DEBUG frame.c:2734 END: 0 = No (End indication field) DFRAME DEBUG frame.c:2734 OHD: 0 = Registration ID (Overhead Messa ge Type field) DFRAME DEBUG frame.c:2736 P: 614 (Parity field) DFRAME INFO frame.c:2723 Transmit: Registration Increment Global Action Message DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2734 ACT: 2 = Registration increment (Global action field) DFRAME DEBUG frame.c:2736 REGINCR: 300 (Registration increment field) DFRAME DEBUG frame.c:2736 RSVD: 0 (Reserved for future use) DFRAME DEBUG frame.c:2734 END: 0 = No (End indication field) DFRAME DEBUG frame.c:2734 OHD: 4 = Global action (Overhead Message Type field) DFRAME DEBUG frame.c:2736 P: 448 (Parity field) DFRAME INFO frame.c:2723 Transmit: Access Type Parameters Global Action Message DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2734 ACT: 9 = Access type parameters (Global action field) DFRAME DEBUG frame.c:2734 BIS: 0 = Ignore Idle-Busy after access ( Busy-Idle status field) DFRAME DEBUG frame.c:2734 PCI_HOME: 0 = No (Home Protocol Capability In dicator) DFRAME DEBUG frame.c:2734 PCI_ROAM: 0 = No (Roam Protocol Capability In dicator) DFRAME DEBUG frame.c:2734 BSPC: 0 = Reserved for backward compatibil ity (Base Station Protocol Capability field) DFRAME DEBUG frame.c:2734 BSCAP: 0 = Reserved for backward compatibil ity (Base Station Core Analog Protocol field) DFRAME DEBUG frame.c:2736 RSVD: 0 (Reserved for future use) DFRAME DEBUG frame.c:2734 END: 1 = Yes (End indication field) DFRAME DEBUG frame.c:2734 OHD: 4 = Global action (Overhead Message Type field) DFRAME DEBUG frame.c:2736 P: 1790 (Parity field) DFRAME INFO frame.c:2723 Transmit: Control-Filler Message DFRAME DEBUG frame.c:2734 T1T2: 3 = Overhead Message (Type field) DFRAME DEBUG frame.c:2736 DCC: 0 (Digital color code field) DFRAME DEBUG frame.c:2736 010111: 23 (bit combination 23) DFRAME DEBUG frame.c:2734 CMAC: 4 = -10 dbW (100 Milliwatts) (Contr ol mobile attenuation field) DFRAME DEBUG frame.c:2736 SDCC1: 0 (Supplementary Digital Color Code s) DFRAME DEBUG frame.c:2736 11: 3 (bit combination 3) DFRAME DEBUG frame.c:2736 SDCC2: 0 (Supplementary Digital Color Code s) DFRAME DEBUG frame.c:2736 1: 1 (bit combination 1) DFRAME DEBUG frame.c:2734 WFOM: 1 = Yes (Wait-for-overhead-message field) DFRAME DEBUG frame.c:2736 1111: 15 (bit combination 15) DFRAME DEBUG frame.c:2734 OHD: 1 = Control-Filler (Overhead Messag e Type field) DFRAME DEBUG frame.c:2736 P: 1921 (Parity field) DFRAME INFO frame.c:3515 (chan 334) Subsequent system/filler frames are not sho wn, to prevent flooding the output. DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 4.080 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms DSDR DEBUG sdr.c:952 read delay = 2.040 ms DSDR DEBUG sdr.c:884 write delay = 2.040 ms [continues like this]

1 1

Problem getting AMPS to start
by Shawn 05 May '24

05 May '24

Hello all. My name is Shawn. I am having a problem getting osmocom amps to successfully start. lsusb shows my B210 on Bus 3, Device 3. uhd is installed. uhd find devices shows: INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.6.0.0-141-g0f2007fc -------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: serial: 191796 name: MyB210 product: B210 type: b200 I am attempting to start AMPS with: amps --sdr-uhd -k 334 -k 332 -p -d -F no --sysinfo sid=18 1234567890 The result is: DSENDER ERROR sender.c:240 No device for transceiver! There is more text before and after the above message. I can paste it if you like. But I think the problem is I am not using proper syntax to tell AMPS to use the my B210. I have tried SoapySDR and have received the same results. I would appreciate help in how I can properly tell the osmocom software to use my B210. Thank you very much, -Shawn

1 0

osmocom-analog installation problem
by gvideki79＠gmail.com 26 Jan '24

26 Jan '24

HELLO Everybody! I have a problem during installation of osmocom-analog to my computer, i am running Oracle VM virtualbox under Win11 OS. There is a syntax error while running ./configure - line 5619: sytax error near unexpected token 'ALSA' line 5619: PKG_CHECK_MODULES(ALSA, ALSA >= 1,0, with alsa=yes, with alsa=no) "make" and "make install " commands do not work. Please help me if you can, I will send you some screenshots. We appreciate your work! Greetings from HUNGARY! George

2 1

2026

2025

2024

2023

2022

2021

osmocom-analog