For the EM7455 we establish connectivity with qmi-network and then in order to detect the daily Normal Release from the network we periodically poll qmicli -p --wds-get-packet-service-status -d /dev/cdc-wdm0. If we do not detect the normal release, the device cannot be accessed (but will appear to be working correctly).
Anyhow, while testing the EM7590 we noticed that qmicli -p --wds-get-packet-service-status -d /dev/cdc-wdm0, will fail for other reasons. So the device cannot detect the normal release. Can we substitute this with an AT command?
I am using the QMI interface, but qmicli appears to hang on that command every couple of hours or so. I run the command three times, giving it 2 seconds to resolve each time. In the ‘hung’ state, all the commands timeout. I do believe this state clears itself eventually, but I’d rather not spend cycles tracking it down. This does not happen with the EM7455.
I cannot use the MBIM interface (drivers/leveraging existing code/etc).
My hope is that by switching to an AT command to monitor the WSD Packet Service, I will avoid the qmi hung state all together.
At+cgpaddr=1, At+cgcontrdp and AT!GSTATUS all fail to detect when the WDS Packet Service state changes and just have the same information as when the Sierra is connected.
How else can this extremely important service be monitored?