Hi,
which is the correct way to put the HL7692 in lowest power consumption possible but able to receive SMS?
Please note the module is connected via UART
Currently we are using
AT+CGATT=0
AT+KSLEEP=0 plus DTR
is this the correct way? I’m asking because we wake up the module using DTR and sending
AT+CGATT=1 But often this last command (AT+CGATT=1) hangs for something like 2 o 3 minutes. Sometimes is immediate, under the same network conditions.
Please note after exiting sleep and before sending AT+CGATT=1 we test the module response sending “AT” command and it always respond in a few milliseconds.
How about not entering at+cgatt=0?
Will it consume more power?
Btw, can you receive the sms with DTR deasserted?
Also have you tuned DRX value?
How about not entering at+cgatt=0?
Will it consume more power?
Yes, we done some tests in the past and we noticed the power consumption was higher without at+cgatt=0.
Unfortunately I don’t have that data in my hand now.
Btw, can you receive the sms with DTR deasserted?
When DTR is deactivated (high electrical level) we can receive SMS watching the “ring” physical pin and waking up the module.
Also have you tuned DRX value?
No, I don’t know nothing about DRX, can you address me?
Best regards
Are you using LTE network
Are you using LTE network
Yes we are using both LTE / 2G
For DRX, you can refer to AT command guide, i saw there is some setting for drx
Btw, can you restart telecom stack by +cfun instead of +cgatt after wake up?
For DRX, you can refer to AT command guide, i saw there is some setting for drx
The only reference in the manual are DRX_Timer_Max and drx_cycle_length under +CGED command.
Are you referring to these?
Btw, can you restart telecom stack by +cfun instead of +cgatt after wake up?
Yes, I can try.
Should I use AT+CFUN=37 (Reset single stack) or AT+CFUN=38 (Reset all stacks) or any other param?
How about
At+cfun=0
At+cfun=1
1 Like
Hi @jyijyi
I’ve done some tests on power consumption with/without using cgatt=0 when modem is in sleep mode (KSLEEP=0, DTR high level).
Whit CGATT=0 the device consume ~6mA
Without CGATT=0 the device consume ~19mA
Both tests were done under good LTE coverage
This is a huge difference for us, and 19mA is far above the technical specification worst case scenario that is 6.7mA
Are we missing something ?
I attached a chart of power consumption without sending CGATT=0: as you can see every ~50sec the module go from ~2mA to +100mA for 10 seconds.
Please let me know
ps: we had the same result using KSLEEP=1
You can still use at+cgatt=0 then.
- At+cgatt=0
- Sleep mode is entered
- To wake up, type AT+KSLEEP=0 plus DTR
- at+cfun=0
- at+cfun=1
@jyijyi Ok, thank you for your support.
Last question. What do you think about power consumption in sleep when CGATT is enabled? Isn’t it too far from what PTS says?
Possible causes?
Thank you
do you have any TCP server or UDP server set up module?
Do you mean the high power consupmtion here?
I’m not sure I understand the question. Yes we have a TCP server with which the module communicates through command as +KTCPSND,+ KTCPRCV. Before going in sleep we call +KTCPCLOSE and +KTCPDEL.
Do you mean the high power consumption here?
Yes, but also check the average. It is 19mA calculated on 9 minutes and 38 seconds timespan
how about not setting up any TCP server or UDP server?
Does it still consume high power consumption during sleep mode?
I found this in the documentation
“In sleep mode, URCs wake up the module and are sent to the terminals in AT command mode.”
If I understand well…
Before the module goes in sleep mode I send +KTCPCLOSE and +KTCPDEL. After that the PDP context will remain unused for a certain period of time and if that period is greater than a timeout (+KCNXTIMER) the PDP context will be automatically deactivated, generating an URC (+KCNX_IND: 1,0,0). That URC wakes up the module. Our device cannot catch this because is in sleep too
Am I correct?
Calling AT+KCNXDOWN before entering in sleep close the context and avoid the URC message after the timeout.
You can verify by not putting host MCU to sleep mode but only putting module to sleep mode