开云体育

Version 0.9.1-1 has been released Changelog: - Rebased releases on GNU Radio 3.10 - Added DMR transceiver (repeater mode and DMO) - Switch to using the polyphase channelizer and synthesizer for the multi- carrier mode - Fixed regressions in some Opus 10K demodulators (2FSK, 4FSK, GMSK) - Removed some broken operating modes Notably, this release is the first to use GNU Radio 3.10. Testing found a number of issues related to package version upgrades. Some of them have been fixed, others may still be present. After the release it was discovered that a number of dependencies were not specified correctly or missing, so it is advised to use the dependency list which has been corrected later on the master branch after the release was made. If you notice any issues running this version, please report them using the Github or Codeberg bug trackers.

Hello all, Wondering if this is a possibility to do. I want to look at playing with some tier 3 features and I have a few duplex mmdvm hotspots based off of pi zero W’s laying around. Can these be purposed to run the RF front end with the trunk controller on a more powerful device (such as a x86 based thin client). Thanks in advance and I apologise if it sounds like a stupid question.

Using LimeSDR equipment (LimeNET-Micro / LimeSDR-mini) and MMDVM + GNU radio as core components, the implementation of a full duplex SDR base station was created in order to support the DMR, System Fusion, D-Star and M17 amateur digital voice standards in a multi-carrier configuration, with up to 7 transmitted carriers within 200 kHz bandwidth, in any combination of operating modes and with a configurable channel separation. The channel / mode matrix is entirely user configurable by using multiple MMDVM instances, each of them dedicated to one operating channel. The long term goal is to continue software development and combine LimeSDR equipment with the LimeRFE front-end and capable computing hardware to supply a self-contained, easily deployable base station in NITB style. The end-user should only need to supply their own antennas, power amplification and duplexing hardware for a complete SDR base station solution. The current testing status has confirmed operation of the DMR and System Fusion standards, while D-Star and M17 modes are still theoretical and need to be tested. There is interest in further extended support for the new M17 open digital voice standard and investigating how a multi-carrier approach can provide amateur radio operators new avenues of experimentation with topics like trunking, multiple access, IP network facilities and other such topics. Work is in progress to improve code, refine user documentation and create deployable packages. A video demonstrating the operation of a four-channel mixed DMR and System Fusion duplex repeater system can be seen here: https://www.youtube.com/watch?v=kbQeckQ6M1g All credit for the work supporting this project goes to Jonathan Naylor, Peter Rakesh and all the people who created or contributed to MMDVM and GNU Radio along the years. Regards, Adrian YO8RZZ

Hallo Adrian, DMR Tier III is mainly running smoothly in the software side here. Now I want to make the next step. I was able to aquire two narrow bandpass filters for input and output. A little too much loss for production use, but TX/RX isolation is definitely good enough for testing. Also, a friend gave me a suitable 70cm preamp that is waiting for testing. Do you have an opinion about the best PA? Currently, with 100% TX gain in qradiolink, I roughly get -19dBm per Carrier directly on the TX connector of the Lime With a small chinese amplifier (WYDZ-PA-1M-750MHz-3W) I can amplify this to about +15dBm per Carrier. I did not check the signal quality yet in depth with multiple carriers transmissing at the same time. From your experience: - What would be a reasonable TX gain setting for the Lime Mini 2 to get 7 clear carriers out of the SDR? - What amplifier chain would you recommend to get the output signal to a resonable level? In the beginning, 10-100mW per Carrier would be fine. At the end I am aiming for at least 50W for all 7 carriers together, so at least 7W per carrier, maybe more to account for filter and cable losses. On the testing method: What's the easiest way to get qradiolink to produce an not necessary modulated FM signal all the 7 channels Thanks in advance Christian DB9CR

The DMR trunking controller has been updated to version 0.1.6 Release information: * More robust handling of SMSs on the control channel * UDT message payloads are grouped together to avoid intermingled CSBKs * Longer than 46 character SMSs sent from the GUI of dmrtc are now sent as several consecutive messages according to the UDT specification, instead of being truncated * Added support for individual packet data call procedures (long SMS in ISO 8- bit format, unit-to-unit and unit-to-group packet data) To use the new version: $ git checkout 0.1.6 To revert back to the old version in case of issues: $ git checkout 0.1 Please report any bugs on the Github issue tracker. To use long SMS, configure your radio to send long message packet data on the dedicated channel (not shared). Message character set must be ISO 8-bit. Note that such SMSs received on the dedicated channel will be re-broadcast on the control channel as multiple UDT messages so all types of radios can receive it. Thanks go to Marek again for the DMR dissectors in ok-dmrlib. Adrian

