开云体育

1. It has trouble registering because of look n2. With fixed plan it registers easily. 2. I understand! That does not work with motorola. Exactly same setings (both tc and radio side) work on

Interesting findings, thanks! I'll try to address them one by one below. It might be a good idea to capture some logs during the registration attempts, both in MMDVMHost and in dmrtc, so we can see

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

Yes, that is already planned and will be implemented at some point as an optional feature.

As sort of addition to wishlist - Auth not just being cosmetic feature, but refuse registration for non-auth'ed radios.

Pioneer wagon n.2 here. Ordered PAs of different designs as well as filters. On my Limesdr Mini 1.2 max tx limit is 101, I use 80 to 100 (100 equals '+74db max' in lime driver). External cooling,

Hello Christian, Answers below: For my prototype SDR repeater based on the LimeNet Micro v1, I have a tunable 6 cavity UHF Procom duplexer. These guys can be factory / home tuned for multi-carrier

It works, thank you. Had to do little patching but it does now... Really stable, great audio quality (unlike HS+dvmhost t3). So far only one small glitch is seen - if during a group call one party

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

The workaround described in my previous email is valid, you just need to apply it while dmrtc is stopped to avoid the config file being overwritten. A fix will also be implemented, but meanwhile you

Of course I tried it. Many times. No go. I'll take a dirty patch right now.

Please change gateway_number = 1; gateway_enabled = 1; and then try again (even if you don't have any DMRGateway started). Seems like there's a bug in that area.

[5/Aug/2024 03:04:35.817] [Info] Received group short data message request to TG from 1002001, slot 1 to destination 1467029 A: false GI: true Format: 0 UDTFormat: 7 Opcode: 26 RSVD: 0 PF:

Nope, no bind errors. --- control_port = 4939; mmdvm_listen_port = 44550; mmdvm_send_port = 44560; gateway_listen_port = 44660; gateway_send_port = 44670; window_width = 1400; window_height =

Right, that makes sense. Without making any changes to the code, fo you not have a message like "Server could not bind to port..." during startup? That points to a different issue. You either have

[5/Aug/2024 02:31:17.547] [Debug] Allocated physical channel 0, logical channel 89, slot 2 to destination 1002223 and source 1002001 Thread 9 "controller" received signal SIGSEGV, Segmentation

Can you please paste the output of the backtrace here? Or open an issue on Github, either way I need the output to figure out what's happening. If you can, the complete output from gdb

#0 0x000055555557ce95 in UDPClient::writeDataToNetwork(unsigned char*, int) (this=this@entry=0x0, data=data@entry=0x7fffd23feb20 <error: Cannot access memory at address 0x7fffd23feb20>,

gbd reported error in udpclient.cpp at line 149 at crash. That's where my c++ knowledge ends. Something with memcpy and out of bounds?

Thanks for sharing your experience here! These are interesting findings, it seems there are some bugs somewhere, as I've never managed to crash dmrtc with my radios. It would be a great help if you