g4klx / mmdvmhost Goto Github PK

During an over , HIGH BER and LATE MESSAGE with BEEP ..... what is this ??

tnx
73

M: 2016-09-28 17:37:17.747 D-Star, received RF header from IW9GRL /9006 to CQCQCQ
M: 2016-09-28 17:37:53.159 D-Star, received RF end of transmission, 35.5 seconds, BER: 0.0%
M: 2016-09-28 17:37:53.826 D-Star, received RF late entry from IW9GRL /9006 to CQCQCQ

I suggest that the brightness of the Nextion displays should be dimmed to e.g. 50% when in idle mode. This allows for a better recognition if the MMDVM is actually transmittig/receiving or not. And it would stop lighting my whole shack during the night. I will make it configurable with an option in the config. Any suggestions?

Helps only restart (stop\start) the service or reboot RaspberryPi

M: 2016-05-06 16:56:33.526 Mode set to Idle
M: 2016-05-06 17:00:04.331 DMR Slot 2, received network voice header from 2509001 to TG 2501
M: 2016-05-06 17:00:04.337 Mode set to DMR
M: 2016-05-06 17:00:10.558 DMR Slot 2, received network end of voice transmission, 6.2 seconds, 5% packet loss, BER: 0.0%
M: 2016-05-06 17:00:16.952 DMR Slot 2, received network voice header from 2501001 to TG 2501
M: 2016-05-06 17:00:17.595 DMR Slot 2, received network end of voice transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2016-05-06 17:00:24.042 DMR Slot 2, received network voice header from 2501001 to TG 2501
M: 2016-05-06 17:00:29.357 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 1% packet loss, BER: 0.0%
M: 2016-05-06 17:00:39.368 Mode set to Idle
M: 2016-05-06 17:00:55.227 DMR Slot 2, received network voice header from 2501001 to TG 2501
M: 2016-05-06 17:00:55.233 Mode set to DMR
M: 2016-05-06 17:00:59.732 DMR Slot 2, received network end of voice transmission, 4.4 seconds, 4% packet loss, BER: 0.0%
M: 2016-05-06 17:01:02.594 DMR Slot 2, received network voice header from 2509001 to TG 2501
M: 2016-05-06 17:01:05.581 DMR Slot 2, received network end of voice transmission, 3.0 seconds, 4% packet loss, BER: 0.0%
M: 2016-05-06 17:01:14.591 DMR Slot 2, received network voice header from 2509001 to TG 2501
M: 2016-05-06 17:01:27.299 DMR Slot 2, received network end of voice transmission, 12.7 seconds, 2% packet loss, BER: 0.0%
M: 2016-05-06 17:01:37.307 Mode set to Idle
M: 2016-05-06 17:19:28.149 Mode set to DMR
M: 2016-05-06 17:19:38.164 Mode set to Idle
E: 2016-05-06 17:55:21.499 No reply from the modem for some time, resetting it
M: 2016-05-06 17:55:21.499 Closing the MMDVM
M: 2016-05-06 17:55:23.500 Opening the MMDVM
I: 2016-05-06 17:55:25.511 MMDVM protocol version: 1, description: DVMEGA HR2.28
E: 2016-05-06 17:55:25.531 No reply from the modem for some time, resetting it
M: 2016-05-06 17:55:25.531 Closing the MMDVM
M: 2016-05-06 17:55:27.532 Opening the MMDVM
I: 2016-05-06 17:55:29.542 MMDVM protocol version: 1, description: DVMEGA HR2.28
E: 2016-05-06 17:55:29.563 No reply from the modem for some time, resetting it
M: 2016-05-06 17:55:29.564 Closing the MMDVM

MMDVMHost-20160428
DVMEGA HR2.28
RaspberryPi2 Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux

