MK II Lite – Release 1.22.0 – Release Notes

This release is a major release which has enhanced protocol handling to ensure delivery of data between the filed devices and the back-end servers. 

This release is to be released in conjunction with the Portal release 1.10.1.

Review Headline Features below for more detail.

Please continue to provide objective feedback that we can act on to ensure you
receive better service and functionality as we strive to constantly enhance our
offering.

Beta Release date: 22/02/2021
Production Release date: 8/03/2021

Firmware Release Versions

WP8548: 3.5.16.1.22.0

WP7607-1: 3.6.12.0.1.22.0

Release Action

Release PriorityRelease Action
MediumAs required

Release Headline Features

Ticket NumberDescription
MKIIPL-254

MKII Lite MQTT Publish - Add MQTT Publish functionality.

MKIIPL-255

MKII Lite MQTT Subscribe - Add MQTT Subscribe functionality.

MKIIPL-264

Move network bits into a driver infrastructure - Improved network management.

MKIIPL-294

MTN SIM balances no longer being sent up correctly - Updated the code to handle thee MTN USSD changes.

MKIIPL-306

Update the "Validate" queries to include the new Dial Order - 

MKIIPL-311

Send SIM balances to server when the bal SMS is received - When the SMS command 'bal' is received and processed, the intercom will also send the update SIM balances to the backend.

MKIIPL-339

Define and implement Transaction Header TOKEN - 

MKIIPL-340

Define packetType MD5 verification groups / map - To improve token delivery and verify the integrity of sent and received data.

MKIIPL-341

Implement transaction control & verification per packet - 

MKIIPL-342

Return ERROR on CRC32 fail, FAIL on MD5 fail and OK on success - Improved token handling to ensure data integrity.

MKIIPL-343

New 'reply token' to include error details - 
Add a validation for tokens.
Log errors to log.
Generate unit/user MD5 hash.
Update all md5 hashes at end of sync.

MKIIPL-344

Append Sequential EventTriggerID (G&D) & EventBillingID to tokens - 

MKIIPL-345

All Billing Events to be linked to the owning/related Trigger Event - 

MKIIPL-346

Update tokens for Tigger & Billing Events - 

MKIIPL-351

Persist logging to files system & create a setting on portal for enabling debug mode on a MKII Lite board - 

MKIIPL-353Fix the watchdog handling operation - 
Add 30s timer to watchdog fed every second from OBR thread under normal operation instead of a infinite loop on graceful restart [0004/7633/sms/gsm fail],  abort after 60s.
Set watchdog timer as a system default of 300 [30s].
Don't clear watchdog on answer, it will clear on hang up.
If the device is not registered do not call.
Set GSM watchdog to 240s to allow network search
MKIIPL-357


Disable HSIC on the MKII Board on the Birth Process - 
Disable HSIC on the MKII Board on the Birth Process.
Mark GPIO 34 as not used on WP76. This pin is not available on the WP76xx. 
Only turn off HSIC if there is no ethernet.
Add script to reset CPU and turn off HSIC.
Detect HSIC enabled and disable on boot [with reboot].
Add support for WP85 devices use CR not NL.
MKIIPL-356

GSM Call Handling - The handling of GSM calls has been improved by better call queue management and adding timers to the call/answer/hang-up functions. 
Move incoming call watchdog protection to incoming call handler.

MKIIPL-358

Change display on MKII Lite to display to unit number in place of the unit Description - The LCD will display the unit number instead of unit description. 

MKIIPL-368

Add a supervisor code to display Comms Protocol setting Socket or MQTT - 

MKIIPL-369Modem Serial number missing from birth packet - Added the modemserial number into the birth packet.
MKIIPL-370Add a supervisor code to display Communication Protocol setting. *#0021 wil display either Comb Protocol or MQTT protocol.
Various Fixes

Combine debug and logging - 
Add option to set logging for 14 days on boot [push notification]
Capture logfile when enabling debug if not set already
Save log file has moved to app control


Allow portal sending message to generate tap/tapx codes - The back end server now handles all TAP/Tapex requests. This is to provide functionality for future multiple access points. 
Manage DTMF generated Tapex codes when display option is set.
Get telephone number from uid number.
Handle failed tap request locally.
Check tap requests before network check.
Update tap usage counts before updating tap table.
Add fail SMS for tap codes.
Do not add codes to table with no usage.
Allow handling replies to push packets for tap from portal.

© 2018 Comb Communications. All Rights Reserverd.
http://www.comb-communications.com