Tony Corbett G0WFV 0db3cf10e8 Attempt to solve one cause of "No reply from modem" loop
"err 101" (network unreachable - effectively cant get to the master because we've lost the network)

This needs trapping and handling properly to smooth the way it currently tries to send from the socket as quickly as it can (effectively every millisecond) until the network is restored,  then does the same for "Opening IPSC" every millisecond or less until the login either times out (in which case I've edited the code to tell it to retry!) or logs into the master successfully.

This error also causes the "no reply from modem loop, however this is now trapped in all cases if the firmware is read successfully by stopping the inactivity timer, allowing the software to continue reading the modem.

It works for this particular error, but others may need to test!
2016-05-14 11:39:56 +01:00
2016-05-10 15:08:06 +00:00
2016-04-19 07:45:49 +01:00
2016-04-19 06:50:51 +01:00
2016-01-14 18:45:04 +00:00
2016-03-21 22:47:58 +00:00
2016-05-03 13:55:23 +01:00
2016-03-01 19:42:24 +00:00
2016-02-15 18:45:57 +00:00
2016-02-15 18:45:57 +00:00
2016-02-15 18:45:57 +00:00
2016-05-05 16:28:45 +10:00
2016-05-10 08:00:41 +01:00
2016-03-07 20:21:55 +00:00
2016-05-10 08:18:10 +01:00
2016-03-07 20:21:55 +00:00
2016-02-15 18:45:57 +00:00
2016-05-10 18:54:35 +01:00
2016-02-15 18:45:57 +00:00
2016-02-15 18:45:57 +00:00
2016-02-01 21:44:40 +00:00
2016-02-01 20:49:52 +00:00
2016-02-01 20:49:52 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-04-19 06:50:51 +01:00
2016-04-19 06:50:51 +01:00
2016-05-12 19:41:58 +01:00
2016-05-05 18:33:43 +01:00
2016-01-14 18:45:04 +00:00
2016-03-07 21:55:02 +00:00
2016-03-07 18:42:05 +00:00
2016-04-19 19:46:16 +01:00
2016-05-10 15:08:06 +00:00
2016-01-14 18:45:04 +00:00
2016-05-09 21:55:44 +01:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 19:58:16 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 23:25:52 +00:00
2016-01-26 07:13:55 +00:00
2016-02-15 21:46:57 +00:00
2016-02-15 21:46:57 +00:00
2016-01-14 18:45:04 +00:00
2016-01-14 18:45:04 +00:00
2016-04-04 17:00:59 +01:00
2016-04-04 17:00:59 +01:00
2016-03-07 20:21:55 +00:00
2016-01-14 18:45:04 +00:00
2016-05-05 18:00:57 +01:00
2016-04-18 21:56:10 +01:00
2016-05-12 17:44:08 +01:00
2016-02-23 21:01:14 +00:00
2016-04-25 18:06:19 +01:00

These are the source files for building the MMDVMHost, the program that interfaces to the MMDVM or DVMega on the one side, and a suitable network on the other. On the D-Star side the MMDVMHost interfaces with the ircDDB Gateway, on DMR, only the BrandMeister network currently.

It supports D-Star, DMR, and System Fusion.

It builds on 32-bit and 64-bit Linux as well as on Windows using VS2015 on x86 and x64. It can optionally control various Displays. Currently these are:

  • HD44780 (sizes 2x16, 2x40, 4x16, 4x20)
  • Nextion TFTs (sizes 2.4", 3.2" and 3.5")
  • Adafruit 16x2 LCD+Keypad Kits
  • TFT displays sold by Hobbytronics in UK
  • OLED 128x64 (SSD1306)

The HD44780 displays are integrated with wiringPi for Raspberry Pi based platforms. The other displays can be directly connected to the UART on Raspberry Pis or with FT-232RL modules to any USB port.

The OLED display needs a extra lib see OLED.md

This software is licenced under the GPL v2 and is intended for amateur and educational use only. Use of this software for commercial purposes is strictly forbidden.

It is only to be used on the main DMR+, the main BrandMeister, and Phoenix (UK) networks. If you wish to use it on any other network, you must get written permission from myself, G4KLX. Each such request will be dealt with on a case-by-case basis.

Description
No description provided
Readme 25 MiB
Languages
C++ 96.8%
C 1.4%
Shell 1.1%
Python 0.4%
Makefile 0.2%