TX audio setting in mmdvm.ini should be splitted to allow different settings for each supported digital mode rather than a global setting in the [modem] section. This allows fine tuning of the modem audio settings to gain optimum performance for each mode.
Second approach would be to keep a global value in the [modem] section and add an additional correction value for each digital mode.

Hi

why in Fusion the BER is very high ?
In DN mode the BER is around 15/20% , but it is lower using VM mode , I noticed also that after pushing the PTT I ear some seconds of tail with my last over .
There will be some future improvements ?
tnx
73

Logging to the master has failed......

Has DVMEGA PI support been broken? Using firmware version 2.29a. The DVMEGA is responding and working OK using G4KLX dstarrepeaterd.

M: 2016-06-22 17:55:18.749 MMDVMHost-20160614 is starting
I: 2016-06-22 17:55:18.749 Modem Parameters
I: 2016-06-22 17:55:18.749 Port: /dev/ttyAMA0
I: 2016-06-22 17:55:18.750 RX Invert: yes
I: 2016-06-22 17:55:18.750 TX Invert: yes
I: 2016-06-22 17:55:18.750 PTT Invert: no
I: 2016-06-22 17:55:18.751 TX Delay: 100ms
I: 2016-06-22 17:55:18.751 DMR Delay: 0 (0.0ms)
I: 2016-06-22 17:55:18.751 RX Level: 50%
I: 2016-06-22 17:55:18.751 TX Level: 50%
I: 2016-06-22 17:55:18.752 RX Frequency: 433637500Hz
I: 2016-06-22 17:55:18.752 TX Frequency: 433637500Hz
I: 2016-06-22 17:55:18.752 Osc. Offset: 0ppm
M: 2016-06-22 17:55:18.753 Opening the MMDVM
E: 2016-06-22 17:55:28.577 Unable to read the firmware version after six attempts

The Date/Time font is too big (or the string is too long). The "AM" or "PM" goes to a new line below the date and there is only room to show the very top of the "AM" or "PM".

Display 20x4, the fourth line (mmdvm idle) is not cleared in listen mode

Hi, gets "Cannot open device - /dev/ttyAMA0" when trying to run MMDVMHost in daemon mode. Have done the commands from README.Daemon.

73 de LB5JE

Compiled today, I started up MMDVMHost and it got stuck trying to establish a P25 network connection. I was updating from an older version and there was no mention of P25 in the configuration file.

I: 2016-09-29 10:11:05.743 P25: enabled
I: 2016-09-29 10:11:05.744 P25 TX Level: 50%
I: 2016-09-29 10:11:07.777 P25 Network Parameters
M: 2016-09-29 10:11:07.787 Opening P25 network connection

I fixed it by including a P25 clause disabling it explicitly.

[P25]
Enable=0
NAC=293

Making the default behavior "disabled" would make updates much easier.

Hi team,

Last commit show this error, from compiler process :

Thread.cpp: In static member function ‘static void CThread::sleep(unsigned int)’:
Thread.cpp:96:2: error: ‘::usleep’ has not been declared
::usleep(ms * 1000);
^
Makefile:21: recipe for target 'Thread.o' failed
make: *** [Thread.o] Error 1

Not an issue, but a request: When changing REFlectors in D-Star, the radio transmits a connected to message. You get an RF feedback stating the new connection.

FOR DMR:
Is it possible to transmit a similar message when a DMR message is received via RF that changes the existing Trunk Group?

When using tail -f, you can see the log entry shown the new trunk group... would be nice if a standard message could be 'transmitted' back through the dvmega...

Thanks for reading.
Rick

Hi Team,

Since the last two updates, I have been experiencing more recurrent the resetting.Today I had this resetting, at least 5 times, on two occasions being totally in a loop.

I did a re-flash firmware to discard, but the resetting is maintained at random.

Partial log :

