OS Lockup during call to Socket

[dboling]

I am testing a 9160DK in an area of intermittent connectivity.  When the connection drops at just the wrong time my call to socket does not return.  Aside from this being a problem, I'd like to work around it by being able to test when a good connection exists. I'm not using the nRF cloud for this test.  What is the best AT call to use to test for a good connection? Thanks.

[Bjørn Kvaale]

I would probably either use the extended signal quality or the signal quality notification set command to read out the rsrp.

[dboling]

Thanks.  Unfortunately, there is some amount of signal when this occurs. I'll have to hack some number for my demos but it isn't a solution for any sort of shipping product.

Is there any plan on fixing the call to socket so that it doesn't lock up?  Most stacks I use will fail the call if the network isn't present. 

[Bjørn Kvaale]

Are you able to provide a modem trace and/or some logging from the LTE link monitor for example?

[dboling]

The trace shows the call to socket and then nothing. I have another timer running that should flash an LED but it doesn't run after the call to socket.

I'll see what other information I can collect and get back to you.