RC7620 (FW 8.07): "AT+KSLEEP=2" command does not seem to work correctly

IoT Modules RC76
1

Hi Guys,
I want to execute the “AT+KSLEEP=2” command to disable sleep mode for UART1. UART1 sleep mode is disabled for the current session only. Although the “AT+KSLEEP=2” command does keep its state after a power cycle UART1 still falls asleep. Only repeated command “AT+KSLEEP=1” followed by “AT+KSLEEP=2” helps. But after the power cycle, the sleep mode turns on again. For comparison, I also have HL7692 - everything works correctly there.
Below is the report. Please advice. Thanks in advance!

AT+KSLEEP=2 //enter no sleep mode (regardless of DTR state)
AT+KSLEEP=2 
OK		   //the command completed successfully
AT+KSLEEP? //status check
AT+KSLEEP?
+KSLEEP: 2 //the UART1 state saved correctly

OK
AT!RESET //reboot
AT!RESET
OK

+SIM: 1 //modem started


+KTCP_NOTIF: 1,5

AT //the commands are sent at intervals of more than 5 seconds - no response
AT //UART1 is sleeping
AT //UART1 is sleeping
AT //
OK //UART1 wakes up after the command (<5sec)
AT+KSLEEP? //status check
AT+KSLEEP?
+KSLEEP: 2 //state saved correctly but UART1 is sleeping

OK
AT+KSLEEP=1 // reset-set helps, but only in the current session
AT+KSLEEP=1
OK
AT+KSLEEP=2
AT+KSLEEP=2
OK

AT //the commands are sent at intervals of more than 5 seconds, the modem is responding
OK //UART1 is not sleeping
AT
OK //UART1 is not sleeping
AT
OK //UART1 is not sleeping
AT
OK //UART1 is not sleeping
AT!RESET //reboot
AT!RESET
OK	//After reboot UART1 goes to sleep again

+SIM: 1 //modem started


+KTCP_NOTIF: 1,5

AT
AT
OK
ATI
Manufacturer: Sierra Wireless, Incorporated
Model: RC7620
Revision: SWI9X07H_00.08.07.00 0ce4c1 jenkins 2021/03/17 02:18:20
IMEI: 353634110241543
IMEI SV: 17
FSN: 7Q1385310310B0
+GCAP: +CGSM

OK
2

This is known issue with internal tracker MOLRC9X07-89.
You need to use your workaround to overcome this issue at this stage.

3

This work around works for me on the RC7620 with firmware version 00.08.07.00.
Thanks help9help.

I did not have this issue with firmware version 00.03.03.00.

However, before going into MUX mode, it was also required to toggle the DTR pin for 100ms.
Otherwise a channel (DLC) could not be opened.

4

Hello jyijyi,

for the RC7620-1 is there a stable firmware version that fixes this problem ?
Sincerely

5

no, i think currently you still need to use this workaround

6

The version 8.07 dates from March 17, 2021 and since no stable version corrects this problem !!
We are in January 2023. For a large manufacturer like SIERRA this is unacceptable.
Do you have a release date for a next stable version ?

7

you can see here:
https://source.sierrawireless.com/resources/airprime/software/rc76xx/rc76xx-firmware-release-9,-d-,0/#sthash.1aZQ1DcY.dpbs

BTW, do you contact distributor?

8

Yes, I have already contacted the distributor.
In June 2022 he wrote to me:

It seems that there is a bug on the R9 version at the update.
It will be fixed in a version R9.0.1, I do not have yet the availability of this new version.
In the meantime, I encourage you to suspend the update to R9

The R9 version corresponding to the link you sent me is still dated March 21, 2022. No R9.0.1 available.
So I ask you again:
Do you have a release date for a next stable version ?

9

Are you using FDT to upgrade?
Are you using AT+KSLEEP=2 as mentioned in this topic?

Is the distributor talking about these known bugs in release note?

image
image906×710 145 KB

I think you still need to contact distributor on this

10

No, I use QMI for update.
Yes, I send to the modem AT+KSLEEP=1 then after AT+KSLEEP=2 so that it never goes into sleep mode.
this fixes the problem. But I’m having other problems especially when roaming and I was hoping to get a newer version of the modem.
No, I do not have a release note from the distributor.

11

release note can be downloaded here:
https://source.sierrawireless.com/resources/airprime/software/release_notes/rc76xx-release-9,-d-,0-customer-release-notes/#sthash.puWwe4NH.mXfBbDRJ.dpbs

If you don’t use AVMS, probably you don’t need to care about first known bug