E: 2016-05-28 00:13:34.465 No reply from the modem for some time, resetting it
M: 2016-05-28 00:13:34.466 Closing the MMDVM
M: 2016-05-28 00:13:36.466 Opening the MMDVM
I: 2016-05-28 00:13:38.477 MMDVM protocol version: 1, description: DVMEGA HR2.28
E: 2016-05-28 00:13:38.497 Connection to the master has timed out, retrying connection
M: 2016-05-28 00:13:38.497 Closing DMR IPSC
M: 2016-05-28 00:13:44.469 Opening DMR IPSC
M: 2016-05-28 00:14:01.511 Logged into the master successfully

Hi, Is it possible to have some status message on the "Idle" page on the LCD screen that shows whether the host is connected to a network server for quick connection diagnostics?

Thanks
Andy

Letest version of MMDVMHost, display HD44780 4x20 does not display any data for ts1, both from RF and network, I only see dmr label scrolling.
Ts2 instead it appears correctly.
Mauri ik1whn

I have no got radio checl or call alert works using a DVMEGA with MMDVMHost so i ask myself if any software issue is happening.
When using a repeater have no problem. It seems to be only a DVMEGA so i thing the DMO mode in MMDVMHost could have any issue...
What do you think about?

Hi Tony,

Sorry still do not understand how to use the pull request. The possibility exists that can receive and record MMDVMHost reports RSSI (dBm).

And this information can be taken published in the corresponding dashboard.

73!

Severino.

Hi Team,

This version with the CW identifier, has an error in the modem module at compile :

g++ -g -O3 -Wall -std=c++0x -c -o Modem.o Modem.cpp
Modem.cpp: In member function ‘bool CModem::sendCWId(const string&)’:
Modem.cpp:1035:45: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
return m_serial.write(buffer, length + 3U) == (length + 3U);

Raspberry B+ ( Jezzy OS version )

73!

Hi, I'm not sure if this is a side issue MMDVM, processing of outgoing SMS sometimes succeeds in being sent, they arrive garbage characters. But sometimes he can not even sending out and fails.

In the case of reception I observe arriving packets (via log), but not end up being processed and never become despatched to the radio.

In the case of courier on APRS, works 100% in both vias (APRS <-> DMR).

73!

Hi

this problem appears during the DSTAR reception through XReflector and ircddbgateway
It seems a not enough buffer space .

Any solutions ?
73

Overflow in the DMR slot RF queue and after that, No reply from the modem for some time, resetting it ...................
Closing the MMDVM
Opening the MMDVM

In an infinite loop , the TX radio go keying continuosly .... please help me !

Would it be possible to add a few buttons to the Nextion screens?

I built a sweet case for my RPi/DVMega using the ModMyPi Modular Case, a Nextion screen, a battery pack, etc, etc...

