CDStarControl::clock(),
CM17Control::clock(),
CNXDNControl::clock(),
CP25Control::clock(),
CYSFControl::clock():
- Leave ASAP when it's disabled.
CDMRSlot::enable(),
CDStarControl::enable(),
CM17Control::enable(),
CNXDNControl::enable(),
CP25Control::enable(),
CYSFControl::enable():
- Log a message when Controller get disabled while running, "<MODE>, RF user has timed out" or "<MODE>, network user has timed out", depending of the RF/Net state.
CMMDVMHost::run():
- After getting the modem data, don't handle it (read/write<Controler>, etc) if the given mode is not enabled.
MMDVMHost:
- Rename CMMDVMHost::processEnableCommand() to CMMDVMHost::enableModemMode().
- Add CMMDVMHost::enableMode() and CMMDVMHost::disableMode(), called now from CMMDVMHost::remoteControl(), which clarify the code.
- CMMDVMHost::remoteControl():
* Fix indentation,
* Simplify ENABLE_x/DISABLE_x cases code.
- CMMDVMHost::setMode():
* Enable pocsag network only if m_pocsagEnabled is true,
* Enable ax25 network only if m_ax25Enabled is true (not m_fmEnabled).
Many hotspot users have 8/9 digit DMR IDs configured, the 7 Digit ID in the radio will then fail the match.
This is a possibly ugly but functional patch that will account for those cases (similar to the recent work on the DMR Access for the same reasons).
Jonathan added this code due to a lack of CRC on P25 checking but some parties desire the ability to have any id.
It's understood that on networked connections, the need to use a 7 digit unique ID like the DMR ID is necessary.
This change is affected by adding a new parameter to the [P25 Network] section called OverrideUIDCheck and it defaults to 0.
The logic is, if the network is enabled, or if the network is disabled and the override is disabled, the check is made, otherwise it is not.
This has been field tested for all 4 configuration cases and found to work as described above.