[image: image.png] I try to tx ft4/ft8 via a pluto. Transmit Wsjtx audio via Sdrangel and Hackrf I can drive a PA and make some contacts, while using QRadioLink and Pluto as receiver on 433 MHz. TX and RX device args in QRadioLink are soapy=0,device=PlutoSDR,driver=plutosdr,label=PlutoSDR#0usb:3.28.5,uri=usb:3.28.5 Would it make sense to try to get HackRF as TX advice? It does not show op, but maybe with some soapy drivers and settings ... End goal should be TX with Pluto. Audio level meter in the screenshot above indicates the audio does arrive in QRadioLink. PTT is pressed, TX freq 2400 MHz. I have the idea there is some TX level config missing or too low, and do not have access to SHF power meter. All hints welcome! 73 de on1aad

Version 0.9.0-1 of QRadioLink is now available as source packages. Changelog: * Added configurable time domain display * Added UDP to ZeroMQ proxy (enables SVXLink audio as one of the FM carriers in MMDVM-multi mode) * FM is now one of the modes supported by MMDVM-multicarrier SVXLink-related changes: you can now add a single FM repeater channel in the multi-carrier transceiver mode. You will need to set the configuration option *zmq_proxy_channel* to the relevant FM channel number (should never be channel 1, so the value goes from 2 to 7). To use the FM carrier with svxlink, start the application using the following CLI parameters: $ qradiolink --mmdvm --udp Then configure svxlink to send audio via UDP to and from the ports configured in qradiolink. When combining MMDVM-SDR with this new functionality, you will need to not start at all the MMDVM instance for the channel number configured here, otherwise the new functionality will not work. What this means is that now you can directly mix FM with DMR, YSF or M17 on your multi-carrier base-station (at the moment only one channel). Note that other applications can also provide audio via UDP as well, so feel free to experiment with this functionality. The documentation will soon be updated with this information. In the future, we are looking at the possibility of implementing an MPT1327 analog trunking base station with svxlink as a network back-end. If you are interested in making this happen and want to contribute, contact me via this mailing list. Adrian

I've created a documentation page to keep track of supported radios and what exactly is supported for each radio: https://qradiolink.org/docs/MMDVM/radios.html Thanks Christian and sky4mazon for your feedback. Adrian

Hello, can anyone shed some light on how to identify Tier III compatible Motorola radios? What Motorola radios would be recommended for dmrtc? On Hypera it's the SW00029 license, can be checked in the CPS in Common/Feature Control, item "DMR Trunking". 73 Christian DB9CR

Decided to start a new thread. Spent about 15 hours testing. Hyteras are great, everything works, sms, location etc. After much ado was able to attach SL4000e. It took ages to get it to register. But it did. So, on moto, only fixed channel plan works. The moment I enable absolute chan assn - it stops working (establishing a call). Even with flex channels setup in moto cps. Same. Only fixed plan works every time (and I do NOT click 'use fixed plan' in dmrtc, just uncheck absolute ch assn). No problem, switched hyteras to fixed plan, all good. Private calls work. Sms does not work, dgna does not work. Ping does. Sms to private and group fails, although hyteras show 'receiving data' then fail out. There are only one option relating to text transmission, and it only has 3 options (Advantage mode, DMR Standard and DMR T3 IOP. none work). Also, channel numbers in moto cps are wildly different from what hytera uses (shows in cps) and dmrtc (same as hyt). For example dmrtc/hyt group 1002222 (flat dial plan) needs to be entered as 1467028 in moto cps. Weird, and I don't thing the difference is static. As usual, willing to contribute. Amazing new life for a lot of hardware.

The crashes in dmrtc related to disabling DMRGateway should now be fixed in the master branch. I've also introduced some sanity checks on some config values. It is no longer possible to set less than one gateway or one channel. If not using gateways, instead of setting number of gateways to zero, use the toggle which enables or disables DMRGateway. Adrian

Hey all and thanks for great work. I'm wondering if I'm dreaming if I want to have LimeSDRmini with DVM-SDR in P25 trunking mode (as dvmhost does)? Thank you!

