RSXT LTE6 - How often SIM interrogated?

Hello to you all,

Firstly, I am completely new to cell phone technology - indeed my wife says I am living in the stone age - but a quick learner and have spent decades doing IT support, albeit older systems.

Secondly, I was quite impressed when our suppliers mentioned they use MikroTik products as a quick web search showed they seemed to be in a different league compared with the usual domestic routers. We are quite rural (in South Wales - so not as rural as some members!) and landline broadband is a bit of a joke. Therefore we are using an SXT antenna with built-in modem to converse with a Hap AC Lite. RouterOS is v6.47.9.

Thirdly, I am impressed with the detail of many of the topics on this forum and the expertise of the members. Although 4G LTE is new to me I was quite surprised to see that the old format of modem commands are used. I used to program them decades ago!

On first installation the system did report a SIM error but came up ok and we were very pleased with the speeds. After a day though the LTE1 interface stayed very dead and we ordered and received a replacement SIM. (I cannot understand what a fiddly job that is up a high ladder! All that engineering and they have a design where the sim automatically falls from your finger into the base of the unit!)

It stayed up and running yesterday evening and we had a “buffering-free” session on the TV for the first time ever. This morning there was no internet access at all and LTE1 was not running. I added LTE logging and increased the memory logging lines to 5000. Disabling and re-enabling the interface did not help. I powered off the antenna and it still did not come back up but then suddenly sprung into life.

I then noticed a few dropouts and one log I captured had this sequence:

15:45:33 lte,async lte1: sent AT+CPIN?
15:45:33 lte,async lte1: rcvd +CME ERROR: SIM failure
15:45:34 lte,async,event lte1: *SIMDETEC:1,SIM
15:45:34 lte,async,event lte1: *ICCID: 8944303603049920075

It has dropped 24 times in about 4 hours so I am wondering how often it has to interrogate the sim.

I do not think that the second SIM is also faulty.

Any help would be gratefully received!

Gerald.

PS I was pleased to see that RouterOS will support MQTT client interface. I use that with Home Assistant to monitor a few things including a ground source heat pump so will attempt to monitor the modem and router.

It seems to have had many problems overnight. Here is the sequence from the last time the modem went down:

09:09:00 lte,error lte1: reply timeout for: AT+EEMGINFO?
09:09:00 lte,account lte1 session: 193s 10412808/580801 bytes 9206/2303 packets
09:09:00 interface,info lte1 link down
09:09:01 lte,async lte1: sent ATE0
09:09:11 lte,error lte1: reply timeout for: ATE0
09:09:12 lte,async lte1: sent ATE0
09:09:15 lte,async lte1: rcvd ERROR
09:09:15 lte,async lte1: sent AT+CFUN?

Would that AT command (EEMGINFO) result in access to the SIM or is it possibly a problem with the modem module itself?

I looked up the command and see that it needs EEMOPT=1 to set the mode. Looking for the command before the above sequence and came across this:

09:05:30 lte,async lte1: sent AT+EEMOPT=1
09:05:30 lte,async lte1: rcvd OK
09:05:30 lte,async lte1: sent AT*MRD_SN?
09:05:30 lte,async lte1: rcvd *MRD_SN:AE3903A8B469
09:05:30 lte,async lte1: sent AT+CPIN?
09:05:30 lte,async lte1: rcvd +CME ERROR: SIM failure
09:05:31 lte,async,event lte1: *SIMDETEC:1,SIM
09:05:31 lte,async,event lte1: *ICCID: 8944303603049920075
09:05:31 lte,async,event lte1: *EUICC: 1
09:05:31 lte,async,event lte1: +MSTK: 14
09:05:31 lte,async,event lte1: +ZEND
09:05:31 lte,async,raw lte1: +CREG: 0
09:05:31 lte,async,raw lte1: $CREG: 0

I think the mess is caused by sim failures but I think it highly improbable that this sim has an error too.

All the failures were sorted out after a firmware upgrade.
The system is now stable.