October 10, 2016 - 10:48pm, 5404 views
I am not getting ^sysstart, I am assuming this is an issue as I can not seem to initiate an IP connection.
at^smso^SMSO: MS OFFOK^SHUTDOWN^SYSLOADING+PBREADY^SYSINFO: 200atiCinterionEHS6-AREVISION 03.001
the JRC is not loaded in the autostart or not present in the FFS
Check if it is in the FFS and enable the autostart AT^SJAM=4 to check it
if not, just reflash the FW again
Somewhere over the rainbow!!! Looking for the Oz Land!!!
^SYSINFO: 200 means that the JRC MIDlet (which is a part of Gemalto software and some of the module's functionality is implemented in that MIDlet) was not started (and there was no attempt to start it).
Please check with AT^SCFG? command if "Userware/Autostart" is set to 1. This setting is global for all MIDlets including JRC. Additionally you configure autostart for each MIDlet in it's jad file.
If "Userware/Autostart" is already set to 1 please check if JRC is installed with AT^SJAM=4 command.
Thank you both for the input. I will say that there was no mention, and very little description in the manual about this function, are there any other features that I need to know of? What did I just enable and why is it a Java function. This is not my first rodeo, I have already certified our product using a Huawei module and it is operational on Verizon. We chose to move from Huawei to Cinterion because of the LTE module, ELS31-V and for our global implementation of our device, a gunshot detection sensor. The project only operates from AT commands with data and SMS, and so far your module looks great, I just need some helpful advice to get the first burst of data and SMS in/out working. If there is anything more that I should know please tell me so I can include it in the start-up code. Our device runs Assembly code only, so no Java, or other higher level languages involved, so I need to know all steps to incorporate it efficiently. Thank you for your input, once we have the EHS-6 tackled will switch to the ELS31-V.
The EHS6 module includes the Java virtual machine and it is possible to run custom Java programs on it. It is also designed this way that the part of the functionality is implemented in the Java MIDlet that is loaded in the factory together with the firmware. Each firmware release is also distributed with it's corresponding JRC MIDlet. The global autostart is enabled by default. So you have just restore the factory setting. With setting 0 no MIDlet (including factory one) will be started automatically. If it's set to 1 the installed MIDlets which have additional parameters in their jad files will be started automatically with each system boot.
ELS31 does not support Java so there is no such problem.
There is no universal advice - please write if you have a problem (like this time here) and somebody will help you.
What I am looking for is an example that I can try on the eval board that Gemalto sent me to evaluate the parts. Instead of randomly trying this command and that command , what I need is a step by step proceedure that shows what commands are needed, in what order, to open up a connection to the carrier and to be able to send/receive data. I have set-up a connection profile with the AT^SICS command, I have a service profile with the AT^SISS command. When I try to open a connection with the AT^SISO=9 command I get a generic CME error..not much use. Do you not have any application notes about taking a bare module and getting a connection established? I eventually will figure it out, but if you have support documentation that outlines the process, that would be of great help.
The commands that you have cited are used for IP services over AT commands. You can find a tutorial here: https://iot-developer.thalesgroup.com/tutorial/concept-board-internet-se... and there are some more in the Knowledge Base. Some short examples you can find in the AT commands specification document.
Please enter AT+CMEE=2 to see more information in case of CME ERROR. You can also use AT^SISE command to see more if possible.
If you want to establish a transparent connection and use the module as a modem you can establish a dialup connection. You need to configure the PDP context with AT+CGDCONT command and initiate the connection with ATD or AT+CGDATA command. But then your application ***** to have its own ppp protocol implementation to establish and maintain the connection.
I am continuing to have issues accessing the internet from the GPRS device. It may be tied to a SIM issue, I have a Canadian SIM on a US carrier (AT&T). They have roaming agreements but not sure if it is registered correctly for data. When I issue a +CREG I get a 0,5. So I am registered but roaming. Does data work when roaming? I have ordered AT&T native SIMs for the network as my next step so any input you might have would be appreciated. Your eaxamples were good, but when it came to opening a connection I got a connection error, so I have narrowed it, I believe, down to the SIM?
Please paste some log (the commands you send with results) - it would be easier to answer then.
Data transfer can work in roaming. The question is if your subscription (Canadian SIM) include data transfer and if you have configured the APN, user and password correctly.
Can you test the SIM with your Huawei device?
The Huawei device is the CDMA version, so no I can not. We are switching the whole program over to Gemalto and because Huawei discontinued the MG323, we were left with the MC323 only. So until the new SIM's arrive I have switched over to the ELS31-V and will get it up and working. Once the AT&Y SIMs arrive I will pick this up.
I expect I will have questions on the ELS31-V but I will start another thread for that project.
OK, so we will continue this later if there would be a need.
© 2013-2023 Thales DIS AIS Deutschland GmbH - a Telit Cinterion Company