Hi Christian, Great, thanks for letting me know. I'll put your radio model in the list as supported now. Private calls are a bit of a problem, same as private SMS, from a routing perspective. If you have only one DMR system (eg. Brandmeister) connected, private calls can be passed on using PassAllPC in DMRGateway.ini for that network configuration. The situation gets trickier if you are connected to multiple systems (DMR+, Brandmeister, etc.). Then it is pretty much impossible to know where a particular private call should be routed to. This is a pretty bad limitation of the current system that needs to be worked on in the future, but I'm open to pretty much any architecture changes that enable more features. SMS should only work between two Tier III sites and radios, the UDT message protocol is only standardized in TS 102 361-4 so Tier II radios will not be able to receive them. In addition, I remember that I needed to modify something in MMDVMHost for UDT short data message support, so classical hotspots might not even be able to pass them on to RF. I'm not sure what the situation is on the reflector software side and if it will support passing through this type of messages. Brandmeister may be able, other networks may not. So needs further testing and maybe additional code. Yes, that seems like the ideal. Unfortunately other DMR networks don't support this system, and many people use other networks, myself included. It would be nice it there was some standards group among us amateurs that aimed at compatibility between implementations. Anyway there is really no need for complications like a SIP trunk. A simple limitation being removed on the reflector side would be enough. And that limitation is the blocking at reflector-side of any calls coming on a timeslot if there is already a call ongoing in that timeslot. Then you can define one Tier III site as one connection only. A call is basically a sequence of UDP packets with a stream id, and as long as you have enough bandwidth there is no reason not to have hundreds of calls at the same time on one UDP socket connection. 73, Adrian

Update: Two radios with different DMR IDs connectd to same dmrtc can do private calls. Private call from radio on dmrtc to brandmeister tier ii doesn't work. Trunking-Radio looks like call established, but nothing arrives on brandmeister radio. SMS between two radios on same dmrtc works. SMS from dmrtc to brandmeister fails: "Sending Message...." -> "Send failed" (pressed PTT on target radio connected to brandmeister Tier II first to make sure that brandmeister knows where the other radio is) Am 10.07.2024 um 17:18 schrieb nospam.groupsio@...:

Hello Adrian, while dmrtc has a headless mode, it seems that still, a connection to an X11 server is needed to start: db9cr@tmo:~/software$ ( cd dmrtc/build ; DISPLAY= ./dmrtc ) qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. db9cr@tmo:~/software$ grep headless ~/.config/dmrtc/dmrtc.cfg headless_mode = 1; In headless mode, dmrtc should be able to start as a daemon without an X11 display available. 73 Christian DB9CR

Hello Adrian, my setup is still not working, but after a lot of testing, I have some insights - maybe that rings a bell? - Sometimes, the Hytera radio is able to book into the dmrtc, but most of the time not. I have not recoginzed a pattern and it's not reproducable. - I tried to access the 7 channels with a Tier II Anytone Radio. On channels 5-7 (below center), I can wake up the transmitter, and MMDVMhost shows a lot of received and transmitted packets. The dmrtx complains (Rejected local id ......., not registered with the site) , but on MMDVM level this is working. Also, channel 4 (the highest frequency), _sometimes_ works. On Channel 1, no wakeup is needed, but also I see no received DMR frames in the log when I press PTT on my anytone. On Channel 2-3 and usually on 4 also, I only see that the downlink was activated, but I do not see any packes being received afterwards. Reseach on the internet raises the suspicion that this could be related to DMRDelay. But why should a different delay be needed for the different channels? I have DMRDelay=90 (and burst_delay_msec=100, if that's related). As some channels work and others not, and the channel is aalways ctivated, I would non suspect rx-/txgain-Problems. - I tried to set the control channel to 7 in dmrtc and in the mmdvmhost config file for channel 7. Magically, the registration works reliably in this setup and I could switch between talkgroups. - When booked in with the hytera and subscribed to tg91, the radio bings and beeps all the time, but I cannot hear any voice transmissions from TG91 on the Hytera. I do see TX data on channel 1 timeslot 1 .My suspicion is that channel 1 TS1 is hardwired somewhere in dmrtc and/or qradiolink, as it's carrier is always on and I cannot disable RF channel 1/Timeslot 1 in DMRTC, even when the control channel in on RF channel 7. - Weirdly, I can partially hear TG91 being transmitted on my Anytone on Channel 1 TS in monitor mode. Any ideas how to make channels 1-4 receive reliably? It's unclear to me what could be the difference to channels 5-7, that do receive reliably. Thanks Christian DB9CR

Greetings, A new feature is being developed at the moment to complement the frequency domain and constellation displays: time domain display. You may want to contribute some suggestions regarding the way this feature should work, so this is the time to do so. Demo video: https://www.youtube.com/watch?v=P-PWfwLN15M Cheers, Adrian

Changelog for version 0.8.12-1: * Consolidate DMR Tier III base station functions * Direct support for Ettus USRP via gnuradio-uhd and libuhd * Reduced roundtrip latency to half (350 ms) for the DMR TDMA RF channel * Added RSSI calculation for MMDVM channel * Compatibility with tag 1.1 of MMDVM-SDR * Added documentation for DMR trunking mode with MMDVM The newly introduced DMR tier III base station functionality is described in this page: https://qradiolink.org/DMR-tier-3-trunked-radio-BTS-software-defined-radio.html Regards, Adrian