BGS5: AT^SMON="INS",2 does not work (Unknown error) | Telit Cinterion IoT Developer Community
June 2, 2016 - 2:48pm, 3020 views
Hi,
we've just received some BGS5 modules and are now porting our MIDlet software from EGS5.
Unfortunately we were not able to use the Network Scan functionality yet. Here's what we tried:
AT+CREG?
+CREG: 0,1
OK
AT+CSQ
+CSQ: 24,99
OK
AT^SNMON="INS",2
+CME ERROR: Unknown
We tried this on two versions of BGS5 modules:
HW-Rev.B1d-4915
ATI1
Cinterion
BGS5
REVISION 01.100
A-REVISION 00.000.10
OK
as well as
HW-Rev.B1d-0616
ATI1
Cinterion
BGS5
REVISION 01.100
A-REVISION 00.000.18
OK
with no difference in the AT^SNMON result.
Any ideas?
Hello,
This command should work for both modules. But there is one important issue here - this command only works if the module is not registered to the network.
Regards,
Bartłomiej
Hi Bartłomiej,
thanks for your fast reply!
so we tried the following:
AT+COPS=2
OK
AT+CREG?
+CREG: 0,0
OK
AT^SNMON="INS",2
+CME ERROR: Unknown
No change regarding the network scan...
I've tested this with my BGS5 REVISION 01.100 A-REVISION 00.000.18 module and it was working.
Please check the AT^SCFG? output - this might not work if the autostart is disabled (JRC is not running).
Regards,
Bartłomiej
Hi Bartłomiej,
thanks again for your fast reply!
So we started the JRC midlet prior to the network scan and .. it worked fine!
This leads us to a related question:
Where should we have found that piece of information that a running JRC midlet is necessary to run a network scan? As far as we can see, it's not documented anywhere!
Or: Is there some kind of document which somehow states which features require a running JRC midlet?
Hello,
The JRC MIDlet is a part of the factory software so it should always be running. Some of the module's functionality is implemented in this MIDlet. Many AT commands are implemented at least partially in JRC. That's why it is enabled for autostart and the global autostart setting (AT^SCFG command)is enabled by default.
You are right that it is not written in the customer documentation which command requires JRC - this information is just an internal implementation detail and I don't expect that it will change - the outcome for the user is that JRC must be running.
But you are also right that the information about the relation between JRC and autostart is probably not emphasized strongly enough in the documents. And some customers disable the autostart during the implementation of their MIDlets without being conscious about the results.
Best regards,
Bartłomiej