Updated/confirmed the latest supported Generic EM7565 radio firmware
Removed the Sierra and Telstra radio firmware packages, leaving only Generic
Tested Password Only and Control Only SMS modes
Tested AT+CGSMS settings 0, 1, 2 and 3
Set SMS Message Format to 3GPP
Rebooted and retested after the changes
The same SMS command functionality works correctly on our AirLink GX450 / MC7304 using Singtel IoT service. Its log shows successful incoming SMS processing:
Welcome to our community!
After checking, I found that the error code 0xE102 (57602) indicates the following:
Error String
Description
eQCWWAN_ERR_SWISMS_MSG_CORRUPTED
0xE102 - The SMS message is corrupted (encoding wrong)
To investigate and narrow down the issue, please get the log and template log from RV55 and GX450 after receiving the SMS by the instructions and send me:
1. The configuration template file is in ACEmanager → Template, provide any name you desire for the Template Name, and then press Download to retrieve the template file.
2. Collect logs procedure:
a. Go AceManager > Admin > Configure Logging
Set all log levels to DEFAULT (NOTICE)
Set Linux Syslog to DISPLAY
b. Reboot the gateway.
c. Perform your test again.
d. Go Admin → View log → Download Logs.
If you cannot upload the log files, you can upload them to Google Drive and share the link with me.
Simon, alongside the logs already requested, I’d compare the received SMS-DELIVER PDUs on the RV55 and GX450 using the same sender and short, manually typed command. Check TP-DCS, TP-UDHI and TP-UDL against the payload. For uncompressed GSM-7, TP-UDL counts septets, not bytes.
I co-founded HiCellTek, where we work on UE-side protocol decoding. Here, 0xE102 tells us the decoder reported an encoding error; it doesn’t yet prove Singtel sent a malformed message. Comparing the working and failing PDUs would help separate an input difference from a parser issue. Keep those captures private with support, as they may contain phone numbers and command passwords.
Thanks for your log.
Could you please share the template logs from RV55 and GX450 following the steps I shared earlier, so we can check in more detail and compare the configurations?
Thanks for your update.
After checking in internal server and your logs, I found that the issue appears to be related to the CDMA/3GPP carrier. Please try the following steps and check if the issue still occurs.
Go to Services => SMS => Advanced => SMS Message Format
If you are currently using CDMA, please change to 3GPP and vice versa
We tested another RV55 from the same batch, purchased together at the same time as the affected monitoring-system RV55, using a Singtel personal prepaid SIM.
For comparison, this RV55 was upgraded and configured to match the affected monitoring-system RV55:
Same latest ALEOS firmware
Same latest radio firmware
Same SMS configuration
Password Only mode
SMS Format tested with Default, CDMA and 3GPP
SMS Storage tested with SM and ME
AT+CGSMS tested with Do Nothing, 0, 1, 2 and 3
On this RV55, SMS commands are working correctly. Both status and reset commands were successfully received and processed, including test messages with additional/sample text.
The Last Incoming Number and Last Incoming Message fields are also populated correctly.
However, the RV55 installed in the monitoring system, which is using the Singtel IoT SIM, still fails and continues to report:
At this point, the main remaining difference is the SIM type:
Working test RV55: Singtel personal prepaid SIM
Affected monitoring RV55: Singtel IoT SIM
Our next test will be to swap/test the SIM cards between both RV55 units to determine whether the issue follows the Singtel IoT SIM. This test is pending site arrangement, and we will update the results once completed.
