PLS62T-W connectivity issue | Thales IoT Developer Community
May 11, 2021 - 9:36am, 2092 views
Hello,
I have troubles with PLS62T-W device (SIM Card - Eseye AnyNet) registration in Armenia.
Below are some AT commands output that may help.
AT+CREG?
+CREG: 2,3
3(Registration denied) or after some period the command returns the registration status 0 (Not registered, ME is currently not searching for new operator).
The mobile operators selection **** is manual:
AT+COPS?
+COPS: 2
Local available operators are:
AT^SXEONS
^SXEONS: (1,"MTS ARM","MTS Arm","28305",0,"",""),(1,"Beeline AM","Beeline","28301",0,"",""),(1,"Ucom AM","Ucom","28310",0,"","")
Network Radio Access Technologies is GSM
AT^SXRAT?
^SXRAT: 0,0
Connecting to operators reports:
AT+COPS=1,0,"Ucom AM",0
+CME ERROR: unspecified GPRS error
AT+COPS=1,0,"MTS ARM",0
+CME ERROR: GPRS services not allowed
AT+COPS=1,0,"Beeline AM",0
+CME ERROR: unspecified GPRS error
Changing the RAT to LTE does not resolve the issue:
AT^SXRAT?
^SXRAT: 3,3
AT+COPS=1,0,"Ucom AM",7
+CME ERROR: no network service
Thanks.
Hello,
Is this Eseye SIM already activated - is AnyNet device created for it in your AWS account?
If the answer is yes, I'd reboot the device and wait for some time. COPS should not return 2 if the module is not manually deregistered from the network and SIM PIN authentication has completed and "+PBREADY" URC has shown up. Module should periodically search for the network and CREG 0 should then change to 2.
I'd change SXRAT to 6,3,2 which is a default.
If SIM is activated and still can't register even though the device is lowered on and the antenna connected for a longer time I'd contact Eseye.
Best regards,
Bartłomiej
Hello,
I am working on the same project with Narine, unfortunately after the previous comment I am responding late considering certain events, I want to inform you that the card is activated and added to AWS device list, but unfortunately the registration is not done. Reboot of the device also not resolve the problem.
On console shows
+CIEV: prov,1,"fallback"
+PBREADY
and
at+EMT:EMQRDY
ERROR
Is the problem with the card registration or the device?
Best regards,
Hambardzum
Hello,
If we are talking about ESEYE intelligent cloud connect, it is the service prepared and offered by ESEYE service in cooperation with Thales (as it works on our terminals).
If the module can't register to the network, the problem might be caused either by the SIM related issues (not properly activated, no roaming partners in your country etc.) or the device (antenna not connected, no coverage, physical device malfunction etc.). I don't think that the additional software running on the device may have anything to do at this stage.
Please make sure that the module is in automatic network selection **** (AT+COPS=0), all RATs are enabled (AT^SXRAT=6,3,2 - the default setting, but you can also try to set AT^SXRAT=2 for UMTS only or ) for GSM or 3 for LTE for test). Please check AT+COPS=? to scan for available networks (it may take a while). Check AT+CPIN?, AT+COPS?, AT^SMONI, AT+CREG?.
If the device can't register you can also test the SIM in some other device to verify if it can register.
If it still can't I would suggest to delete the thing from AWS and register again. If it still doesn't help, please contact ESEYE.
BTW you can also enable system out from the running applications with at^scfg="Userware/Stdout","interface_name" to see the application output.
BR,
Bartłomiej
Hello,
thank you for quick response. After some firmware updates and device reset AT+COPS show 2(Current operator (registered)).
Now I think I accidentally removed all the modules because at+EMT and at+emqsubopen commands showing ERROR all time.
I understand correctly that these are additional commands that need to be reinstalled on the device?
Where I can find MQTT lib/module for PLS62T-W device?
As for the applications please check with AT^SJAM=4 and AT^SJAM=5 the list of installed and running applications. Paste the answers here. Please also verify with AT^SCFG? if "Userware/Autostart" is set to 1.
In case not all apps are installed you'd have to contact ESEYE.
Hello,
Results below
AT^SJAM=4
^SJAM: "a:/EseyeUpdater.jad","EseyeUpdater","Eseye","2.0.27",1,331295,0,2
^SJAM: "a:/JRC-1.62.04.jad","Java Remote Control MIDlet Suite","Cinterion","1.62 .04",1,593441,0,1
^SJAM: "SLAE.jad","SL Agent Module Services","Gemalto M2M GmbH","2.1.9",0,429531 ,0,0
OK
AT^SJAM=5
OK
AT^SCFG?
^SCFG: "MEopMode/Prov/AutoSelect","on"
^SCFG: "MEopMode/Prov/Cfg","fallback"
^SCFG: "Serial/Ifc","0"
^SCFG: "RemoteWakeUp/Ports","current"
^SCFG: "RemoteWakeUp/Ports","powerup"
^SCFG: "Gpio/****/ASC1","std"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","gpio"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/HWAKEUP","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","rsv"
^SCFG: "Gpio/****/SYNC","std"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","PLS62-W"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MEopMode/CregRoam","0"
^SCFG: "MeOpMode/SRPOM","0"
^SCFG: "MEopMode/RingOnData","off"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "Radio/Band/2G","0x00000074"
^SCFG: "Radio/Band/3G","0x0004019B"
^SCFG: "Radio/Band/4G","0x080E08DF"
^SCFG: "Radio/Mtpl/2G","0"
^SCFG: "Radio/Mtpl/3G","0"
^SCFG: "Radio/Mtpl/4G","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","005B","Cinterion Wireless Modules ","PLSx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "Urc/Ringline","local"
^SCFG: "Urc/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","0"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","0"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
OK
I have already changed ^SCFG: "Userware/Autostart","0" to 1
For future steps I will contact to ESEYE. Thank you for your support.
Regards
Hambardzum
It seems that you have already played a bit with the device.
There are 3 application which are necessary for ESEYE service to work. In your case two of them are missing. So yes, please contact ESEYE.
BR,
Bartłomiej
Hello BARTŁOMIEJ,
How else can I use the device other than the MQTT for AWS, is there a similar experience?
For example Kafka, ZeroMQ, XMPP etc. I want to test other possibilities as well․
Best Regards
Hambardzum Minasyan
Hello,
As far as I know the Eseye solution only provides MQTT protocol. Implementing other protocols is possible, there may be customers who already did it for their purposes but I don't know any similar to Eseye ready to use service.
Regards,
Bartłomiej
Pages