I think it would be awesome if one had the ability to safely reboot/shutdown/restart MMDVMHost/See Voltage all from the screen, which would make it truly portable (I wouldn't need my phone or a PC to SSH in to reboot, etc).

Also, is it possible to wire the screen up, inside the case? It's kinda annoying having it hanging outside the case, but I have no idea where else to wire it too.....

Thanks so much, you guys rock.

K2AAM

Hi,
Today clone repository and make, but this step show error :

++ -g -O3 -Wall -std=c++0x -c -o MMDVMHost.o MMDVMHost.cpp
MMDVMHost.cpp: In member function ‘int CMMDVMHost::run()’:
MMDVMHost.cpp:165:24: warning: NULL used in arithmetic [-Wpointer-arith]
if (mmdvm_uid == NULL) {
^
MMDVMHost.cpp:171:24: warning: NULL used in arithmetic [-Wpointer-arith]
if (mmdvm_gid == NULL) {
^
I'm installing a raspberry, with the latest version of jezzy and all updated components.

73

almost every 4-5 hours, with Arduino Due, Raspberry 2 & 3 i Have this error:
E: 2016-05-09 10:51:12.970 MMDVM TX buffer has overflowed

And the modem stop to work, not blink tx and rx on arduino due..

What Can I do? Arduino Due sources and MMDVMHost are updated.

Hi Team,

I'm compiling the new commit ( fa29cb0 ), and it is generating the following error :

g++ -g -O3 -Wall -std=c++0x -c -o YSFControl.o YSFControl.cpp
YSFControl.cpp: In member function ‘bool CYSFControl::writeModem(unsigned char*)’:
YSFControl.cpp:107:17: warning: unused variable ‘fn’ [-Wunused-variable]
unsigned char fn = fich.getFN();
^
YSFControl.cpp:108:17: warning: unused variable ‘ft’ [-Wunused-variable]
unsigned char ft = fich.getFT();
^
YSFControl.cpp:109:17: warning: unused variable ‘dt’ [-Wunused-variable]
unsigned char dt = fich.getDT();
^
YSFControl.cpp:167:17: warning: unused variable ‘fn’ [-Wunused-variable]
unsigned char fn = fich.getFN();
^
YSFControl.cpp:168:17: warning: unused variable ‘ft’ [-Wunused-variable]
unsigned char ft = fich.getFT();
^
YSFControl.cpp:169:17: warning: unused variable ‘dt’ [-Wunused-variable]
unsigned char dt = fich.getDT();
^
73!

Raspberry B+ ( OS RASPBIAN JESSIE )

Latest git pull and OLED wont work (wont compile).

i tested Oled LIBs and ArduiPi_OLED.....libs work ok.

g++ -g -O3 -Wall -std=c++0x -pthread -DOLED -I/usr/local/include -L/usr/locacl/lib -c -o MMDVMHost.o MMDVMHost.cpp
MMDVMHost.cpp: In member function ‘void CMMDVMHost::createDisplay()’:
MMDVMHost.cpp:1076:70: error: invalid new-expression of abstract class type ‘COLED’
m_display = new COLED(displayType, displayBrightness, displayInvert);
^
In file included from MMDVMHost.cpp:40:0:
OLED.h:75:7: note: because the following virtual functions are pure within ‘COLED’:
class COLED : public CDisplay
^
In file included from MMDVMHost.h:27:0,
from MMDVMHost.cpp:19:
Display.h:74:15: note: virtual void CDisplay::writeCWInt()
virtual void writeCWInt() = 0;
^
Display.h:75:15: note: virtual void CDisplay::clearCWInt()
virtual void clearCWInt() = 0;
^
In file included from MMDVMHost.cpp:40:0:
OLED.h: At global scope:
OLED.h:37:22: warning: ‘logo_glcd_bmp’ defined but not used [-Wunused-variable]
static unsigned char logo_glcd_bmp[] =
^
OLED.h:56:22: warning: ‘logo_dmr_bmp’ defined but not used [-Wunused-variable]
static unsigned char logo_dmr_bmp[] =
^
Makefile.Pi.OLED:23: recipe for target 'MMDVMHost.o' failed
make: *** [MMDVMHost.o] Error 1
root@raspberrypi:/home/pi/MMDVMHost# ~

Hi to all
I have this kind of issue after the last updates : "D-Star, invalid slow data header" and the BER is too high !!!

What does it mean ?

thank you
73

Hello, I'm trying to use a TCXO at 11.289600 mhz.
Decode stops after about 0.7 seconds and I can't improve the situation acting on the OscOffset parameter.
I guess the problem is the integer division by 24000 and 48000.
Could MMDVM support my TCXO or should I throw it in the garbage and get a different frequency?
thanks.

Would it be possible to roll in additional connector support into MMDVMHost for this?

Details at the githubs below:

Client:
https://github.com/sharkrf/srf-ip-conn

Server:
https://github.com/sharkrf/srf-ip-conn-srv

Hi Team,

I am not sure if, there are possibilities to program or configure for MMDVMHost operate to DMR (BrandMeister):

• Duplex mode 100%.
• Both operate slot (Slot 1 and Slot 2) transparently

Thank,

73!

YSFPayload will not compile.

This is not related to the discussion of disabling all formats by default. This morning I was working with P25 networking and having some issues getting 2 machines running P25 networking to talk to each other.

I decided to turn off everything but P25 and "build up from there". I disabled DMR and DMR networking, D-Star and D-Star networking, Fusion and Fusion networking. Finally, I enabled P25 with debug enabled and disabled P25 networking. I started MMDVMHost and watched the console output. When I keyed the radio there was nothing on the console. No COS light on the audio board.

Once I turned on DMR, I got console output when I keyed the P25 radio. I think that P25 uses the Id value in the DMR section. If a user wants to build a P25 only system, he still ends up with DMR also.

I ran out of time this morning to re-test and will do more tonight.

From last pull, it starts to not loading DMR Ids as it was used to.

Last time on logs, after update was this morning.

Tried to see "Fix reading of IDs #151" but no longer there...

The 'eye' icon in the idle screen flickers, like it's overwritten by something and re-drawn again.

When tuned to an active frequency (FM repeater) it appears stable.

MD380tools commit 9a49993

Hi
using the blacklist to stop tg91, MMDVMHost stop to work. no errors in log

From last pull, it starts to not loading DMR Ids as it was used to.

Last time on logs, after update was this morning.

I: 2016-09-22 11:30:26.004 Loaded 43359 DMR Ids to the callsign lookup table

Hi,
after the last fix to discover the issue regarding the beeping in dstar, the log file after 1hour reach hundred of MB!! Is it possible myself, if already is usefull for debugging, disable this logging?
tnx 73

DMRAccessControl.cpp: In static member function 'static unsigned int DMRAccessControl::DstIdRewrite(unsigned int, unsigned int, unsigned int, bool)':
DMRAccessControl.cpp:219:94: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]

73

There is still an issue up to the recent commit 3214CF8 since Juli 21: Some stations have no audio but show persistent lost audio messages.
In the attached log you'll find DG9VH talking to DK4XW: While DG9VH was audible as usual, DK4XW suffers from persistent audio losses resulting in no audio output during his transmissions.
Later on (after the log) also the transmissions of DG9VH suffered from this effect.
When using commit C82CE29 as of Juli 20, all transmissions are fine.

issue_log.txt

Maybe can be a good idea integrate support for I2C display based on PCF8574 (very cheap)
( For example:
http://www.ebay.com/itm/IIC-I2C-TWI-SP-I-Serial-Interface1602-16X2-Character-LCD-Module-Display-Blue-/310565065847?hash=item484f1ed477:g:mPQAAOSwofxUhQre )

This code work, need to be integrated in HD4478.cpp and .h

import wiringpi2 as wiringpi

wiringpi.wiringPiSetupSys();

af_base = 100

af_rs = af_base + 0
af_e = af_base + 2
af_db4 = af_base + 4
af_db5 = af_base + 5
af_db6 = af_base + 6
af_db7 = af_base + 7

af_backlight = af_base + 3

def backlight_on():
wiringpi.digitalWrite(af_backlight, 1)

def backlight_off():
wiringpi.digitalWrite(af_backlight, 0)

wiringpi.pcf8574Setup(af_base, 0x27)

lcd_handle = wiringpi.lcdInit(4, 20, 4, af_rs, af_e, af_db4, af_db5, af_db6, af_db7, 0, 0, 0, 0)

backlight_on()

wiringpi.lcdPrintf(lcd_handle, "Hello World!")

I had the following issue when using MMDVMhost.exe (compiled with VS2013 for windows 32bit, running on Windows 10, 64-Bit) with a raw control panel for the DVMEGA on an arduino and trying to send SMS from a MOTO SL4000:

Debug Error!
Program: C:\MMDVMHost\mmdvmhost.exe
Module: C:\MMDVMHost\mmdvmhost.exe
File: C:\my_path\mmdvmhost-master\dmrslot.cpp Line: 1100

Run-Time Check Failure #2 - Stack around the variable 'payload' was corrupted.

73 de Meinhard "Mike", DL2MF

After the last update the compile of Makefile.Pi.HD44780 failed !!!

thank you
73 de IW9GRL

Hello,

the software does never send the CW-Id because the timer "m_cwIdTimer" is only started in case of MODE_ERROR or MODE_LOCKOUT. See lines 938 et seq. in MMDVMHost.cpp

    if (m_mode == MODE_ERROR || m_mode == MODE_LOCKOUT) {
        m_modem->sendCWId(m_callsign);
        m_cwIdTimer.start();

Sorry I can't write a patch because I'm to busy today to test it after writing.

Best wishes!

Hi
Recently with some Om friends, we noticed that if some trouble poweroff the Lan router connected to raspberry or disconnect manually the ethernet cable, mmdvmhost stop working and tg9 doesn't work.
Is this issue known?
73

RX buffer has overflowed

Seems to occur regardless of configuration, leaving one confused if there is an issue or not?

I noticed the following effect, when playing around with a DVMEGA hotspot on arduino:

M: 2016-03-17 13:46:25.848 Opening the MMDVM
I: 2016-03-17 13:46:27.893 MMDVM protocol version: 1, description: DVMEGA HR2.23
I: 2016-03-17 13:46:27.947 Display Parameters
I: 2016-03-17 13:46:27.947     Type: None
I: 2016-03-17 13:46:27.947 DMR Network Parameters
I: 2016-03-17 13:46:27.947     Address: master.up4dar.de
I: 2016-03-17 13:46:27.947     Port: 62031
I: 2016-03-17 13:46:27.962     Slot 1: disabled
I: 2016-03-17 13:46:27.962     Slot 2: enabled
I: 2016-03-17 13:46:27.978 Info Parameters
I: 2016-03-17 13:46:27.978     Callsign: DL2MF
I: 2016-03-17 13:46:27.993     RX Frequency: 434225000Hz
I: 2016-03-17 13:46:27.993     TX Frequency: 434225000Hz
I: 2016-03-17 13:46:27.993     Power: 1W
I: 2016-03-17 13:46:27.993     Latitude: 0.000000deg N
I: 2016-03-17 13:46:27.993     Longitude: 0.000000deg E
I: 2016-03-17 13:46:28.009     Height: 48m       <----------------------- #### height entered `#####`
I: 2016-03-17 13:46:28.009     Location: "Celle"
I: 2016-03-17 13:46:28.009     Description: "DV4MF2_DVMEGA"
I: 2016-03-17 13:46:28.009     URL: "www.dl2mf.de"
M: 2016-03-17 13:46:28.025 Opening DMR IPSC
I: 2016-03-17 13:46:28.028 DMR Parameters
I: 2016-03-17 13:46:28.029     Id: 2623082
I: 2016-03-17 13:46:28.031     Color Code: 1
I: 2016-03-17 13:46:28.031     Timeout: 600s
M: 2016-03-17 13:46:28.031 Mode set to Idle
M: 2016-03-17 13:46:28.147 Logged into the master succesfully:

Result:
2623082 DL2MF DV4MF2_DVMega DV4MF2_V2.1a 434.225 MHz 434.225 MHz 1 Slot 1 & 2 linked

M: 2016-03-17 13:48:56.645 Opening the MMDVM
I: 2016-03-17 13:48:58.668 MMDVM protocol version: 1, description: DVMEGA HR2.23
I: 2016-03-17 13:48:58.699 Display Parameters
I: 2016-03-17 13:48:58.699     Type: None
I: 2016-03-17 13:48:58.699 DMR Network Parameters
I: 2016-03-17 13:48:58.699     Address: master.up4dar.de
I: 2016-03-17 13:48:58.699     Port: 62031
I: 2016-03-17 13:48:58.715     Slot 1: disabled
I: 2016-03-17 13:48:58.715     Slot 2: enabled
I: 2016-03-17 13:48:58.738 Info Parameters
I: 2016-03-17 13:48:58.738     Callsign: DL2MF
I: 2016-03-17 13:48:58.738     RX Frequency: 434225000Hz
I: 2016-03-17 13:48:58.738     TX Frequency: 434225000Hz
I: 2016-03-17 13:48:58.753     Power: 1W
I: 2016-03-17 13:48:58.753     Latitude: 0.000000deg N
I: 2016-03-17 13:48:58.753     Longitude: 0.000000deg E
I: 2016-03-17 13:48:58.753     Height: 0m       <----------------------- #### height set to 0 `#####`
I: 2016-03-17 13:48:58.753     Location: "Celle"
I: 2016-03-17 13:48:58.753     Description: "DV4MF2_DVMEGA"
I: 2016-03-17 13:48:58.769     URL: "www.dl2mf.de"
M: 2016-03-17 13:48:58.769 Opening DMR IPSC
I: 2016-03-17 13:48:58.769 DMR Parameters
I: 2016-03-17 13:48:58.769     Id: 2623082
I: 2016-03-17 13:48:58.769     Color Code: 1
I: 2016-03-17 13:48:58.769     Timeout: 600s
M: 2016-03-17 13:48:58.769 Mode set to Idle
M: 2016-03-17 13:48:58.900 Logged into the master succesfully:

Result:
2623082 DL2MF DV4MF2_DVMega DV4MF2_V2.1a 434.225 MHz 434.225 MHz 1 Linked in DMO mode

I did use the latest MMDVM sources (from 03-15 2016) and did compile the mmdvmhost.exe with VS2013 as a Win-32 Exe, Platform Toolset has been adapted to Visual Studio 2013 (v120).

Couldn't find a reason for this when checking the definition of the height parameter and the setConfig:
m_dmrNetwork->setConfig(callsign, rxFrequency, txFrequency, power, colorCode, latitude, longitude, height, location, description, url);

Any idea?

Using 14f36a1

Start fails on RPI B with following output (see end of log):
pi@mmdvm:~/src/MMDVMHost $ MMDVMHost /etc/mmdvm/MMDVM.ini
I: 2016-05-19 19:22:42.800 This software is for use on amateur radio networks only,
I: 2016-05-19 19:22:42.802 it is to be used for educational purposes only. Its use on
I: 2016-05-19 19:22:42.804 commercial networks is strictly prohibited.
I: 2016-05-19 19:22:42.805 Copyright(C) 2015, 2016 by Jonathan Naylor, G4KLX and others
M: 2016-05-19 19:22:42.807 MMDVMHost-20160517 is starting
I: 2016-05-19 19:22:42.807 Modem Parameters
I: 2016-05-19 19:22:42.807 Port: /dev/ttyACM0
I: 2016-05-19 19:22:42.808 RX Invert: no
I: 2016-05-19 19:22:42.808 TX Invert: no
I: 2016-05-19 19:22:42.809 PTT Invert: no
I: 2016-05-19 19:22:42.809 TX Delay: 100ms
I: 2016-05-19 19:22:42.809 DMR Delay: 7 (0.3ms)
I: 2016-05-19 19:22:42.810 RX Level: 10%
I: 2016-05-19 19:22:42.810 TX Level: 50%
I: 2016-05-19 19:22:42.811 RX Frequency: 430575000Hz
I: 2016-05-19 19:22:42.811 TX Frequency: 439975000Hz
I: 2016-05-19 19:22:42.811 Osc. Offset: 0ppm
M: 2016-05-19 19:22:42.812 Opening the MMDVM
I: 2016-05-19 19:22:44.824 MMDVM protocol version: 1, description: MMDVM 20160509 24kHz (D-Star/DMR/System Fusion/CW Id)
I: 2016-05-19 19:22:44.845 Display Parameters
I: 2016-05-19 19:22:44.845 Type: None
I: 2016-05-19 19:22:44.846 D-Star Network Parameters
I: 2016-05-19 19:22:44.846 Gateway Address: 127.0.0.1
I: 2016-05-19 19:22:44.846 Gateway Port: 20010
I: 2016-05-19 19:22:44.846 Local Port: 20011
M: 2016-05-19 19:22:44.846 Opening D-Star network connection
I: 2016-05-19 19:22:44.846 DMR Network Parameters
I: 2016-05-19 19:22:44.847 Address: master.up4dar.de
I: 2016-05-19 19:22:44.847 Port: 62031
I: 2016-05-19 19:22:44.847 Local: 3350
I: 2016-05-19 19:22:44.847 Slot 1: enabled
I: 2016-05-19 19:22:44.847 Slot 2: enabled
I: 2016-05-19 19:22:44.912 Info Parameters
I: 2016-05-19 19:22:44.913 Callsign: DG9VH
I: 2016-05-19 19:22:44.915 RX Frequency: 430575000Hz
I: 2016-05-19 19:22:44.917 TX Frequency: 439975000Hz
I: 2016-05-19 19:22:44.918 Power: 1W
I: 2016-05-19 19:22:44.918 Latitude: 49.233154deg N
I: 2016-05-19 19:22:44.919 Longitude: 6.833815deg E
I: 2016-05-19 19:22:44.919 Height: 5m
I: 2016-05-19 19:22:44.919 Location: "Voelklingen"
I: 2016-05-19 19:22:44.919 Description: "Multi-Mode Repeater"
I: 2016-05-19 19:22:44.921 URL: "www.dg9vh.de"
M: 2016-05-19 19:22:44.921 Opening DMR IPSC
I: 2016-05-19 19:22:44.922 System Fusion Network Parameters
I: 2016-05-19 19:22:44.922 Reflector Address: 192.168.178.59
I: 2016-05-19 19:22:44.923 Reflector Port: 4711
M: 2016-05-19 19:22:44.923 Opening YSF network connection
I: 2016-05-19 19:22:44.924 CW Id Parameters
I: 2016-05-19 19:22:44.925 Time: 10 mins
I: 2016-05-19 19:22:44.925 D-Star Parameters
I: 2016-05-19 19:22:44.925 Callsign: DG9VH
I: 2016-05-19 19:22:44.926 Module: B
I: 2016-05-19 19:22:44.926 Self Only: no
I: 2016-05-19 19:22:44.927 Timeout: 180s
I: 2016-05-19 19:22:44.928 DMR Parameters
I: 2016-05-19 19:22:44.928 Id: 2625094
I: 2016-05-19 19:22:44.929 Color Code: 1
I: 2016-05-19 19:22:44.929 Self Only: no
I: 2016-05-19 19:22:44.930 Prefixes: 0
I: 2016-05-19 19:22:44.930 Timeout: 180s
I: 2016-05-19 19:22:44.930 Lookup File: /var/mmdvm/DMRIds.dat
I: 2016-05-19 19:22:44.931 TX Hang: 4s
I: 2016-05-19 19:22:45.231 Loaded 35206 DMR Ids to the callsign lookup table
I: 2016-05-19 19:22:45.232 System Fusion Parameters
I: 2016-05-19 19:22:45.233 Callsign: DG9VH
I: 2016-05-19 19:22:45.234 Timeout: 180s
MMDVMHost: malloc.c:3695: _int_malloc: Assertion `(unsigned long) (size) >= (unsigned long) (nb)' failed.
Aborted

E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.995 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.996 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.997 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.997 DMR Slot 2, overflow in the DMR slot RF queue
E: 2016-07-14 19:18:38.997 DMR Slot 2, overflow in the DMR slot RF queue

After the yesterday updated strange strings appear like this:

73