Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Wed, 07 Jul 2021 15:41:50 GMT

Enabling +CGEREP. did the trick. Thank you!

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Wed, 07 Jul 2021 07:43:43 GMT

No worries, Joshua! :-)

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Tue, 06 Jul 2021 19:28:02 GMT

Actually, It was a goof on my part. I switched to a different board, which isn't new enough to support XPOFWARN, so it doesn't work. Sorry about that. I'll get that other board back and I expect things will then work.

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Tue, 06 Jul 2021 18:39:44 GMT

Markus,

I'll do that and report back the findings.

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Mon, 05 Jul 2021 11:26:43 GMT

Thanks a lot for the feedback, Joshua!

Due to limited support capacities because of the summer vacation period here in Norway, I would suggest that you revert to your previous version of the SDK and test this. If you can confirm that it works, we can close this ticket and you can create a new one for the SDK 1.6.0 issue.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Fri, 02 Jul 2021 21:15:21 GMT

Markus,

I went to test this today, but in the meantime, I'd updated to SDK 1.6.0, and now something odd is happening.

When I try to issue

AT%XPOFWARN=1,32

or any other valid variant of the %XPOFWARN command, I get a -8 error back from the AT command processor. Other AT commands seem to work perfectly. I'll dig into this more next week (Monday is a holiday here, so it'll be Tuesday) but I'm curious if you have any insight into why this might have changed?

Regards,

Josh

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Fri, 02 Jul 2021 08:36:04 GMT

Hello again Joshua,

I now have talked to our modem team and got the following feedback:

For receiving the +CGEV notifications, the application must subscribe to those notifications using +CGEREP.

Could you try that and see if that makes any difference?

Alternatively, %MDMEV notification can also be used for getting battery low notifications.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Wed, 30 Jun 2021 05:29:11 GMT

Thanks, Joshua! I will check this with our modem team and come back to you.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Tue, 29 Jun 2021 14:37:02 GMT

There is no difference in behavior with 1.3.0.

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Tue, 29 Jun 2021 14:16:21 GMT

I of course get your point, Joshua :-) But officially, we can not give support to non-official released firmware.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Tue, 29 Jun 2021 14:08:01 GMT

Markus,

Our FAE supplied that. I'd not see the final 1.3.0 was out, so I'll pull that and re-try. Since this feature has been out a long time, and was supposed to be in 1.2.1, I really don't have high hopes that it'll be working in 1.3.0, but I'll let you know what happens.

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Tue, 29 Jun 2021 14:00:20 GMT

Thanks, Joshua!

Where did you get the pre-alpha modem firmware from? I’m not really aware of that we are providing not official released modem firmware.

Anyway, my recommendation would be to upgrade to the official mfw 1.3.0 release and check if that makes any difference.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Tue, 29 Jun 2021 13:16:02 GMT

Markus,

I'm using 1.3.0-44.prealpha.

I've used 1.2.1 as well, but my most careful testing was on the 1.3.0-44.

Let me know if there's something else you'd like me to look at.

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Tue, 29 Jun 2021 05:34:32 GMT

That is interesting… and not really as expected I would say! I think the code snippet you are using should work fine. And the fact that you are getting other AT notifications confirms that as well.

What modem firmware are you using? I might wanna report this to our modem team and check with them. You can use the +CGMR command in case you are unsure.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Mon, 28 Jun 2021 15:27:42 GMT

I tried this, and even tried sneaking up on the voltage threshold 2 mv at a time, and never saw the low voltage warning. Is it possible something in the SDK is disabling this, or "eating" the response before my handler can get it? Is there a recommended project to use to test this feature in isolation?

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Mon, 28 Jun 2021 06:15:17 GMT

Thanks for the feedback, Joshua! I would recommend you to set the power off warning to its highest level:

AT%XPOFWARN=1,33

and drop the supply voltage to a constant level of 3.2V, as this should make sure that the modem is able to run through the whole shut-down process.

As you can see in this table, which was measured at a supply voltage of 3.7V, the current consumption can vary a lot depending on the modem state.

Regards,

Markus

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

JVantol — Fri, 25 Jun 2021 16:17:27 GMT

Markus,

using XVBATLVL does get me "%XVBATLOWLVL: 3382" warnings, as the voltage drops. But I never see the warning that the modem is going offline because of low voltage.

It's possible I'm reducing the voltage too fast, and the modem goes straight to shutdown, without first issuing a warning, but I would have thought you should get the warning anyway so that you can tell WHY the modem went down.

I'm going to test this further, but if you have any thoughts on what might be going on I would appreciate them.

Regards,

Josh

RE: Not seeing +CGEV: ME BATTERY LOW when battery voltage drops after enabling with AT%XPOFWARN

Albrecht Markus Schellenberger — Fri, 25 Jun 2021 11:37:54 GMT

Hello Joshua,

[quote user=""] but not the "+CGEV: ME BATTERY LOW" response that I was expecting when I lowered the battery voltage. [/quote]

how fast did you lower the battery voltage? Could it be possible that the voltage drops too fast and thus the modem doesn’t manage to send low battery level notification before it has to shut down?

[quote user=""]The handler installs successfully, the AT%XPOFWARN=1,31 command gets an "OK" response, and I see lots of other modem responses being printed by my XPOFWARN_Handler, [/quote]

Could you try the %XVBATLVL instead? Does that make any difference?

Regards,

Markus