|
M172DMR
|
01-01-2021, 09:19 PM
Change the name from DMRIds.dat to DMRIDs.dat in your M172DMR.ini file to match your fiename. You will want to update that file every so often too. You can get an update here: http://www.dudetronics.com/ar-dns/DMRIDs.dat
03-05-2021, 01:17 PM
Hello everyone,
after many tests I could not find the problem, some help please? D: 2021-03-05 10:31:43.664 0010: C8 84 0B 7E B1 87 C7 62 50 31 30 51 BD E4 AA C7 *...~...bP10Q....* D: 2021-03-05 10:31:43.664 0020: 41 21 10 00 00 00 0E 23 23 4D 8E 49 95 C9 A2 61 *A!.....##M.I...a* D: 2021-03-05 10:31:43.664 0030: 20 5D 8E 8B 93 00 00 * ].....* D: 2021-03-05 10:31:43.664 DMR Slot 2, DelayBuffer: appending data D: 2021-03-05 10:31:43.720 Network Received D: 2021-03-05 10:31:43.721 0000: 44 4D 52 44 07 21 E3 7E 00 08 B7 0D 3C DD 48 90 *DMRD.!.~....<.H.* D: 2021-03-05 10:31:43.721 0010: C8 84 0B 7E BF B5 C7 01 21 69 C8 A1 73 8C 6E E2 *...~....!i..s.n.* D: 2021-03-05 10:31:43.721 0020: 33 47 F7 D5 DD 57 DF D3 F6 1C EF 71 BB 6A C6 27 *3G...W.....q.j.'* D: 2021-03-05 10:31:43.721 0030: 62 5E 19 C2 EB 00 00 *b^.....* D: 2021-03-05 10:31:43.721 DMR Slot 2, DelayBuffer: appending data D: 2021-03-05 10:31:43.757 DMR Slot 2, DelayBuffer: returning data, elapsed=0ms M: 2021-03-05 10:31:43.757 DMR header received from IS0GQX to TG 2231 D: 2021-03-05 10:31:43.758 DMR Slot 2, DelayBuffer: returning data, elapsed=1ms D: 2021-03-05 10:31:43.788 Network Received D: 2021-03-05 10:31:43.789 0000: 44 4D 52 44 08 21 E3 7E 00 08 B7 0D 3C DD 48 81 *DMRD.!.~....<.H.* D: 2021-03-05 10:31:43.789 0010: C8 84 0B 7E D8 3B 81 21 46 61 88 F4 10 FD 44 C6 *...~.;.!Fa....D.* D: 2021-03-05 10:31:43.789 0020: 32 01 30 A0 A0 00 F9 10 7D 44 69 0F 19 8A E6 67 *2.0.....}Di....g* D: 2021-03-05 10:31:43.789 0030: 33 A5 1C 43 70 00 00 *3..Cp..* D: 2021-03-05 10:31:43.789 DMR Slot 2, DelayBuffer: appending data D: 2021-03-05 10:31:43.820 DMR Slot 2, DelayBuffer: returning data, elapsed=64ms Segmentation fault I am using: HBlink on VPS; M172DMR on raspberry M17Reflector on VPS Thanks in advance 73, Bruno IS0GQX https://multiprotocol.is0.org/ (12-15-2020, 06:49 AM)DV8AWC Wrote: Nice work Doug. Is there a way to run multiple instances of M172DMR on the same rpi? Yes, I run 3 instances on the same Pi. Just make an ini file for each instance. (03-05-2021, 01:17 PM)is0gqx Wrote: Hello everyone, I have tested on all current Pistar builds on Pi2 and higher, and the current PiOS version *without* doing any updates after install from image. The md380 firmware crashes on PiOS after updating software, and I haven't looked into why. -Doug
03-07-2021, 08:39 AM
(03-06-2021, 07:36 PM)AD8DP Wrote:(12-15-2020, 06:49 AM)DV8AWC Wrote: Nice work Doug. Is there a way to run multiple instances of M172DMR on the same rpi? Ciao Doug, many thanks for your kind and appreciated reply. 73, Bruno
09-01-2021, 05:48 PM
The same thing happens to me, the same Segmentation fault.
I have tried it on raspberry pi 2, pi3, and pi4, with debian buster distribution and I always get this segmentation fault problem.
The md380 firmware segfaults started on RPi kernels > 5.4.x. The problem has been resolved in latest git of md380_vocoder and also requires the latest git for all cross mode tools in my fork of MMDVM_CM that use md380_vocoder: M172DMR, DMR2M17, P252DMR, DMR2P25, and USRP2DMR.
https://github.com/nostar/md380_vocoder https://github.com/nostar/MMDVM_CM An explanation of the issue can be read at my pull request for md380-emu in the md380tools repo here: https://github.com/travisgoodspeed/md380tools/pull/932 |
|
« Next Oldest | Next Newest »
|
